The PMI clock starts at close
Post-Merger Integration (PMI) for Microsoft 365 has a fixed start date — deal close — and a negotiated end date defined in the purchase agreement and the Transition Services Agreement. 90 days is the standard window for mid-market M&A. Enterprise M&A extends to 120-150 days. The window is short because TSA economics, value-creation plan timelines, and quarter-boundary financial reporting all align around the 90-day mark.
The PMI clock is not paused for ramp-up. By Day 1 of post-close, the integration team must have visibility into both source tenants, the destination tenant strategy, the named senior architect, and the Day-1 target. Pre-close diligence support is the leverage point — engaging EPC Group 30-45 days before close means Days 1-15 of planning are pre-staged.
Days 1-30: plan and stand-up
The first 30 days deliver Migration Architecture, RACI matrix, risk register, Tooling Decision Record, identity coexistence design, cutover plan, and TSA exit milestones. Identity coexistence design is the most consequential deliverable because every other workstream depends on it. The chosen pattern — single-tenant absorption, multi-tenant federation, or Cross-Tenant Access Settings — determines the rest of the engagement.
By Day 30, the engagement has a documented path to Day-1 readiness and Build phase is ready to execute. The Engagement Excellence Charter is signed by all parties. The named senior architect is on every steering committee meeting. The first weekly written status report has gone out.
Days 31-60: build and migrate
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. Pilot waves of 50-100 users validate the migration tooling, the identity coexistence pattern, and the Microsoft Purview label preservation before full-tenant cutover. Pilot results inform any change-control needed for the cutover window.
Days 61-90: cutover and stabilize
The 5-day cutover window typically lands around Day 75. Day 1 of cutover transitions identity. Day 2 resolves email coexistence. Day 3 cuts over SharePoint, OneDrive, and Microsoft Teams content. Day 4 validates Power BI workspaces and Power Platform solutions. Day 5 completes end-user enablement and hypercare entry.
Hypercare runs daily for 14 days with status reports to the deal team and IT leadership. The Defect Closure Log captures every issue. By Day 90, Run-State Operating Model is documented and approved. Open defects roll into the post-hypercare backlog. Managed service handoff is complete if applicable.
Identity coexistence across the 90 days
Identity coexistence is the hardest operational challenge in PMI. The design pattern is chosen in Days 1-30. Stand-up runs in Days 31-60. The final transition executes in Days 61-90. Throughout the 90 days, Microsoft Entra B2B and Cross-Tenant Access Settings enable transitional access between source and destination tenants for users who need cross-tenant collaboration during integration.
The choice between single-tenant absorption (all source users move into the destination Entra ID), multi-tenant federation (both tenants remain operational long-term with federation between them), or Cross-Tenant Access Settings (transitional access only) is driven by deal economics, user volume, identity complexity, and regulatory environment. The chosen pattern is documented in an Architecture Decision Record signed by the senior architect.
Communication plan and end-user enablement
The end-user enablement workstream owns communications across the 90 days. Pre-Day-1 communications start at Day 60 with welcome messaging. Day 75 sends the cutover schedule. Day 80 sends the Day-1 instructions including SSO claim updates, MFA enrollment guidance, and support escalation paths. Day-1 itself includes a help desk briefing on common cutover issues.
The end-user enablement lead attends every steering committee meeting alongside the senior architect. Skipping or rushing this workstream is the single biggest predictor of hypercare ticket storms. The 14-day hypercare period exists precisely because no amount of pre-enablement eliminates Day-1 +1 questions.
Compliance baseline maintained
The Diligence phase establishes the regulatory baseline. Days 1-30 rebuild Microsoft Purview labels, retention policies, eDiscovery configuration, and Defender alerting in the destination tenant. Days 31-60 validate the baseline through controlled content migration. Days 61-90 re-validate at cutover. The Compliance Baseline artifact documents the configuration applied. Named artifacts produced during the migration form the audit trail.
Common PMI failure modes
The most common failures: deal team did not engage IT in Diligence, so Days 1-30 are spent rebuilding source-tenant visibility instead of planning; identity coexistence under-designed, leading to authentication failures at cutover; Microsoft Purview baseline not rebuilt before content migration, creating audit gaps; end-user enablement skipped, leading to hypercare ticket storms. The M&A Microsoft 365 Tenant Migration Playbook prevents all four through staged Build-phase deliverables that are gated before cutover begins.
How to start a PMI engagement
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 90-day plan, the tooling decision, and the fixed-fee anchor.