ADDS trusted A. OnPrem EX2013 B.Office 365 into new ADDS and New 0365 Tenant?'s%20(each%20with%20their%20own%20forest%20and%20single%20domain)%20that%20have%20operated%20in%20a%20trusted%20ADDS%20forest%20configuration.%20Each%20forest%20contains%20their%20own%20respective%20mail%20system.%20One%20has%20on-premise%20Exchange%202013.%20The%20other%20ADDS%20forest%20has%20O365%20and%20uses%20Azure%20AD%20Connect%20to%20sync%20on-premise%20ADDS%20users%20to%20o365.%20These%20mail%20systems%20are%20utilizing%20Galsync%20(enow)%20to%20support%20cross%20forest%20GAL's.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20not%20(yet)%20using%20o365%20SharePoint%2C%20one%20drive%2C%20or%20other%200365%20services%20other%20than%20email.%20*We%20will%20later%20in%20the%20new%20named%20entity.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20now%20going%20to%20merge%20these%20two%20environments%20(ADDS%20forest(s)%20%2F%20domain(s))%20into%20a%20new%20named%20ADDS%20entity%20(forest%20and%20domain)%20-%20and%20new%20o365%20tenant.%20This%20new%20named%20entity%20will%20utilize%20many%20of%20the%20o365%20offerings.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20migrated%2Fmerged%20trusted%20forests%2C%20and%20Exchange%20on-premise%202010%2F2013%20systems%20together%20via%20ADMT%20and%20mailbox%20moves.%20This%20looks%20to%20be%20a%20bit%20more%20challenging.%3CBR%20%2F%3EHas%20anyone%20performed%20a%20similar%20migration%2Fmerge%3F%20Would%20they%20be%20willing''t%20make%20duplicates%20with%20actual%20AD%20users%3C%2FP%3E%3CP%3EAdd%20UPN%20Suffixes%20to%20your%20Domain%2FForest%3C%2FP%3E%3CP%3EInstall%2FUpgrade%20AD%20Connect%20%2C%20provision%20users%20on%20new%20Tenant%3C%2FP%3E%3CP%3EAdd%20Authoritative%20Domains%26nbsp%3B%20run%20Hybrid%20Wizard%20and%20check%20all%20domains%20%2C!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

We have two company's (each with their own forest and single domain) that have operated in a trusted ADDS forest configuration. Each forest contains their own respective mail system. One has on-premise Exchange 2013. The other ADDS forest has O365 and uses Azure AD Connect to sync on-premise ADDS users to o365. These mail systems are utilizing Galsync (enow) to support cross forest GAL's.
We are not (yet) using o365 SharePoint, one drive, or other 0365 services other than email. *We will later in the new named entity.
We are now going to merge these two environments (ADDS forest(s) / domain(s)) into a new named ADDS entity (forest and domain) - and new o365 tenant. This new named entity will utilize many of the o365 offerings.
I have migrated/merged trusted forests, and Exchange on-premise 2010/2013 systems together via ADMT and mailbox moves. This looks to be a bit more challenging.
Has anyone performed a similar migration/merge? Would they be willing to share how they did it?
Any insight, links, or thoughts are very much appreciated.
I found something similar in this forum on reddit -
Thanks in advance,

5 Replies
So you are going to change UPNs , Primary SMTPs etc? right ?If you think of it, the whole process looks like a scary one , but really it is quite straightforward . First things first , AD Sync is your friend and the very tool that is going to keep things in line . Create your new Tenant , and verify the Mail Domains. You will go Hybrid so people will continue to work, and maybe in the end you may Decommission Exchange 2013 right ?


Yes, you are correct.  We are going to change UPNs , Primary SMTPs etc and we will decommission Exchange 2013.

Would you recommend something about the process that might help?


Thank you.


Hello@Kevin Watkins 

Sorry for the late answer , i was quite engaged. So have you started yet ? One this i would like to point out is to carefully plan your Identities , just make clear which one is which and what aliases are on them

What about your PST files ?  Are they holding a lots of GB ? In a similar case we uploaded all Data and made the Import Jobs from 365 Admin.

We have not begun.
PST's should be relatively small.
Thanks fro your insight. Much appreciated.


Hello@Kevin Watkins

Well if you allow me to summarize

Verify domains in Azure or O365 , keep in mind it MAY take 24 hours to move from one Tenant to another , plan before hands and add extra waiting time just in case

Check external guest identities that they don't make duplicates with actual AD users

Add UPN Suffixes to your Domain/Forest

Install/Upgrade AD Connect , provision users on new Tenant

Add Authoritative Domains  run Hybrid Wizard and check all domains , select centralized mail transport if you keep your MX onpremise

In the meantime export all PSTs and plan for the Import procedure with AzCopy

Let me know your thoughts !