Read time 9 minutes
This guide elucidates the step-by-step process for transitioning from SharePoint 2010 to SharePoint 2016 through a two-stage procedure. Given that there is no direct upgrade path available, the first stage involves upgrading from SharePoint 2010 to SharePoint 2013 followed by a subsequent upgrade from SharePoint 2013 to SharePoint 2016.
SharePoint 2016 has many advanced features. That is why SharePoint 2010 users want to migrate to SharePoint 2016. Some new features in SharePoint 2016 are:
Upgrading from one version of SharePoint Server to another version is a sequential procedure with the steps:
We are adhering to a two-step process to transition from SharePoint Server 2010 to SharePoint Server 2016. Consequently, we must traverse these five stages for each of the two phases: first, the SharePoint 2010 to SharePoint 2013 upgrade, and then the SharePoint 2013 to SharePoint 2016 upgrade.
Download an automated tool, Kernel Migration for SharePoint to perform bulk migration from SharePoint 2010 to SharePoint 2016.
There are certain things to know before migrating to SharePoint 2016. So, let us start the manual process for the migration.
Before upgrading the content, a new server farm needs to be created in SharePoint 2016.
Prerequisites for creating a new SharePoint Server 2016 farm
Now, create the SharePoint Server 2013 farm –
In this step, you have to create a SharePoint 2010 web application, create backups of the SharePoint 2010 content databases and then restore them into the SQL Server of SharePoint 2013.
You can either use central administration or PowerShell cmdlets to retrieve all content databases of the web application.
If using central administration, navigate to Central Administration >> Application Management >> Manage Content Databases.
If using PowerShell cmdlet, the syntax is:
To initiate the transfer of the backed-up databases to the fresh SharePoint server, commence by launching the 2013 SQL Server Management Studio. Once opened, navigate to the Object Explorer and establish a connection to the database. Expand the Database section, locate your specific database, right-click on it, and opt for Restore Database. Proceed by supplying the necessary information and following through with the procedure until completion.
The migration of SharePoint 2010 service applications to a recently established SharePoint farm necessitates the deployment of one or more SQL Servers for each service application. The list of service applications slated for migration from SharePoint 2010 to SharePoint 2013 encompasses Business Data Connectivity, Managed Metadata, PerformancePoint Services, Secure Store, Search, and User Profile.
To upgrade the service applications databases, follow the procedure:
# Stores the identity for the Search service instance on this server as a variable
# Starts the service instance
Upgrade Secure Store service application by typing the following command:
Use this cmdlet to view the proxies in the default group:
Scan content databases of the web application by running this PowerShell command:
It helps in reporting various issues – missing features, solution dependencies, orphaned sites, wide lists, etc.
After this test, attach content databases to SharePoint Server 2013 web applications. First mount the root site collection’s database. If migrating ‘My sites,’ then migrate its host first. Run this command:
Now, you can easily access site collection in SharePoint 2010 mode.
The subsequent phase involves the enhancement of site collections, necessitating the transformation of SharePoint Server 2010’s outdated appearance and features. To accomplish this, the site collection administrator must transfer all site collections to SharePoint Server 2013. This can be achieved by simply selecting the links provided in the upgrade reminder banner within the site collection.
To verify Site Collection upgrade, within the Site Collection, go to Site Settings > Site Collection Administration > Site Collection upgrade > Review Site Collection Upgrade Status. Thus, you can view the upgrade status for the Site Collection.
You can easily get the upgrade status from the Upgrade Status page in Central Administration (follow Central Admin > Upgrade and Migration > Check upgrade status).
Thus, the SharePoint Server 2010 database is migrated to SharePoint Server 2013.
The objective now is to perform an upgrade from SharePoint Server 2013 to SharePoint Server 2016. To accomplish this, it’s necessary to establish a SharePoint 2016 farm. Subsequently, follow the same procedure used during the previous upgrade from SharePoint Server 2010 to SharePoint Server 2013, involving the backup and restoration of the SharePoint Server 2013 database. The steps closely resemble the earlier process, with the key distinction being the transition between SharePoint Server 2013 and SharePoint Server 2016. Notably, unlike the previous upgrade, there’s no requirement to create a new web application in this case, as the database is being migrated into an existing production-ready web application, SharePoint Server 2016. Consequently, the upgrade from SharePoint 2013 to SharePoint 2016 can be accomplished manually.
Upgrading from one SharePoint Server version to another manually is feasible. But it is a quite complex process. It is time-consuming and error-prone. Also, technical knowledge of PowerShell commands is needed.
Effortless data migration between SharePoint Server (2010) and SharePoint Server (2016) can be achieved through the utilization of professional software designed for upgrading or downgrading SharePoint versions, including SharePoint Server 2010, 2013, 2016, and 2019, as well as SharePoint Online within Microsoft 365. This SharePoint Migration tool boasts a user-friendly interface and facilitates seamless migration between various SharePoint versions. It enables bulk migration of sites, libraries, and more, user mapping, metadata and permissions migration, and even offers the convenience of scheduling migrations. Furthermore, this tool supports migration for both SharePoint on-premises and SharePoint Online environments. For additional information, please visit the website.
The process of migrating from SharePoint 2010 to SharePoint 2016 manually consists of two sequential stages, presenting inherent complexity and difficulty, particularly for users with technical backgrounds. Consequently, it is advisable to opt for an automated migration tool to ensure a seamless and straightforward transition.