How to upgrade from SharePoint 2010 to SharePoint 2016 Step by Step (Part 2)

This post is the second part of a two part step by step tutorial on how to migrate a SharePoint 2010 farm to SharePoint 2016.

To read the first part, click here.

Introduction

The SharePoint world is rapidly moving into the Cloud with SharePoint Online and Office 365, but some organizations are still not ready to move completely to Office 365 and SharePoint Online.

Upgrading to SharePoint 2016 or SharePoint 2019 that have support for hybrid scenarios can be a valid solution.

This post is based on upgrading a SharePoint 2010 farm into SharePoint 2016 using the database attach approach but should also be valid if you want to upgrade to SharePoint 2019. This post assumes that the we will only migrate the content database(s) from the source SharePoint 2010 to SharePoint 2016 and all other SharePoint databases are created in the target SharePoint 2016 farm during its installation process.

If you want to learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, click here and here.

There is another valid migration approach to migrate from SharePoint 2010 to SharePoint 2016 by using content migration. In this approach, the upgrade is not based in a database upgrade process but on content migration and typically a 3rd party solution is necessary to do the content migration. A few 3rd party solutions that can do the job are ShareGate, AvePoint and Metalogix.

Upgrading a SharePoint farm using the database attach approach can be a complex task and the upgrade process is composed by a series of steps:

• Migrating Custom Developed Solutions from SharePoint 2010 to SharePoint 2016 (outside of the scope of this post)
• Upgrade to a temporary SharePoint 2013 farm
• Upgrade to the target SharePoint 2016 farm

IMPORTANT NOTE: In a typical upgrade process, the below steps should be performed twice if there are custom developed solutions:

• The first time, to test the migration process and allow custom developed solutions to be properly migrated and tested by the end users
• The second time, to perform the final migration, after all custom developed solutions are migrated and tested by the end users

This post will cover:

• Upgrade to the target SharePoint 2016 farm

Upgrade to the target SharePoint 2016 farm

IMPORTANT NOTES:

• Migrating from SharePoint 2010 directly to SharePoint 2016 is not supported. To migrate from SharePoint 2010 to SharePoint 2016 we must first migrate to a temporary SharePoint 2013 farm and then migrate to SharePoint 2016
• To to be able to migrate to SharePoint 2016, the temporary SharePoint 2013 farm must at least have the March 2013 Public Update installed. For more details, click here

The migration is performed using the database attach upgrade method (the only supported method to upgrade from SharePoint 2010 to SharePoint 2016 using a database upgrade approach).

In the upgrade process, for both the temporary SharePoint 2013 and the target SharePoint 2016 farms, you should create an empty web application so that a valid SharePoint content database is created. To learn more on how to install a SharePoint 2016 farm (process also valid for SharePoint 2013), click here and here.

After having all custom developed solutions migrated to SharePoint 2016 (if there are any), you should follow the following steps:

• SharePoint 2013: Go to “Manage content databases” in Central Administration, select the web application and then the option “Remove content database”. This will make the web application unattached from any web application in the temporary SharePoint 2013 farm

• SharePoint 2013 Database Server (final migration only): Place the database in read-write mode so that users will be able to change content in the target SharePoint 2016 farm. This can be achieved by the following T-SQL command: ALTER DATABASE <CONTENT_DB_NAME> SET read_write
• SharePoint 2013 Database Server: Backup of the content database(s)

• SharePoint 2013 (final migration only): Go to “Manage content databases” in Central Administration, select the web application, then the option “Add content database” and finally select the name of the content database previously removed. This will make the web application available again in the temporary SharePoint 2013 farm

• SharePoint 2016 Database Server: Copy the database backup file from the temporary SharePoint 2013 database server to the database server that supports the target SharePoint 2016 farm
• SharePoint 2016:  Go to “Manage content databases” in Central Administration, select the web application where you want to migrate to and then the option “Remove content database”. This will make the database unattached from any web application.

• SharePoint 2016 Database Server: Restore the content database backup from the temporary SharePoint 2013 database server. The restore must replace the content database that was created during the SharePoint 2016 installation.

• SharePoint 2016:  If you have custom developed farm solutions, deploy all the migrated WSPs in the target SharePoint 2016 farm.
• SharePoint 2016  Execute the first of a series of PowerShell commands to associate the restored content database to the SharePoint 2016 farm (in this example the web application URL is http://sp2016): Test-SPContentDatabase -Name <Content_DB_Name> -WebApplication http://sp2016
  
  • This PowerShell cmdlet will test the content database against the web application to verify if all customizations referenced within the content database are also installed in the farm
  • In my case, I got some missing features errors but none of them are upgrade blocking

• SharePoint 2016:  Execute the second of a series of PowerShell commands to associate the restored content database to the SharePoint 2016 farm: Mount-SPContentDatabase -Name “<Content_DB_Name>” -DatabaseServer “<DBAlias>” -WebApplication “http://sp2016”
  • This PowerShell cmdlet attaches an existing content database to a web application
  • In my case, no errors or warnings were shown

• SharePoint 2016:  Execute the third of a series of PowerShell commands to associate the restored content database to the SharePoint 2016 farm: Test-SPSite http://sp2016
  • This PowerShell cmdlet runs a series of health checks on the site collection and its contents
  • In my case, I got a warning but once again nothing that is upgrade blocking

• SharePoint 2016:  Execute the fourth of a series of PowerShell commands to associate the restored content database to the SharePoint 2016 farm: Repair-SPSite -identity http://sp2016
  • This PowerShell cmdlet is similar to the Test-SPSite cmdlet but fixes any issues that it finds
  • The result was identical to the Test-SPSite cmdlet: no upgrading blocking issues were found

• SharePoint 2016:  Execute the fifth of a series of PowerShell commands to associate the restored content database to the SharePoint 2016 farm: Upgrade-SPSite http://sp2016 -VersionUpgrade
  • This PowerShell cmdlet will upgrade the site collections associated to the web application to SharePoint 2016 mode. Before this cmdlet was executed, the site collections were still in SharePoint 2013 mode.

After the migration is complete, your SharePoint web application is successfully displayed in your brand new SharePoint 2016 environment!

To read the first part of this two part step by step tutorial, click here.

Related Articles

If you want to convert your tenant’s root classic site into a modern SharePoint site, click here.

To learn why your business should migrate to SharePoint Online and Office 365, click here and here.

If you are a SharePoint administrator or a SharePoint developer who wants to learn more about how to install a SharePoint 2019 farm in an automated way using PowerShell, I invite you to click here and here.

If you want to learn how to upgrade a SharePoint 2013 farm to SharePoint 2019, click here and here.

If you want to learn all the steps and precautions necessary to successfully keep your SharePoint farm updated and be ready to start your move to the cloud, click here.

If you learn how to greatly speed up your SharePoint farm update process to ensure your SharePoint farm keeps updated and you stay one step closer to start your move to the cloud, click here.

If SharePoint 2019 is still not an option, you can learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, click here and here.

If you are new to SharePoint and Office 365 and want to learn all about it, take a look at these learning resources.

If you are work in a large organization who is using Office 365 or thinking to move to Office 365 and is considering between a single or multiple Office 365 tenants, I invite you to read this article.

If you want to know all about the latest SharePoint and Office 365 announcements from SharePoint Conference 2019, click here and here.

If your organization is still not ready to go all in to SharePoint Online and Office 365, a hybrid scenario may be the best choice. SharePoint 2019 RTM was recently announced and if you to learn all about SharePoint 2019 and all its features, click here.

Happy SharePointing!