SharePoint Online tenant-to-tenant migration

A tenant change, a consolidation after an acquisition, a spin-off: move your sites with their full history, in several passes, while people keep working.

Short answer

Tauri Migration copies sites from one tenant to another in four phases (taxonomy, structure, content, permissions) and re-runs incrementally until cutover. It only needs admin consent in each tenant.

What arrives in the target tenant

Item	Kept	How
Files and list items	Yes	With attachments and metadata, lookup columns included
Version history	Yes	Every version, replayed in order, or the last N
Authors and dates	Yes	Created by, Modified by, Created, Modified, translated to target accounts
Managed metadata columns	Yes	Terms copied, GUIDs re-mapped
Content types, views, settings	Yes	Copied before the content
Permissions and groups	Yes	Broken inheritance reproduced down to item level
Existing sharing links	No	Direct sharing with people is carried over
Pages, web parts, workflows	No	Rebuild them in the target

How it works

Prepare both tenantsAn admin in each tenant consents to the application. Target site collections and user accounts exist. The migration account is site collection admin on both sides and term store admin in the target.
Describe the migrationA project holds both connections. Each action lists its site or folder pairs, entered on screen or imported from the Excel template.
Translate identitiesOne domain rule covers most accounts (contoso.com to fabrikam.com, guests included). Add a line for each user whose address changes in another way, and one per Entra group.
ValidateThe validate command tests both connections and finds every account of the table in the target tenant, without writing anything.
First passTaxonomy, structure, content, then permissions. People keep working in the source meanwhile.
Incremental passesEach re-run only sends what is new or changed. An item deleted by mistake in the target is recreated.
CutoverSet the source to read-only, run a last incremental pass, then open the target. The CSV report lists every warning.

Key features

Copies into existing sites, including to combine several source sites into one.
Whole site or folder pairs, each folder to any location in the target.
Unlimited incremental re-runs, resuming at the exact version after an interruption.
Target re-checked on every pass: an item deleted in the target is recreated.
Identity mapping by domain, user and Entra group, guests included.
Planning in Excel, live tracking and a CSV report for every run.
Source left intact: the tool copies, and you archive the source when you decide.

Volume and timing

SharePoint limits the number of requests per tenant. For large volumes, the tool can sign in with a certificate, using an application’s quota rather than a user’s, and fast mode imports new files in packages through the SharePoint Migration API. Run the trial on a representative site: the gauge shows real throughput, to extrapolate to the whole tenant.

Frequently asked questions

Can people keep working during the migration?

Yes. They work in the source during the first passes. On cutover day, the source goes read-only for one last incremental pass.

Are guest accounts (#ext#) translated?

Yes. A domain rule applies to every account not listed, guests included. A guest can also get its own line in the identity table.

Can two sites be merged into one?

Yes. Several pairs can target the same site, or different folders of one library. Missing lists and columns are added.

Are Microsoft Teams migrated?

No. The files of the SharePoint site behind a team can be migrated, but not channels, conversations or team settings.

Test it on your own tenant

The 14-day trial migrates 10% of every library, with versions, metadata and permissions. After you subscribe, an incremental run migrates the rest.

Start the free trial See pricing