A Microsoft 365 tenant-to-tenant migration moves users, mailboxes, OneDrive files, SharePoint sites, Teams and often domains from one Microsoft 365 tenant to another. It is most common after mergers, acquisitions, divestitures and rebrands. Because both environments are live and the same email domain cannot exist in two tenants at once, the project needs careful identity mapping, coexistence planning and a tightly controlled cutover.
Key Takeaways
- A domain can only be verified in one tenant at a time, so domain moves need a planned cutover window.
- Map every source identity to a target identity before moving any data.
- Microsoft offers native cross-tenant mailbox and OneDrive migration options with specific licensing requirements; third-party tools cover broader workloads.
- Coexistence (shared free/busy, GAL sync, mail routing) keeps the business running during the transition.
- Teams chats, Planner, Power Platform and Forms need special attention because they move less cleanly than mail and files.
When Do You Need a Tenant-to-Tenant Migration?
- Mergers and acquisitions: consolidating the acquired company into the parent tenant, ideally planned during an IT due diligence review.
- Divestitures: carving a business unit out into its own new tenant.
- Rebranding: moving to a new tenant with a new primary domain.
- Tenant consolidation: merging multiple regional tenants, for example US and UAE entities, into one.
For broader integration planning, see our M&A IT integration service.
Step 1: Discovery and Scoping
- Inventory users, shared mailboxes, groups, Teams, SharePoint sites and OneDrive accounts in the source tenant.
- Record data volumes per workload.
- Identify domains, apps using Entra ID single sign-on, and devices enrolled in Intune.
- Confirm which workloads are in scope: mail, files, Teams, Planner, Power Automate flows, Power BI.
Step 2: Identity Mapping
Create a mapping file that links each source account to a target account. Decide naming conventions, whether users keep their old email address as an alias, and how licenses will be assigned in the target. Clean identity data prevents broken permissions later.
Step 3: Prepare the Target Tenant
- Create target accounts and assign licenses.
- Apply security baselines: MFA, Conditional Access, and Entra ID hardening.
- Build SharePoint and Teams structures for incoming content.
- Configure the migration tooling and required permissions in both tenants.
Step 4: Coexistence
During a staged migration, users in both tenants still need to email, meet and collaborate. Typical coexistence components include:
- Mail routing between tenants using connectors and temporary domains.
- Global Address List synchronization so users can find each other.
- Calendar free/busy sharing through organization relationships.
- Teams external access or B2B guest access for cross-tenant collaboration.
Step 5: Pre-Stage Data
Copy mailbox content, OneDrive files and SharePoint sites in the background while users keep working. Delta passes reduce the final cutover window.
Step 6: Domain Cutover
| Task | Timing |
|---|---|
| Lower DNS TTL | Several days before cutover |
| Final delta sync | Start of cutover window |
| Remove domain from source tenant | Cutover window |
| Verify domain in target tenant and update UPNs/addresses | Cutover window |
| Update MX, SPF, DKIM, DMARC and Autodiscover | Cutover window |
| User communication and profile reset | Morning after cutover |
Most organizations run the domain cutover over a weekend to limit disruption.
Step 7: Post-Migration
- Re-enroll devices into the target Intune tenant.
- Re-share files where permissions did not translate.
- Rebuild Power Automate flows and Teams apps.
- Decommission or retain the source tenant according to legal and retention requirements.
Common Tenant-to-Tenant Pitfalls
- Underestimating Teams chat and channel migration complexity.
- Forgetting apps and devices that send mail using the old domain.
- Not planning for Outlook profile and OneDrive sync client resets.
- Skipping a pilot because the move “is just Microsoft to Microsoft”.
If you are also budgeting the project, our Microsoft 365 migration cost guide explains the main cost drivers.
How Skytech Enterprise Helps
Skytech Enterprise plans and delivers tenant-to-tenant migrations for organizations in the USA and UAE, including coexistence, domain cutover and security hardening. Book a scoping call.
Frequently Asked Questions
Can two Microsoft 365 tenants use the same domain at once?
No. A domain can be verified in only one tenant at a time, which is why tenant-to-tenant projects use temporary domains and a planned cutover window.
Does Microsoft have a native tenant-to-tenant migration tool?
Microsoft offers native cross-tenant mailbox and OneDrive migration capabilities that require specific licensing and configuration. Many projects also use third-party tools to cover Teams, SharePoint and other workloads.
Can Teams chats be migrated between tenants?
Teams channels and files can be migrated with specialized tools, but private chat migration is more limited. Plan expectations with users before cutover.
How long does a tenant-to-tenant migration take?
Small projects can be completed in weeks; complex M&A consolidations often take several months because of coexistence, legal timelines and staged cutovers.
Will users need to re-set up Outlook and OneDrive?
Usually yes. Outlook profiles, OneDrive sync and mobile apps typically need to be reconnected to the target tenant after cutover.
What happens to the source tenant afterward?
It is either retained for a period for legal or retention reasons or decommissioned after data is exported and licenses are cancelled.