Fix the SharePoint Could Not Replace Root Site Error
Question details
The user needs to replace a SharePoint root site without encountering a site replacement error.

- Product
- SharePoint Online
- Device & OS
- not provided
- Scenario
- Replacing the tenant's root site with another SharePoint site.
- Observed behavior
- The replacement fails with a "Could not replace root site" message when the replacement site is a classic team site or certain modern sites not connected to a group.
Sign in with an account that has the SharePoint administrator or global administrator role, and identify the current root site and the site you want to use as its replacement. Check Microsoft's current site replacement requirements, including whether the replacement site is eligible.
Replace the Root Site with a Communication Site
Use a communication site as the replacement when a team site triggers the error.
The reported issue affected some classic and modern non-group sites. A communication site was a reliable workaround in the reported case; current eligibility requirements may differ.
In SharePoint, select Create site, choose Communication site, and complete the setup, or identify an existing eligible communication site.
In the SharePoint admin center, go to Sites > Active sites and select the tenant's root site.
Select Replace site, enter the communication site's URL as the replacement, and follow the prompts to complete the operation.
Open the tenant's root site URL in a browser and confirm that the communication site appears.

Check Site Swap Warnings with SharePoint PowerShell
Use PowerShell to investigate a failed replacement and capture any site-type warning.
Work with Office Documents While Managing SharePoint Sites
WPS Office is a free, lightweight alternative for working with documents in a familiar interface. Its Microsoft Office format compatibility helps with a seamless move between office suites, although it cannot fix SharePoint site replacement errors.

Frequently Asked Questions
Why does SharePoint say it could not replace the root site?
The replacement site may be ineligible, or the operation may encounter a SharePoint issue. In the reported case, some classic team sites and modern non-group sites failed; check the site against Microsoft's current replacement requirements.
Can I use a team site instead of a communication site?
Some non-communication sites may be eligible under Microsoft's current rules, but the reported issue affected certain team sites. If an eligible site fails, check service advisories in the Microsoft 365 admin center or contact Microsoft support.
How can I see a more specific site swap warning?
Connect to SharePoint Online with Connect-SPOService and review the output from Invoke-SPOSiteSwap. The command attempts the replacement, so verify the source, target, and archive URLs first.
What happens to the existing root site?
A successful site replacement moves the existing root site to an archive URL. Review the replacement prompts or Microsoft's current documentation for the archive details before proceeding.




