Overview of the Upgrade Process to SharePoint 2013

The database-attach method is the optimal process for upgrading from SharePoint 2010 Products to SharePoint 2013. The first step calls for the creation and configuration of a SharePoint 2013 farm. Next, copy the content and service application databases from the SharePoint 2010 Products farm. Then, attach and upgrade the databases to upgrade data to the new version. Last, have site owners upgrade individual site collections.

upgrade-1
Figure: The sequence of upgrade stages
 

Step 1: Create a SharePoint 2013 Farm

Creating the new SharePoint 2013 farm involves two actions:

  1. A server farm administrator installs SharePoint 2013 to a new farm. The administrator configures farm settings and tests the environment.
  2. A server farm administrator sets the SharePoint 2010 Products farm to read-only so that users can continue to access the old farm while the upgrade is in progress.upgrade-2

 

Step 2: Copy the SharePoint 2010 Products Databases

In the second step of the upgrade process, copy the databases to the new environment. For these tasks, use SQL Server Management Studio.

  1. With the farm and databases in read-only mode, a server farm administrator backs up the content and service application databases from the SQL Server instance on the SharePoint 2010 Products farm.
  2. The server farm administrator restores a copy of the databases to the SQL Server instance on the SharePoint 2013 farm and sets the databases to read-write on the new farm.upgrade-3
    Figure: Use SQL Server Tools to Copy Databases

 Step 3: Upgrade SharePoint 2010 Products Databases and Service Applications

In the third step, upgrade the databases and service applications.

  1. A server farm administrator configures the service applications for the new farm. The following service applications have databases for upgrade during this process:
    • SharePoint Server 2010 and SharePoint Foundation 2010
      • Business Data Connectivity service application
    • SharePoint Server 2010 only
      • Managed Metadata service application
      • Performance Point Services service application
      • Search service application
      • Secure Store Service application
      • User Profile service application
  2. A server farm administrator creates a web application on the SharePoint 2013 farm for each web application on the SharePoint 2010 Products farm.
    upgrade-4
    Figure: Create Web Applications for Upgrade
  3. A server farm administrator installs all server-side customizations.
    upgrade-5

    Figure: Copy customizations to the New Farm
  4. A server farm administrator attaches the content databases to the new farm and upgrades the content databases for those web applications.
    upgrade-6

    Figure: Upgrade the Databases by Using Windows PowerShell

Step 4: Upgrade the SharePoint 2010 Products Site Collections

The final stage in the upgrade process is to upgrade the site collections. In SharePoint 2013, site owners upgrade their sites. The upgrade process for My Sites is slightly different from other types of site collections.

Upgrade My Sites

IMPORTANT! This section applies to SharePoint Server 2013 only.

A server farm administrator upgrades the My Site host. Then, individual users can upgrade their My Sites or the farm administrator can upgrade them by using Windows PowerShell. The following illustration shows four stages for the My Site host and My Sites during the upgrade process.

upgrade-7
Figure: Stages in Upgrading My Sites
 
  1. The My Site host has not been upgraded. My Sites cannot be upgraded yet.
  2. A server farm administrator has upgraded the My Site host. No My Sites have been upgraded.
  3. Some users have upgraded their My Sites.
  4. All My Sites have been upgraded.

Note: A server farm administrator can force an upgrade of My Sites without waiting for users to upgrade them. 

Upgrade other SharePoint 2010 Products site collections

Owners of all other site collections can upgrade their sites as soon as a notification appears on their site’s home page advising that the new version is available. The following illustration shows four stages for a site collection during the upgrade process.

upgrade-8
Stages in upgrading site collections
  1. The site owner runs the site collection health checks to determine readiness for upgrade. The site owner addresses issues before continuing with the next step.
  2. Optionally, the site owner requests an upgrade evaluation site collection. A timer job runs to create the site collection; the site owner receives an email message when the evaluation site collection is ready. The site owner previews the new user interface. After several days or weeks, the evaluation site collection expires and is deleted by a timer job. A server farm administrator can determine the length of time before expiration.
  3. When ready, the site owner can start the upgrade process. The site collection health checks are run again automatically. The site owner must address issues before upgrading. If health checks return no issues, the upgrade starts.
  4. When the upgrade is complete, the site owner sees the Upgrade Status page that contains the status and a link to the upgrade logs. The site owner reviews the site to make sure that everything works correctly.

NOTE: A server farm administrator can force the upgrade of specific site collections without waiting for site owners to upgrade them.

Models

Upgrade process
upgrade-9

Upgrade testing
upgrade-10