Microsoft 365 Migration

Move a SharePoint Subsite to a New Root Site Collection

Jason MillerJason Miller Nov 14, 2026 868 views

Question details

The user wants to move a SharePoint subsite so that it becomes the root site of a separate site collection.

Product
Microsoft SharePoint
Device & OS
not provided
Scenario
A SharePoint administrator needs to separate an existing subsite into its own site collection while retaining the required content and configuration.
Observed behavior
A SharePoint subsite cannot be converted into the root of a separate site collection through a standard setting.
Before you start

Identify whether the source is SharePoint Online or SharePoint Server, and confirm that you have the necessary administrator permissions. Inventory the subsite's libraries, lists, pages, permissions, workflows, and customizations before selecting a migration approach.

Solution 1Recommended

Create a Site Collection and Migrate the Subsite Content

Use this approach when the subsite needs its own site collection and its required content and settings must be recreated or migrated.

This is a migration, not an in-place conversion. The available tools and procedures depend on the SharePoint version and the types of content and customizations involved.

A new site collection has its own root site. It is not necessarily the tenant's existing root site.

1
Review the source subsite

Open the subsite and review its Site contents and site settings. Record the libraries, lists, pages, permissions, workflows, and customizations that must be moved or rebuilt.

2
Create the destination

For SharePoint Online, open the SharePoint admin center, select Sites > Active sites, and choose Create. Select an appropriate site type and URL for the new site collection. For SharePoint Server, use the administration procedure for your version.

3
Choose a migration method

Review Microsoft documentation and the capabilities of any migration tool for your source and destination. Confirm support for the required content, metadata, version history, and permissions before running a test migration.

4
Move and validate

Use the selected tool or administration procedure to migrate the required content. Open the destination site to check pages, files, lists, access, links, and functionality; recreate any settings or customizations that the method does not transfer.

5
Plan the cutover

After validation, coordinate a final content update with site owners and direct users to the new site URL. Review links and integrations that still point to the old subsite.

Create a Site Collection and Migrate the Subsite Content
Get version-specific guidance: If the migration requires PowerShell or complex customizations, consult Microsoft Support or the Microsoft SharePoint community with your SharePoint version and migration requirements.
Free Microsoft Office alternative

Work With Office Documents in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for working with Office documents after a move. It does not migrate SharePoint sites, permissions, or configuration.

Open and edit documents used by your team alongside a SharePoint migrationCompatible with Microsoft Word, Excel, and PowerPoint file formatsFamiliar editing tools make the transition easierFree and lightweight for everyday document work
microsoft office alternative - wps office

Frequently Asked Questions

Can I convert a SharePoint subsite into a separate site collection with a setting?

No. Create a new site collection and use an appropriate migration approach to move the required content and recreate settings that cannot be transferred.

Will permissions and version history move automatically?

Not necessarily. Check the selected migration tool's documentation for support, then test permissions and version history on the destination before cutover.

Where do I create a new SharePoint Online site collection?

In the SharePoint admin center, go to Sites > Active sites and select Create. Choose the site type and URL that suit the destination.

Does a new site collection replace the tenant root site?

No. A new site collection has its own root site, but creating it does not automatically replace the tenant's existing root site.

What should I do if the subsite contains custom workflows?

Inventory the workflows in the source site and check whether the chosen migration method supports them. Plan to rebuild or replace unsupported workflows and test them at the destination.