Moving a SharePoint subsite to another site collection or modern SharePoint site isn’t as straightforward as dragging and dropping. SharePoint doesn’t offer a native “Move Subsite” button, so you need to use workarounds like Save as Template or PowerShell scripts. In this article, we’ll walk you through how to move a SharePoint subsite to another site efficiently and securely.
Before diving into the how-to, let’s understand the reasons for moving a subsite:
Migrating from classic to modern experience
Restructuring your SharePoint architecture
Moving content to another site collection or tenant
Enforcing compliance or access control policies
Preparing for a SharePoint Online flat architecture
No. SharePoint Online does not provide a built-in feature to move a subsite directly to another site collection or site. You must recreate and migrate the content using workarounds such as:
Save as Template + Import
PowerShell + PnP cmdlets
Manually recreating the subsite and migrating data
Let’s break these down.
Navigate to the Subsite.
Go to:
Site Settings > Save site as template
(If not visible, append /_layouts/15/savetmpl.aspx
to your URL.)
Check "Include Content" (if needed) and save.
Download the .wsp
file once the template is saved.
Navigate to the target site > Site Settings > Solutions.
Upload and activate the .wsp
file.
Create a new subsite using that template.
Related article: How to Create a Blog in SharePoint Online
Install PnP.PowerShell
Connect to both source and target sites
Tip: Always test on a dev environment before running in production.
If the subsite is small, you can manually recreate the subsite structure and use:
OneDrive sync for documents
Copy-paste for pages and lists
Site scripts or JSON templates for settings
Permissions: Reapply site permissions after migration.
Workflows: Rebuild Power Automate or SharePoint Designer workflows.
Navigation: Update links pointing to the old subsite.
Metadata: Preserve content types, columns, and views.
Testing: Validate the migrated site thoroughly.
Read also: Set Retention Policy in SharePoint Online
An organization had an HR subsite under their main portal. As part of a modernization effort, they created a new HR communication site and used ShareGate to:
Migrate libraries, lists, and pages
Retain metadata and permissions
Modernize classic web parts
They updated links and removed the old subsite post-validation.
Plan first: List what content needs to be migrated.
Assess compatibility: Classic vs modern, custom scripts.
Automate with PowerShell where feasible.
Test migrations on a trial site.
Archive the old subsite instead of immediate deletion.
Back up before migrating.
Additional resource: Move Documents from One SharePoint Site to Another
Although there’s no built-in method to move a SharePoint subsite to another site, you have multiple reliable options depending on your needs. Whether you use PowerShell, templates, or premium tools, ensure you test thoroughly, back up your data, and follow best practices to avoid disruption.
No direct way. You must export and import content using a tool like ShareGate or PowerShell across tenants.
No. Microsoft recommends flat site architecture using hub sites instead of subsites.
Not always. Custom scripts, workflows, and permissions may need manual work.
Related article: SharePoint Tenant to Tenant migration