SharePoint 2016 detects legacy sites while testing database from SharePoint 2013

Question

I'm attempting to mount a database from a SharePoint 2013 server, but I get the following error: "14 site(s) using SharePoint 2010 experience".

I've already deleted a few site collections that couldn't be upgraded on the selected content database, and I ran the 'Upgrade-SPContentDatabase' command in SharePoint PowerShell which confirmed that the database is up to date. Not sure where else to go here. Is there a PowerShell command to check the version of the site collection and upgrade that site collection if it is somehow causing the issue? Maybe the subsites inside of that site collection are causing the issue.

Answer 1

Hi @Max Johnson ，

It seems that you have some sites that are still using the SharePoint 2010 experience, which is not compatible with the SharePoint 2016 farm.

You must upgrade all SharePoint 2010 mode sites to 2013 mode (that is, compatibility level 15) on the existing 2013 farm before you mount the database on the new SharePoint 2016 farm. You can use the following PowerShell command to check the compatibility level of a site collection:

Run below powershell to check if all site collection are in the same version:

get-spsite 

For example, here are my test results：

If there are sites with a collection compatibility level other than 15, run below script to upgrade Sites:

$webApps = Get-SPWebApplication -Identity "http://servername:12345/"
$sites = $webApps.Sites>
foreach($site in $sites)
{ Upgrade-SPSite -Identity $site -VersionUpgrade -Unthrottled $site.Dispose() }

Hope the information can help you.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.