{"id":5970,"date":"2015-09-10T12:00:46","date_gmt":"2015-09-10T11:00:46","guid":{"rendered":"http:\/\/www.markwilson.co.uk\/blog\/?p=5970"},"modified":"2015-09-14T20:27:21","modified_gmt":"2015-09-14T19:27:21","slug":"moving-mailboxes-tofrom-exchange-online-using-the-eac","status":"publish","type":"post","link":"https:\/\/www.markwilson.co.uk\/blog\/2015\/09\/moving-mailboxes-tofrom-exchange-online-using-the-eac.htm","title":{"rendered":"Moving mailboxes to\/from Exchange Online using the EAC"},"content":{"rendered":"
One of the advantages with deploying Exchange Online in a hybrid configuration (i.e. Exchange on-premises and Office 365 Exchange Online in the cloud) is that you can easily move mailboxes back and forth.<\/p>\n
It can be done with PowerShell but one of the straightforward methods is from the Exchange Admin Center (EAC), where there’s an option (to the bottom right of the mailbox panel, under recipients in the Enterprise tab) to move a mailbox to Exchange Online, or to another database (locally), with most of the settings pre-populated for you (like the target mail domain or tenantname<\/em>.mail.onmicrosoft.com).<\/p>\n
Moving back requires a slightly different process though and needs to be performed from the migration panel in the Office 365 tab of EAC.<\/p>\n
You’ll also need to know the name of the database you want to move the mailbox to on-premises, and the mail domain name.<\/p>\n
One of the challenges I found with moving mailboxes to\/from Exchange Online using the EAC was that I sometimes see a migration batch marked as “Completed” but with 0 of 0 synced, 0 of 0 finalized, 0 failed.\u00a0 This seems to happen if a previous mailbox move had failed; deleting the failed migration batch before re-attempting seems to allow the mailbox move to run successfully.<\/p>\n","protected":false},"excerpt":{"rendered":"