Copy SharePoint sites, lists, libraries and pages to another site or another Microsoft 365 tenant, with version history, metadata and permissions. No PowerShell, and a compare of source and destination when it finishes.
The source and destination are two separate sign-ins, so they can be in two different Microsoft 365 tenants. Content goes across through Microsoft's Migration API. Before any content moves, every source user and group is matched against the destination tenant: exact matches on user name or email address are applied for you, and the rest are shown in a grid where you pick the destination person or group, or skip them. That is what keeps authors and permissions pointing at real people after a merger, an acquisition, a demerger or a change of provider.
Each one is a tile in ShareMaster's Migration Tools menu. All migration tools.
Copy schema and content
The most thorough copy. Lists and libraries go across with their schema, content types, fields, views and folder structure, plus every item, file, version and permission. Copy a whole site end to end, or tick only the lists and libraries you want. Source and destination can be on the same tenant or on two different ones, and a OneDrive can be either end.
Into lists that already exist
Copies items, files, folders and, if you want them, permissions into destination lists that already exist with a matching schema. Nothing about the destination's structure is changed, so it suits a destination someone has already built.
Schema, no content
Copies list and library definitions, content types, columns, views and folder structure, with no items or files. Use it to stage a tenant before a bulk content load.
Same tenant, server-side
A fast move or copy inside one tenant, using SharePoint's own server-side Copy To and Move To rather than the Migration API. Pick what to move in a two-pane browser, or drive it from a CSV with one row per folder pair. Runs can be resumed, and reversed.
Either direction, one tenant or two
Copy a person's OneDrive into a SharePoint site, or SharePoint libraries into someone's OneDrive. Pick the person from the tenant's users or type their email address, tick the libraries, folders or files to copy, and choose the library or folder they land in. Version history, Created and Modified dates and authors, and permissions come across, on one tenant or between two. The OneDrive's own name, logo and settings are never touched.
Run history
Every clone and Move / Copy run is kept in History on this computer. An interrupted run resumes with one click, and an incremental clone copies only what has changed since the last one. Upload, download and Dropbox runs keep their reports there too.
Migration is in the Clone Master plan: $900 USD for one year or $1,300 for two, excluding tax. Clone Master includes everything in the plans below it, so recycle bin restore, version trimming, storage clean-up and archiving come with it. See pricing.
It depends entirely on where the content is coming from.
| Tool | Cost | Moves content from | Tenant to tenant? |
|---|---|---|---|
| SPMT (SharePoint Migration Tool, Microsoft) | Free | SharePoint Server 2010 to 2019, file shares | No |
| Migration Manager (Microsoft, in the admin centre) | Free | File shares and on-premises content, at scale with agents | No |
| Cross-tenant SharePoint migration (Microsoft) | Licensed | SharePoint Online | Yes, but Enterprise Agreement customers only |
| PnP PowerShell | Free, open source | Anything you can script | Yes, if you write it |
| ShareMaster (Clone Master plan) | $900/yr or $1,300/2yr | SharePoint Online and OneDrive, plus Dropbox | Yes |
| Enterprise migration suites | Quoted, typically far higher | Many sources | Yes |
If your source is on-premises or a file share, stop here and use SPMT. It is free, Microsoft supports it, and paying anyone for that job is a waste of money. We would rather tell you that than sell you something you do not need.
The one thing the free tools do not do is the thing people most often need: move SharePoint Online content from one Microsoft 365 tenant to another. Microsoft's own documentation is explicit that SPMT can migrate from on-premises SharePoint Server but not from another SharePoint tenant in Microsoft 365.
Microsoft does have a cross-tenant SharePoint migration capability. Per their documentation the feature and its licences are currently available only to Enterprise Agreement customers, and setup runs through PowerShell.
Sources: SPMT FAQ and Cross-tenant SharePoint migration overview, Microsoft Learn, checked 11 August 2026. Licensing terms change; verify against current Microsoft documentation before planning.
14-day free trial, no credit card. ShareMaster runs on your own Windows PC.