Email Migration

Fix an Office 365 Exchange Migration Batch Stuck in Starting

Natalie TaylorNatalie Taylor Nov 22, 2026 868 views

Question details

Determine whether an Exchange 2010 mailbox has migrated to Office 365 and resolve a migration batch stuck in Starting.

Fix an Office 365 Exchange Migration Batch Stuck in Starting
Product
Exchange Online and Exchange 2010
Device & OS
not provided
Scenario
An administrator is moving mailboxes from Exchange 2010 to Office 365 in a migration batch.
Observed behavior
One mailbox is reported as failed while others complete, and restarting the batch leaves the affected mailbox in Starting status.
Before you start

Sign in with an account that can manage Exchange migrations, and identify the affected mailbox and migration batch. Have access to both the Exchange Online and Exchange 2010 admin environments so you can verify the mailbox location.

Solution 1Recommended

Verify the mailbox migration and recreate the batch only if needed

Use this approach to distinguish a reporting error from an incomplete move before submitting the mailbox again.

1
Review the migration report

Open the Exchange admin center, go to Migration, and select the affected batch and mailbox. Open or download the available migration report and note any errors or timestamps.

2
Check the mailbox location

In the Exchange Online admin center, look for the user under Recipients > Mailboxes. Confirm that the mailbox is accessible in Office 365 and contains the expected mail; also check the on-premises Exchange recipient configuration.

3
Inspect the move status

If a move request is still available, connect to Exchange Online PowerShell and run Get-MoveRequest for the user, followed by Get-MoveRequestStatistics -Identity <user> -IncludeReport. Compare the results with the migration report.

4
Check migration prerequisites

If the mailbox has not moved, review the reported error and check the source mailbox, network connectivity, migration account permissions, and endpoint settings in the Exchange admin center.

5
Recreate the failed migration

After resolving any identified issue, remove the old batch in Migration and create a new batch for the mailbox that still needs to move. Check the new batch report for progress or further errors.

Verify the mailbox migration and recreate the batch only if needed
A reported failure may be a status error: If the mailbox is already in Exchange Online and works as expected, do not submit it for migration again. Deleting an old batch does not undo completed mailbox moves, but check for other active migrations in the batch before removing it.
Free Microsoft Office alternative

Work with Office documents in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format compatibility, making it easier to move document workflows. It does not migrate Exchange mailboxes or repair Office 365 migration batches.

Review migration checklists and reports in a familiar document interfaceOpen and edit Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a free, lightweight office suite for everyday document workContinue working with existing Office files when moving document workflows
microsoft office alternative - wps office

Frequently Asked Questions

Can a mailbox be migrated even if the batch reports a failure?

Yes. A status-reporting error can show a failure after the mailbox has moved. Check Recipients > Mailboxes in the Exchange Online admin center and verify that the user can access the expected mail before trying another migration.

Where can I find details about the stuck mailbox?

In the Exchange admin center, open Migration, select the batch, and inspect the affected mailbox's report. If its move request is still available, Get-MoveRequestStatistics in Exchange Online PowerShell can provide additional details.

Will deleting the old migration batch undo completed moves?

No. Removing the batch does not move completed mailboxes back to Exchange 2010. Before deleting it, check whether any other mailboxes in the batch are still actively migrating.

What should I check before creating a new batch?

First confirm that the mailbox has not already moved. Then review the migration report and check source-mailbox health, network connectivity, migration permissions, and the migration endpoint configuration.