Tenant-to-Tenant Migration with Orchestrator – Technical Overview (Microsoft 365 | Preview)

Tenant-to-tenant migration with Orchestrator in Microsoft 365 introduces a native, API-driven, and highly validated approach for cross-tenant migrations. It is designed for enterprise scenarios where sequencing, dependencies, and governance are critical.

Note: This capability is currently in preview. Features and behavior may change before GA.

Architecture and execution model

• Migration is executed through batches (jobs) managed via Microsoft Graph (Beta)
• User-level execution: one user failing validation does not block others in the same batch
• Mandatory Standalone Validation before migration submission
• Date-driven cutover using completeAfterDateTime

Supported workloads (actual scope)

• Exchange Online
• Microsoft Teams
• ODSP (OneDrive for Business)

Important clarification on SharePoint Orchestrator does not migrate shared SharePoint content such as Team sites, Channel sites, or collaboration sites. The ODSP workload covers personal user data (OneDrive) only. SharePoint team/workload sites remain out of scope and require separate tooling or processes.

Critical prerequisites

• Identity Mapping (CTIM) is mandatory and must remain stable during migration
• Target users must not have Exchange mailboxes or OneDrive sites provisioned before migration
• Licenses must be assigned only after Identity Mapping (ExchangeGuid stamping)
• Migration apps and service principals (Teams, Meetings, CTMS) must be correctly provisioned
• Organization Relationships and Migration Endpoints must be in place
• Exchange autoforwarding must be enabled for Meetings migration

Validation and lifecycle

• Standalone Validation acts as a full “what-if” check
• Key states include:
• Cancellation or user removal is possible only before cutover

Post-migration cleanup

After completion, tenants must be returned to a non-migration state:

• Remove Identity Mapping data
• Remove Organization Relationships
• Remove Migration Endpoints
• Revoke migration app permissions and service principals
• Decide whether to retain or remove MailUsers in the source tenant

Skipping cleanup leaves the tenant in an exception state.

When this approach fits

• Mergers and acquisitions
• Divestitures and tenant splits
• Regulated environments requiring strict control
• Scenarios where dependency-aware sequencing matters more than speed

Technical conclusion

Orchestrator is not a one-click solution. It delivers native orchestration, deep validation, and predictable execution when Identity Mapping, licensing order, and scope boundaries are fully understood.

For experienced administrators and architects, it represents a major step forward in tenant-to-tenant migrations within Microsoft 365, even while still in preview.