Microsoft 365 Launches New Tenant-to-Tenant Migration Orchestrator Tool

Microsoft has introduced a new tenant-to-tenant migration orchestrator in public preview that enables organizations to securely move OneDrive files, Exchange mailboxes, and Teams chats and meetings between Microsoft 365 tenants. This service is designed to simplify complex migration workflows while maintaining continuity and collaboration during mergers, acquisitions, divestitures, and organizational restructurings.

Organizations can adopt one of three primary migration strategies tailored to their specific needs. Single-Event Migration involves moving all users and workloads in one go, which makes it ideal for smaller or less complex migrations. Moreover, Phased Migration spreads the process over time by migrating users in batches, which is better suited for large enterprises or scenarios with added complexity. Tenant Move/Split transfers only a subset of users to a new tenant, while others remain in the original, which is a common approach during divestitures.

Supported migration scenarios and strategies

Microsoft noted that this new tenant-to-tenant migration experience requires that both the source and destination tenants have Microsoft 365 E3/E5 or equivalent licenses. Moreover, a Cross-Tenant User Data Migration add-on license must be assigned for each user whose mailbox or OneDrive data is being migrated, and this license can be applied to either tenant.

Administrators can opt in to test this new migration orchestrator solution with new PowerShell Graph commands to migrate Exchange mailboxes, OneDrive files, and Teams chats across Microsoft 365 tenants. It includes built-in integration with enterprise-grade security and compliance standards. Organizations subject to regulations such as GDPR or HIPAA should align with internal and legal teams before migration.

Security, compliance, and data residency benefits

A major advantage of Microsoft’s migration orchestrator solution is that moves happen inside the Microsoft 365 cloud to avoid any external staging or third‑party transit. This capability reduces risk, eliminates data egress, and typically delivers faster, more predictable throughput for large workloads because the service can perform controlled, service‑side copies within Microsoft datacenters.

In practice, this solution also helps organizations meet residency and compliance objectives, since content is moved tenant‑to‑tenant without leaving Microsoft’s infrastructure. Moreover, migrations are orchestrated with admin‑governed trust, consent, and auditing across source and target tenants to minimize end‑user disruption.

Limitations and considerations

Microsoft’s tenant-to-tenant migration orchestrator solution comes with certain limitations that require planning. Mailboxes under any type of legal or compliance hold (such as eDiscovery) cannot be moved unless those holds are released, which can be challenging during ongoing investigations. Moreover, only IPM content (data visible to email clients) is migrated, and non-IPM folders (like Microsoft Teams compliance records) remain in the source tenant to preserve regulatory integrity.

Furthermore, items protected by sensitivity labels must have those labels removed before migration, as label policies don’t transfer between tenants. Keep in mind that organizations that rely heavily on sensitivity labels may need third-party tools to complete the migration.