In this series of posts you will learn how to perform the upgrade process from SharePoint 2010 to SharePoint 2013.
You will come to know how to Plan for the upgrade, what are all the new requirements, changes in process, various stages of the upgrade process, how to resolve the issues while SharePoint migration.
I will cover the details in the below order
3. Migration Approach
4. Upgrade Process
Before starting to upgrade, we must understand what is in your SharePoint 2010 Products farm and set up a new farm based on SharePoint 2013 Products. For that we have to analyze the current SharePoint 2010 environment, get the information about the complexity and customization of your current system. If your SharePoint 2010 environment is complex then proper planning is required.
The following steps should be followed when upgrading from SharePoint 2010.
a) Document your current system to include us
b) Test your upgrade in a non production environment with a copy of production data.
c) Have a proper rollback plan and test it during trail upgrade.
d) Validate a successful upgrade by testing all components detailed in your solution documentation.
e) Check capacity planning because of new environment it initially requires lots of space for databases and its log files due to redesigning the table structure in new version of SharePoint 2013.
Note: If it is a complex farm and have lots of customization, then make sure run the trail upgrade as many times as possible until all issues will get resolved during trail upgrade, make sure the trail upgrade environment should be similar to production with real data and document each and every step during trail upgrade process.
SharePoint server :
Office 2010 or office 2013 :
SharePoint 2013 supports only DB attach method for migration of SharePoint 2010.
The database attach upgrade approach involves upgrading the content in your environment. The configuration that comes along with SharePoint 2010 will not come along with this approach.
For this approach we should have SharePoint 2013 environment to attach the content databases from SharePoint 2010 environment. While performing this approach we have to document all the customization during trail upgrade. This information is very much critical to perform the database upgrade approach in production environment.
Note: It is important not to introduce any new customizations or components into the production environment while performing the trail upgrade. There might be chances that we might end up with new custom components missing in the new SharePoint 2013 environment.
In next post part2 of upgrade from SharePoint 2010 to 2013, we will see an Upgrade Improvements section in migration approach.
Hope you have enjoyed the SharePoint migration part1 of this series.
Devendra Velegandla is a four-time recipient of Microsoft's Most Valuable Professional (MVP) award (2014-2017) for Office Servers and Services MVP and SharePoint Server. He received the MCC award for his contributions in Microsoft MSDN/TechNet forums. He loves sharing articles, videos, and tutorial on SharePoint and Office 365.