New SharePoint version is always exciting with new features and better interfaces , but also equally stressful considering we have to move all our data from current version to the new version. Below are some basic information about migration to SharePoint 2016.
- No direct migration path from 2007, 2010 to 2016: If you are still running a SharePoint 2007 or 2010 version then things will be little more harder for you as 2007 or 2010 to 2016 native migration (database attach & upgrade) is not possibly directly. You have to first migrate to SharePoint 2013 and then from 2013 to 2016. See Upgrade from 2010 to 2013 process. If you are in 2007 then you have a double hop process in front i.e. first migrate to 2010 , then to 2013 and finally you can go to 2016.
- Ways to avoid multiple migrations to reach to 2016: If you are running in MOSS 2007 or SharePoint 2010 , the only way to avoid multiple hops during migration is by using some third party migration tools like ShareGate, Metalogix , DocAve and tons of other tools out there in the market.This will make perfect sense if you do not want all data to be migrated but want to selectively migrate content from the existing 2007, 2010 or 2013 sites to SharePoint 2016.
- Migration from 2013 to 2016 : The native upgrade also require that your SharePoint 2013 database version is 15.0.4481.1005 (March 2013 Public update) or higher and if you have sites migrated from 2010, they should be visually upgraded to 2013 mode. Database attach and upgrade method should be used to migrate from 2013 to 2016.