Move on-premises mailboxes to Exchange Online
You can use the remote move migration wizard on the Office 365 to move existing user mailboxes in the on-premises organization to the Exchange Online organization.
- Logon office 365 portal with administrator account, open Exchange Admin Center.
- Select Recipients and click migration.
- Click Add
, and then select Migrate to Exchange Online.
4. On the Select a migration type page, select Remote move migration and then click Next.
5. On the Select the users page, click Add 
and select the on-premises users
and click Add.
6. Click OK, and then click Next.
7. On the Confirm the migration endpoint page, verify that the FDQN of your on-premises Exchange server is listed when the wizard confirms the migration endpoint.
8. On the Move configuration page, enter name in New migration batch name and then click Next.
9. On the Start the batch page, select at least one recipient to receive the batch complete report. Verify that the Automatically start the batch option is selected, and then select the Automatically complete the migration batch check box. Click New.
Move Exchange Online mailboxes to the on-premises organization
- Logon office 365 portal with administrator account, open Exchange Admin Center.
- Select Recipients and click migration.
- Click Add
, and then select Migrate from Exchange Online.
4. On the Select the users page, select Select the users that you want to move and then click Next.
5. On the Select the users page, click Add 
and then select the Exchange Online users to move to the on-premises organization, click Add and then click OK. Click Next.
6. On the Confirm the migration endpoint page, verify that the FDQN of your on-premises Exchange server is listed when the wizard confirms the migration endpoint. Click Next.
7. On the Move configuration page, enter a name for the migration batch in the New migration batch name text field. Then enter the target delivery domain in the Target delivery domain for the mailboxes that are migrating to Office 365 field.
8. Choose whether to also move the archive mailbox for the selected user and enter the database name you’d like to move this mailbox to in the Target database text field.
9. On the Start the batch page, select at least one recipient to receive the batch complete report. Verify that Automatically start the batch is selected, and then select the Automatically complete the migration batch check box. Click New.
Hope you enjoy this post.
Cary Sun
Twitter:@SifuSun
I’m in the process of doing this after migrating users to Exchange Online and runnig the command to convert a mailbox to mailcontact (exchange 2010) I can send email internally fine and send externally fine but when I try to send externally to internally I get an error in the messaging logs 550 relaying blocked, read new mail, add XXX G_RELAY_ALLOW_IP or enable smtp authentication. Any ideas?
Hi SilT,
Check your connectors, it won’t create connector automatically if you ran the wizard in minimal hybrid mode. try rerun the wizard in Full mode.Let me know if you still have issues.
Thanks.
Cary
Great Stuff. I am using third-party tool to migrate from 2016 to office 365. 2106 is setup as a source.com and office 365 as target.com for example. Now when I migrate a mailbox on the Source ECP it shows as an office 375 mailbox and also creates an MEU which looks fine. On the Target Hybrid environment from the ECP it shows just an MEU and no mailbox. However the mailbox has been migrated and can be logged on. On the Office 365 console it comes up as a Mailbox. its just the Hybrid on Target cannot see a mailbox. AADsync looks fine. The issue I am having is sending an external from Gmail never reaches that mailbox if I use its source email address. the Hygiene engine says its delivered but I cant trace that email.. Internally from source it works ok, on the target MEU the target address is xx.onmicrososoft.com which looks ok. Any help or ideas appreciated. I cant figure out if this how the objects should be after the migration.