Step by Step Guide to Migrate from SharePoint 2010 to SharePoint 2013

Sandeep Saxena | Updated On - May 02, 2023 |

Read time 9 minutes

The charm of the latest added features drives migration from an older version to a new one of any platform. Similarly, it is the case with SharePoint as well. As you know, SharePoint 2010 version became very popular among organizations after its release due to its essential features and remarkable collaboration capabilities. After capturing the user’s requirements with SharePoint 2010, Microsoft developed SharePoint 2013, loaded with even better utilities.

With the launch of SharePoint 2013, SharePoint’s market share and positioning have reached a completely different level. However, SharePoint 2010 is still used across many organizations, and most look forward to upgrading SharePoint 2010 to 2013 for a more robust and immensely successful experience.

If you also want to migrate SharePoint 2010 to SharePoint 2013 so that you can include the latest features in your network and enhance the productivity of your work, then this guide is for you. Here, we have discussed a method that utilizes the database-attach approach, which involves creating and configuring a SharePoint 2013 farm and then copying the databases of content and service applications from the SharePoint 2010 Products farm. After upgrading SharePoint 2010 to 2013 version, site owners can upgrade individual site collections.

Pre-requisites to migrate from SharePoint 2010 to SharePoint 2013-

Like the conditions required to migrate Exchange 2010 Public Folders to Office 365, keep the requirements below in mind before migrating SharePoint 2010 to 2013.

• Update SharePoint 2010 farm on your SharePoint 2010 farm with the latest service packs/patches
• Update SharePoint 2010 farm with latest service packs/patches installed on your SharePoint 2010 farm
• Document farm configuration settings in SharePoint Server 2010
• Change your SharePoint 2010 web applications from classic mode to claims
• Clean up the environment by deleting unused site collection, removing unused features, and deleting orphaned users and sites. Also, clean up old document versions and remove features that are not supported by SharePoint 2013

And don’t forget to run a database consistency check before backing up the database of the SharePoint 2010 farm.

Note: There is no direct procedure to migrate from SharePoint 2010 to SharePoint 2013. You can’t reuse your existing Hardware for SharePoint 2013 or install both SharePoint 2010 and SharePoint 2013 on the same machine. So, the only way to upgrade is to migrate.

We will briefly overview the direct method of SharePoint 2010 to SharePoint 2013 migration. This process involves multiple steps, as given below:

The first step in migration is to install and configure a new SharePoint 2013 farm. Set up all farm configurations in Source SharePoint 2010 farm, including all essential configurations such as AAM, Email settings, managed pats, etc. Then, install all the third-party software, language packs, custom features, and solutions of SharePoint 2010 farm into your SharePoint 2013 farm. Create a web application similar to your existing SharePoint 2010 farm for SharePoint 2013 farm.

Since we use the existing content database from SharePoint 2010, you can delete the default content database linked with the new web application. If you fail to delete the root site database of the existing web application, running a “Test-SPContentDatabase” cmdlet as a part of the migration process can result in orphaned site issues. This happens because the root site collection exists in both content databases, resulting in conflict.

Also, the farm administrator should set the SharePoint 2010 Products to read-only status. This will allow users to access the old database even during the migration.

Next, you must create a backup of the SharePoint 2010 content databases and restore them to SharePoint 2013’s SQL Server.

It can be done in two ways, using central administration or using PowerShell cmdlet.

1. By using central administration: To retrieve all content databases of a particular web application, you must identify and list all source content databases from central administration.

   You can do it by following this path in your SharePoint 2010:

   (Central Administration >> Application Management >> Manage Content Databases)
   

2. By using the PowerShell cmdlet: Use the PowerShell cmdlet to retrieve all content databases of a particular web application.

   Use the below syntax:

   Get-SPContentDatabase -Web Application “<Site Name>” | Select Name

You can create a backup of databases from the SharePoint 2010 SQL Server by logging into the SQL server box of the SharePoint 2010 farm. And then, all you’ve to do is open SQL Server Management Studio and expand the databases node.

To restore all databases from SharePoint 2010 to SharePoint 2013 SQL Server, copy all required databases backup files to your target SharePoint 2013’s SQL Server database location. Once you have copied the database files, the next step is to open the SQL Server Management Studio and click Restore Database.

Simply execute the PowerShell cmdlet: Test-SPContentDatabase cmdlet and scan content databases of the provided web application.

For this, you can use the syntax:

This syntax will report various issues such as missing features, solution dependencies, orphaned sites, wide lists, etc.

Once you’ve fixed all the issues reported by Test-SPContentDatabase, you can start attaching content databases to SharePoint 2013 web application. Always try to mount the root site collection’s database first, and if you’re migrating ‘My sites,’ then migrate its host first.

After mounting the content database to the web application, you can easily access the site collection in SharePoint 2010 mode.

The last step in this migration process is upgrading the site collections. After migrating from SharePoint 2010 to SharePoint 2013, all migrated site collections will be on SharePoint 2010 with their old look and feel and other functionalities. Therefore, you’ve to migrate all site collections to SharePoint 2013 explicitly. Site Collection administrators can do this by clicking on the links available from the upgrade reminder banner.

Upgrades are time-consuming when many site collections are on a particular content database. You can easily get the upgrade status from the “Upgrade Status” on the central administration page.

Follow this path:

Here is the SharePoint 2010 site migrated to SharePoint 2013:

The Final site after the site collection upgrade:

Thus, you can successfully migrate SharePoint 2010 to SharePoint 2013.

1. It doesn’t support granular migration.
2. It is very time-consuming.
3. You can verify content before migration, but for that, you should have knowledge of various PowerShell commands.
4. With it, you can’t migrate unlimited content with utmost concurrency.
5. Confusion due to the involvement of multiple steps
6. Manual migration will increase the chances of errors and data loss.

Due to these limitations, organizations face various challenges while migrating to SharePoint 2013.

Fortunately, Kernel Migrator for SharePoint (KMS)– an automated SharePoint migration solution to migrate content from SharePoint 2010 to SharePoint 2013 is designed to overcome the limitations of the native migration method.

It helps you to avoid these risks by lessening the time and expenses involved in the migration. Also, it ensures complete data integrity.

• Its installation and user interface are quite user-friendly.
• Not only content, but it also migrates metadata automatically during migration.
• Users can easily remap between Source and SharePoint Servers.
• It also migrates permissions from the Source to the destination.
• It allows you to schedule the migration jobs to create an unbroken one-way synchronization between two lists, libraries, or sites of the same/different SharePoint Server. The selected destination will be synchronized with the new/updated content and objects of the source.
• Migrate a large amount of content in bulk or perform granular migration to move only the needed content.
• Migrates document versions between SharePoint platforms
• Added migration facilities – File Systems, Public Folders, OneDrive, and Google Drive

1. Add Source – Add SharePoint 2010
2. Add Destination – Add SharePoint 2013
3. Create Migration jobs to perform simple and timely migration. You can migrate site, list/library, and items from source SharePoint to destination SharePoint.
4. Schedule the content migration jobs from SharePoint 2010 to SharePoint 2013.
5. You can also perform bulk migration of the site, list/library, and items using CSV files.
6. With Migration history, view the stored records of all real-time migration jobs, scheduled migration jobs, and downloads from SharePoint.

Note: You can experience the tool’s functioning by downloading its free trial version from its website.

Yes, migration can be that simple!

When you have such an easy and simple way to perform the migration, then why go for native migration methods? With Kernel Migrator for SharePoint, organizations can have better control over the migration process and can solve a wide variety of common, yet complex migration scenarios.