I want to upgrade sharepoint 2013 on-premise to sharepoint 2016 on-premise I have tried Database attach option for 2 weeks but had some problems that couldnt troublshout after all and because we only need one of our subsites to be upgraded in 2016 i decided to look for a another way only to migrate this subsite to our new environment i have tried backup-spsite from site collection but had some errors related to sql corruption I appreciate any help


2 Answers 2


What is the error you are getting while doing the content db migration, would you please share here? By the way for common troubleshooting in content db migration, you may refer the below article :

SharePoint Migration: Basic tips and tricks in migration project

As a second approach, you may use the third party migration tool like sharegate, Metalogix or Microsoft SharePoint migration tool.

Sharegate and Metalogix - trial version is available, you can download it and Microsoft SharePoint Migration tool is a free version, you may use this as well.

Metalogix Download Location :


Sharegate Download Location :


Microsoft SharePoint Migration tool Download location :


  • i have found database name of my web application and site collections by get-spcontentdatabase next i backed up successfully from sql ms and then restored it
    – sinaazar
    Jan 12, 2020 at 14:43
  • i have found database name of my web application and site collections by get-spcontentdatabase next i backed up successfully from sql ms and then restored it after run test-spcontentdatabase against my web app in new environment it appeared some missing assembly and webparts but no upgrade blocking so i mounted and it succesfully finished after that i defined managed path in central admin but when i open my main site collection it says "sorry sth went wrong . an unexpected error has occured" i did troubleshout lots of errors up to reaching this point but i cant find cause of this..
    – sinaazar
    Jan 12, 2020 at 14:50
  • do you have any link about how to upgrade with metalogix?
    – sinaazar
    Jan 12, 2020 at 14:55
  • 01/12/2020 18:40:56.16 w3wp.exe (0x5904) 0x0064 SharePoint Foundation General b9y3 High Failed to open the file 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\Resources\core.fa-IR.resx'. bac72a9f-f7be-50ca-e636-5d85b911b5ee
    – sinaazar
    Jan 12, 2020 at 15:14
  • above comment is one of high level events in uls logs based on correllation ID
    – sinaazar
    Jan 12, 2020 at 15:15

If it is just one site, I would try Export-SPWeb (or stsadm -o export) to export the site.

Then copy the files to the new server and use Import-SPWeb (or stsadm -o import).

For individual sites and libraries, I have found it to be more reliable than backup or saving the site as a template with content.

It’s not always as full fidelity as I would like depending on the site though.

To clear the site collection lock:

$site = Get-SPSite https://yourSP.com
  • i tried to export a subsite(intranet/adm/pmo) it exported into 7 .cmp file ...should i import all of them? and should i create new empty site collection in 2016 farm or it will be created automaticlly?
    – sinaazar
    Jan 13, 2020 at 5:48
  • i tried to import it like this "import-spweb -identity "portal:82/adm/pmo" -path c:\pmo-backup\pmo.cmp
    – sinaazar
    Jan 13, 2020 at 5:51
  • i got this error---->"cannot add content to the site collection because it is locked ..."
    – sinaazar
    Jan 13, 2020 at 5:53
  • See the end of my edited comment above for the commands to clear the site collection lock.
    – mannaggia
    Jan 13, 2020 at 9:10
  • And you only import one file. Use the same name you used in the export command.
    – mannaggia
    Jan 13, 2020 at 9:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.