Troubleshoot Slow Exchange 2013 to Exchange Online Mailbox Migration
Question details
Determine why an Exchange 2013 mailbox migration to Exchange Online is transferring little data and encountering synchronization errors.

- Product
- Microsoft Exchange Server 2013 and Exchange Online
- Device & OS
- not provided
- Scenario
- A remote migration batch is moving on-premises Exchange 2013 mailboxes to Exchange Online.
- Observed behavior
- The batch transferred very little data overnight and later reported mailbox connection and corrupted-item errors during synchronization.
Identify the affected mailbox and migration batch, and make sure you can access the Exchange admin center and Exchange Online PowerShell. Note the time of the latest error so you can match it to the migration report.
Test Whether the Source Mailbox Is Causing Repeated Migration Attempts
Use a different on-premises mailbox to determine whether the connection problem is specific to the original mailbox.
Repeated migration attempts can occur when the source mailbox is temporarily locked or cannot be accessed reliably. A comparison mailbox helps narrow the investigation but does not by itself identify the cause.
In the Exchange admin center, open Migration, select the batch, and review the affected mailbox's status and error details.
Create a test migration for another on-premises Exchange 2013 mailbox using the same migration endpoint, then compare its progress and errors with the original mailbox.
If only the original mailbox fails, check its accessibility and Exchange server logs around the reported error time. If both mailboxes fail, review the migration endpoint and connectivity to the on-premises Exchange environment.

Review Migration Reports for Corrupted Items and Principal Translation Errors
Use the detailed migration report to identify recurring item errors and cross-forest identity or permission issues.
Work With Office Documents During Your Exchange Migration
WPS Office is a free, lightweight alternative for working with Office documents. Its familiar interface and format compatibility make it easy to move everyday document work to WPS. It does not migrate Exchange mailboxes or fix Exchange connection errors.

Frequently Asked Questions
Why might an Exchange migration repeatedly retry a mailbox?
The source mailbox may be temporarily locked or inaccessible. Check its migration report and test another on-premises mailbox through the same endpoint to help isolate the issue.
How can I see detailed errors for a migration user?
In Exchange Online PowerShell, run Get-MigrationUserStatistics -Identity user@example.com -IncludeReport | Format-List Status,Error,Report with the affected mailbox address.
What do cross-forest principal translation errors mean?
They indicate that the migration encountered a problem translating an identity or security principal between environments. Review the report for the named principals and check their corresponding identities and permissions.
Should I raise the corrupted-item limit to finish the migration?
First inspect the migration report to understand which items are affected and whether they can be recovered or repaired. Raising a limit can allow items to be skipped and may result in data loss.




