logo
search
Email Migration

How to Fix Mailbox Migration Failures from Exchange to Exchange Online

Steve KSteve K Sep 25, 2026 869 views

Question details

Users are experiencing failures when migrating several mailboxes from an on-premises Exchange organization to Exchange Online within a hybrid deployment.

How to Fix Mailbox Migration Failures from Exchange to Exchange Online
Product
Microsoft Exchange Online
Device & OS
not provided
Scenario
Moving mailboxes to the cloud in an Exchange hybrid deployment environment.
Observed behavior
Several mailboxes fail to migrate successfully to Exchange Online and generate migration errors in the batch report.
Before you start

Ensure you have Exchange Administrator permissions and verify that your on-premises Exchange server has a stable internet connection to Microsoft 365 migration endpoints.

Solution 1Recommended

Verify Migration Endpoints, Permissions, and Connectivity

Check the core configuration requirements for hybrid mailbox migrations to resolve common endpoint and connectivity issues.

Most mailbox migration failures in a hybrid setup are caused by incorrect endpoint configurations, insufficient administrator permissions, or firewalls blocking connectivity to Microsoft 365.

1
Verify Migration Endpoint

Go to the Exchange admin center (EAC), navigate to Migration, and check the migration endpoints to ensure the on-premises server details are accurate and fully reachable.

2
Check Administrative Permissions

Ensure the administrator account used for executing the migration has both the 'Recipient Management' and 'Organization Management' roles properly assigned.

3
Test Connectivity

Use the Microsoft Remote Connectivity Analyzer tool online to test Exchange Server connectivity and verify that local firewalls are not blocking Microsoft 365 IP addresses or necessary ports.

Check Migration Logs: Reviewing the detailed migration logs in the Exchange Admin Center can provide specific error codes to help pinpoint the exact cause of the sync failure.
Free Microsoft Office alternative

Discover WPS Office for Seamless Productivity

While troubleshooting your Exchange mailbox migration, you may also be looking for cost-effective ways to manage your business documents. WPS Office is a lightweight, highly compatible alternative to Microsoft Office, offering fully featured Word, Excel, and PowerPoint applications for free.

  1. 1. Download WPS Office: Visit the official WPS website and click 'Free Download' to get the installer for your operating system.
  2. 2. Install the Software: Run the downloaded installer file and follow the clear on-screen instructions to complete the setup process in minutes.
  3. 3. Open Office Documents: Launch WPS Office, click 'Open', and select any Microsoft Word, Excel, or PowerPoint files to start editing immediately with full formatting compatibility.
Fully compatible with Microsoft Word, Excel, and PowerPoint formatsLightweight design ensures fast installation and smooth performanceIncludes a robust built-in PDF toolkit for easy editing and conversionFamiliar user interface requires absolutely no learning curve
microsoft office alternative - wps office

Frequently Asked Questions

Why do mailbox migrations pause or fail at 95% in an Exchange hybrid setup?

Migrations often pause or fail at 95% because they are waiting for the final synchronization and mailbox switchover. This can occur if the target delivery domain is incorrectly configured, the migration batch is set to manual completion, or there are unexpected backend connectivity drops.

How can I view detailed error messages for individual failed mailboxes?

You can view detailed errors by navigating to the Exchange admin center, going to Recipients > Migration, selecting the migration batch in question, clicking 'View details', and then choosing the specific user to review the 'Skipped item details' or error summary.

Do I need to assign Microsoft 365 licenses before migrating mailboxes?

Yes, you must ensure that the target user account in Microsoft 365 has a valid Exchange Online license assigned before the migration completes. If the user is unlicensed, the migration process will fail to properly provision the cloud mailbox.