Carve-Out Microsoft 365 Tenant Migration: TSA Exit, Clean Separation, Day-1 Independence
Standalone Microsoft 365 tenant standup for divested business units. Identity de-provisioning, content separation, regulatory baseline maintained, TSA exit in 60-120 days.
Carve-out engagements are a sub-practice of EPC Group's M&A Microsoft 365 tenant migration practice. Across 216+ M&A engagements completed between 2023 and 2025, carve-outs and divestitures represent a significant share of the work. The four-phase carve-out playbook compresses standalone tenant standup into a 60-120 day execution window with a 5-day cutover average.
Why Carve-Out Migrations Are Different From Standard M&A Migrations
A standard M&A migration consolidates two or more source tenants into one destination tenant. A carve-out goes the other direction: it pulls a business unit out of an existing parent tenant and builds a complete standalone Microsoft 365 environment for it. The destination tenant doesn't exist on Day 1 of the engagement — it has to be built from scratch while the source tenant remains operational.
Transition Services Agreements (TSAs) typically grant 60-180 days of continued access to the parent tenant after deal close. TSA expiration is a contractual deadline, not a target. If the standalone tenant isn't ready on TSA exit day, the divested entity loses access to its own users, email, files, and collaboration tools. There is no extension by default.
The EPC Group carve-out playbook is built around this constraint — four compressed phases (Separate, Isolate, Cutover, Stabilize) with parallel workstreams, pre-close diligence support, and TSA Exit Confirmation as the contractual deliverable.
The Carve-Out Microsoft 365 Migration Playbook
A four-phase methodology optimized for TSA exit deadlines.
Separate
Weeks 1-2
Source-tenant inventory of carve-out scope. Identity isolation plan. Content extraction plan. TSA scope and exit milestones documented. Pre-close diligence support where the deal team needs visibility before close.
Named Artifacts
Isolate
Weeks 3-6
New destination tenant standup. Identity de-provisioning from parent. Content extraction. Regulatory baseline re-established in the new tenant. Microsoft Purview labels, Conditional Access, and DLP policies rebuilt from carve-out scope.
Named Artifacts
Cutover
5-day average execution window
Identity transition. Email and collaboration cutover. SharePoint, OneDrive, and Microsoft Teams content live in destination tenant. End-user enablement. Hypercare period begins immediately.
Named Artifacts
Stabilize
Weeks 7-12
Hypercare with daily reporting for the first 14 days. TSA exit confirmation. Defect closure. Adoption measurement. Optional continuation under a Managed Microsoft Cloud and Analytics retainer.
Named Artifacts
Senior-Architect Bench Standard
Every carve-out engagement 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.
Carve-outs come with TSA deadlines and reduced operational visibility — the buyer and the divested entity often have no shared institutional knowledge of the parent tenant configuration. A senior architect on day one is non-negotiable.
Frequently Asked Questions
- What is a carve-out Microsoft 365 tenant migration?
- A carve-out Microsoft 365 tenant migration is a divestiture from a parent tenant into a new standalone destination tenant. It applies when a business unit is being spun off, sold to a third party, taken private, or otherwise separated from the parent organization. Unlike a consolidation migration, the carve-out requires building a complete standalone Microsoft 365 environment in 60-120 days while preserving compliance posture and meeting TSA expiration deadlines.
- How does EPC Group handle TSA expiration timelines for carve-out scenarios?
- Transition Services Agreements (TSAs) define how long the divested entity can keep using the parent's Microsoft 365 tenant after deal close. TSA expiration dates are non-negotiable. EPC Group runs pre-close diligence in parallel with deal-team work so Day-1 readiness lands before the TSA window closes. Typical carve-out execution is 60-120 days. Pre-close diligence support is available 30-45 days in advance when needed.
- What happens to shared content between the parent and the divested business unit?
- Shared content is categorized during the Separate phase into three buckets: content that moves with the carve-out (owned data, customer records, IP), content that stays with the parent (corporate functions, non-divested business records), and dual-residency content (governance documents, HR records under legal retention). Each category has a different extraction methodology. The Tooling Decision Record names AvePoint Fly, ShareGate, or Quest as the extraction engine based on permission fidelity needs.
- How is identity de-provisioning handled in a carve-out?
- Identity isolation runs across four layers: Active Directory accounts are exported and stood up in the new destination Entra ID tenant, group memberships are scoped to carve-out users only, license SKUs are reclaimed from the parent and assigned in the new tenant, and Conditional Access policies are rebuilt with carve-out-specific named locations and device trust. Cross-tenant access is permitted only during the cutover window. Final de-provisioning from the parent happens at TSA exit, not before.
- How does EPC Group preserve compliance posture during a carve-out?
- The Diligence phase establishes the regulatory baseline appropriate to the divested entity — HIPAA, FedRAMP, SOC 2, FINRA, CMMC, or GxP. Microsoft Purview sensitivity labels, retention policies, eDiscovery configuration, and Microsoft Defender alerting are rebuilt in the destination tenant before content lands. Compliance is re-validated at cutover. Named artifacts produced during the migration form the audit trail used by the divested entity's compliance team post-carve-out.
- What Microsoft 365 workloads are migrated during a carve-out?
- All Microsoft 365 workloads: Exchange Online, OneDrive for Business, SharePoint Online, Microsoft Teams (including private channels, shared channels, and Planner data), Power BI (workspaces, datasets, semantic models), Power Platform (Power Apps, Power Automate, Power Pages, Copilot Studio), Microsoft Purview (sensitivity labels, retention, eDiscovery), Microsoft Entra ID, Microsoft Defender, Microsoft Intune, Microsoft Viva, and Microsoft Copilot deployment readiness.
- How long does a typical carve-out migration take?
- Standard carve-out execution is 60-120 days from kickoff to TSA exit. Mid-market carve-outs (1,000-5,000 users) typically land at 60-90 days. Enterprise carve-outs (5,000-25,000+ users) typically land at 90-120 days. Cutover execution within that window averages 5 days. Pre-close compressed engagements can deliver Day-1 readiness in 30-45 days when EPC Group is engaged during diligence.
- What is the pricing model for carve-out engagements?
- Fixed-fee Statements of Work scoped during the Diligence phase. Pricing depends on user count, workload mix, identity complexity, tooling stack, and TSA timeline. Mid-market carve-outs typically range from $50,000 to $250,000. Enterprise carve-outs typically range from $250,000 to $1,500,000+. Post-carve-out Managed Microsoft Cloud and Analytics retainers range from $6,500 to $35,000 per month for the new standalone entity.
- Can EPC Group support pre-close carve-out diligence?
- Yes. Pre-close diligence support is one of the most common engagement entry points. The deal team brings EPC Group in 30-45 days before close to deliver source tenant audit, carve-out scope definition, identity isolation plan, TSA exit plan, and Day-1 readiness gap analysis. Parallel workstreams mean execution can start the day after close instead of starting from a cold-state inventory exercise.
- How do I start a carve-out Microsoft 365 migration 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 playbook phase plan, the tooling decision, and the fixed-fee anchor.
Start a Carve-Out Microsoft 365 Migration Engagement
Pre-close diligence support, TSA exit planning, standalone tenant standup, identity de-provisioning, content separation.
Or email contact@epcgroup.net