Splitting a Microsoft 365 Tenant After a Divestiture or Carve-Out: The Reverse of a Merger, and the Six Things That Make It Harder

In a merger, the acquired tenant is a source that will be switched off: everything is in scope, and when the last mailbox moves the old tenant is abandoned. Tenant-to-Tenant Migration After a Merger covers that direction.

In a divestiture, scope is a line drawn through a working tenant. The SharePoint site the sales team shared with the unit has files on both sides of the line, the Team where they planned launches has channels for both, and the support@ shared mailbox is used by both. Each is a decision: copy, split, or one side loses it.

The seller keeps obligations too. Litigation holds, retention policies and audit history apply to data the buyer now wants; Microsoft's cross-tenant migration will not move a mailbox on hold, and nothing moves audit logs. The seller releases, exports or keeps, and the sale agreement usually says which.

The new tenant needs to exist weeks before the first user moves. Decide the tenant name, the data residency region, the billing relationship and the first administrators, and give the new company a tenant it owns from day one.

Baseline it before data arrives: Conditional Access and MFA, Intune enrollment, DLP and retention that match what the seller had, and the domains it will keep. Then license it, which is where NCE bites.

Annual subscriptions bought through a Cloud Solution Provider cannot be reduced mid-term: under Microsoft's Partner Center rule, a license count can be decreased only within seven days of the order or of adding licenses, and after that it stays until renewal. So when 80 of 300 users leave in month four, the seller pays for 300 until renewal while the buyer buys 80 new licenses.

Three ways to soften it: put the split's timing next to the renewal date in the negotiation; use monthly-term subscriptions for the replacements where the higher monthly price is acceptable (Microsoft NCE Explained covers the terms); and plan the seller's reduction at renewal with License Cleanup Before Renewal so the leavers and the unassigned seats come off in one window.

Microsoft's own tools add a one-time Cross-tenant User Data Migration license per user for mailbox and OneDrive moves, assignable on the source or the target user, with no exceptions. Cross-tenant SharePoint site migration uses a separate Cross-Tenant Shared Data Migration license priced per 100 GB moved, available only to Enterprise Agreement customers per Microsoft, so for a CSP customer the sites move with migration tooling.

A custom domain can be verified in only one Microsoft 365 tenant at a time, and that rule shapes the whole split.

If the divested unit has its own domain, the domain moves: every address under it is removed or rewritten in the seller's tenant, the domain is removed and verified in the buyer's tenant, and the addresses are recreated there. Inbound mail for that domain is down between the removal and the new MX going live; The Domain Cutover in a Tenant-to-Tenant Migration explains the window and how an MX spooler keeps mail queued through it.

If the unit shares the parent's domain, the domain stays with the seller and the leaving users get new addresses in the buyer's domain. The seller forwards or auto-replies on the old addresses for the transition period, and the buyer's users update signatures, listings and customers.

1. Shared SharePoint sites and Teams. A site with members on both sides cannot be split by a tool. The buyer's folders are copied to the new tenant and the site is pruned so each side keeps what it owns; Teams with channels for both sides are the same problem.

2. Teams itself. Microsoft's cross-tenant features do not move teams and channels. Its orchestrated user data migration, in public preview at the time of writing, moves a user's personal and group chats with the mailbox and OneDrive; teams, channels and their files are out of scope. Channel files move with migration tooling; channel conversations are usually exported.

3. Holds and eDiscovery. A mailbox on any type of hold is blocked from cross-tenant migration. Legal decides, per custodian, whether the hold is released before the move or the person moves with a copy and the original stays.

4. Audit logs and retention. Audit history stays with the tenant where it was generated; nothing migrates it. Retention policies and labels are tenant-specific and do not migrate with the mailbox. The buyer starts with a blank audit log, so anything it needs to prove about the past is exported first. If Your Tenant Were Breached, What Could You Prove? is about that evidence.

5. Devices and applications. Intune-managed devices belong to one tenant; a leaving user's laptop is unenrolled from the seller and re-enrolled in the buyer, one rebuild per device. App registrations, Power Automate flows and third-party integrations are recreated, not moved. Entra joined device tenant-to-tenant migration covers the device path.

6. The transition services agreement clock. A TSA gives the buyer a defined period of access to the seller's systems and the seller a defined period of exposure. Both want it short, and the migration, domain cutover and device re-enrollment have to fit inside it.

Between the legal split and the last mailbox move, the two tenants must work together without becoming one.

• Cross-tenant synchronization in Entra ID creates the other tenant's users as B2B collaboration users automatically. Each synchronized user needs a Microsoft Entra ID P1 license in their home tenant; Business Premium and Microsoft 365 E3 include it, and Microsoft Entra ID P1 on its own is $84.00 per user per year (Microsoft list price, September 2026 price list, annual commitment).
• Cross-tenant access settings decide what the other tenant's users can reach and whether their MFA is trusted.
• Shared channels in Teams let a project run across the line without duplicating the team.
• Guest access, with expiry dates, to the specific sites the buyer still needs; Guest and External Users in Microsoft 365 covers the licensing.

All of it is timeboxed to the TSA and removed at the end, with the exit planned from day one.

1. Inventory by the line: users, mailboxes and holds, OneDrives, sites, teams, shared mailboxes, groups, devices, applications and domains.
2. New tenant stood up, baselined and licensed.
3. Identity: users created in the buyer's tenant, with cross-tenant sync and access settings for coexistence.
4. Data: mailboxes with the Microsoft license, OneDrives, SharePoint sites, then Teams, with holds and audit exports resolved before each wave.
5. Domain cutover if the unit takes its domain, with the spooler in place; otherwise address changes and forwarding.
6. Devices re-enrolled, applications recreated, integrations repointed.
7. Seller cleanup: leaving users disabled or converted to shared mailboxes per policy, guests removed at TSA end, licenses reduced at renewal.

Our services map to steps 3 to 6: Entra ID Tenant-to-Tenant Basic Transition at $1,300; Microsoft 365 Tenant-to-Tenant Cutover Email Migration at $35 per mailbox plus a $3,500 tenant fee; SharePoint Online Tenant-to-Tenant Migration at $100 per site plus a $2,500 tenant fee; OneDrive Tenant-to-Tenant Migration at $10 per user plus a $1,500 tenant fee; and Microsoft Teams Tenant-to-Tenant Migration at a $3,500 tenant fee plus a fee per team.

Can two Microsoft 365 tenants share one domain during a divestiture?

No. A domain is verified in one tenant at a time. Either the domain moves with the unit, behind an MX spooler, or it stays with the seller and the leavers get new addresses with forwarding.

Can we reduce our Microsoft 365 licenses when part of the company leaves?

Not mid-term on an annual subscription. Under NCE the count can be reduced only within seven days of ordering or adding licenses; otherwise it changes at renewal.

Do audit logs move to the new tenant?

No. Audit history stays with the tenant that generated it, and retention policies do not migrate either; export what the buyer will need before the users move.

Can Microsoft Teams be migrated to another tenant?

Not with Microsoft's own cross-tenant features, which exclude teams and channels. Its orchestrated migration, in public preview, covers a user's chats; teams and channels move with migration tooling.

• Microsoft Learn, MicrosoftDocs source files opened on 27 September 2026: "Cross-tenant mailbox migration" (ms.date 28 September 2025): per-user one-time license on source or target, audit logs and retention policies not migrated, mailboxes on hold blocked; "Cross-tenant SharePoint site migration overview" (14 August 2025): Cross-Tenant Shared Data Migration licenses per 100 GB, Enterprise Agreement customers only, Teams content and channels excluded; "What is cross-tenant synchronization in Microsoft Entra ID?" (29 May 2026): P1 per synchronized user
• Microsoft Tech Community, "Public Preview: Cross-tenant Orchestrated User Data Migration" (preview, chats in scope, teams and channels out); Partner Center "Create customer subscriptions" (seven-day reduction window); Microsoft Q&A (one domain, one tenant). Not opened; as reported by search excerpts on 27 September 2026; verify on Microsoft Learn.
• IT Partner blog articles linked above
• IT Partner price sheet, Commercial segment, September 2026 US price list; IT Partner service pages and engineering notes, September 2026