How Does Office 365 Tenant-to-Tenant Migration Work?
A complete tenant migration typically involves four phases: assessment, preparation, execution, and post-cutover validation. Here is what each phase involves:
Phase 1: Pre-Migration Assessment
Before any data moves, you need a clear picture of the source environment. This means auditing the total number of user mailboxes, shared mailboxes, archive folders, OneDrive volumes, SharePoint sites, and Teams channels that need to move.
Key pre-migration tasks include:
- Inventory all source users and map them to destination accounts.
- Verify destination tenant licensing — users need active mailboxes on the target tenant to receive migrated data.
- Register an Azure Active Directory application on both source and destination tenants (you will first need to find microsoft 365 tenant id) and grant the required API permissions (Mail.Read, Mail.ReadWrite, Mailbox.Migration).
- Identify any VIP or executive accounts that need priority migration treatment.
- Review any third-party integrations (CRMs, HR systems, security tools) that connect to the source tenant and will need reconfiguration post-migration.
Phase 2: Migration Preparation and Coexistence Setup
During execution — especially for large organizations migrating in batches — users on the source and destination tenant need to work together without disruption. This period is called coexistence.
Coexistence requires:
- Mail routing between source and destination domains so emails reach the right mailbox during the transition.
- Calendar free/busy sharing so users on both tenants can see each other's availability.
- A Global Address List (GAL) sync so users can find contacts across both tenants during the cutover window.
Poorly configured coexistence is one of the most common causes of business disruption during Office 365 tenant migrations.
Phase 3: Data Migration Execution
This is the phase where data actually moves from the source tenant to the destination. Modern tenant migration tools handle this through a secure, direct tenant-to-tenant connection — no intermediate cloud storage, no routing data through a third-party server.
A well-executed migration will:
- Migrate primary mailboxes, In-Place Archive folders, shared mailboxes, and public folders.
- Preserve folder hierarchy, metadata, read/unread status, and email threading.
- Migrate OneDrive files with permissions and sharing settings intact.
- Transfer SharePoint Online sites including document libraries, permissions, and site structures.
- Move Microsoft Teams personal chats (1:1) and channel conversations with full message history.
- Run delta sync passes — incremental migrations of any new data that arrived during the initial pass — to minimize the cutover window.
Phase 4: Post-Migration Validation and Cutover
After data migration completes, the final phase involves validating data integrity, decommissioning the source tenant or converting source mailboxes to forwarding stubs, and ensuring users can operate normally on the destination tenant.
Post-migration checklist items typically include:
- Verify email, calendar, and Teams functionality for a representative sample of users.
- Update MX records and DNS to route new email to the destination tenant.
- Reconfigure any third-party applications that authenticate against the old tenant.
- Remove or convert source user accounts once migration is confirmed successful.
- Export the migration summary report for compliance and audit purposes.
