Tenant-to-tenant Microsoft 365 migration — Teams, mailbox, OneDrive, SharePoint, chat history. Resume, merge, parallel uploads, production-validated.
About this edition
Six migration tools with resume, merge, and parallel uploads — production-proven on 153K-file runs. Run from your own laptop on the desktop SKU, with checkpoints persisted locally.
What you get
Teams Migration — channels, members, files; 153K-file production runs validated
Mailbox + Shared Mailbox Migration — full mailbox cut-over with delegates
OneDrive Migration — drives with permissions and version history
SharePoint Migration — sites, lists, documents, and pages
Chat History Export — compliance-ready Teams chat archive
Resume + merge + parallel uploads (4x throughput) baked into every tool
Who it's for
M&A IT lead. Consolidating two acquired companies’ M365 tenants into one within a 90-day window — Run all six migration tools in parallel against the same source/target pair; resume from the last checkpoint after any interruption.
Tenant-rebranding admin. Moving an entire organisation from contoso.onmicrosoft.com to a new branded tenant — Full data fidelity (Teams + mail + drive + sites) in one toolkit — no third-party hosted intermediate.
Divestiture project manager. Splitting a subsidiary out of a parent tenant with strict data-isolation requirements — Zero-knowledge architecture means no vendor sees the migrated content; everything streams source→target through your own runtime.
Edition identity
SKU id: migration.
Tools included: 6.
Tagline: Move Teams, mailboxes, OneDrive, and SharePoint between Microsoft 365 tenants..
Limitations & out-of-scope
Move: Move requires admin consent on both source and target tenants. Throughput is capped by Microsoft Graph throttling (~400 requests / 10 s per app per tenant) and by destination-tenant ingestion quotas. Items already present at destination are detected via content hash and skipped.