ShareMaster is shaped by your feedback. Tell us what to build next →
Features All features overview
Migration Tools Overview Structure and content OneDrive ↔ SharePoint Content only Structure only Move / Copy Upload from this computer Download to this computer Dropbox to SharePoint Copy a team Resume and incremental runs
Recycling Bin Overview Browse a site's recycle bin Empty recycle bins in bulk Restore and purge history
Archive Overview Configure the tenant On Demand Archive Restore Archived Files Archive Savings Report Blob Viewer
Optimise Storage Tools Overview Delete all items in a list Delete all files and folders in a library Remove empty folders Remove duplicate files Reduce image sizes Delete sites and subsites
SharePoint Tools Overview Tenant Explorer SharePoint Explorer Easy Settings Fix renamed groups List Explorer Search the Preservation Hold Library
Search & Indexing Overview Search query Item search properties Reindex Crawl log
Replace Overview Replace in SharePoint Replace in local files Find password-protected files
Shared Links Overview Report shared links Report unique permissions Remove a person from sharing links Remove shared links Remove unique permissions
Version History Overview Version trimming Version trimming report Reset file version
Reports Overview Inventory report Folder inventory Site and subsite storage Storage growth Security matrix Teams permissions Pre-migration analysis Compare items Dropbox to Microsoft 365 compare Duplicate file report Empty folder report Image size report Recycle bin report Unused licences Report history
Developer Tools Overview Query Builder PnPjs Console Property Bags SPFx Customizers Webhooks Customisation audit
V2 Pricing Services Demos Blog Guides Use cases Compare Tools Alerts FAQ Contact
  1. Home
  2. Compare
  3. SharePoint Site Cloning Options

Cloning a SharePoint Site: 4 Options Compared

Four ways to copy a SharePoint site exist today, and they are not equal. Pick the wrong one and you lose permissions, metadata, or hours of effort finding out afterwards.

Method Copies files Copies permissions Cross-tenant Effort
Manual download / upload Files only No Yes Very high
SharePoint admin backup / restore Yes Yes No Medium
PnP PowerShell Partial Partial Limited High
Clone Master Yes Yes Yes Low

Option 1: Manual Download and Upload

The simplest approach for small sites: download files via the browser or OneDrive Sync, then upload them to the destination. For a site with one document library, no custom lists, and permissions that will be set fresh at the destination, this works.

At scale it falls apart quickly. File metadata - modified date, created-by, and version history - does not survive a manual download. No permissions transfer. You must recreate lists with lookup columns, calculated fields, and content types by hand. Any site with several hundred files or more than a couple of lists becomes a multi-day project.

When manual copy makes sense

  • Fewer than 100 files, no custom lists or content types
  • Permissions will be configured from scratch at the destination
  • No tooling budget and the site structure is trivially simple

Option 2: SharePoint Admin Backup and Restore

Microsoft 365 admins can back up individual site collections from the SharePoint admin centre and restore them to a new URL within the same tenant. This preserves site structure, permissions, lists, and file content, making it a genuine alternative to manual work for same-tenant scenarios.

Key limitations to understand

  • Same tenant only. Restoring to a different Microsoft 365 tenant is not supported.
  • Backup policy required. A Microsoft 365 Backup storage policy must be active for the site before you can trigger a restore.
  • Blunt instrument. Backup/restore creates a full site replica at a new URL. You cannot selectively clone a single library or list from a larger site.
  • Storage cost. Backup retention periods add to your Microsoft 365 storage footprint.
Note: The SharePoint admin backup/restore is designed for disaster recovery and rollback, not routine site cloning. It is the right tool when you need an exact same-tenant replica but a poor fit for anything more surgical.

Option 3: PnP PowerShell

PnP PowerShell exposes cmdlets such as Get-PnPList, Copy-PnPFile, and Add-PnPListItem that can reconstruct a site's structure and content programmatically. It is the most flexible manual path for admins comfortable with scripting.

What PnP PowerShell handles well

  • Creating list and library schemas at the destination
  • Applying content type associations programmatically
  • Automating repetitive structure provisioning across many new sites

Where it struggles

  • Permission cloning requires additional Set-PnPListItemPermission loops that add significant script complexity
  • Large libraries throttle under Microsoft 365 API rate limits without careful retry logic
  • Cross-tenant scenarios require app registrations in both tenants and token management
  • Scripts need ongoing maintenance as the SharePoint API evolves

For template-driven site provisioning across many sites, PnP PowerShell is the right choice. For a one-off clone of a real site with live data, the script development time often exceeds the alternative.

Option 4: Clone Master

Clone Master is the dedicated site migration and cloning tool in the ShareMaster suite. It connects to source and destination sites from the Windows desktop, with no scripting required.

  1. Connect to the source SharePoint site using your Microsoft 365 account.
  2. Select the lists, libraries, or entire site to clone.
  3. Connect to the destination (same tenant or a different tenant).
  4. Map source elements to destination locations.
  5. Run the migration. Clone Master handles throttling, retries, and permission mapping automatically.

Files, list items, metadata, version history, and permissions all transfer without additional scripting. Cross-tenant site cloning, which normally requires significant infrastructure work with PnP or third-party enterprise tools, becomes a point-and-click operation.

Learn more about Clone Master

Decision Matrix: Which Option Fits Your Situation?

Your situation Best option
Tiny site, files only, permissions set fresh at destination Manual download / upload
Full site replica within the same tenant, disaster recovery context SharePoint admin backup / restore
Templated site provisioning or automating structure at scale PnP PowerShell
Complete clone with permissions, metadata, or cross-tenant destination Clone Master

For a step-by-step walkthrough of a full cross-tenant migration, see the related guide on migrating a SharePoint site to another tenant. For a broader tool comparison including enterprise migration platforms, see the Clone Master vs ShareGate vs Migration Manager comparison.

Frequently Asked Questions

Can you copy an entire SharePoint site including permissions?

Yes, but not with every method. Manual download/upload and basic PowerShell scripts typically exclude permissions. SharePoint admin backup/restore preserves permissions within the same tenant. Clone Master copies site structure, lists, libraries, files, and permissions across sites and tenants.

Does SharePoint Online have a built-in site clone feature?

SharePoint Online does not have a one-click site clone. The closest native options are the SharePoint admin backup/restore (same tenant only) and saving a classic site as a .wsp template. Modern communication and team sites have limited template support that does not carry content.

What is the easiest way to clone a SharePoint site to another tenant?

Cross-tenant cloning requires a dedicated migration tool. Native SharePoint features do not support moving sites between Microsoft 365 tenants. Clone Master connects to both tenants, copies site structure and files, and re-maps permissions at the destination without PowerShell scripting.

Last updated