Upgrade Scenarios For SharePoint Server 2019

In this article, we will explore high level scenarios of upgrading to SharePoint Server 2019 from prior SharePoint on-premises versions.

Overview

 
As a SharePoint administrator and developer, we support customer portals on various on-premises versions of SharePoint, i.e., SharePoint 2010, 2013, or 2016 (Microsoft Office SharePoint Server 2007 has already reached the end of support in October 2017). We always strive to build future-proof SharePoint solutions which will support upcoming versions of SharePoint. Every new release of SharePoint version alarms us to upgrade to the newer version.
 
In this article, we will explore high-level scenarios of upgrading to SharePoint Server 2019 from prior SharePoint on-premises versions.
 

Upgrade Scenarios

 
Upgrade from SharePoint 2016
 
The upgrade scenario for SharePoint Server 2019 is not changed. Like previous version upgrades, SharePoint Server 2019 supports a direct upgrade from its immediate predecessor; i.e. SharePoint Server 2016. The database should be at SharePoint 2016 RTM or a higher version to upgrade to SharePoint Server 2019.
 
Upgrade from SharePoint 2013
 
There is no direct upgrade path from SharePoint 2013 to 2019. You must first upgrade to SharePoint Server 2016 and then upgrade to SharePoint Server 2019.
 
Upgrade Scenarios For SharePoint Server 2019 
Image source: docs.microsoft.com
 
Below service applications have databases that can be upgraded,
  • User Profile service application
  • Search service application
  • The Managed Metadata service application
  • The Secure Store service application
  • Business Data Connectivity service application
  • PerformancePoint Services service application

High-Level Upgrade Scenarios

 
Upgrade from SharePoint 2013 to SharePoint 2016
 
Upgrade from SharePoint 2013 to SharePoint 2019 requires us to upgrade to SharePoint 2016 first. SharePoint 2016 cannot be skipped in a migration path.
 
The below points need to be considered/carried out on SharePoint 2013.
  • SharePoint 2016 and 2019 by default supports claims authentication. On the other hand, SharePoint 2013 supported windows authentication as a default mode. Therefore the web applications in windows authentication should be first converted to claims authentication.
  • All site collections should be upgraded from 14 modes to 15 modes by using Upgrade-SPSite cmdlet.
  • Backup all content and service application databases from SharePoint 2013 (SQL Server) and restore to SharePoint Server 2016 (SQL Server).
The below points need to be considered/carried out on SharePoint 2016.
  • Setup SharePoint 2016 farm. For setting up service applications database use the one restored from SharePoint 2013.
  • Create new web applications with a temporary database.
  • Install any full trust solutions.
  • Dismount temporary database from web applications. Upgrade restored content databases by running Mount-SPContentDatabase cmdlet.
  • Perform additional configuration changes that are not part of the service application and content database (e.g. incoming/outgoing email settings, etc.)
Upgrade from SharePoint 2016 to SharePoint 2019
 
Upgrading from SharePoint 2016 to SharePoint 2019 is relatively simpler and straight forward as compared to upgrading from SharePoint 2013 to SharePoint 2016 due to the below reasons,
  • Claims authentication is default mode in both SharePoint 2016 and 2019. This reduces the burden of converting the authentication mode.
  • Upgrading databases mode to level 15 is not needed.
The below points need to be considered/carried out on SharePoint 2016.
  • Backup all content and service application databases from SharePoint 2016 (SQL Server).
  • Restore these databases to SharePoint 2019 (SQL Server)
The below points need to be considered/carried out on SharePoint 2019.
  • Set up SharePoint 2019 farm. For setting up service applications database use the one restored from SharePoint 2016.
  • Create new web applications with the temporary database.
  • Install any full trust solutions.
  • Dismount temporary database from web applications. Upgrade restored content databases by running Mount-SPContentDatabase cmdlet.
  • Perform additional configuration changes that are not part of the service application and content database (e.g. incoming/outgoing email settings, etc.)

Summary

 
Scenarios for upgrading to SharePoint Server 2019 have not changed. SharePoint Server 2019 supports a direct upgrade from its immediate predecessor i.e. SharePoint Server 2016. Upgrade from SharePoint 2016 to 2019 is straightforward considering both are using claims authentication and default mode is 15.