Home » Exchange Server » Hybrid Mailbox Move Fails with Mismatched Archive GUID Error

Hybrid Mailbox Move Fails with Mismatched Archive GUID Error

While performing a remote mailbox move to off-board a user from Office 365 to Exchange Server 2013 on-premises you may encounter an error due to a mismatched archive GUID.

Error: MigrationPermanentException: Recipient ‎’office365bootcamp.net/Staff/People/DirSync/Alan.Reid‎’ has mismatched archive GUID ‎(00000000-0000-0000-0000-000000000000)‎. Expected value: 77d97d5b-8f61-4fd4-b355-1463525a068f.

In this example a Hybrid configuration has been established and the user Alan Reid is being migrated to the on-premises Exchange 2013 server. Alan is archive-enabled in Office 365.

Using PowerShell connected to Exchange Online and looking at the properties of the cloud mailbox the archive GUID is visible:

For the on-premises object the archive GUID does not match.

To resolve the issue and allow Alan’s mailboxes to be moved we can set the on-premises archive GUID to the expected value so that they match.

Resume the migration batch and it should now proceed without the archive GUID error.

Paul is a Microsoft MVP for Office Servers and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul is a co-author of Office 365 for IT Pros and several other books, and is also a Pluralsight author.
Category: Exchange Server


  1. andrew says:

    does this work with exchange 2010? I’m getting ‘Set-remotemailbox’ is not recognized as the name of a cmdlet

  2. Mahantesh RJ says:

    Thanks for the nice article, it helped me to offload the mailbox from o365 when I was stuck with an error of mismatch of guid.

  3. Cappy says:

    How do you identify the folks w/ mismatched archive folders? You used to be able to find them in the old portal – originally under Users/Active Users/”Users with errors” filter, but that whole filter was turned off a year or so ago. Then, again under the old portal, you could see the error box if you opened the user’s properties. But I’m not seeing anything in the new portal anywhere that identifies this problem.

    So we can’t get ahead of it, we just have to wait for the user to call us….

  4. Joel says:

    Hi Paul,

    What about the opposite direction? Onboarding from exchange 2013 set up in hybrid with office 365.

    Error: MigrationPermanentException: The archive GUIDs on source ‎’first last’ and target ‎’first last’ recipients don‎’t match. Source archive GUID: 00000000-0000-0000-0000-000000000000, target archive GUID: 5xxxxxxx-0xxx-4xxx-bxxx-fxxxxxxxxxxx. (edited for privacy).

    The user was attempted to migrate twice, then we disabled his in place archive, exported it to PST, then are now attempting to migrate just his mailbox with no archive.

    • Menz says:

      Hello Joel,
      I have the same question as you. I am trying to migrate a user from on premises exchange 2013 to Exchange online/office 365 but the user keeps failing. I too disconnected the in-place archive for the user since it seems like it was the issue. I too, exported his archive to .PST and then tried to migrate the user again and got the “has mismatched archive GUID” message I did all the steps in this article except change the GUID as I am not sure the “remoteMailBox” command should be used in this case.

      I wonder what command I should use?

Leave a Reply

Your email address will not be published. Required fields are marked *