In the hybrid environment where both Exchange on-premises and Exchange Online exist together, the migration is conducted through a migration endpoint when performed using the manual Office 365 or Exchange Server migration using the Exchange Admin Center interface. The endpoints are the connectors that join both the platforms to migrate mailboxes from one deployment to another. Administrators have control over selecting the maximum limit of mailboxes in the batch migration from source to destination account via settings of Max. Concurrent Migrations under the Migration endpoint and that process we are going to learn here.
First, let us go through the basic stages included in the native migration from Exchange to Office 365.
Migration of mailboxes from an on-premises Exchange Server to Office 365 using the hybrid configuration involves the steps:
Thus, migration to the cloud using the hybrid configuration starts with the creation of migration endpoints.
Migration endpoints define the connection settings between Exchange on-premises and Office 365. It has information such as FQDN of the on-premises server, a description (Name), and Exchange Online log in credentials. To ensure the best performance of a migration endpoint, there are a few parameters you can configure as per your requirements.
But you can increase the limit for the concurrent mailboxes using the Exchange Admin Center or PowerShell.
You can set the concurrent limit for migration while creating a migration endpoint or edit an existing migration endpoint. Here is the procedure to create the migration endpoint –
If you have already created the migration endpoint, but you want to alter the value of concurrent migration, then you can change it also. Follow the below steps:
There is a special cmdlet ‘MaxConcurrentMigrations’ to set the concurrent limitation. First, you need to connect the windows PowerShell with Exchange Online and then run the command. Here are the steps:
The command will allow you to run any script even if it does not have a digital signature.
It will ask you to input the Administrator credentials and place it into the $livecred variable.
The command creates a session with Exchange Online.
The command places the session to the $importresults variable.
Here at the EndpointName, you will input the name of migration endpoint, and at Value, you will input the desired value for concurrent migration.
The concurrent value (MaxConcurrentMigration) creates a limit for the total number of mailboxes you can migrate in the migration batch. Because of such complex settings, it is evident that Exchange to Office 365 migrations are complex. However, if you like to have a more controlled migration, you can use the Kernel Office 365 Migration. This Office 365 migration tool allows you to conduct a migration without any hassles. You just need to select a source Exchange and destination Exchange Online account, provide credentials, and apply proper filters. You can execute the migration immediately or schedule it at your convenience.