Read time 9 minutes
Migration from an older version to a new one is driven by the charm of new features added in the newer versions. This applies to SharePoint as well. SharePoint 2013 was Microsoft’s next SharePoint version loaded with some great features after capturing the imagination of users with SharePoint 2010. As you know, SharePoint 2010 version became very popular among organizations after its release, due to its basic features and remarkable collaboration capabilities.
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 organizations and many of these organizations are looking forward to upgrading to the more powerful and immensely successful 2013 version. This context is relevant even after the release of many new SharePoint versions. This is because there are many users who still use older SharePoint versions like SharePoint 2010.
If you also want to integrate SharePoint 2013 features into your network, then this guide is for you. This method utilizes the database-attach method to upgrade from SharePoint 2010 to SharePoint 2013. This involves creating and configuring a SharePoint 2013 farm and then copying the databases of content and service applications to it from the SharePoint 2010 Products farm. After upgrading to the new version, site owners can upgrade individual site collections.
Pre-requisites for SharePoint 2010 to SharePoint 2013 migration
Before you start migration keep these things in mind –
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 upgrade possible from SharePoint 2010 to SharePoint 2013. So, the only way to upgrade is to migrate. You can’t reuse your existing Hardware for SharePoint 2013 and you can’t install both SharePoint 2010 and SharePoint 2013 on the same machine.
Kernel Migrator for SharePoint offers easy migration from SharePoint to SharePoint, public folders to SharePoint, and File System to One-drive, Google drive, SharePoint and Microsoft Teams.
We will provide a brie of overview of direct upgrade from SharePoint 2010 to SharePoint 2013. This involves multiple steps as given below:
The very first step in migration is to install and configure a new SharePoint 2013 farm. Setup all farm configuration in source SharePoint 2010 farm and it should include 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 the content databases which results 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.
The second step is to create a backup of the SharePoint 2010 content databases and after that restore them into SharePoint 2013’s SQL Server.
This can be done in two ways, either by using central administration or by using PowerShell cmdlet.
You can create a backup of databases from 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 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 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 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 explicitly migrate all site collections to SharePoint 2013. This can be done by Site Collection administrators by clicking on the links available from the upgrade reminder banner.
Undoubtedly, upgrades are time-consuming when there is a huge number of site collections present on the particular content database. You can easily get the status of the upgrade 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 site collection upgrade:
Thus, you can successfully migrate SharePoint 2010 to SharePoint 2013.
Due to these drawbacks, organizations that are looking to upgrade to SharePoint 2013 face various challenges.
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 integrity of the data.
Note: You can experience the tool’s functioning by downloading its trial version from its website for free.
When you have such an easy and simple way to perform the migration, then why go for native migration methods. With this tool, organizations can have better control over the migration process and can solve a wide variety of common, yet complex migration scenarios.