Blog Post

Microsoft 365 Insider Blog
2 MIN READ

Simplify cross-tenant user migrations with Microsoft 365 orchestrator

Rebecca_W_Wood's avatar
Rebecca_W_Wood
Icon for Microsoft rankMicrosoft
Mar 05, 2026

Hi, Insiders! I am Rebecca Wood, a Product Manager on the Enterprise and Cloud team. I’m excited to tell you about cross-tenant orchestrated user data migration in Microsoft 365, our new product for moving user data and workloads between separate Microsoft 365 tenants.

Simplify cross-tenant user migrations with Microsoft 365 orchestrator

The orchestrator, also known as cross-tenant orchestrated user data migration, is a self-service product for customers undergoing mergers, acquisitions, and divestitures.

It was made for customers who wanted to use an in-house Microsoft solution that keeps all Microsoft 365 data within the Microsoft boundary. For the first time, we’re offering a product that moves Teams Chats! In addition, we have built an improved experience for migrating Teams Meetings.

How it works

Orchestrator is an opt-in feature that runs through PowerShell, where tenant admins can batch and schedule the migration of a user's mailbox, OneDrive, Teams meetings, and Teams chats.

Learn more.

Scenarios to try

This feature is best used with mergers and acquisitions scenarios, whether you’re aiming for tenant consolidation or tenant separations.

Availability

Cross-tenant user data migration is available as an add-on to the following Microsoft 365 subscription plans:

  • Microsoft 365 Business Basic, Standard, and Premium
  • Microsoft 365 F1/F3/E3/E5
  • Office 365 F3/E1/E3/E5
  • Exchange Online
  • SharePoint in Microsoft 365
  • OneDrive
  • EDU

 

It is available to customers who have a license under an Enterprise Agreement, cloud solution providers, Web direct customers, Small Business, and Education customers. It is an opt-in feature that requires the purchase of an add-on Cross-Tenant User Data Migration license for each migrating user.

Feedback

Please share your feedback with the experience here.

 

Learn about the Microsoft 365 Insider program and sign up for the Microsoft 365 Insider newsletter to get the latest information about Insider features in your inbox once a month!

Updated Mar 05, 2026
Version 2.0
microsoft 365

2 Comments

  • kec's avatar
    kec
    Copper Contributor
    Mar 24, 2026

    While good to see as a starting point, it's not an option for me until there is the ability to pre-sync data and then control finalization of the sync and cutover. Setting a "not before date" is inadequate.  Particularly when dealing with large mailboxes, communicating that at some point any time after xx-xx-xxxx the mailbox will cutover is not feasible option.    

    • Rebecca_W_Wood's avatar
      Rebecca_W_Wood
      Icon for Microsoft rankMicrosoft
      Mar 24, 2026

      Thank you for considering our product. For mailboxes, the sync will begin when the migration is submitted. At this time, admins also provide a "Complete After Date". The Complete After Date will be the earliest that users will feel an impact of the migration: mailboxes will cut over, OneDrives will move, and Teams data will move.

      The amount of time required for sync is based on the total amount of content that is moving. We recommend customers submit migrations to allow for up to two weeks of syncing given average migration batch sizes. 

      This product provides two ways to be more precise on the actual cutover timing: 1) customers can view when the mailboxes have synced (the Exchange Mailbox status for the user will be "synced"), and 2) the Complete After Date can be updated.

      In the case of a large mailbox migration, customers can do the following: 1) submit the batch with ample time for syncing, say 2 weeks in advance of target migration cutover date, 2) provide a Complete After Date with the intended cutover date or a date further in the future, 3) monitor the batch for the synced state of all mailboxes, and 4) update the Complete After Date once mailboxes have all synced to the precise date and time that cutover is acceptable.

      Please let us know what other questions or concerns you have!