Remote mailbox is not moved from on-premises Exchange 2010 to Exchange Online when move shows as Completed

Kehtib: Exchange OnlineExchange Server 2016 Enterprise EditionExchange Server 2016 Standard Edition

Note The Hybrid Configuration wizard that's included in the Exchange Management Console in Microsoft Exchange Server 2010 is no longer supported. Therefore, you should no longer use the old Hybrid Configuration wizard. Instead, use the Office 365 Hybrid Configuration wizard that's available at For more information, see Office 365 Hybrid Configuration wizard for Exchange 2010.


Consider the following scenario.
  • You are using Office 365.
  • You perform a move request for a remote mailbox from an on-premises Exchange 2010 server to Exchange Online.
  • After you perform the move request, the Exchange Management Console shows the status of the request as Completed.
In this scenario, the mailbox isn't moved, and the move request isn't listed on the migration page of the Exchange admin center in Exchange Online.


This issue occurs if the on-premises mailbox that you want to move was created in Exchange 2016 or Exchange 2013, and you have an on-premises environment that's also running Exchange 2010. In this scenario, you can't move the mailbox from an Exchange 2010 server.


Perform the remote mailbox request from the Exchange admin center in Exchange Online.


To check whether the move process is working correctly, follow these steps:
  1. Open the Exchange admin center on the on-premises Exchange server.
  2. Click Office 365, click recipients in the left navigation pane, and then click migration.
  3. View the move status of the mailboxes. You should see the following values:
    • The status shows as Syncing during the mailbox move process.
    • The status shows as Completed after the mailbox is successfully moved.
Note You can also run the following cmdlet in the Exchange Management Shell to check the status of the migration batch:
Get-MigrationBatch –Identity <Batch Name> 
Still need help? Go to Microsoft Community or the Exchange TechNet Forums.