Tenant-to-tenant migration software

Native tools or third-party software

Native tools suit a team comfortable with PowerShell, a move that fits their workload list, and a cutover that can absorb a single file pass. A third-party tool suits a team that needs other workloads, delta passes, or one console for every wave.

How a project runs, start to finish

The length depends on object count, data size, and how many waves the business can absorb, so plan in phases rather than dates:

1. Discovery: inventory users, mailboxes, OneDrive accounts, sites, teams, groups, and holds.
2. Setup: connect both tenants and assign any licenses the method needs.
3. Pilot: move a small group and check what arrived.
4. Waves: move the rest in batches the help desk can support.
5. Cutover: final file passes, the domain move, and sign-in changes.
6. Cleanup: validate, then retire the source tenant on your own schedule.

With native tools, OneDrive and SharePoint cannot run delta passes, so schedule those moves close to cutover. Up to 4,000 OneDrive accounts can be scheduled in advance at a time.

Buyer checklist

• List every workload you must move: mail, OneDrive, SharePoint, Teams, chat, and groups.
• Find mailboxes on hold before you pick a method; native moves skip them.
• Decide whether you need delta passes for files, or can take one pass near cutover.
• Count users and objects to price licenses for each option.
• Ask each vendor which workloads are validated today, and how a failed run is retried.
• Plan a pilot, user communication, and help desk cover for cutover day.
• Decide who does the work: your team with a tool, or a consultant end to end.

The project path in Migrate

1. Connect the source and destination tenants for the client.
2. Map users, mailboxes, OneDrive accounts, sites, teams, and groups.
3. Precheck readiness. Prechecks are read-only.
4. Run a pilot with a small set of objects.
5. Migrate in scheduled waves.
6. Validate what moved. Validation is read-only.
7. Cut over.
8. Sign off the project with its evidence.

For what a wave is and how to size one, see what a migration wave is.

Workloads

Migrate plans Exchange Online, OneDrive, SharePoint, Teams, chat, and Microsoft 365 Group workloads. Its support matrix marks each item as tested live between Accred test tenants or tested with recorded data, and items still marked coming soon are not available for customer migrations.

Pricing

Migrate has no seats, plan, or trial. An Owner or Admin turns it on in Hub at no charge, and every active member can open it with a role from their Hub role: Owners and Admins manage it, Members run migrations, and Viewers can view. Each migrated object uses one license at $5, once, whether it is a mailbox, a OneDrive, or a SharePoint site, team, or Microsoft 365 group. Teams chats are included with the user’s mailbox license. Reruns, retries, and incremental passes reuse the same license. No data caps: one license covers an object whatever its size. Scans, prechecks, and validation never use a license. A license includes the self-serve migration in Accred Migrate and email support. Hands-on help, such as fixing site permissions, Teams remediation, or a site-by-site cutover, is quoted separately as Accred Consulting work. Buy licenses by card in Hub, up to 500 per purchase; above that, or to pay by invoice, request a quote in Hub.

When to choose something else

If you need a production migration this month, use an established tool, or have the migration done for you. The MigrationWiz, ShareGate, and Quest comparison covers the established options. Accred Consulting’s tenant-to-tenant migration service runs the project end to end.

Questions

Sources

1. Cross-tenant mailbox migration · Microsoft Learn
2. Cross-tenant OneDrive migration · Microsoft Learn
3. Cross-tenant SharePoint migration · Microsoft Learn