Tenant-to-tenant migrations in Microsoft 365 are among the most complex IT projects an enterprise can undertake. Done wrong, they result in lost emails, broken calendar delegation and weeks of user confusion. This guide covers the proven approach we use for zero-data-loss migrations.
1 Understanding the Challenge
M365 tenants are isolated environments. Unlike on-premises Exchange, there is no built-in cross-tenant sync. You must migrate mailboxes, calendars, contacts, OneDrive files, SharePoint sites, Teams and M365 Groups — each with different tools and timelines. Add in UPN changes, email domain cutovers and coexistence requirements and the complexity multiplies quickly.
2 Pre-Migration Assessment
Before moving a single mailbox: audit mailbox sizes and item counts, identify shared mailboxes, resource mailboxes and distribution groups, map all SharePoint sites and OneDrive shares, document Teams with their channels and private channels, identify external sharing dependencies, and document MFA, conditional access and compliance policies that must be recreated.
3 Tool Selection
For large enterprises (500+ mailboxes): BitTitan MigrationWiz is the industry standard. It handles coexistence, calendar free/busy sync and supports batched migrations with rollback. Microsoft's own Cross-Tenant Mailbox Migration (CTMM) is now generally available and handles mailbox data without third-party licensing costs but requires PowerShell expertise. For SharePoint and Teams: ShareGate is the preferred tool for content migration with metadata preservation.
4 Coexistence Setup
During migration, both tenants must be able to route email and calendar to each other. Set up inbound connectors, SPF/DKIM for both domains, and cross-tenant free/busy sharing via Organisation Relationships. Users need to resolve each other's calendar availability. If you skip coexistence, calendar invitations break and users cannot see availability for colleagues mid-migration.
5 Domain Cutover Strategy
Domain cutover is the highest-risk step. Plan for a weekend window. Remove the domain from the source tenant (requires removing it from all users first), add it to the destination tenant, update MX, SPF, DKIM and DMARC DNS records, and verify mail flow. We recommend a 48-hour DNS TTL reduction before cutover to speed up propagation. Have a rollback plan for every step.