Protiviti / SharePoint Blog

SharePoint Blog

April 09
Key Points for Any SharePoint 2010 to 2013 Migration

​Most of my migrations from 2010 to 2013 have been very similar. 

Whether we are migrating one server or 5 servers there have been some consistent themes.  As experienced Consultants, we have come to understand that these are the key points to understand and be aware of:

1) Discovery, perform a discovery phase prior to migrating focusing on:

  • WebApps
  • Authentication-  as you can see we have one webapp using claims below.  The others use Classic authentication and will need to converted.

  • Alerts
  • File sizes and types- it is important to understand the overall size and types of files being migrated. In this case their are very few files, but at times you may be faced with 100 of thosands of items some of which may be blocked by default in an upgrade scenario (exe, msi, bat0

  • Permissions
  • Custom Solutions
  • MasterPages
  • Overall Site Collection Size- this will help you plan outages and coordinate with the business.  In our scenario below, the fictitious Portal is the largest site.

  • Workflows
  • Infopath
  • Hardware Load Balancing schemes
2) Potential Issues
a. Most 2010 sites are using classic authentication
b. Alerts have to be updated to the new URL
c. We need to restore the MySites, UserProfiles, BDC, Secure Store, Managed Metadata prior to the web applications.  We can use PowerShell to find the names.


d. Auto alerts need to be turned off especially ones related to site collection cleanup and profiles
e. SSL certificates in 2012 need to be SAN certificates
f. For extremely large farms where you may have 50+ content databases use automated backups and restores
i. Automate restore of SQL backups in a folder directory using stored procedures
ii. Automate upgrade of content databases using PowerShell
3) New Technologies, HA and DR configuration options have changed
a. Use AlwaysOn as a gold standard for the Data Tier.  This si a complex topic and requires research and testing prior to configuring.
b. Use Multiple Search Servers to provide redundant Crawl, Query and Index Components.  All of these are complex topics, but in the end you should have a search that looks like the below image.


c. Use Multiple Application Servers
d. Script out key service application backups
e. Monitor SQL db and log sizes
f. Configure routine maintenance on sql dbs


As you can see, the subjects listed span several technologies including Application Tiers, Active Directory, SQL platforms and customizations using C# and .net.   For your typical Enterprise client that would include AppDev, SQL teams, Infrastructure Teams,  Technology Specialist, Records Management and InfoSec.  Each of these groups has a key governance role to play when upgrading SharePoint.

If you go into a migration with a full understanding of these facets of the migration you will minimize your exposure to project overruns and unneeded complications.

- Andy

Need help planning your SharePoint Migration or Upgrade? Take a look at our SharePoint Pre-Migration Assessment​ offering. ​

Quick Launch

© Protiviti 2020. All rights reserved.   |   Privacy Policy