20 Jan 2014
In general, I have covered all possible activities to be performed at a high level for performing the migration from SharePoint 2010 to SharePoint 2013 in my previous articles.
Always perform the test migration in your SIT or Model Office Environment before proceeding to configure the Pre-Production, Production and DR.
Develop an automated PowerShell script especially for building the configuration of the SharePoint Servers. This would be very helpful in building multiple servers within shorter time.
3rd Party Migration tools can helps save time and will be useful only when you have large content with less customizations, Unstructured content which you plan to revamp and redefine, Move external content into SharePoint, Granular migration of content, If your content is business critical and the users are not ready to wait for a smaller period of time in read only mode during the migration as the tools provide greater flexibility in incrementally performing the migration while you do it in a phased manner.
If you have not used Remote Blob Storage, Plan to enable it and migrate content into RBS from your content database after performing the migration as this would help largely in your cost to manage data in SQL Server.
Though migrating in a live environment is not easy and will end up in encountering different level of issues, my idea is to provide a consolidate view of the different set of activities that needs to be performed at various stages of the version upgrade and will definitely help in preparing and planning for the upgrade.