Forum Discussion
Migrating Subsidiary Company from Exchange to Office 365
- May 19, 2017
I seem to have found it... Express Migration
https://blogs.technet.microsoft.com/exchange/2016/11/28/new-exchange-online-migration-options/
Hi,
Does this company already has a hybrid connection in place?
Then you could do it with a remote move migration.
BR
- MicrowizAug 16, 2022Copper Contributor
How would i preform this if parent company is being nasty, with the situation. wanting Our company to do this manually and within two weeks ? afterward they shut down there servers. we cant access any of the important things to complete steps can you please point me in the right direction. Company A wants Company B out by a certain time, (2wks) but only gives out XL of name files phones and mailboxes Please help
- Lee WalkerJun 23, 2017Copper Contributor
Hi
I have installed the Office 365 Hybrid Wizard and using the new Express Minimal Migration method.
https://support.office.com/en-gb/article/Use-Minimal-Hybrid-to-quickly-migrate-Exchange-mailboxes-to-Office-365-fdecceed-0702-4af3-85be-f2a0013937ef?ui=en-US&rs=en-GB&ad=GB
Seems to be going well so far.
Thanks
Lee
- Kamal IbrahimJun 29, 2017Copper Contributor
Hi Lee,
I am intrested to know when migration is finished and post migration behavious. Could you please keep us posted because i have never done Minimal Hybrid.
Regards,
Kamal
- Lee WalkerJul 12, 2017Copper Contributor
Still going ok.. Had a couple of issues I thought I'd mention, probably basic stuff but I'm not too experienced:
- Had to add the domain names into the Allowed Domains List in Exchange Online Admin Center > Protection > Spam Filter. Because it was starting to put Mail from on premise users into migrated users junk. This may be because the on premise sends through a Third Party.
- A couple of users didn't have a proxy address for <domain>.mail.onmicrosoft.com I think these were new starters which explains why the HCW didn't add the details.
- I cancelled a Batch from the Office 365 > Users > Data Migration > Exchange, because some had errors. But when I tried to start again, it kept failing. After I left it a while (Exchange TTL I believe) most of them worked. Two didn't appear to have worked because it said Failed in the Status section, so I re-ran and still kept failing saying "InvalidRecipientTypeException: Unsupported recipient type 'Mailbox' provided. Only 'Mailuser' is supported for this migration type." I checked with the users and they seemed fine (they were using Outlook and had the message saying the Administrator has made a change so close and re-open Outlook) and having looked in Exchange Online they had been migrated. So it was just the Status on the Data Migration page that was wrong - Manged to get the status to say Completed by simply deleting the Migration Batch. Lesson learnt - Don't cancel a Migration Batch - If there is an error with one, then let the others finish.Aside from that, it seems straight forward. I had to do contacts and groups manually. There are no rooms/resources for me to do.
Oh, and there's no waiting at 95% sync. When you Start the Migration, it will go through and switch as well, whereas I remember the Cutover Migration waits at 95% sync until you finalize.
Regards
Lee
- Stephan BisserJun 23, 2017Brass Contributor
Well that's the way to go.
Migrate via the hybrid connection...
BR