Tenant-to-Tenant Migration Tools Compared: Native vs Five Vendors

EPC Group is a Houston-based Microsoft consulting firm operating since 1997, with six Microsoft Solutions Partner designations and 216+ M&A tenant migrations covering 1.83M users. Governed Microsoft AI, Data & Cloud — since 1997.

Our disclosure, up front

EPC Group has delivered tenant-to-tenant and M&A migrations using Microsoft's native path, Quest On Demand Migration, BitTitan MigrationWiz, ShareGate, Cloudiway and AvePoint. We hold no reseller agreement and take no referral commission on any of them. Every other comparison on page one of this query is written by a company paid when you pick its product. Our bias is toward whichever option reduces total project cost — frequently the free one.

What Microsoft native actually ships in 2026 — the fair baseline

Every commercial tool must be measured against what you already own, and that baseline is materially larger than it was two years ago.

Cross-tenant mailbox migration (generally available). New-MigrationBatch through the Move Mailboxes role, requiring a migration application consented in both tenants, an Exchange Online migration endpoint, an organization relationship, and a mail-enabled security group in the source scoping which mailboxes may move. Only user-visible content moves — email, contacts, calendar, tasks, notes. After the move the source mailbox is deleted and converted to a MailUser stamped with a routing address, which is what gives you mail-routing coexistence.

Cross-tenant OneDrive and SharePoint migration. SharePoint Online PowerShell, a trust between tenants, pre-created target users and groups, and an identity mapping file. Content never leaves the Microsoft 365 cloud, and a redirect is left on the source so existing links keep working until it is deprovisioned.

The Microsoft 365 Migration Orchestrator (preview). The significant addition. It coordinates Exchange mailboxes, OneDrives, Teams chats and meetings in one dependency-ordered batch across three architecture models — Single-Event, Phased, and Tenant Move/Split — mapped to acquisitions, large enterprises and divestitures. It requires Cross-Tenant Identity Mapping (CTIM), which maps source users one-to-one to target users and stamps the required attributes.

Licensing. A per-user, one-time Cross-Tenant User Data Migration add-on covers Exchange and OneDrive in an orchestrated move and can be assigned on either side. During preview, Teams chats and meetings need no additional licence. SharePoint site moves use the separate Cross-Tenant Shared Data Migration licence, per 100 GB, EA customers only. Microsoft publishes no list price for either on Learn.

What native still cannot do. No identity migration. No Teams channels or team structure through the Orchestrator. No delta passes on files. No GCC or GCC High for SharePoint or OneDrive. No mailboxes or OneDrive accounts on hold. No public folders, client-side rules, send-as permissions or auto-mapping profiles. No on-premises Exchange or file-share source. No device re-join. Those gaps are the entire commercial market.

The capability matrix

Every vendor claim below is drawn from that vendor's own published product or documentation pages, cited in Sources. Where a vendor does not publish a capability, this table says so rather than guessing.

When the free native path is enough

Use the native path — and buy no tool — when all of the following are true. If any one fails, escalate.

1. Both tenants are commercial cloud. Not GCC, not GCC High, not sovereign.
2. You can accept one cutover per user with no delta pass. If the business needs users working in the source for weeks after their files move, native does not fit.
3. No mailbox or OneDrive in scope is on hold. Holds block the move outright.
4. You do not need Teams channels or team structure. Sites can move via the separate SharePoint feature on an EA; team structure cannot move natively at all.
5. You do not need identity, device or on-premises source migration.
6. You have PowerShell capability in-house. The native path is entirely script-driven. There is no console for a junior admin.
7. Your evidence requirements are satisfiable from move reports.

The native path suits simple, commercial-cloud, sub-1,000-user consolidations where the acquirer controls both tenants and the timeline is not compressed. It becomes insufficient the moment identity, devices, GCC, on-premises remnants, long coexistence or Teams channel structure enter scope.

The Native-First Escalation Ladder

The Native-First Escalation Ladder is EPC Group's selection framework. Its governing rule: you do not choose a tool, you escalate to one, and each escalation must be justified by a named gap you can point at in Microsoft's own documentation. Start at rung one; stop at the first rung that covers your scope.

Two rules make the ladder work. Write the gap down — if your team cannot name the documented limitation forcing an escalation, you are buying comfort, not capability. And run the ladder after the assessment, not before.

Scenario-to-tool routing

Total cost of tooling — including the labour the tool does not remove

Half one — tool licence, for an illustrative 500-user consolidation, at rates as published at time of writing (July 2026):

Flat-fee versus per-user is the biggest commercial decision here, and it inverts around scale: per-user is cheaper below a few hundred users, flat annual pricing usually wins above roughly a thousand. That is exactly why the vendor with flat pricing publishes a 500-user comparison and the vendor with per-user pricing does not.

Half two — the labour no tool removes. Price these at your own blended rate; we will not invent an hourly figure. Each exists on every project regardless of tool:

• Discovery and inventory — mailboxes, sites, teams, holds, sensitivity labels, guest and service accounts, delegate chains, third-party integrations.
• Identity mapping and target object preparation. Native requires exact ExchangeGUID, ArchiveGUID and every x500 proxy on the target MailUser or the move does not start. Tools automate some of this; none decide your UPN strategy.
• Remediation — 400-character paths, oversized sites, labels with user-defined permissions and source Customer Key encryption (both block native SharePoint migration outright), holds, previously-provisioned target mailboxes.
• Batch design. Principals and delegates must move together; so must departments that share content. Business-relationship modelling, not a technical task.
• Communications and training — new UPN, new sign-in, Outlook reprofiling, Teams re-sign-in, OneDrive resync. See our Teams Premium features guide.
• Cutover operations, hypercare and reconciliation — staffed hours, an escalation bridge, a named rollback decision-maker, and item counts in versus out per workload in a form an auditor accepts.
• Source decommission and the domain move, which cannot happen while any user, group, distribution list, team, shared or resource mailbox or admin sign-in still uses the domain.

In EPC Group's delivery experience the licence line is routinely the minority of total project cost. Vendors compete on the line item that matters least. Our view on structuring the engagement around it is in delivery partner and vendor risk.

The procurement questions checklist

Send these in writing and require written answers. The answers, not the demo, are the evaluation.

1. Which in-scope workloads do you migrate, and which do you explicitly not migrate? Provide the published support matrix, not a sales summary.
2. Do you support GCC and GCC High as source, target, or both? Link the documentation.
3. What is your position on mailboxes and OneDrive accounts under legal hold?
4. Do you migrate 1:1 chat, or only channel conversations?
5. Do you preserve mailbox delegate and calendar permissions across tenants? Microsoft's native path does not — what do you do differently?
6. What happens to sensitivity labels, encryption and Purview policy on migrated content?
7. Can we run delta passes after the initial move? How many, at what cost?
8. What is the licence model, list price and term, and what happens if the project overruns it?
9. What audit artefact do you produce — item-level reconciliation, per user, per workload?
10. What is your support SLA during a cutover weekend, and is it included or an add-on?
11. What are the top five reasons your migrations fail, and the remediation for each?
12. Under what circumstances would you tell us to use Microsoft's native tooling instead of yours?

Question 12 separates vendors. One that cannot answer it honestly will not tell you the truth about question 11 either.

What breaks — failure modes

What changed in 2026

• The Migration Orchestrator entered public preview, adding Teams chats and meetings to native scope for the first time. If you evaluated tools before it shipped, your business case is out of date.
• Cross-Tenant Identity Mapping became the required identity step for orchestrated migrations, removing the most error-prone manual task in the native path.
• Microsoft published a consolidated tenant-to-tenant planning page with a three-way approach table: orchestrated, individual workload, or partner and third-party tools. Microsoft naming third-party tools as a legitimate approach is itself new.
• Microsoft's documentation now names the Orchestrator's exclusions plainly — Teams and Channels and SharePoint Sites are out of scope. That sentence is the strongest argument a commercial vendor has.
• ShareGate published flat annual pricing tiers and a competitor cost comparison, pushing price transparency into a category that had none.
• Quest published a Commercial/GCC → GCC High Teams support matrix with an explicit unsupported list — currently the clearest government-cloud migration documentation in this market.

Where to go next

If you are being asked to pick a tool before anyone has run an assessment, stop. The assessment decides the tool; the demo does not. EPC Group runs a fixed-scope tenant assessment producing the workload inventory, the hold and label remediation list, the identity strategy and a scored recommendation against this matrix — and we are paid the same regardless of which option wins. Start with Microsoft consulting or Azure cloud migration consulting.

Related: Exchange to Office 365 migration · SharePoint migration services · Microsoft 365 E3 vs E5 · E3 vs E5 · Teams Premium · Box vs SharePoint · My Sites in SharePoint · SharePoint consulting Dallas · Data governance firms · Microsoft Frontier Company · CFO AI governance · EPC Group

Frequently asked questions

Sources and verification

1. Microsoft Learn — Plan a Microsoft 365 tenant-to-tenant migration
2. Microsoft Learn — Tenant-to-tenant migration with orchestrator: overview
3. Microsoft Learn — Orchestrator: planning and prerequisites
4. Microsoft Learn — Resolve errors during orchestrated migration (preview)
5. Microsoft Learn — Cross-tenant mailbox migration
6. Microsoft Learn — Cross-tenant SharePoint migration
7. Microsoft Learn — Cross-tenant SharePoint migration FAQs
8. Microsoft Learn — Cross-tenant OneDrive migration
9. Microsoft Learn — Cross-tenant OneDrive migration FAQs
10. Microsoft Learn — Cross-Tenant Identity Mapping
11. Microsoft Learn — Microsoft 365 migration overview
12. Microsoft Learn — FastTrack: Cross-Tenant Migration
13. Microsoft Learn — Cross-tenant synchronization overview
14. Microsoft Learn — Plan for multitenant organizations
15. Microsoft Learn — Remove a domain from Microsoft 365
16. Microsoft Learn — SharePoint limits
17. Quest — On Demand Migration
18. Quest — Teams migration from a commercial tenant to a GCC High tenant
19. BitTitan — MigrationWiz Microsoft 365 Tenant Migrations
20. BitTitan — MigrationWiz Pricing
21. ShareGate — Tenant-to-tenant migration
22. ShareGate — Pricing
23. Cloudiway — Microsoft 365 tenant-to-tenant migration
24. Cloudiway — Microsoft Teams migration
25. Cloudiway — Pricing
26. AvePoint — Fly