In a move between two Microsoft 365 tenants, the thing that locks up the project is not data volume but the domain: if example.com remains in the source tenant even as a secondary address on a single shared mailbox, it can’t be verified in the target. Mergers, acquisitions or a business unit being spun off bring this work onto the agenda. The difference from an on-premises-to-cloud migration is that both sides are live cloud services and the domain can’t be used in two places at once. Below we go through the order in which workloads are moved, the domain-driven switchover window, the scope of Microsoft’s native tools versus third-party tools and post-migration cleanup.
Scenarios that trigger the migration
The scenario determines the direction and speed of the move:
- Acquisition: Users of the acquired company are moved to the parent company’s tenant. The domain is usually moved too; the brand can be kept for a while.
- Merger of equals: Two tenants are consolidated into a single new or existing tenant. Naming and policy decisions must be made before the technical work.
- Divestiture: Users and data of the business unit being sold are carved out into a new tenant. Which data goes to the departing side is a legal decision; IT only implements it.
- Tenant consolidation: Consolidating regional or trial tenants opened over the years into a single tenant.
In every scenario the first question is: during the transition, will the two organizations see each other’s calendars, reach each other in Teams and work on shared files? If the answer is yes, a coexistence layer is set up between the two systems infrastructures before the move. If this layer is skipped, the first week is spent on “I can’t see the other side” requests.
Workloads and dependency map
Workloads in a tenant depend on each other. A Teams team relies on a Microsoft 365 group, the SharePoint site connected to the group and often a shared mailbox. In a move done without a dependency map, users run into broken links.
| Workload | Dependency | Migration note |
|---|---|---|
| Identities | All workloads | Created first in the target |
| Mailboxes | Identity, domain | Including shared mailboxes |
| OneDrive | Identity | Sharing links break |
| SharePoint sites | Groups, permissions | The URL changes |
| Teams | Group, site, mailbox | Messages aren’t moved by the native tools |
| Power Platform, Forms | Connections, ownership | Most are rebuilt |
| Devices | Entra ID, Intune | Re-enrollment required |
For the inventory, export mailboxes, groups, sites, teams and app registrations in both tenants. Separately flag mailboxes in the source tenant under a retention policy or litigation hold; they are handled differently in the move and deletion steps.
The dependencies discovered late are usually these: Power Automate flows, Power BI workspaces, Forms, Planner plans and third-party app integrations. List them with their owners and classify them as “to be rebuilt” or “to be moved.” A flow with an unknown owner dies in the migration.
The domain constraint and the switchover window
A domain can be verified in only one tenant at a time. This single rule sets the project schedule. To bring example.com into the target, every user, group, contact, shared mailbox and resource in the source tenant that uses that domain as a UPN, primary or secondary SMTP address must be switched to another domain (usually *.onmicrosoft.com). The domain is then deleted from the source and verified in the target.
You can list the objects that use the domain with Microsoft Graph PowerShell:
Connect-MgGraph -Scopes "Domain.Read.All","Directory.Read.All"
Get-MgDomainNameReference -DomainId "example.com" -All |
Select-Object Id, @{n="Type";e={$_.AdditionalProperties["@odata.type"]}},
@{n="Name";e={$_.AdditionalProperties["displayName"]}}
On the Exchange Online side, proxy addresses must be checked separately:
Connect-ExchangeOnline
Get-Recipient -ResultSize Unlimited |
Where-Object { $_.EmailAddresses -match "@example\.com$" } |
Select-Object Name, RecipientTypeDetails, PrimarySmtpAddress
When the domain deletion is refused because of an object, the culprit is usually a forgotten distribution group, an old contact object or a proxy entry left as a secondary address. The switchover window is the time between removing the domain from the source and it becoming usable in the target; during this time external mail flow and users’ sign-in names are affected. Practical measures:
- Lower the TTL values of the MX, Autodiscover and SPF records a few days before the switchover.
- Schedule the switchover for a time when mail traffic is low, such as a weekend. Sending servers queue mail for an MX they can’t reach and retry, but the retry period depends on the sender. Keep the window short.
- Try bulk address-change scripts in a test tenant or on a small pilot group first; on thousands of objects this takes time.
- Put the switchover order into a written runbook: change addresses in the source, delete the domain, verify it in the target, assign addresses in the target, update MX and Autodiscover, send a test email.
Native cross-tenant features and third-party tools
Microsoft offers some native features for moving between tenants. Their scope is narrower than third-party migration tools, but they don’t require installing an extra product.
| Scope | Microsoft native | Third-party tools |
|---|---|---|
| Mailbox | Cross-tenant mailbox migration | Usually available |
| OneDrive | Cross-tenant OneDrive migration | Usually available |
| SharePoint sites | Check the current status in the documentation | Usually available |
| Teams chat and channel messages | None | Varies by product |
| Coexistence | Organization relationship, B2B, cross-tenant sync | Some offer extra features |
Native cross-tenant mailbox migration requires: an app registration in the target tenant, an organization relationship defined between the two tenants, a migration endpoint in the target and a mail user object prepared in advance in the target for each user being moved. The target mail user’s ExchangeGuid must be the same as the source mailbox. If the GUID doesn’t match, the move won’t start. A cross-tenant migration license is also needed for each user. When the move completes, the mailbox in the source becomes a mail user and forwards mail to the target; mail flow is kept this way until the switchover window.
When choosing a third-party tool, get clear answers to these questions: Does it move Teams chats and channel messages, and if so, in what form? Can it rewrite permissions and sharing links? Does it support incremental passes? Are the migration reports sufficient for audit? Try it with your own pilot data, not in a demo environment.
Identity mapping and user communication
The basic input for all tools is an identity mapping file. Identities in the source and target must match one to one; shared mailboxes and resource accounts must also be in the file. To rebuild the identity lifecycle and privilege ownership after a merger or divestiture, you can get support through our identity and access management consulting.
SourceUPN,TargetUPN,Type,Wave
[email protected],[email protected],User,1
[email protected],[email protected],SharedMailbox,1
[email protected],[email protected],User,2
Users with the same name, unlicensed mailboxes of employees who have left and names spelled differently in the two tenants (with and without Turkish characters) are resolved by hand in the mapping file. An automatic mapping script won’t treat “Şahin” and “Sahin” as the same person. The wave column is used to group the move by department or location.
Write down clearly what changes on the user side: a new sign-in name, recreating the Outlook profile, adding the account on mobile devices, restarting OneDrive sync, switching to the new tenant in Teams and old sharing links no longer working. Sharing this in a short guide before the wave starts reduces support requests.
The limits of moving Teams and SharePoint
Teams and SharePoint are more complex than mailboxes, because content, permissions, URLs and links are bound together:
- SharePoint site URLs change; hyperlinks in documents, Excel links and browser bookmarks point to the old address.
- Sharing links (“anyone with the link”) must be recreated in the target, including shares with external users.
- Teams meetings are tied to the organizer in the source tenant; recurring meetings are recreated in the target.
- Teams chats aren’t moved by the native tools. If there is a legal or operational need for message history, either a tool that supports it is chosen or the source tenant is kept read-only for a while and the data exported with eDiscovery.
During the transition, using Entra ID cross-tenant synchronization to create users as B2B users (external members by default) in the other tenant makes it easier for the two organizations to reach each other in Teams and share files.
Post-migration cleanup
- Devices: Re-enroll devices registered in the source tenant in the target. If Autopilot is used, delete the hardware hashes from the source and upload them again to the target; the steps are in our device setup with Windows Autopilot guide.
- Licenses: Remove migrated users’ source licenses not immediately but after verification is complete; a mailbox whose license is removed is deleted after the retention period.
- Retention obligations: If there is data under litigation hold or a retention policy, closing the source tenant should require the legal department’s approval.
- Backup: Back up the required data before closing the source tenant; for methods, see our article on Microsoft 365 backup.
- App registrations and SSO: Reconfigure the enterprise apps from the source tenant in the target and disable the old registrations.
- DNS: Update old Autodiscover, SPF and DKIM records for the target tenant; enable DKIM signing in the new tenant.
Closing the source tenant closes the way back. Don’t rush.
Moving from on-premises Exchange to the cloud carries different risks; for those methods, see our guide to Exchange Online migration methods. For support with the technical planning of mergers and acquisitions, see our Microsoft 365 and cloud services and IT consulting pages. The current prerequisites for native mailbox migration are in Microsoft’s cross-tenant mailbox migration documentation.
Frequently asked questions
Can a domain be used in two tenants at the same time?
No. A domain can be verified in only one Microsoft 365 tenant at a time. To use it in the target, you need to remove it from every object using it in the source and delete the domain from the source; that requires a planned switchover window.
Can Teams chat history be moved to the new tenant?
Microsoft’s native cross-tenant tools don’t move Teams chat and channel messages. Channel files live in SharePoint, so they can be moved; if the messages also need to be moved, third-party tools that support this are considered, or the messages are archived in the source.
Does cross-tenant mailbox migration require an additional license?
Yes. Microsoft’s native cross-tenant mailbox and OneDrive migration features require a separate migration license for each user moved. Check Microsoft’s documentation and your license provider for the current license name and terms.
What happens to the devices of migrated users?
Devices Entra-joined to the source tenant and enrolled in Intune don’t move to the target automatically. Devices are removed from the source and re-enrolled in the target; Autopilot registrations are also deleted in the source and recreated in the target.