Why a deal changes the migration
A tenant-to-tenant migration inside one company can take as long as it needs. A consolidation after an acquisition cannot: signing sets the clock, close starts it, Day One is the date the business judges the deal by, and the transition-services agreement ends on a date the seller controls. Two organizations with different security postures, policies and habits have to work together before they merge, and everything that is not finished when the agreement ends is either lost or paid for at the seller’s rate. The program below is built around those four dates, in the order that keeps the risk down: identity before data, coexistence designed to end, waves that reconcile, and an exit with evidence.
The six phases
Users, licenses, domains, mailboxes, SharePoint and OneDrive volumes, Teams, Power Platform environments, Entra app registrations, Conditional Access, sensitivity labels, retention policies and third-party integrations on both sides; overlap analysis for duplicate domains, colliding group names and conflicting app registrations; the deal calendar (signing, close, Day One, transition-services-agreement end) mapped to a migration calendar.
Target identity model (single Entra tenant, hybrid with one or two directories, B2B coexistence during transition), object matching and attribute mapping, UPN and domain cut-over order, Conditional Access and MFA alignment so security posture does not drop on Day One, privileged-role clean-up on the acquired tenant before it is trusted.
Free/busy and mail flow across tenants, shared address list, Teams external access and cross-tenant chat, B2B guest patterns for shared workspaces, and the rules that keep sensitivity labels and DLP effective while two tenants are both live. Coexistence is designed to be dismantled, not to become permanent.
Mailboxes, OneDrive, SharePoint sites, Teams (with channels, files and chat history where the tools allow), Power Platform solutions and Power BI content moved in waves by business unit, with permission mapping, sharing-link remediation, label preservation, delta passes and a reconciliation report per wave. Tool selection follows the scenario: Microsoft cross-tenant mailbox and OneDrive migration, ShareGate, AvePoint or Quest as the estate demands.
A Day One runbook the business signs: which populations are on which tenant, what works and what waits, the service-desk script, the communications, the rollback line. Identity, mail and Teams are the Day One non-negotiables; the long tail of content follows in waves.
The transition-services agreement ends on a date the seller controls. The plan works backward from it: every dependency on the seller's tenant enumerated, every one closed before the date, the decommissioning evidence collected, and the acquired tenant retired or, for a divestiture, handed over clean.
Contracted records
Three consolidations with redacted primary-source records in the EPC Group Evidence Center — purchase orders, statements of work and countersignatures, not testimonials:
- Tarleton State University — Office 365 cross-tenant migration (2021): a university tenant consolidated across tenants under FERPA and state requirements.
- Prairie View A&M University — Google Workspace to Microsoft 365 migration (2020): a non-Microsoft source brought into a Microsoft 365 tenant, the pattern most acquisitions of Google-based companies follow.
- Superior Court of California, County of Amador — Exchange 2019 and Active Directory migration (2024) and the Exchange Online and Microsoft 365 migration (2026): identity and mail moved in a court environment with the evidence discipline that implies.
These are engagement records, not endorsements. The M&A figures on this page — 216+ tenant migrations, 1.83 million users, 2023–2025 — are the registry figures every EPC Group page renders.
The buyer’s checklist — ten questions for any consolidation partner
- 1Does the plan start from the deal calendar — signing, close, Day One, TSA end — and work backward, or from a tool?
- 2Is the target identity model decided before any data moves, and does security posture hold on Day One (Conditional Access, MFA, privileged roles)?
- 3How are duplicate domains, colliding group names and conflicting Entra app registrations resolved, and who owns each decision?
- 4What is the coexistence design, and what is the plan to dismantle it?
- 5Are mailboxes, OneDrive, SharePoint, Teams, Power Platform and Power BI all in scope, with a reconciliation report per wave?
- 6How are sensitivity labels, retention policies and sharing links preserved or remediated during the move?
- 7What does the Day One runbook contain, who signs it, and what is the rollback line?
- 8What is the TSA-exit dependency list, and what evidence proves the seller's tenant is no longer needed?
- 9Which regulated-industry controls apply (HIPAA, FINRA and SEC, FedRAMP, CMMC, FERPA) and how are they evidenced through the move?
- 10Who is the named senior architect on the statement of work, and are there contracted records for comparable moves?
A partner who cannot answer the first, seventh and eighth questions in writing is selling a migration, not a consolidation.
Participants, duration, prerequisites
An executive sponsor on the acquirer's side and a counterpart on the target's; both tenants' Microsoft 365 and identity administrators; the security and compliance leads; HR and legal for the population and TSA questions; the business-unit leads in Day One scope. EPC Group: one senior architect who leads the program end to end, with migration engineers for the waves.
Six to twelve weeks from discovery to Day One for a mid-size acquisition with one target tenant; waves and TSA exit run to the agreement's end date. Carve-outs, multi-tenant targets and regulated estates are scoped up front, in writing.
The deal calendar; the transition-services agreement or its draft; read-only administrative access to both tenants for discovery; the populations and business units in Day One scope; and the regulatory obligations that travel with the data.
Why EPC Group
- Scale on exactly this work: 216+ M&A tenant migrations covering 1.83 million users between 2023 and 2025, on top of 6,500+ SharePoint implementations and 11,000+ enterprise engagements since 1997.
- The whole estate, not just mail and files — Teams history, Power Platform and Power BI move with owners, labels and reconciliation reports.
- Microsoft Solutions Partner holding all six designations, including Modern Work and Security.
- G2 Leader — seven consecutive quarters (4.4/5 on G2).
- Contracted records in the Evidence Center for university, court and enterprise consolidations.
- Senior architect on every statement of work — the person who scopes the program leads it through TSA exit.
Frequently Asked Questions
What is Microsoft 365 tenant consolidation for M&A?
The program that brings an acquired company's Microsoft 365 tenant — identities, mail, files, Teams, Power Platform, Power BI and the policies around them — into the acquirer's tenant (or, in a divestiture, out of it) on the deal's calendar: discovery on both sides, an identity decision, a coexistence design for the months in between, data movement in waves, a Day One runbook and a transition-services-agreement exit. EPC Group has completed 216+ M&A tenant migrations covering 1.83 million users between 2023 and 2025.
How is this different from a standard tenant-to-tenant migration?
Three things: the calendar is set by the deal, not by IT; two organizations with different security postures, policies and habits have to coexist before they merge; and there is a hard stop — the transition-services agreement — after which the seller's tenant is gone whether or not the work is done. Standard migrations optimize for minimal disruption; M&A consolidations optimize for a defensible Day One and a clean TSA exit, and accept more disruption to get there.
What happens on Day One?
Identity, mail and Teams for the populations the business has named: acquired users sign in, receive mail on the acquirer's domain, see the shared address list and can meet and chat across the combined organization. Content — SharePoint sites, OneDrive, Teams files and history, Power Platform and Power BI — follows in waves under coexistence. The Day One runbook the business signs says exactly which populations, what works, what waits, and where the rollback line is.
How do you handle identity when both companies run Entra ID?
By deciding the target model first — single tenant, hybrid with one or two directories, or B2B coexistence during transition — then matching objects, mapping attributes, sequencing UPN and domain cut-overs, aligning Conditional Access and MFA so posture does not drop, and cleaning privileged roles on the acquired tenant before it is trusted. Identity is the decision everything else waits on, which is why it is phase two, not phase five.
What is coexistence and how long does it last?
The period when both tenants are live and users on each need to work with the other: cross-tenant free/busy and mail routing, a combined address list, Teams external access and cross-tenant chat, B2B guests for shared workspaces, and label and DLP behavior that stays effective across the boundary. It lasts as long as the waves take — weeks to months — and it is designed from the start to be dismantled at TSA exit, because coexistence that becomes permanent is the most expensive outcome of all.
What about Teams chat history, Power Platform and Power BI?
They are in scope and they are the parts most migration-only vendors leave behind. Teams channels, files and chat history move with the tools that support them; Power Platform environments, solutions, connections and DLP policies are rebuilt or migrated as solutions with owners reassigned; Power BI workspaces, semantic models, gateways and row-level security are migrated with the capacity and licensing decisions made explicitly. Each gets a reconciliation report per wave.
How do you handle regulated industries?
The controls travel with the data: sensitivity labels and retention preserved or re-applied, eDiscovery holds honored across the move, audit trails kept, FERPA, HIPAA, FINRA and SEC, FedRAMP or CMMC obligations mapped to the target tenant before the first wave. Higher-education and public-sector consolidations — see the Tarleton State and Prairie View A&M records — carry FERPA and state requirements; the Superior Court of California, County of Amador records show the same discipline in a court environment.
What does the engagement cost and how long does it take?
Fixed-scope, priced after a scoping call that confirms both tenants' size, the identity model and the deal calendar; there is no rate card, and Microsoft licensing is quoted at list. Duration follows the deal: six to twelve weeks from discovery to Day One for a mid-size acquisition with a single target tenant, with waves and TSA exit running to the agreement's end date. Multi-tenant or carve-out programs are scoped up front.
Can you show contracted records for comparable work?
Yes. The EPC Group Evidence Center publishes redacted primary-source records — purchase orders, statements of work, countersignatures — including the Tarleton State University Office 365 cross-tenant migration (2021), the Prairie View A&M University Google Workspace to Microsoft 365 migration (2020) and the Superior Court of California, County of Amador Exchange and Microsoft 365 migrations (2024, 2026). They are engagement records, not endorsements. The firm's M&A figures — 216+ tenant migrations, 1.83 million users, 2023–2025 — are the registry figures every EPC page renders.
What do you need from us to start?
The deal calendar; an executive sponsor on the acquirer's side and a counterpart on the target's; read-only administrative access to both tenants for discovery; the transition-services agreement or its draft; and the business units in Day One scope. The scoping call turns that into a written scope, a participant list and the first two weeks.
Related EPC Group services and references
Book the scoping call
Thirty minutes with the architect who will lead the consolidation. Bring the deal calendar and the transition-services agreement; you leave with the phase plan against those dates and a straight answer on what Day One can and cannot include.
Related reading
- EPC Group Pioneers M&A Cloud Consolidation with Secure, AI-Driven Tenant Migrations
- Multi-Tenant Microsoft 365 Consolidation: Merging Tenants Without Breaking Anything
- Tenant-to-Tenant Migration: The Enterprise Guide for Mergers, Acquisitions & Divestitures
- How to Get Data from a Power BI Dataset via an API
- Key Differentiators Between Data Lakes and Data Warehouses: Which One Is Best for You?