Skip to content

Migration

What is tenant-to-tenant migration?

By Suresh Girinathuni

Quick answer

Tenant-to-tenant migration relocates workloads between Microsoft 365 tenants: Exchange mailboxes, SharePoint sites, Teams and chats, OneDrive accounts, and often domain names and identity configuration. Drivers are mergers, acquisitions, divestitures, and tenant consolidations. The work is dominated by identity mapping, domain moves, Teams chat fidelity limits, permission remapping, and staged coexistence — the file copy is the easy part.

Key takeaways

  • M&A-driven moves of mail, files, Teams, identity, and domains.
  • Identity mapping and coexistence dominate the plan.
  • Chat fidelity and permissions need expectation-setting early.

Detailed Explanation

Tenant-to-tenant migration relocates workloads between Microsoft 365 tenants: Exchange mailboxes, SharePoint sites, Teams and chats, OneDrive accounts, and often domain names and identity configuration. Drivers are mergers, acquisitions, divestitures, and tenant consolidations. The work is dominated by identity mapping, domain moves, Teams chat fidelity limits, permission remapping, and staged coexistence — the file copy is the easy part.

How it works

Both tenants coexist during the program: mail routes between them, identity objects are matched or recreated through mapping tables, and each workload moves in waves with delta passes catching stragglers. Domains transfer last because mail flow follows the domain — cutover is a routing and DNS event more than a copy event.

Limitations and considerations

Teams chat history, permissions fidelity, and app registrations migrate imperfectly — inventory these early and set stakeholder expectations before committing dates. Coexistence mail flow and domain transfer windows need explicit sequencing.

For broader context, see the Migration Hub — it collects the guides around this topic.

When to use it

Plan tenant-to-tenant as a program with identity, messaging, collaboration, and change-management tracks — never as a lift-and-shift weekend.

Practical example

An acquired 300-person company migrates mailboxes first with coexistence, then SharePoint and Teams in dated waves, transferring the domain last after validation sign-off per workload.

Related Questions

What is Microsoft 365 migration?Microsoft 365 migration moves users, documents, collaboration workloads, and related configuration into Microsoft 365 services.What should I check before a Microsoft 365 migration?Check eight things before moving data: source inventory, permissions and sharing, file/path restrictions, ownership, target information architecture, security and retention needs, migration tooling plus pilot scope, and communication with a validation plan.How long does a SharePoint migration take?There is no universal duration: a small library moves in days while enterprise programs run weeks to months. Data volume, item count, versions, permissions, remediation, throttling, and validation depth set the timeline — not copy speed alone.What is ShareGate?ShareGate is a third-party Microsoft 365 migration and administration product, popular for SharePoint and Teams moves, pre-migration assessment, reporting, and ongoing management tasks.

Related nxtM365 Guides

MigrationExchange Online Migration Step-by-Step GuideA practical Exchange Online migration guide covering mailbox inventory, identity, licensing, DNS, mail flow, pilot batches, cutover, validation, and post-migration support.MigrationSharePoint Online Migration Step-by-Step GuideA practical SharePoint Online migration guide covering site inventory, cleanup, information architecture, permissions, migration tools, pilot waves, validation, governance, and user adoption.

Sources