Read time: 5 minutes
A migration between Exchange Server and Office 365 is considered completed after all the messages from the source mailbox are transferred to the destination mailbox. This process is called syncing, and when the batch migration is in the final stages, then it denotes status as syncing. But in some cases, when the size of the mailbox is too large, or the receiving Office 365 mailbox does not have proper permissions, then syncing is stalled, and the migration will get stuck for an unlimited period.
You can view the status of the mailbox migration batches in the Exchange Admin Center. In the above case, you will see that syncing process still running but none of the mailboxes has migrated yet.
Get Kernel Office 365 Migration Tool to seamlessly migrate Office 365 data in a safe and easy way.
As you can see in the above image, even after the considerate time of starting the migration batch, the status is Syncing, and under the Mailbox status, zero mailboxes have been synced from the total four in the batch. If you want to check it in detail, click on the View details option. It shows that the migration has stuck, and you need a proper solution in the specific situation.
If you have faced such a problem earlier, then you may be aware of the struggle to complete the migration. But here is a solution that you can follow and resume a stuck migration request.
First, you should know the actual status of the migration by running the following command –
After it shows the status as Syncing, then OK. But if it shows the status as Queued for a long time, you need to troubleshoot the problem.
Now, go to Exchange Management Shell and run the same command –
Now the status of the migration batch should be changed to Syncing or any other stage of migration.
After running the command successfully, restart the Exchange services like Microsoft Exchange Search, Microsoft Exchange Search Host Controller, and Microsoft Exchange Mailbox Replication.
Now recheck the status of the migration.
The status of the migration should change to Migrating or Syncing. But keep in mind that you need to enable content indexing after successfully completing the migration.
Using the troubleshooting methods mentioned here, you can effectively resolve this issue.
Similar to the above process, completing the migration process also includes the below options:
If you want to prevent from the above issue, it is recommended to choose the manual to complete the batch option. As this is a manual method, you need not wait to complete the syncing process.
It is now common for organizations to face unexpected issues during Exchange to Office 365 migrations. Shortage of physical resources, lack of expert supervision, unavailability of professional migration tools, etc., are some of the reasons for the issues that occur while migrating Exchange to Office 365. By using a professional tool like Kernel Office 365 Migration, many of these issues can be foreseen and avoided. Also, this tool helps in automating many migration tasks.