Microsoft 365 tenant-to-tenant migration is one of the most complex enterprise scenarios. Whether you're consolidating tenants after a merger, divesting a business unit, or reorganizing your corporate structure — this guide walks you through every step, every gotcha, and how to get it done with zero data loss.
When Do You Need Tenant-to-Tenant Migration?
Mergers & Acquisitions
Consolidating two separate Microsoft 365 tenants into a single unified environment after company acquisition or merger.
Divestitures & Spin-offs
Separating business units or subsidiaries into their own independent Microsoft 365 tenant environment.
Tenant Consolidation
Merging multiple regional or departmental tenants into a single global Microsoft 365 environment for better management.
If your Microsoft 365 was purchased through GoDaddy, you need defederation — not a standard tenant migration. It's faster and preserves all your data. Read the GoDaddy defederation guide →
What Gets Migrated in Tenant-to-Tenant Migrations?
Exchange Online
Mailboxes, emails, calendars, contacts, tasks, notes, shared mailboxes, distribution lists
OneDrive for Business
Personal files, folder structures, sharing permissions, version history
SharePoint Online
Sites, document libraries, lists, permissions, workflows, metadata
Microsoft Teams
Teams, channels, chat history, files, tabs, connectors (requires specialist tools)
Groups & Distribution Lists
Microsoft 365 Groups, security groups, mail-enabled groups, memberships
User Identities
Active Directory sync, user profiles, licenses, security settings
Security & Compliance
Retention policies, DLP policies, sensitivity labels, compliance records
Third-Party Apps
App registrations, service principals, API permissions (requires reconfiguration)
Have questions about this topic?
Our migration specialists can help. Chat live or request a free consultation.
Complete Tenant-to-Tenant Migration Process
Discovery & Assessment
1–3 daysUnderstand the scope and complexity of your migration before a single mailbox moves.
- Inventory source tenant — total users, mailbox sizes, OneDrive data, SharePoint sites, Teams channels
- Identify dependencies — third-party integrations, custom apps, Power Automate flows, workflows
- Map org structure — departments, security groups, distribution lists, shared mailboxes
- Document configurations — mail flow rules, retention policies, DLP, sensitivity labels
- Review licensing — confirm target tenant has sufficient M365 licenses for all users
Target Tenant Preparation
1–2 daysConfigure the destination tenant before any data moves.
- Create user accounts in target tenant (matching source UPNs)
- Assign appropriate Microsoft 365 licenses to all users
- Set up mail routing connectors for coexistence period
- Recreate security groups and distribution lists
- Configure retention, compliance, and DLP policies to match source
- Verify domain ownership in target tenant admin center
Data Migration Execution
4–12 daysMigrate mailboxes, files, and collaboration data in controlled waves.
- Pilot migration — migrate 5–10 test users first; validate email flow, OneDrive access, Teams
- Batch migrations — migrate in waves by department or location to minimize disruption
- Delta sync — continuously sync changes from source to target until final cutover
- Final cutover — update DNS records, decommission source access, verify everything
Tools note: Migration tools: Use Microsoft native tools (PowerShell, SharePoint Migration Tool) or third-party platforms like BitTitan MigrationWiz, AvePoint FLY, or Quest On Demand Migration.
Coexistence & Mail Routing
Ongoing throughout migrationEnable seamless communication between source and target tenants while migration runs.
- Mail flow connectors — route email transparently between both tenants
- Free/busy sharing — calendar availability visible across tenants during migration
- Organization relationships — allow cross-tenant resource sharing
- Remote mailbox setup — transparent access to already-migrated mailboxes
Post-Migration Activities
1–2 weeksVerify, clean up, and hand off a fully operational environment.
- Update DNS MX records — point to target tenant for final email delivery
- Reconfigure applications — update all third-party app connections and OAuth tokens
- Mobile device setup — users reconfigure Outlook, Teams on phones and tablets
- Validation testing — verify email flow, file access, Teams, SharePoint end-to-end
- Decommission source — after 30–90 day retention period, retire the old tenant
Common Challenges in Tenant-to-Tenant Migrations
No Native Microsoft Migration Tool
The problem: Unlike standard email migrations, Microsoft provides no built-in tool for tenant-to-tenant moves.
Our solution: Use third-party migration platforms — BitTitan MigrationWiz, AvePoint FLY, or Quest On Demand Migration. We partner with all three for seamless end-to-end delivery.
Microsoft Teams Migration Complexity
The problem: Teams channels, tabs, apps, and especially chat history are notoriously difficult — Microsoft's native tools don't move them.
Our solution: Use specialist Teams migration tools and plan for chat history separately. Some organizations archive old Teams data and start fresh — we help you decide which approach fits your needs.
SharePoint Permission Preservation
The problem: SharePoint and OneDrive permissions reference user identities, which differ between tenants — they don't auto-map.
Our solution: Build a user mapping file linking source to target tenant users. Migration tools use this to correctly reassign all permissions, preserving your full security model.
Cutover Downtime Risk
The problem: Final cutover requires DNS updates and credential changes, creating a brief window of disruption.
Our solution: Schedule cutover during off-hours with pre-communicated user instructions. Delta sync minimizes the final migration window to minutes — not hours.
Third-Party App Reconnection
The problem: Every integrated app (Salesforce, Zoom, DocuSign, Power Automate) is tied to the source tenant and must be re-authorized.
Our solution: Document all app registrations in the assessment phase. We create a reconnection runbook so every integration is re-enabled in order, without missing critical workflows.
Migration Timeline & Investment
Typical Timeline
Migration Investment
Want an exact number? Use our interactive migration cost calculator to get a per-user estimate for your tenant-to-tenant project in seconds.
Frequently Asked Questions
A typical Microsoft 365 tenant-to-tenant migration for small to mid-sized organizations takes 1–3 weeks end-to-end. Discovery and planning takes 1–3 days, target tenant setup 1–2 days, pilot migration 1–2 days, full migration waves 4–12 days, and stabilization 1–2 weeks. Larger enterprise migrations with 500+ users may take 4–8 weeks depending on complexity and data volume.
Email addresses typically stay the same if you're using the same domain. The underlying User Principal Name (UPN) and mailbox location change to the new tenant, and users will need to reconfigure Outlook and mobile devices once — but their email address stays consistent for all external communication.
Teams chat history migration requires specialized third-party tools — native Microsoft tools don't move it. Most organizations use BitTitan, AvePoint, or Quest to migrate Teams channels, files, tabs, and chat history. Some prefer to archive old Teams data and start fresh in the new tenant.
Coexistence is enabled through mail flow connectors, free/busy calendar sharing, organization relationships, and remote mailbox setup. This lets source and target tenant users email each other, see calendar availability, and access shared resources throughout the migration period — which typically lasts 4–12 weeks.
Small businesses (10–50 users) typically pay $500–$2,500 including tool licensing and support. Mid-market companies (51–500 users) are priced around $50 per user, covering full-service migration with project management. Enterprise organizations (500+ users) should contact us directly for a custom quote based on scope and complexity.
Yes, with proper user mapping. SharePoint and OneDrive permissions reference user identities, which change between tenants. The solution is to create a user mapping file linking source to target users — migration tools use this to correctly reassign all permissions in the new tenant.
Planning a Tenant-to-Tenant Migration?
We've successfully migrated hundreds of organizations through mergers, acquisitions, and restructuring — with zero data loss.
Get a Free Migration Quote
No spam, just expert advice.
Related Articles
Ready to Start Your Tenant Migration?
Workspace Migration specialises in complex Microsoft 365 tenant consolidations. We've successfully migrated hundreds of organizations through mergers, acquisitions, and restructuring — zero data loss, minimal disruption, delivered on time.