Microsoft 365 Orchestrator: Simplify Cross-Tenant Migration

Every IT team that has lived through a merger, acquisition, or divestiture knows the drill. Mailboxes have to be transferred to a new tenant, OneDrive files will have to be migrated, and Teams conversations have to survive the transfer too. In such types of migrations mean either merging scripts or using different third-party solutions. The stepping stone of Microsoft 365 Orchestrator has made it easier and given a single process for administrators instead of three different processes.

This guide will explain what changes, how much it costs, how Microsoft 365 throttling affects timelines, and what needs to be prepared before launching. For a broader walkthrough of the full process, see our cross-tenant migration guide for Microsoft 365.

What Office 365 Orchestrator Actually Moves?

Microsoft has released a public preview of its service for tenant-to-tenant migrations on 16 Dec 2025. Although this service is sometimes called Tenant to Tenant Orchestrator, the correct name for it is Microsoft 365. Built on Microsoft Graph PowerShell commands, it coordinates four workloads in a dependency-aware sequence:

• Exchange Online mailboxes, including visible content, contacts, calendar items, tasks, and notes
• OneDrive for Business personal content
• Teams chats (preview)
• Teams meetings (preview, dependent on a successful mailbox move)

It moves content, not identities, so administrators still have to create every target user first. Two migration models sit underneath this: a single-event cutover for all users at once, and a phased approach that moves batches over time. A third option migrates only a subset of users, which suits divestitures.

So, can this tool handle a genuine cross-tenant mailbox migration on its own? 

Yes, mailbox migration is one of the native tasks it performs, which utilizes the same cross-tenant mailbox migration technology from Microsoft that has been in service for a long time, but is now implemented as part of a coordinated batch procedure as OneDrive as well as Microsoft 365 Teams migrations.

Licensing and Costs of Microsoft 365 Migration Orchestration

Every user whose mailbox or OneDrive content moves needs a Cross-Tenant User Data Migration license. A few points worth budgeting around:

• It’s a one-time, per-user fee, not a recurring charge, assignable to either the source or target user object.
• One license covers both mailbox and OneDrive for that user.
• During preview, Teams chat and meeting migration need no license beyond the Cross-Tenant User Data Migration license.
• The add-on is sold against Business Basic/Standard/Premium, F1/F3/E3/E5, and standalone Exchange, SharePoint, and OneDrive plans.
• GA pricing hasn’t been published; current quotes come from your Microsoft account team or CSP.

SharePoint sites sit outside this license. Shared team site content runs through Cross-Tenant Shared Data Migration instead, billed per 100 GB and currently limited to Enterprise Agreement customers. Budget time too, not just licenses: hold remediation, validation retries, and helpdesk tickets after cutover all add real hours.

Before You Start: Orchestration Prerequisites

A rushed setup is the fastest way to lose a weekend to failed batches. Confirm the following on both tenants first:

1. Licensing. Microsoft 365 E3/E5 or equivalent on both tenants, plus Cross-Tenant User Data Migration licenses for every migrating user.
2. Global administrator access for setup, with Migration Administrator rights sufficient to run the actual commands on the target.
3. A mail-enabled security group in the source tenant to scope exactly which users are eligible.
4. Properly created target users with no mailbox or OneDrive site already provisioned, and identity mapping completed before licensing.
5. Application permissions granted on both sides, plus an organization relationship and migration endpoint.
6. A completed Standalone Validation pass, which checks licenses, permissions, and mapping without moving data. Results expire after seven days.

Check for litigation, retention, or eDiscovery holds early, since any account under a hold is blocked from migrating, and remediation is a legal task, not a technical one. Regulated data under GDPR or HIPAA needs legal and compliance sign-off before scheduling anything.

Batches and the Final Cutover of Cross-Tenant Mailbox Migration

Office 365 orchestrator Migrations run as batches, each capped at 100 users per Microsoft’s documentation, so larger populations simply mean more batches. Every batch validates automatically on creation, and admins can rerun validation until it passes.

Cutover is date-driven, not manual. Administrators set a completeAfterDateTime value on the batch. A final cutover is the point where that date passes and the mailbox, along with any included Teams chats and meetings, moves to the target automatically. Make sure to cancel any transactions before your cutover date; once cutover occurs, there are no built-in reversibility functions until the feature comes out of preview. One thing to keep in mind: it may take up to an hour for any security group changes to register, so make last-minute batch adjustments accordingly.

How Does Throttling Affect Microsoft 365 Orchestrator?

Throttling rarely shows up during a small pilot and then hits hard once the full population starts moving. Graph, Exchange Online, and SharePoint Online all enforce service protection limits to keep the platform stable for every tenant sharing it.

A few mechanics matter here:

• Exceeding a threshold returns an HTTP 429 response with a Retry-After header telling the app how long to wait.
• Limits apply per app, per tenant, and sometimes per user, and aren’t affected by your subscription tier.
• Outlook enforces fixed per-mailbox limits that admins can’t adjust or request increases for.
• SharePoint Online throttling tends to hit harder during business hours than at night and on weekends.
• For genuinely bulk extraction, Microsoft recommends Graph Data Connect over standard REST calls.

Migration tools need proper backoff and retry logic, and realistic timelines that account for slower windows. Throttling is one of the more common reasons migrations stall, alongside other pitfalls covered in why M365 tenant-to-tenant migrations fail.

Where Gaps Remain, and Where SysInfo Fits!

Even with the orchestrator running, several content types stay outside its scope: SharePoint team and channel sites, Teams channels as structures, distribution and security group memberships, Power Platform automations, Intune configurations, and sensitivity-labeled content. Cross-cloud moves, such as Worldwide to Government Community Cloud, aren’t supported, and OneDrive/SharePoint moves are one-time events with no incremental sync.

This is where the SysInfo Microsoft 365 Tenant to Tenant Migration Tool becomes useful, particularly for teams that don’t want their timeline tied to a preview-to-GA roadmap.

It’s desktop software for Windows and macOS that enables the connection of tenants via OAuth 2.0 and incorporates the Graph API and Migration API for Teams programs. It allows for the transfer of various items, including mailboxes, OneDrive, calendar, and contacts, as well as migration of SharePoint sites and Teams P2P chats and Planners in one solution, with assurance of mapping from source to destination. Global Administrator access on both tenants is still required, the same as for the built-in orchestrator, and it has been developed in accordance with GCC compliance. The point isn’t replacing Microsoft’s tooling; it’s not leaving SharePoint and Teams channel content in a separate manual process while the native feature is still in preview.

Moving 10 TB Between Tenants

A 10 TB migration runs into the same throttling and licensing mechanics described above, just at a scale where small inefficiencies compound. A few things matter more here:

• Network bandwidth between tenants is a factor Microsoft explicitly calls out, alongside mailbox sizes and holds.
• Phased migration beats a single-event cutover at this volume, keeping each batch within the 100-user limit.
• SharePoint content bills separately, per 100 GB, not through the orchestrator’s per-user licensing.
• Off-peak scheduling reduces the odds of hitting SharePoint and Graph throttling.
• Holds are usually the real bottleneck, not the transfer itself.

Many teams handling this volume lean on a consolidated tool rather than juggling native per-workload batching alongside a separate SharePoint process. Our guide on how to scale enterprise migrations with SysInfo goes deeper into batch sizing for large data sets.

Final Thoughts

The introduction of the Microsoft 365 Orchestrator has made life much easier for administrators who have always been forced to use separate tools to carry out any number of activities for a single move. The MS365 Orchestrator is not yet complete, and issues such as the migration of SharePoint sites, synchronization of Teams channels, and memberships will continue to exist until such time as the full-fledged solution is available or a special tool is adopted to assist.

Frequently Asked Questions

About The Author:

Simran Bhatia

Simran Bhatia is a technical content writer engaged in writing clear, concise, and SEO-optimized content. With a background in computer science and a passion for writing, I thrive to deliver complex technical content in simple layman terms.