Multiforest migration to Office 365

%3CLINGO-SUB%20id%3D%22lingo-sub-1171530%22%20slang%3D%22en-US%22%3EMultiforest%20migration%20to%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1171530%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Community%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20of%20our%20customer%20has%20the%20below%20environment%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGoal%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20below%20forests%20needs%20to%20be%20synchronized%20to%20a%20single%20office%20365%20tenancy%20(%20which%20could%20be%20a%20brand%20new%20tenancy%20)%20so%20they%20can%20keep%20single%20email%20name%20space%2C%20single%20SharePoint%2C%20single%20one%20drive%20organisation%20for%20all%20forests.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFOREST%20A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExchange%202013%20on-prem%20and%20EXO%20in%20Hybrid%3C%2FP%3E%3CP%3EADFS%20is%20installed%20to%20sync%20Security%20enabled%20AD%20groups%20to%20O365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsers%20using%20SharePoint%20Multiple%20sites%20and%20OneDrive%3C%2FP%3E%3CP%3ESSO%20enabled%20by%20ADFS%2C%20no%20write%20back%3C%2FP%3E%3CP%3E2250%20mailboxes%20hosted%20in%20EXO%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFOREST%20B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELocal%20AD%20in%20on-prem%3C%2FP%3E%3CP%3ENo%20hybrid%3C%2FP%3E%3CP%3EAAD%20sync%20installed%20to%20sync%20to%20O365%3C%2FP%3E%3CP%3E1700%20mailboxes%20hosed%20in%20EXO%3C%2FP%3E%3CP%3ENo%20SPO%2FOneDrive%20users%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFOREST%20C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELocal%20AD%20in%20on-prem%3C%2FP%3E%3CP%3ENo%20hybrid%3C%2FP%3E%3CP%3EAAD%20sync%20installed%20to%20sync%20to%20O365%3C%2FP%3E%3CP%3E1800%20mailboxes%20hosed%20in%20EXO%3C%2FP%3E%3CP%3ENo%20SPO%2FOneDrive%20users%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFOREST%20D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eon-prem%20Exchange%202013%3C%2FP%3E%3CP%3E500%20mailboxes%20hosted%20on-prem%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EQuestions%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20we%20plan%20for%20it%3F%3C%2FP%3E%3CP%3EAny%20Best%20practices%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMany%20thanks%20in%20advance.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1171530%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMultiforest%20migration%20to%20Office%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1172862%22%20slang%3D%22en-US%22%3ERe%3A%20Multiforest%20migration%20to%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1172862%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F301435%22%20target%3D%22_blank%22%3E%40Newlife%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBased%20on%20your%20scenario%20the%20advice%20is%20to%20migrate%20Forest%20B%2CC%20and%20D%20to%20Forest%20A%20using%20a%20third-party%20tool%20and%20then%20when%20you%20have%20all%20consolidated%20on%20the%20same%20active%20directory%20and%20hybrid%20implemented%2C%20you%20can%20migrate%20to%20online.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOr%20you%20can%20create%20all%20users%20on%20Forest%20A%2C%20synchronize%20them%20and%20use%20a%20third-party%20tool%20to%20migrate%20the%20data%20from%20Tenant%20to%20Tenant.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERead%20more%20here%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmailbox-migration%2Fmigrate-mailboxes-across-tenants%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmailbox-migration%2Fmigrate-mailboxes-across-tenants%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%20regards%2C%3C%2FP%3E%0A%3CP%3ENuno%20%C3%81rias%20Silva%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1172806%22%20slang%3D%22en-US%22%3ERe%3A%20Multiforest%20migration%20to%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1172806%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BStart%20reading%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fhybrid%2Fplan-connect-topologies%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fhybrid%2Fplan-connect-topologies%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThen%20the%20planning%20depends%20on%20who%20must%20go%20first(duplicate%20names%20for%20the%20desired%20shared%20namespace)%2C%20timing%2C%20coexistence%20for%20free%20busy%2C%20GAL%20sync%20and%20different%20approaches%20for%20each%20scenario%2C%20as%20you%20may%20be%20able%20to%20move%20the%20data%20to%20the%20target%20tenant%20using%20native%20tools%20for%20the%20on-premise%20only%20environments%20and%20use%203rd%20party%20tools%20to%20move%20data%20for%20the%20tenant%20to%20tenant%20or%20save%20and%20export%20data%20depending%20on%20legal%20holds%2C%20archiving%2C%20journaling%2C%20relays%20that%20are%20in%20place%20on%20each%20forest.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3EErick%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

Hi Community, 

 

One of our customer has the below environment:

 

Goal:

 

All below forests needs to be synchronized to a single office 365 tenancy ( which could be a brand new tenancy ) so they can keep single email name space, single SharePoint, single one drive organisation for all forests.

 

FOREST A

 

Exchange 2013 on-prem and EXO in Hybrid

ADFS is installed to sync Security enabled AD groups to O365.

 

Users using SharePoint Multiple sites and OneDrive

SSO enabled by ADFS, no write back

2250 mailboxes hosted in EXO

 

FOREST B

 

Local AD in on-prem

No hybrid

AAD sync installed to sync to O365

1700 mailboxes hosed in EXO

No SPO/OneDrive users

 

FOREST C

 

Local AD in on-prem

No hybrid

AAD sync installed to sync to O365

1800 mailboxes hosed in EXO

No SPO/OneDrive users

 

FOREST D

 

on-prem Exchange 2013

500 mailboxes hosted on-prem

 

Questions:

 

How can we plan for it?

Any Best practices?

 

Many thanks in advance. 

 

8 Replies
Highlighted

@Newlife Start reading: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-topologies

Then the planning depends on who must go first(duplicate names for the desired shared namespace), timing, coexistence for free busy, GAL sync and different approaches for each scenario, as you may be able to move the data to the target tenant using native tools for the on-premise only environments and use 3rd party tools to move data for the tenant to tenant or save and export data depending on legal holds, archiving, journaling, relays that are in place on each forest. 

 

Regards

Erick

Highlighted

Hi @Newlife,

 

Based on your scenario the advice is to migrate Forest B,C and D to Forest A using a third-party tool and then when you have all consolidated on the same active directory and hybrid implemented, you can migrate to online.

 

Or you can create all users on Forest A, synchronize them and use a third-party tool to migrate the data from Tenant to Tenant.

 

Read more here https://docs.microsoft.com/en-us/exchange/mailbox-migration/migrate-mailboxes-across-tenants

 

Best regards,

Nuno Árias Silva

Highlighted

@Nuno Silva Thank you very much for your inputs. 

 

I don't think your first approach (moving Forests B, C, D to forest A and then migrate to Office 365) will help because we're creating brand new tenant in Office 365 and then we need one more tenant to tenant migration which can be done by 3rd party tool only. right? please confirm. 

Highlighted

Hi @Newlife,

 

You can create a new tenant and use a third-party tool to migrate all your data to a new tenant, but if you have an infrastructure already implemented with hybrid and using many services and have a lot of users compared to all other forests. The best way for time and cost is to consolidate all into the Forest A and then migrate the others, but you can migrate all to a new tenant if you need it. All of these migrations depending on the workload you are using you need to use third-party tools to each of workload.

 

Best Regards,
Nuno Árias Silva

 

Highlighted

@Nuno Silva - now the approach have got slightly changed. 

 

It has basically 2 phases:

 

Phase 1 :

 

Keep any one of the Office 365 Tenant and leverage single AAD Connect to sync from all the 4 on-prem ADs to this Office 365 Tenant.

 

Phase 2:

 

Create the brand new Office 365 Tenant and leverage Skykick for tenant to tenant migration.

 

Let's focus on Phase 1 and

 

Is there any best practices to complete Phase 1?

 

Many thanks!

Highlighted

Hi @Newlife,

 

The best way to archive the phase 1 please read the section "Multiple forests, single Azure AD tenant" on the following link https://docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-topologies.

 

After identity is implemented in place, that you can start migration.

 

Best Regards,
Nuno Árias Silva

Highlighted

@Nuno Silva - Thank you for your prompt response. 

 

Let's say, on Phase 1,

 

We'd only need to migrate just the ADs from Forest B, C, D to Forest A and not the Exchange/SP severs, will it be the same approach or do we need to leverage ADMT tool?

 

Another question is, in order to keep only one AAD connect to sync objects from all other ADs, where do we need to place the AAD server, is that on domain joined, or DMZ zone?

 

Please assist.

Highlighted

Hi @Newlife,

 

You can use ADMT to migrate from Domain A to B and Etc, but depending on the final scenario.

 

The AAD Connect will need to access to all AD's. 

 

Best Regards,
Nuno Árias Silva