Tenant Migration
What is Tenant Migration?
A tenant migration is the process of moving an organization’s Microsoft 365 (or similar cloud platform) data, users, configurations, and services from one cloud tenant to another. This is required in scenarios including company mergers and acquisitions where separate tenants must be consolidated, carve-outs or divestitures where a portion of an organization is separated into its own tenant, rebranding scenarios that require a new primary domain, and situations where an existing tenant has accumulated so many legacy issues that a clean-slate migration is more practical than remediation in place.
Tenant migrations are among the most complex Microsoft 365 projects an IT team can undertake because they involve moving every user’s email history, calendar, contacts, OneDrive files, Teams data, SharePoint content, and application configurations simultaneously while keeping business operations running continuously throughout the migration period.
What Is Migrated in a Tenant Migration
- Exchange Online: mailboxes, calendar items, contacts, shared mailboxes, distribution groups, and mail flow settings
- OneDrive for Business: user files and folder structures with permissions
- SharePoint Online: site collections, document libraries, pages, and permissions
- Microsoft Teams: teams, channels, chat history, and associated SharePoint sites
- Microsoft Entra ID: user accounts, groups, conditional access policies, and app registrations
- Microsoft 365 applications and licenses: re-provisioning and configuration of all M365 applications in the destination tenant
Key Phases of a Tenant Migration
Discovery and Planning
Inventory all content, users, groups, and configurations in the source tenant; mapping them to the destination tenant structure; identifying dependencies and complexity; and establishing the migration sequence, tools, and cutover timeline.
Configuration and Coexistence
Setting up the destination tenant with required domains, licenses, security policies, and user accounts. Establishing coexistence configurations that allow source and destination tenant users to communicate and collaborate during the migration period.
Phased Migration Execution
Migrating content in waves, typically prioritizing specific business units, departments, or data types. Phased migration reduces the risk of a single large failure and allows lessons from early waves to improve subsequent migrations.
Cutover and Decommission
Final DNS changes, client reconfiguration, and decommissioning of the source tenant once all migration waves are complete and validated.
Key Takeaways
- Tenant migration moves users, data, and configurations between Microsoft 365 tenants, typically triggered by M&A, divestitures, or rebranding.
- Migrated content includes Exchange mailboxes, OneDrive, SharePoint, Teams data, Entra ID objects, and application configurations.
- Tenant migrations are complex, high-risk projects that require detailed planning, phased execution, and coexistence configuration.
- Phased migration by user group reduces risk and allows early-wave learnings to improve subsequent migrations.
- Specialized migration tooling (such as BitTitan MigrationWiz or Quest on Demand Migration) is typically required for large-scale tenant migrations.