As you embark on the journey of migrating SharePoint 2010 to 2013, the task might prove daunting. Among other things, it is vital to take into consideration a number of factors, one of the more important being your SharePoint environment. Are you operating an intranet or making use of custom applications? Also what are you current configurations?
Regardless of your unique situation, here are 7 tips to help you with successfully migrating Sharepoint 2010 to 2013:
1. Take a fresh-start Approach: Know that your experience migrating to SharePoint 2010 would be different from migrating to SharePoint 2013. Decide on what server and Windows operating system (OS) to work on. Microsoft SQL Server 2012, Office Web Application Server and the Windows 2012 operating system are main options.
2. Look for Important Changes: If you are operating on a new OS and servers, there will be changes to how things operate. For example, in Windows Server 2012 a number of features are deprecated including the Remote Data Service, SMTP and related tools. These changes mean you will have to consider ways to manage mail by using the System.Net.Smtp. API or installing the deprecated SMTP feature.
3. Script the Whole Process: PowerShell scripts allow you to save time by automating several processes when working in a Windows environment. By making use of scripts, you are able to reduce errors to migration because you can easily repeat newly created functions as well as more easily perform dry runs.
4. Perform Dry Runs & Tests: About 2 or 3 dry run tests should come before an actual live test. Dry Runs help you understand process timing and disk space needed. Each dry run should follow exactly the same steps of which any forced deviation out of pre-defined steps indicates a non-successful dry run. By performing web performance tests you can simulate how an end user will experience a SharePoint application or site. Web performance tests can be conducted using the Web Performance Test Recorder or by recording HTTP requests in a browser session.
5. Determine How Much Space is Needed: Following dry runs, you should figure out how much you need in terms of disk space. A rule of thumb for space needed is 3 or 4 times the amount of content. You should also determine the amount of time needed for the migration or upgrade.
6. Configure Destination Environment: Before migration, test that all aspects of the new farm or destination environment are properly configured. This is especially the case if you are not moving services to a new destination. Firstly, test to ensure that all settings are in place. This will allow you to determine if errors are a result of the migration process rather than misconfiguration in the destination environment.
7. Prepare for Problems: Although this may sound like common sense, it is often an overlooked step when migrating SharePoint 2010 to 2013. There should always be a streamlined process in order to gather user complaints, keep up with issue updates, and manage support effectively. Failure to adhere to this basic principle could result in an unstable environment for users alike.
When it comes to migrating SharePoint 2010 to 2013, there are numerous things to think about. However, paying attention to these 7 tips will help mitigate some of the more popular issues that could occur with migration. These tips are provided not as a step-by-step guide to migrating SharePoint 2010 to 2013 but rather as important notes to keep in mind through the migration process in order to mitigate common problems. It is also important to note that knowledge on these tips have been garnered from working in a SharePoint environment with branded intranet and customized services.