Email Migration

Complete an Exchange Migration Batch Stuck at Synced

Camila MilosovichCamila Milosovich Nov 14, 2026 868 views

Question details

The user wants to complete an Exchange hybrid migration batch that is at Synced and determine when it is safe to remove the batch.

Complete an Exchange Migration Batch Stuck at Synced
Product
Microsoft Exchange and Exchange Online
Device & OS
not provided
Scenario
An administrator is moving mailboxes from an on-premises Exchange environment to Exchange Online using a hybrid migration batch.
Observed behavior
The migration batch shows Synced rather than Completed.
Before you start

Sign in to the Exchange admin center with an account authorized to manage migration batches. Check the batch and mailbox migration reports for errors, and choose a suitable time for the final mailbox cutover.

Solution 1Recommended

Complete and verify the Exchange migration batch

Use this method when the batch is synced, its mailbox migrations have no unresolved errors, and you are ready for the final cutover.

Synced means the initial mailbox synchronization has finished; it does not necessarily mean the final migration cutover has occurred. A batch configured for manual completion must be completed by an administrator.

1
Review the batch

In the Exchange admin center, open Migration and select the synced batch. Review its mailbox details and reports, and resolve any errors before proceeding.

2
Complete the batch

With the batch selected, choose Complete this migration batch, or Complete migration batch, and confirm the action. Allow time for the final synchronization and cutover to finish.

3
Verify the mailboxes

Check that the batch and its mailbox entries show Completed. In the Exchange admin center, verify that the migrated mailboxes are in Exchange Online; the mailbox type may be shown as Office 365. Also check the corresponding on-premises recipient, which may appear as a User or remote mailbox depending on the management view.

4
Remove the completed batch

After verifying the migrated mailboxes and confirming users can access them, select the completed batch under Migration and choose Delete or Remove. Confirm the removal.

Complete and verify the Exchange migration batch
Keep the batch until verification is complete: Removing a completed migration batch cleans up the migration record; it does not delete the migrated mailboxes. Review or save any migration reports you need before removing the batch.
Free Microsoft Office alternative

Work with Office documents after your Exchange migration

WPS Office is a free, lightweight alternative for editing documents, spreadsheets, and presentations in a familiar interface. Its Microsoft Office format compatibility helps teams move their files into an everyday workflow, though it does not complete Exchange migration batches.

Use a familiar interface for everyday document editingOpen and edit Microsoft Office formats, including DOCX, XLSX, and PPTXWork with document attachments shared after your mailbox migrationGet a free, lightweight Office alternative
microsoft office alternative - wps office

Frequently Asked Questions

Why does my migration batch still show Synced?

Synced indicates that initial synchronization has finished, but the final cutover may still be pending. If the batch was configured for manual completion, select it under Migration in the Exchange admin center and choose Complete this migration batch.

Should I complete the batch if one mailbox has an error?

Review the affected mailbox's migration report from the batch details and resolve the error before completing the batch. Completion should be started when the mailboxes are ready for final cutover.

How can I confirm that a mailbox has moved to Exchange Online?

Check that its migration entry shows Completed, then find the mailbox in the Exchange admin center and verify that it is hosted in Exchange Online. The mailbox type may be displayed as Office 365.

When can I delete the migration batch?

Remove it after the batch has completed, the migrated mailboxes have been verified, and users can access them. Save any reports you need first, because removing the batch cleans up its migration record.