What is cross-tenant migration?
Also known as
Definition
A tenant-to-tenant migration is just that: a process that lets you move data from one Microsoft 365 tenant to another. It's like moving houses, but instead of physical things, it's moving data.
A cross-tenant migration involves identity, content, permissions, and collaboration experiences that all have to land correctly in the target tenant for people to keep working without disruption. Each workload behaves differently across tenants, and every decision made in the source environment—how access was structured, how content was organized, which policies were in place—has to be accounted for in the target.
The trigger is usually a business event: a merger, an acquisition, a divestiture, or a decision to consolidate multiple tenants into one. Each scenario comes with different scope, sequencing, and cutover complexity—and different pressure on the IT team to get it right fast.
tip
Run a source analysis before you start. It shows you what's in your environment, what's going to cause problems, and what needs fixing before anything moves. ShareGate Migrate's source analysis does exactly that.
Why it matters
Business doesn't stop for a migration. Users need access to their email, files, and collaboration tools the moment the organizational change takes effect. That's what makes cross-tenant migrations high stakes.
- Organizational change: A merger, acquisition, or divestiture doesn't mean anything in Microsoft 365 until the tenants align.
- Business continuity: A T2T migration changes where every user works, where their files live, and how they collaborate, all at once. That's the business risk.
- Consolidation: Cross-tenant migrations are the moment to simplify. What you don't clean up before the move becomes a governance problem in the target tenant.
Commonly confused with: File copy
A cross-tenant migration isn’t just moving files. It involves identity mapping, permissions planning, workload sequencing, and making sure collaboration experiences land correctly in the target tenant.
What we see out there
Acquisitions with no repeatable process.
Organizations running ongoing acquisitions often have no standard tooling or process in place. Each migration is treated as a one-off, with different vendors, different approaches, and different outcomes. The cost isn't just time. It's the inconsistency that creates governance problems in the target tenant.
Cross-workload dependencies caught mid-project.
Teams needs Exchange. Exchange needs identity. Groups need to exist before workloads can land. Organizations that plan around one workload at a time regularly hit these dependencies mid-migration, when the cost of fixing them is highest.
Frequently asked questions
What actually moves in a cross-tenant migration?
Users, data, and workloads. That includes mailboxes, files, SharePoint sites, Teams, and the groups and permissions that connect them.
How long does a cross-tenant migration take?
It depends on data volume, number of users, workload complexity, and whether you're running a cutover or phased migration. Microsoft's own guidance lists factors that affect timeline: number of users and mailbox sizes, volume of OneDrive and SharePoint content, mailboxes on legal hold (which block migration), and network bandwidth between tenants. Small organizations can complete a migration in days. Large enterprises with complex environments typically plan for weeks to months.
What is user mapping and why does it matter?
User mapping connects source tenant users to their corresponding accounts in the target tenant, so content, permissions, and shared resources land with the right people. Without it, migrated content ends up orphaned or associated with the wrong accounts. In Microsoft's cross-tenant tooling, identity mapping must be completed before any content migration begins. If user mapping is wrong, permissions break and content goes to the wrong place.
How do Teams and SharePoint migrate cross-tenant?
It depends on the tooling and the scenario. At a minimum, mailboxes, personal files, and SharePoint sites need to move. Teams data, group memberships, and permissions all need to be accounted for. Microsoft's own guidance recommends working with a partner or third-party tool. No single Microsoft native tool handles everything. ShareGate Migrate handles all of it in one place.
