This is a presentation showing how SharePoint administrators can upgrade SharePoint 2010 to SharePoint 2013. Vyapin also offers a tool allowing administrators to migrate SharePoint 2010 content to SharePoint 2013.

1. How to upgrade from SharePoint 2010 to
SharePoint 2013 – A quick guide
A
Vyapin Software Systems Private Limited
presentation

2. Run health checks
• Before each upgrade the Site Collections
administrators must run health checks to
identify and repair errors that can affect the
upgrade
• After all health checks return results with all
clear the Site Collection can give the go ahead
for upgrade

3. Create a new SharePoint 2013 Farm
• Install the pre-requisites for SharePoint 2013
• Setup the SharePoint 2013 Farm
• Set the older SharePoint Farm to read-only

4. Copy SharePoint 2010 databases
– Content database & Service Application database
• Back up the existing SharePoint 2010 service
application database and the content database
into the 2010 Farm
• Use the SQL Server backup and restore process
to restore the backed up files to the new
SharePoint 2013 Farm
• Set the new Farm as Read-Write, to allow
changes

5. Upgrade the Service Applications and databases
• Configure service applications to use the new
Farm
• Create equivalent SharePoint 2013 Web
applications for each application in SharePoint
2010 Farm. During this procedure, the URLs and
Port numbers used by Web applications in
SharePoint 2010 are reused for the Web
applications created in SharePoint 2013
• Create SharePoint 2013 customizations similar
to the ones existing in SharePoint 2010

6. Upgrade Content databases
• Test the existing database using the cmdlet
“Test-SPContentDatabase” to identify errors
and the missing components
• Deploy the missing components
• After all errors have been eliminated, attach the
content databases to their Web applications
using the cmdlet “Mount-SPContentDatabase”

7. Upgrade the Site Collections
• Before Site owners can upgrade their Sites, the
Farm administrator must upgrade the MySite
host
• The SiteUpgrade option under Site Settings can
be used to begin the upgrade
• After all errors have been eliminated, attach
content databases to their Web applications
using the cmdlet “Mount-SPContentDatabase”

8. Check the Site Collections
• Site Collections administrators must run health
checks to identify and repair errors that may
have occurred during the upgrade