Read time: 5 minutes
Platform migration for a business is necessary to maintain the data in its most cost-effective and productive form. An essential requirement of this migration is keeping the older data functional in the new platform. For email communication, the mailbox should remain active and healthy enough to adapt to a new environment. Microsoft understands such requirements for a business and offers some native migration methods to migrate Exchange to Office 365.
Office 365 is the collection of cloud services in which Exchange Online is included as the email service. In Office 365 cloud, there is the same email as in the on-premises Exchange Server. After the migration, Office 365 end users can access emails anywhere on any browser and device.
Though there are different migration strategies for Exchange to Office 365, cutover migration is the simplest of them all. When you migrate your entire mailbox contents from any version of Exchange Server to Office 365 or Microsoft 365, it is termed Exchange Cutover migration. Typically, it is a small-scale migration suitable for small organizations.
To accomplish the cutover migration, the on-premises Exchange Server should be 2003 or later versions including 2019 and the number of mailboxes is lesser than 2000. But, it also supports older versions of Exchange Server and can migrate ms exchange 2010 mailboxes to Office 365 quickly. The Exchange experts recommend that to shorten the length of the migration period, the user should migrate 150 or fewer mailboxes.
You cannot directly start the Exchange cutover migration from on-premises Exchange to Office 365 as you require to perform some changes to the source Exchange Server environment first.
Note – The cutover migration method can migrate mailbox, mail users, contacts, and mail-enabled groups along with their memberships. You should remove other objects before starting the migration.
After accomplishing all the prerequisites, you can move forward and start the migration. There will be different steps at various stages of migration.
Exchange cutover migration migrates the email address of selected mailboxes from Exchange to Office 365 and the domain name works as the bridge between these two. So, you should verify that you own the same domain in Office 365 too.
The migration endpoint has all the credentials and settings to connect Exchange Server with Office 365. Majorly, it has several mailboxes that you can migrate simultaneously.
Note – If the connection with the server is not done, then input the details of the Exchange Server and RPC proxy server.
A new migration endpoint will be created. The Exchange cutover migration will require this endpoint to connect with Office 365.
The Office 365 cutover migration batch will start to appear in the migration category.
The earlier three steps create a batch that gets saved in the migration section under the recipients category. But the batch does not start automatically.
The Office 365 cutover migration batch will take time to migrate all the mailboxes and you can continue to use them without interruption.
Cutover migration migrates all the mailboxes from an Exchange Server to Office 365. Due to the prerequisites and multiple steps, it takes too much time. So you can opt for an automated solution. Kernel Migrator for Exchange lets you create an instant migration job. The Exchange migration tool is started with the minimum information of user accounts and it is migrated with utmost security. It conducts migration without changing the integrity of data, providing great flexibility in terms of migration. It does not limit you regarding the number of mailboxes (as in cutover migration). You can choose an unlimited number of mailboxes and migrate them from Exchange to Office 365.
I was moving data using this method, but missing the owner verification step and facing error. After following the steps given above I could easily migrate data and now its working fine. Thank you Aftab for this quick guide.