History intact
Version history, Created and Modified, and Created By and Modified By, re-pointed at the new tenant's accounts.
Copy whole sites, or just the lists and libraries you pick, from one Microsoft 365 tenant into another. Version history, the original dates and authors, and permissions matched to the people in the new tenant. Run it again before cut-over to catch what changed.
How do I migrate SharePoint from one tenant to another?
Microsoft's own cross-tenant SharePoint migration is a paid add-on for Enterprise Agreement customers, driven by PowerShell on both tenants, and it only moves a site into a destination that does not exist yet. Microsoft's free SharePoint Migration Tool does not go tenant to tenant at all. Everyone else uses a migration tool: ShareMaster copies sites, lists and libraries between two tenants through Microsoft's Migration API, keeping versions, Created and Modified dates and authors, and permissions mapped to the destination's people.
Version history, Created and Modified, and Created By and Modified By, re-pointed at the new tenant's accounts.
Exact user name and email matches applied for you, the rest picked or skipped in one grid before anything copies.
Merge into a destination that already exists, land as a subsite under it, or let the app create a new site.
Incremental runs pick up what changed since the last one, and a stopped run resumes where it stopped.
Moving SharePoint between tenants usually comes with a business event: an acquisition folding a company into the parent's tenant, a division being sold off, a rebrand onto a new domain, or a consolidation of several tenants into one. Whatever the reason, there are three routes, and which one is open to you depends more on your licensing than on the content.
| SharePoint Migration Tool (SPMT) | Microsoft cross-tenant migration | ShareMaster | |
|---|---|---|---|
| Tenant to tenant | No: on-premises and file shares into Microsoft 365 | Yes | Yes |
| Who can buy it | Free | Enterprise Agreement customers, as a paid add-on | Anyone, $900 USD a year |
| How you run it | Desktop app | PowerShell on both tenants, with a trust set up between them | Desktop app, signed in to each tenant |
| Destination site | Not applicable | Must not already exist | New, existing (merge), or a new subsite |
| Part of a site | Not applicable | Whole site only | Whole site, or the lists and libraries you pick |
| Catch up changes later | Not applicable | No: one move, no delta passes | Incremental and differential re-runs |
| User mapping | Not applicable | A mapping file you prepare | Automatic exact matches, the rest in a grid |
Microsoft's facts come from its cross-tenant SharePoint migration documentation. If you hold an Enterprise Agreement and are moving whole sites once, into a clean tenant, Microsoft's route is worth pricing. If any of those conditions do not hold, it is not available to you, and that is the case this page is about. For the full picture of what each tenant needs before a move, see the cross-tenant prerequisites reference.
Three things decide how smoothly a tenant move goes, and none of them is the tool. Create the destination users first, so authorship and permissions have someone to map to. Check the destination's storage, because version history is usually what fills it; the version cap in Settings is there if you need it. And plan for time: a large site takes hours through the Migration API, so run the bulk early and keep the incremental pass for cut-over weekend.
Copying inside one tenant instead? To duplicate a whole site the same clone works with a single sign-in, and for files between libraries Move / Copy uses SharePoint's own server-side copy. Still choosing a tool in general? The SharePoint migration tool overview compares every option, including Microsoft's free ones.
Start a 14-day free trial, no credit card. Run the pre-migration analysis and a trial clone of one site, then decide.
Last updated