The post How to upgrade from SharePoint 2013 to SharePoint 2019 Step by Step (Part 1) appeared first on Blog IT.
This post is the first part of a two part step by step tutorial on how to migrate a SharePoint 2013 farm to SharePoint 2019.
To read the second 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 2019 that has support for a hybrid scenario can be a valid solution to allow a gradual move to the cloud.
This post is based on upgrading a SharePoint 2013 farm to SharePoint 2019 using the database attach approach but is also valid if you want to upgrade to SharePoint 2016 (to learn more about upgrading to SharePoint 2016, click here and here). This post assumes that the we will only migrate the content database(s) from the source SharePoint 2013 to SharePoint 2019 and all other SharePoint databases are created in the target SharePoint 2019 farm during its installation process.
If you want to learn more about how to install a SharePoint 2019 farm in an automated way using PowerShell, here and here.
There is another valid migration approach to migrate from SharePoint 2013 to SharePoint 2019 by using a 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 2013 to SharePoint 2019 (outside of the scope of this post)
- Upgrade to a temporary SharePoint 2016 farm
- Upgrade to the target SharePoint 2019 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:
- Migrating Custom Developed Solutions from SharePoint 2013 to SharePoint 2019 (details about the migration of custom solutions are outside of the scope of this post)
- Upgrade to a temporary SharePoint 2016 farm
Migrating Custom Developed Solutions from SharePoint 2013 to SharePoint 2019
This step is outside the scope of this post but a few notes are important to mention if you have custom developed solutions that you want to migrate from SharePoint 2013 to SharePoint 2019:
- First, you should analyze the source SharePoint 2013 farm and look for custom developed solutions and in particular for farm solutions and/or sandboxed solutions
- If custom developed solutions are found and if you want to take the easiest migration path, you could simply upgrade your custom developed solutions to SharePoint 2019 without changing the solution architecture. This typically involves migrating server-side code from SharePoint 2013 to SharePoint 2019, possible migration of master pages and adjustments to CSS and JS files
- Despite more difficult, if possible, you should consider migrating the existing solutions to one of the following development models:
- SharePoint Framework: the latest and the recommended development model for modern SharePoint solutions, enabling an easier migration path to SharePoint Online and Office 365
- SharePoint Add-Ins: this development model is still supported and can be a valid solution depending on your scenario. However, when possible. you should consider migrating solutions to the SharePoint Framework development model
To learn all about Upgrading a SharePoint 2013 farm to SharePoint 2019, click here.
Happy SharePointing!
The post How to upgrade from SharePoint 2013 to SharePoint 2019 Step by Step (Part 1) appeared first on Blog IT.
Oldest comments (0)