For organizations in a deal with a close date, or a rename that changes the sign-in and email domain.
We plan and run the IT side of a merger, acquisition, or rebrand. That means what has to work on day one, two tenants and directories combined into one, and workloads moved from the seller’s cloud.
The day-one plan sets the gates and the waves. Tenant and directory consolidation, any rename, and workloads moved out of the seller’s cloud follow that plan.
The decisions, owners, and gates for the integration, and the short list of what has to work on the first morning.
A close date on the calendar, with decision rights, owners, and the first-morning list still undecided.
Scoped per tenant and user count
Two Microsoft 365 tenants and Active Directory forests brought into one, with identities mapped and sign-in kept working.
A deal that combines two tenants and their directories, or splits one, with accounts to pair and verify with HR first.
A new name and a new sign-in and email domain, with the applications that would break mapped and handled first.
An institution or company changing its name, with a date it has to be done by.
Workloads that have to move from the seller’s cloud to yours, inventoried, estimated, and placed in your tenant.
Not sure which fits? Request a meeting
It depends on the deal timeline and how many organizations combine. A tenant move can cut over in one weekend after weeks of preparation, while several organizations merging into one directory move in waves over a longer period. The Assess phase at the start typically takes 3–4 weeks.
A big-bang move puts the whole organization on the new tenant over one weekend, with fewer moving parts but a hard cutover. Coexistence keeps both sides working for a period, which costs more and needs cross-tenant access set up. The Assess phase recommends one, with the limitations written down.
It depends on licensing, security baseline, and how much each side would have to move. That often favors the larger or better-run tenant, and the Assess phase makes the recommendation.
Teams and Power Platform apps are rebuilt in the target, since they don’t transfer cleanly between tenants, and SharePoint content moves with permissions reviewed. The move runs as a tenant-to-tenant migration, timed to the deal’s wave plan.
The number of tenants, directories, and users sets most of it, along with whether the two sides must coexist. Remapping applications and sign-ins adds to it, and so does how hard the close date is.
A program sponsor, leads for identity, messaging, collaboration, applications, and compliance, HR to verify identities, and a help desk queue for the cutover weekend. We bring the plan, the runbooks, and the people to run them.
It starts with a 60-minute call. If we need more to scope it, a short questionnaire follows. Then a written proposal and statement of work. Once you approve, we begin with the Assess phase.
