Migrate from SharePoint 2010 to SharePoint 2016

Migration approach

Basically, migration of SharePoint 2010 to 2016 is not directly supported and this is the biggest challenge companies may face. So, if you want to upgrade the version, you must pass all the relevant databases through SharePoint 2013 beforehand.

Since the 2010 project solution cannot run directly in 2016, any custom farm solutions you have must be upgraded to 2016, which will be very easy, however there will be issues around deprecated features.

Before migration, keep the following points in mind:

• Update SharePoint 2010 with latest service packs/patches
• Change SharePoint 2010 web application authentication mode from classic to claim
• Delete unused features and remove sites as well as users that are not used in SharePoint 2010 web application

Database migration steps:

1. Configure a new SharePoint 2013 Farm

The first step in migration is to install and configure the SharePoint 2013 farm. Install the required third party software or custom features to the SharePoint 2013 farm. Create a web application similar to SharePoint 2010 for SharePoint 2013. You have to use existing database from the SharePoint 2010 web application, and hence, delete default content database linked with the new web application.

2. Backup restore content database from 2010 to 2013

Create a backup of the SharePoint 2010 web application content database and then restore it to SharePoint 2013 SQL server.

There are two ways to get a content database of the web application:

I. Central Administration – Application Management – Management Content Databases

II. Using Powershell:

Get-SPContentDatabase -WebApplication ‘Web Application url’ | Select Name

3. Upgrade content databases and site collections(2013)

To verify the content database for a new web application, run the following command in PowerShell cmdlet

Test-SPContentDatabase -Name <Database name> -WebApplication ‘Web Application URL’

The above syntax report rectifies various issues when you migrate from SP 2010 to SP 2013 or migrate from SP 2013 to SP 2016 such as missing site templates, features, and other solutions dependencies etc.

4. Create SharePoint 2016 farm

After fixing all the issues reported by Test-SPContentDatabase, you can run the Mount-SPContentDatabase for attaching content databases to the SharePoint 2013 web application.

Mount-SPContentDatabase -Name ‘Database name’ -DatabaseServer ‘DB Server Name’ -WebApplication ‘Web Application URL’ -confirm: $false

5. Backup restore content database from 2013 to 2016

After running attached content database you can access site collection in SharePoint 2010 mode. This can be done by clicking on the upgrade reminder banner in a site collection.

6. Upgrade content databases and site collections(2016)