The 5-Phase M&A Microsoft 365 Tenant Migration Playbook

Why M&A Microsoft 365 migrations need their own playbook

Standard Microsoft 365 tenant migrations are governed by organizational priorities, internal change windows, and IT roadmaps that can flex. M&A migrations are governed by deal close dates, Transition Services Agreement (TSA) expiration timelines, and Day-1 ownership requirements that are non-negotiable. The standard playbook fails under that pressure because it assumes elastic timelines and full source-tenant visibility — two assumptions that almost never hold in M&A.

The M&A Microsoft 365 Tenant Migration Playbook compresses the seven-phase Engagement Operating Model into five M&A-optimized phases. Workstreams run in parallel where the standard playbook serializes them. Pre-close diligence support is a first-class deliverable. Identity coexistence is designed in the Plan phase, not improvised during cutover. Day-1 readiness is the contractual deliverable, not a stretch goal.

Phase 1: Diligence — pre-LOI through deal close

The Diligence phase supports the deal team during the transaction. EPC Group works from limited source-tenant visibility — typically what the deal team can extract under the data room rules — to deliver a Source Tenant Audit, Identity & License Inventory, regulatory exposure assessment, and Day-1 Readiness Gap Analysis. The gap analysis answers the question: what would it take to have users productive in the destination tenant the day after close?

This phase is where M&A Microsoft 365 migrations are won or lost. If the deal team enters close without a Day-1 plan, the post-close timeline is compressed by 30-60 days. If the deal team enters close with EPC Group's Day-1 Readiness Gap Analysis in hand, Phase 2 starts on Day 1 of post-close and execution begins immediately.

Phase 2: Plan — Weeks 1-2 post-close

Plan delivers the Migration Architecture, Tooling Decision Record, Cutover Plan, identity coexistence design, and TSA exit milestones. The Tooling Decision Record names Quest On Demand Migration, AvePoint Fly, ShareGate, BitTitan MigrationWiz, or native Microsoft Cross-Tenant Migration as the execution engine based on identity complexity, workload mix, content fidelity requirements, regulatory baseline, and deal timeline.

Identity coexistence design is the single most consequential decision in Phase 2. The chosen pattern — single-tenant absorption, multi-tenant federation, or Cross-Tenant Access Settings — determines the rest of the engagement. Plan also documents the named senior architect, RACI matrix, and Engagement Excellence Charter for the engagement.

Phase 3: Build — Weeks 3-8

Build executes the migration iteratively. Identity coexistence is stood up first because every other workstream depends on it. Workload migrations follow in waves: Exchange Online, OneDrive for Business, SharePoint Online, Microsoft Teams, Power BI, Power Platform, Microsoft Purview configuration, Microsoft Defender alerting, Microsoft Intune device management. Each wave produces a Workload Migration Report and updates the Risk Register.

Weekly Written Status Reports under the Engagement Excellence Charter give the deal team and the buyer's IT leadership real-time visibility into progress. Real-time risk escalation prevents Day-1 surprises. Predictable change control means scope changes go through Architecture Decision Records, not back-channel side agreements.

Phase 4: Cutover — the 5-day execution window

Cutover is executed in waves over the 5-day average window. Day 1 transitions identity from source to destination tenant. Day 2 resolves email coexistence — mail flow routes to the destination, MX records flip, autodiscover updates propagate. Day 3 cuts over SharePoint, OneDrive, and Microsoft Teams content. Day 4 validates Power BI workspaces, Power Platform solutions, and Microsoft Copilot deployment readiness. Day 5 completes end-user enablement and hypercare entry.

The 5-day window is averaged across 216 M&A migrations. Smaller engagements collapse to 2-3 days. Larger engagements with significant identity complexity extend to 7-10 days. The Go-Live Readiness Assessment, produced 5 business days before cutover, determines whether the window is approved to proceed.

Phase 5: Stabilize — Weeks 9-12

Stabilize covers the 14-day hypercare period with daily status reporting and the longer stabilization tail through Week 12. Defect resolution, adoption measurement, and Run-State Operating Model documentation happen here. The Defect Closure Log captures every issue raised during hypercare with root cause, owner, and resolution time.

Many engagements continue under a Managed Microsoft Cloud and Analytics retainer post-Stabilize. The retainer covers ongoing tenant management, governance enforcement, Microsoft Copilot adoption, Power BI workspace administration, and Microsoft Purview policy tuning. Run-state retainers range from $6,500 to $35,000 per month based on tenant size and workload mix.

The senior-architect bench standard for M&A engagements

Every M&A engagement under the Playbook is led by a senior architect with a minimum of 10 years of Microsoft enterprise consulting experience. The senior architect is named in the Statement of Work, attends every steering committee meeting, and remains accountable through Run state. Founder Errin O'Connor personally reviews every engagement architecture and signs off on every project charter.

No junior bait-and-switch. No vendor handoff at Day-1. Predictable change control under the Engagement Excellence Charter. Every status report, every artifact, and every architectural decision goes through the named senior architect.

How the M&A Playbook relates to the broader Engagement Operating Model

The Engagement Operating Model (EOM) is EPC Group's parent methodology for all engagements. The M&A Playbook is one of four specialized playbooks that compress the EOM for specific engagement shapes — alongside the Managed Service Playbook, the Microsoft Copilot & Purview Playbook, and the Power BI & Microsoft Fabric Modernization Playbook.

The relationship: every M&A engagement is an EOM engagement, but not every EOM engagement is an M&A engagement. The Playbook adds M&A-specific concepts — pre-close diligence, TSA exit milestones, Day-1 readiness — while inheriting the EOM's senior-architect standard, Engagement Excellence Charter, and named artifact discipline.

Tooling decision rationale across the 216-engagement track record

Across 216 M&A migrations, EPC Group has executed with every major tenant migration tool plus native Microsoft. Quest On Demand Migration leads when identity complexity dominates — multi-forest Active Directory, complex Entra ID, 25,000+ users. AvePoint Fly leads when SharePoint and Teams permission fidelity matters and sensitivity label preservation is non-negotiable. ShareGate leads for SharePoint-heavy migrations where content cleanup and governance reset before Microsoft Copilot deployment are part of scope.

BitTitan MigrationWiz leads for well-scoped mailbox, OneDrive, and Teams migrations under aggressive timelines with simpler identity scope. Native Microsoft Cross-Tenant Migration leads for same-Entra-tenant SharePoint cross-site moves and Microsoft-supported scenarios where third-party tooling is unnecessary. The Tooling Decision Record published in Phase 2 documents which tool, which workload, which scenario.

How to start an M&A engagement under the Playbook

Schedule a discovery call at epcgroup.net/schedule, email contact@epcgroup.net, or call (888) 381-9725. Pre-close engagements are supported — EPC Group can be brought in during diligence to support the deal team. After the discovery call, a scoped Statement of Work is delivered naming the senior architect, the playbook phase plan, the tooling decision, and the fixed-fee anchor.