Summary: Sometimes, while migrating data from local Exchange Server to Microsoft 365 using hybrid method, the migration batches stuck at syncing. In this post, we will see how to fix this issue and migrate the data. We will also mention an EDB converter tool that can migrate EDB data to Microsoft 365 with minimal effort and without any issue.
![[Fixed] Migration Stuck at Syncing when Migrating to Microsoft 365](https://www.stellarinfo.com/blog/wp-content/uploads/2017/02/free-download-1.png)
You can use hybrid migration method to perform smooth migration from on-premises Exchange Server to Microsoft 365. For migrating mailboxes and other data from local server to cloud, you can create migration batches. After creating and starting the migration batches, you can check the status of migration batches using the Get-MigrationUserStatistics PowerShell command (see the below example) in the Exchange Management Shell (EMS).
Get-MigrationUser -BatchId "<batch name>" | Get-MigrationUserStatistics
This will show the Status of migration batch, the Items Synced, and the Items Skipped. However, you may find that the migration is stuck at syncing. This means that the migration batch has not even started yet. Below, we will discuss the troubleshooting steps to fix the migration stuck at syncing issue when migrating to Microsoft 365. But before that, let’s find out the reasons behind such an issue.
Causes for Migration Stuck at Syncing Issue
A migration batch gets stuck in the synchronization phase due to the following reasons:
- Bandwidth issues from the local Exchange Server to the Microsoft 365 may stop or delay the migration of data.
- Blocked ports or limited traffic from the internal network. It’s important that the Exchange Server has full unrestricted access to the internet, until the transfer of data is complete.
- Issue with the mailbox or mailboxes in the batch. If there is an issue with the mailbox, like consistency or other issues, this might affect data migration.
- Configuration issues with the local Exchange Server.
- Misconfiguration of the hybrid setup. Manually changing the send/receive connectors or any other configuration can stop or delay the transfer of data.
- Large mailboxes can affect the migration. Therefore, cleanup of the local mailboxes should be done prior to the migration.
How to Fix Migration Stuck at Syncing issue when Migrating to Microsoft 365?
Here are some possible solutions to fix the migration stuck at syncing issue.
1. Recreate and Modify the Migration Batch
You can delete the migration batch and then recreate it. This will help resolve the problem (if any) in the creation of the migration batch.
First, you need to stop the migration batch as the Exchange Server will not allow you to delete the migration batch if it is in progress. For this, open the Exchange Management Shell (EMS) and run the below command:
Stop-MigrationBatch -Identity "<batch name>"
Once this is complete, you can remove the migration batch by using the Remove-MigrationBatch command (see the below example).
Remove-MigrationBatch -Identity "<batch name>"
After this is complete, run the Get-MigrationBatch PowerShell command to check if the migration batch is deleted.
After this, you can recreate the migration batch and see if the issue persists. If the issue persists, it means there is a problem with one or more mailboxes in the migration batch. In such a case, you can reduce the number of mailboxes or try to create a migration batch per mailbox to identify the problematic mailbox. Then, you can tackle the issue with that mailbox.
2. Create Migration Batch from Exchange Admin Center (EAC)
It might happen that the migration batch was not set correctly from the Exchange Management Shell (EMS). In such a case, you can try to create the migration batch from the online Exchange Admin Center (EAC) by following these steps:
- Open the Exchange Admin Center (EAC).
- Click on the Schedule tab.
- On the Add migration batch window, tick the Automatically start the batch in the Start the migration batch by section.
- Also, tick the Automatically complete the migration batch option in the End the migration batch by section. Make sure to select the Automatically complete the migration batch. If it is not selected, the migration batch will not start.
An Alternative Solution to Migrate Data to Microsoft 365
There are various challenges you can face when migrating data from local Exchange Server to Microsoft 365 using the native methods. You can look for a fast and reliable solution to migrate data smoothly and with no issues. One such solution is to use a specialized EDB converter tool, such as Stellar Converter for EDB. With this tool, you can open multiple live/standalone Exchange Server databases from any version (5.5 to 2019) and of any size. Then, you can export the mailboxes and other data from the database directly to a live Exchange Server or Microsoft 365 tenant. You can also granularly export the EDB data to PST and other file formats. Even after decommissioning the server, you can use this tool to extract the data from the EDB database. To facilitate smooth and quick migration, the tool offers features, such as automatic mailbox matching, parallel exports, and priority exports.
Conclusion
When migrating data from on-premises Exchange Server to Microsoft 365 in a hybrid setup, you may encounter a situation where the migration stuck at syncing. You can follow the above given solutions to resolve this issue. Alternatively, you can use an EDB to PST converter tool, like Stellar Converter for EDB to migrate the data from Exchange database directly to Microsoft 365 without any issue. This tool can also export EDB file data to a live Exchange Server database even without a running server.
