Acquisition migration into existing hybrid tenant

%3CLINGO-SUB%20id%3D%22lingo-sub-226820%22%20slang%3D%22en-US%22%3EAcquisition%20migration%20into%20existing%20hybrid%20tenant%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226820%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehave%20a%20unique%20scenario%20and%20seeing%20if%20i%20can%20do%20the%20work%20without%20leveraging%20a%20tools%20based%20migration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20is%20my%20scenario%3C%2FP%3E%3CP%3ECompany%20A%20is%20in%20a%20hybrid%20configuration%20with%20Exchange%20on%20prem%26nbsp%3Band%20office%20365%3C%2FP%3E%3CP%3ECompany%20B%20was%20acquired%20and%20is%20fully%20exchange%202010%20on%20prem%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethere%20is%20already%20a%20plan%20under%20way%20to%20do%20an%20AD%20migration%20of%20the%20user%20objects.%26nbsp%3B%20The%20forest%20will%20go%20away%20once%20the%20consolidation%20is%20done%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20where%20i%20can%20do%20remote%20mailbox%20moves%20from%20the%20source%20envrioment%20without%20attaching%20AAD%20connect%20to%20that%20envrioment%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20envision%20a%20scneario%26nbsp%3Bsuch%20as%20the%20following%3C%2FP%3E%3CP%3E1)%20configure%20enough%20of%20the%20hybrid%20envrioment%26nbsp%3Bin%20company%20b%20to%20enable%20a%20remote%20mailbox%20move%20to%20Office%20365%20(making%20the%20routing%20addresses%2C%20migration%26nbsp%3Bendpoint%2C%20accepted%20domains%20etc.)%3C%2FP%3E%3CP%3E2)%20leverage%20AD%20migration%20tools%20to%20sync%20the%20necessary%20exchange%20AD%20data%20to%20the%20source%20forest%20to%20create%20the%20concept%20of%20a%20on%20prem%26nbsp%3Bmailbox%20in%20Office%20365%20(and%20groups%20etc.)%3C%2FP%3E%3CP%3E3)%20perform%20a%20remote%20mailbox%20move%20of%20the%20mailbox%20data%3C%2FP%3E%3CP%3E4)%20finalize%20the%20migration%3C%2FP%3E%3CP%3E5)%20sync%20the%20updated%20mailbox%20attributes%20to%20Company%20A's%20forest%20so%20that%20it%20is%20seen%20as%20a%20remote%20mailbox%20on%20both%20sides%3C%2FP%3E%3CP%3E6)%20user's%20outlook%20client%20would%20get%20the%20redirect%20from%20on%20prem%26nbsp%3Bto%20o365%20and%20not%20require%20a%20redownload%20fo%20the%20OST%20as%20the%20mailbox%20GUID%20is%20the%20same.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eit's%20a%20very%20large%20environment%20(4000%20users%2C%2020TB%20of%20data)%20so%20i'd%20like%20to%20avoid%20going%20tools%20based%20if%20at%20all%20possible.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-226820%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
New Contributor

Hi,

 

have a unique scenario and seeing if i can do the work without leveraging a tools based migration.

 

Here is my scenario

Company A is in a hybrid configuration with Exchange on prem and office 365

Company B was acquired and is fully exchange 2010 on prem

 

there is already a plan under way to do an AD migration of the user objects.  The forest will go away once the consolidation is done

 

Is there a way where i can do remote mailbox moves from the source envrioment without attaching AAD connect to that envrioment?

 

I envision a scneario such as the following

1) configure enough of the hybrid envrioment in company b to enable a remote mailbox move to Office 365 (making the routing addresses, migration endpoint, accepted domains etc.)

2) leverage AD migration tools to sync the necessary exchange AD data to the source forest to create the concept of a on prem mailbox in Office 365 (and groups etc.)

3) perform a remote mailbox move of the mailbox data

4) finalize the migration

5) sync the updated mailbox attributes to Company A's forest so that it is seen as a remote mailbox on both sides

6) user's outlook client would get the redirect from on prem to o365 and not require a redownload fo the OST as the mailbox GUID is the same.

 

it's a very large environment (4000 users, 20TB of data) so i'd like to avoid going tools based if at all possible. 

0 Replies