M&A Microsoft 365 Tenant Consolidation Playbook — 5-Day Average Cutover
Just closed an acquisition and now you have two Microsoft 365 tenants, two identity stores, two Purview postures, and two Copilot licensing footprints. EPC Group has run 216+ of these in a 24-month program window moving 1.83 million users. This is the playbook.
The 5-day cutover
- Sunday night — Exchange Online mail migration begins; smart-host routing engaged so mail keeps flowing during the migration.
- Monday–Tuesday — Mailboxes migrate in user waves.
- Wednesday — SharePoint and OneDrive move.
- Thursday — Teams tenant-to-tenant migration finalizes.
- Friday — Cutover complete: users authenticated to new tenant, mail flowing, files present, Teams channels intact.
Users experience a change, not an outage — they can work from their old mailbox until their wave lands in the new one.
The 4-8 weeks before cutover
- Discovery — full source-tenant inventory: users, groups, licenses, domains, gateways, sensitivity labels, retention labels, eDiscovery holds, Purview policies, workflow subscriptions, Power Automate flows, gateway clusters, third-party ISV apps.
- Mapping — target-tenant policy pre-population. Domain-verification tokens pre-staged. Guest access graphs mapped. License SKU differences reconciled.
- Pre-migration data movement — bulk SharePoint and OneDrive delta sync so cutover-day data volumes are minimal.
The 30 days after cutover
- User support burndown (typically 15% of users report a first-week issue).
- Retention policy verification on migrated content.
- Purview eDiscovery hold continuity attestation.
- Source-tenant decommissioning: license retirement, MX-record removal, DNS cleanup.
The five gotchas that blow up an M&A tenant consolidation
- Conflicting custom domains — every SMTP domain, vanity, and Teams @-mention has to move with zero MX-record downtime.
- Guest access and B2B collaboration graphs — don't survive source-tenant retirement without deliberate re-hydration.
- Retention, sensitivity, and eDiscovery holds — need cross-tenant re-application scripting.
- Copilot licensing — doesn't transfer automatically; new tenant means new SKU assignments and new prompt-history isolation.
- SP2013 workflows and citizen-developer Power Automate flows — break in the target tenant's DLP posture and surface only when business users complain.
Frequently Asked Questions
How fast can a tenant consolidation actually be?
EPC Group's average across 216+ M&A tenant migrations (2023-2025 program moving 1.83 million users) is a 5-day average cutover. That is the cutover — the point-in-time move from source tenant to target tenant. Discovery, mapping, and pre-migration data movement precede it by 4-8 weeks depending on size. Post-migration reconciliation and decommissioning follow by 30 days. Total elapsed for a mid-market target (500-2,000 users, no regulated data): 6-8 weeks. Enterprise target (5,000+ users, regulated data): 12-20 weeks.
What does "5-day cutover" actually mean?
The 5-day cutover is a Monday-through-Friday work-hour move. On Day 0 (Sunday night), Exchange Online migration begins. On Days 1-2, mailboxes migrate in waves. On Day 3, SharePoint and OneDrive migrate. On Day 4, Teams tenant-to-tenant migration finalizes. On Day 5, cutover complete: users authenticated to new tenant, mail flowing, files present, Teams channels intact. Users experience a change but not an outage — mail continues to flow (via smart-host routing) during the entire window and users can work from their old mailbox until their wave lands in the new one.
What are the "gotchas" that blow up a tenant consolidation?
(1) Custom domains with conflicting sub-tenant assignments — every SMTP domain, custom vanity, and Teams @-mention domain has to be moved with zero MX-record downtime. (2) Guest access and B2B collaboration graphs that don't survive the source-tenant retirement. (3) Retention labels, sensitivity labels, and Purview eDiscovery holds that need cross-tenant re-application. (4) Copilot licensing that doesn't transfer automatically — new tenant means new licensing SKU assignments. (5) SP2013 workflows and Power Automate flows built by unknown citizen developers that break in the target tenant's Data Loss Prevention posture.
How does EPC Group handle regulated data during a tenant consolidation?
Two parallel workstreams before cutover: (1) Purview eDiscovery Premium legal holds moved to the target tenant with re-application scripting so hold continuity is unbroken. (2) Retention policies and sensitivity labels re-hydrated in the target tenant with auto-labeling policies applied to migrated content so labels persist through the move. For HIPAA and financial-services engagements, EPC Group produces the Compliance Continuity Attestation — a signed document confirming that at no point during the migration was any regulated dataset outside of a compliant posture.
What is unique about the 216-migration EPC Group program?
Three things: (1) Scale — 216+ tenant migrations moving 1.83 million users in a 24-month program window means the runbook is fully automated for every recurring failure mode. (2) Repeatability — the same senior architects have run 30-50 migrations personally. (3) Toolchain — EPC Group runs a hardened combination of Microsoft-native cross-tenant tools plus commercial ISV tools (Quest On Demand, BitTitan, SkyKick, ShareGate) with a lived-experience view of which tool works for which shape of engagement. Most competitors have run a small handful of M&A migrations across the same period.
Talk to the team that built this
If you are staring at a tenant consolidation — announced deal, LOI signed, integration planning kickoff — EPC Group has run this at every scale in every regulated vertical.
Email contact@epcgroup.net or call 888-381-9725.
North America's oldest continuous Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.