Migration
Tenant to Tenant Migration: A Practical Microsoft 365 Guide
Mergers, demergers and restructures all end up in the same place: moving people and data from one Microsoft 365 tenant to another without breaking how they work.
Key takeaways
A tenant to tenant migration moves users, mailboxes, OneDrive, SharePoint and Teams from one Microsoft 365 tenant to another. Most of the risk sits in identity and domains, not data: decide on identity mapping, email addresses and domain cutover before anything moves.
In practice: inventory both tenants, list what has to be rebuilt rather than migrated, choose native or third-party tools after a pilot with real data, plan coexistence for phased moves, and build UK GDPR, data location and retention obligations into the plan from day one.
A tenant to tenant migration moves users, mailboxes, OneDrive, SharePoint sites and Teams from one Microsoft 365 tenant into another, usually after a merger, acquisition, demerger or restructure. Done well, people log in on Monday to the new tenant with their mail, files and chats intact. Done badly, it becomes weeks of lost permissions, broken links and calls to the service desk.
This guide covers what a tenant to tenant migration involves, how to choose between Microsoft's native tools and third-party tools, the identity and domain decisions that drive everything else, and a step-by-step checklist you can adapt for your own project.
When do organisations need a tenant to tenant migration?
Most projects start with a business event rather than an IT decision. The common triggers are:
- Merger or acquisition: the acquiring organisation wants everyone in one tenant so they share one directory, one security model and one set of licences.
- Demerger, divestment or spin-off: part of the organisation is leaving and needs its users and data separated into a new or existing tenant.
- Consolidation: years of acquisitions have left several tenants that are expensive and hard to govern.
- Public sector restructures: bodies merge, split or transfer functions, and their Microsoft 365 estates have to follow.
The trigger matters because it sets the timeline. Legal completion dates, transitional service agreements and announcement days often fix the cutover date before anyone has sized the data.
What actually moves (and what doesn't)
It is easy to think of a migration as "moving mailboxes and files". In practice there is a much longer list, and some of it cannot be moved by any tool and has to be rebuilt.
| Area | Typically migrated | Usually rebuilt or re-planned |
|---|---|---|
| Exchange Online | User and shared mailboxes, calendars, contacts | Mail flow rules, connectors, distribution list ownership |
| OneDrive | Files and folders | External sharing links |
| SharePoint | Sites, libraries, lists, metadata, permissions (tool-dependent) | Custom solutions, hard-coded URLs, some site designs |
| Teams | Teams, channels, files; chats and meetings with supported tools | Apps, bots, tabs and some channel settings |
| Identity | Users and groups (created or mapped in the target) | Conditional Access, MFA registration, privileged roles |
| Devices | Not migrated as such | Intune enrolment, Autopilot registration, Outlook and OneDrive profiles |
| Power Platform | Environments, apps and flows have their own process | Connections re-authenticated |
| Compliance | Some content retains labels (check your tool) | Retention policies, DLP policies, eDiscovery cases, label configuration |
Write this list down early for your own tenants. The "rebuilt" column is where most of the unplanned effort hides.
Native Microsoft tools or third-party tools?
Microsoft now offers native cross-tenant options for mailboxes, OneDrive and SharePoint, and its Migration Orchestrator can coordinate mailboxes, OneDrive, SharePoint and Teams together in batches. Microsoft's own tenant-to-tenant planning guidance sets out the approaches side by side. Third-party tools such as ShareGate and BitTitan MigrationWiz remain widely used, particularly for SharePoint restructuring and complex Teams estates.
| Consider native tools when | Consider a third-party tool when |
|---|---|
| The estate is mostly mailboxes and OneDrive | You want to restructure SharePoint during the move, not lift and shift it |
| You want to keep everything inside Microsoft’s service boundary | You need detailed pre-migration reports and permission mapping |
| Your team is comfortable with PowerShell and Graph configuration | You need to migrate only selected content, or filter by date or site |
| Users follow a straightforward one-to-one identity mapping | You have many tenants, complex coexistence needs or a hard deadline |
Licensing gotcha: Microsoft's native cross-tenant migration for mailboxes and OneDrive requires an add-on licence per migrated user (Cross-Tenant User Data Migration), and the Migration Orchestrator has its own prerequisites, including Teams and Exchange Online licences in both tenants for users whose chats and meetings are moving. Third-party tools are licensed separately. Check Microsoft's current documentation and your reseller before you budget, as these requirements change.
Identity and domains: the decisions that shape everything
Most of the risk in a tenant to tenant migration sits in identity, not data. Get these decisions made and agreed before anyone moves a single file.
Identity mapping
Every source user needs a matching target user. Microsoft's native tooling relies on identity mapping, and it is strict about order: users must not already have a mailbox or OneDrive provisioned in the target before migration, or the migration can fail. That means planning how and when accounts are created, licensed and mapped, rather than simply bulk-creating users and assigning licences.
UPNs and email addresses
Decide whether users keep their existing addresses (for example the acquired company's domain) or move to the acquirer's domain. Keeping the old domain is gentler for users and customers, but it means the domain has to move tenants.
Domain cutover
A custom domain can only be verified in one Microsoft 365 tenant at a time. To move it, you remove it from every object in the source tenant, remove the domain, then verify it in the target. Between those steps mail for that domain needs a plan, so domain moves usually happen in a planned cutover window, often a weekend, with DNS TTLs lowered in advance.
Hybrid and Entra Connect
If either tenant syncs from on-premises Active Directory, the sync configuration has to be redesigned. Decide which forest is authoritative for migrated users and how Entra Connect or cloud sync will point at the target. Our identity and privileged access work often starts here, because a migration is a good moment to clean up admin roles and stale accounts rather than carry them across.
Coexistence: running two tenants at once
Few organisations can move everyone in one weekend. In a phased migration, some users are in the target and some are still in the source, and they need to work together. Plan for:
- Mail routing between tenants so mail reaches the right mailbox wherever it currently lives.
- Free/busy sharing through an organisation relationship, so people can still book meetings across the two groups.
- Teams federation or cross-tenant access settings so chat and calls keep working between tenants.
- Shared resources such as shared mailboxes and Teams owned by people moving in different batches. Batch by team and working group, not alphabetically.
UK considerations most guides miss
Most published guidance is written for a global audience. For UK organisations, a few extra points are worth building into the plan.
- UK GDPR and the transfer itself: moving employee and customer data between two legal entities is processing of personal data. Make sure there is a lawful basis and, for anything large or sensitive, consider a data protection impact assessment. Involve your data protection officer early, not at sign-off.
- Data location: check the data location of both tenants in the Microsoft 365 admin centre. If one tenant stores core data in the UK and the other in the EU, decide whether that matters for your contracts and policies before you consolidate.
- Retention and legal holds: public bodies and regulated firms often have records obligations. Mailboxes on hold can block native migration, so identify holds early and agree with legal and records teams how retention will be preserved in the target. Our information protection and DLP team can help align labels and policies across both tenants first.
- Security clearance and sensitive data: in public sector and defence-related work, check whether migration engineers and any third-party tool vendors need to meet specific security requirements before they can access the data.
A step-by-step tenant to tenant migration checklist
- Confirm scope and dates. Which users, workloads and domains are moving, and which dates are fixed by the business or legal process.
- Inventory both tenants. Users, groups, mailboxes and sizes, OneDrive and SharePoint volumes, Teams, apps, Power Platform environments, devices, licences and holds.
- Make the identity decisions. Identity mapping, UPN and address strategy, domain moves, and how on-premises sync will work afterwards.
- Prepare the target tenant. Licences, security baselines, Conditional Access, sensitivity labels, retention and DLP policies, ready before users arrive.
- Choose and test your tools. Run a pilot with real data from a willing team, and measure how long it takes so you can size later batches.
- Clean up the source. Remove stale accounts, empty sites and old Teams. Every item you do not migrate saves time and risk.
- Plan coexistence and batches. Group users by how they work together, and set up mail routing, free/busy and cross-tenant access.
- Communicate early. Tell users what will change, when, what they need to do (such as re-registering MFA or re-enrolling devices) and where to get help.
- Run pre-staging syncs. Copy the bulk of the data ahead of each cutover, so the cutover itself only moves recent changes.
- Cut over. Final sync, domain move if needed, DNS changes, licence switch-over and device and client reconfiguration.
- Validate and support. Check item counts, permissions and access for a sample of users and sites, and provide extra service desk cover for the first days.
- Decommission the source. Only once retention obligations are met, data has been verified and the business has formally signed off.
Have a rollback position for each cutover. For most batches that means leaving source data in place and read-only until validation is complete, so users can be pointed back if something goes wrong.
How long does it take?
There is no honest single answer. Duration depends on the number of users, data volumes, the workloads in scope, how much SharePoint restructuring is involved and how many decisions the business still needs to make. A small, mail-focused move can take weeks; a multi-tenant consolidation with hybrid identity and strict records rules is a programme measured in months. The pilot in step 5 is the best way to get a realistic estimate for your own estate.
Who this guide is for
IT managers, heads of IT and programme leads facing a merger, acquisition, demerger or public-sector restructure, who need to bring two Microsoft 365 estates together or pull one apart without disrupting the people who use them.
Konsolute plans and delivers tenant-to-tenant migrations covering users, mailboxes, OneDrive, Teams and SharePoint, with identity and domain changes planned in. Find out more about our Microsoft 365 migration services.
Our team holds SC and DV clearance and works with nuclear, energy and public sector clients. We build plans that stand up to inspection, not just a pilot.
WE CAN HELP
Planning a tenant to tenant migration?
Talk to our team about scoping, tooling and a cutover plan that fits your deadlines.
FAQ
Tenant migration FAQs
Tools, identity, Teams, devices and compliance.
Yes. Microsoft provides native cross-tenant migration for mailboxes, OneDrive and SharePoint, and the Migration Orchestrator can coordinate several workloads, including Teams, in batches. These tools have licensing and configuration prerequisites, so check the current Microsoft Learn documentation before deciding.
They can, but only if their domain moves to the target tenant. Because a domain can only be verified in one tenant at a time, keeping existing addresses means planning a domain cutover window. Some organisations instead move everyone to the acquirer’s domain and keep the old domain as an alias once it has moved.
Teams, channels and their files can be migrated with most tools. Chat and meeting migration is supported by Microsoft’s Migration Orchestrator and some third-party tools, but it has stricter prerequisites, such as identity mapping and licences in both tenants. Confirm exactly what your chosen tool supports during the pilot.
Usually, yes. Devices joined to Entra ID or enrolled in Intune in the source tenant need to be re-joined or re-enrolled in the target, and Outlook, OneDrive and Teams clients need reconfiguring. Plan this as part of each user’s cutover, not as an afterthought.
Policies do not move automatically. Recreate your label taxonomy, retention and DLP policies in the target before migration, and test how labelled and encrypted content behaves after it moves.

