How does a Microsoft 365 tenant-to-tenant migration work for Teams, SharePoint and mail?

How a tenant-to-tenant migration is sequenced

A Microsoft 365 tenant-to-tenant migration moves people, mail, files and conversations from one tenant to another after a merger, acquisition, divestiture or consolidation. Microsoft documents two native approaches: an orchestrated migration that moves mailboxes, OneDrive, Teams chats and Teams meetings together in coordinated batches, and individual cross-tenant tools for mailbox, OneDrive and SharePoint when each workload needs its own timeline, with partner or third-party tools for complex cases (Microsoft Learn, Plan a Microsoft 365 tenant-to-tenant migration, accessed 2026-10-20). EPC Group, a Houston-based Microsoft consulting firm, runs these migrations in a fixed order because each workload depends on the one before it: identity first, then mail, then OneDrive and SharePoint, then Teams, then the domain. Changing that order is the usual cause of a cutover weekend that runs into Tuesday.

Step 1: identity, the part the tools do not do

Microsoft is explicit that its migration tooling moves content, not identities. The customer is responsible for creating and configuring users in the target tenant, and every workload then reads a one-to-one identity map of source users and groups to target users and groups; a source user cannot be mapped to several target users, and any change to the map must be re-uploaded in full (Microsoft Learn, An overview of tenant-to-tenant migration with orchestrator in Microsoft 365, accessed 2026-10-20; Step 5: SharePoint Identity mapping, accessed 2026-10-20). For the months between deal close and cutover, Microsoft Entra cross-tenant synchronization provisions users from one tenant into the other as B2B collaboration users so they can use Teams, SharePoint and shared applications across the boundary while their accounts stay managed at home (Microsoft Learn, What is cross-tenant synchronization?, accessed 2026-10-20). EPC Group's Microsoft 365 consulting practice builds the target accounts, licenses and Conditional Access before any data moves, and schedules the custom domain transfer as its own cutover window because mail routing changes with it.

Step 2: mail with cross-tenant mailbox migration

Cross-tenant mailbox migration lets tenant administrators move Exchange Online mailboxes with familiar tools, Exchange Online PowerShell and the New-MigrationBatch cmdlet. The target user must exist as a MailUser with specific attributes before the move; afterward the source mailbox is converted to a MailUser whose external address points at the destination, which keeps mail routing and coexistence working until the source is cleaned up. Only user-visible content moves, email, contacts, calendar, tasks and notes; the source mailbox is deleted after success and is not recoverable there; mailboxes on any kind of hold are blocked; and a per-user Cross Tenant User Data Migration license must be purchased first or the batch fails with a licensing error (Microsoft Learn, Cross-tenant mailbox migration, accessed 2026-10-20). Microsoft advises batches of no more than 2,000 mailboxes submitted two weeks before cutover, since synchronization has no user impact (same source). Items that do not migrate include public folders, client-side rules, Outlook profiles, send-as and send-on-behalf permissions and mailboxes with more than 12 auxiliary archives (Microsoft Learn, Cross-Tenant Migration, accessed 2026-10-20).

Step 3: OneDrive and SharePoint

Cross-tenant OneDrive migration is a move, not a copy. Two SharePoint administrators establish a trust between tenants, users and groups are precreated, the identity map is uploaded, and each OneDrive is moved with only a few minutes of read-only time and a redirect left at the old location so existing links keep working. Up to 4,000 accounts can be scheduled at a time, incremental or delta passes are not possible, accounts under a hold are blocked until the hold is removed, and the feature is not supported for GCC, GCC High or DoD tenants (Microsoft Learn, Cross-tenant OneDrive migration, accessed 2026-10-20). SharePoint sites follow the same trust and map; users and groups keep their permissions on migrated content if they are in the map, sharing links redirect to the new location, and for group-connected sites the target URL must match the alias of the new Microsoft 365 group or the move fails (Microsoft Learn, Cross-tenant SharePoint migration FAQs, accessed 2026-10-20; Step 5: SharePoint Identity mapping, accessed 2026-10-20). Sensitivity labels are not exported between tenants and must be recreated in the target (Microsoft Learn, Cross-tenant mailbox migration, accessed 2026-10-20). EPC Group's SharePoint consulting practice inventories sites by owner and size, retires what nobody claims, and recreates the label taxonomy before the first site moves.

Step 4: Teams chats, meetings, and what stays behind

Teams is where expectations most often diverge from the tooling. Microsoft's Migration Orchestrator can migrate one-to-one and group chats and Teams meetings in the same batch as mailboxes and OneDrive; the meeting workload depends on a successful mailbox migration and cannot be selected alone. Chats are recreated as new threads in the target while the source copies remain in edited form, duplicate threads can exist on both sides, and meeting URLs are updated for meetings that occurred within the previous 60 days while older meeting chats become new group chats (Microsoft Learn, An overview of tenant-to-tenant migration with orchestrator in Microsoft 365, accessed 2026-10-20; End-user experience, accessed 2026-10-20). Teams and channels themselves, along with SharePoint sites, are shared data that the Cross-Tenant User Data Migration solution does not migrate; they remain in the source tenant (same overview). EPC Group's approach is to rebuild the team structure in the target, move each channel's files as a SharePoint site, and either migrate channel history with partner tooling or preserve it as a searchable archive, a decision made per team with its owner.

What breaks, and how cutover is planned

The predictable breakages are the ones to plan for: send-on-behalf delegates must be re-stamped on target mailboxes after conversion; client-side Outlook rules and profiles are rebuilt by users; labels and retention policies are recreated; meeting links older than 60 days are not updated; and OneDrive redirects last only until the source tenant is deprovisioned (Microsoft Learn, Cross-tenant mailbox migration; Cross-tenant OneDrive migration; both accessed 2026-10-20). EPC Group plans cutover as waves rather than a single event: a pilot wave of a few dozen users across departments exercises every workload end to end, then department waves follow with explicit exit criteria. Each wave has a pre-cutover checklist (licenses, identity map, mailbox batch synced, OneDrive scheduled), a cutover window, and a next-business-day support plan. Timeline is governed by data, not headcount: Microsoft's published estimates for cross-tenant mailbox moves run from one day for mailboxes up to 10 GB to three to six days for 100 to 200 GB, with no support above 200 GB, in the duration table referenced from the cross-tenant mailbox migration FAQ (Microsoft Learn, Cross-tenant mailbox migration, accessed 2026-10-20), so the large-mailbox population sets the wave length.

Documented work

ANON-CASES: EPC Group engagement data in manufacturing and financial services covers mid-size and large organizations consolidating or separating Microsoft 365 tenants after acquisitions and divestitures, delivered by the firm's Microsoft 365 consulting practice. Client names are not published here. Engagements are described by industry and organization size only, and no outcome figures are quoted that cannot be traced to a signed deliverable. EPC Group is a Microsoft Solutions Partner with all six Solutions Partner Designations as of October 2026.

Frequently Asked Questions

Talk to a senior architect

If your organization has a deal closing and two tenants to reconcile, a 30-minute discovery call with a senior EPC Group architect will cover the identity plan, the workload order and a first-pass wave schedule. See the M&A tenant migration service hub for engagement structures.

Email contact@epcgroup.net or call 888-381-9725.

a Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations.