Yes, You Can Move Straight From SharePoint 2007 to SharePoint 2013
UPDATE: Moving to SharePoint 2016? Read the latest version of this blog, "Yes, You Can Move Straight From SharePoint 2010 to SharePoint 2016"
A recent survey showed that a large number of SharePoint customers are still using versions of SharePoint older than 2010. So how do they move to the SharePoint 2013? This is a common question currently being asked on SharePoint forums. Worryingly, most answers are either wrong or not completely correct.
Searching the Internet using your favorite search engine will reveal what Microsoft says on this. Namely, that there is only way to upgrade from SharePoint 2007 to SharePoint 2013. First you must upgrade to SharePoint 2010. Only then can you upgrade to 2013. However with Metalogix Content Matrix the answer is different. You can migrate from 2007 directly to SharePoint 2013.
Notice the difference? You can migrate but you can’t upgrade. Sounds like semantics but there is an important difference.
Microsoft defines an upgrade as the complete A to B transfer of the SharePoint Databases from one version of SharePoint to the next. The databases are then physically changed (or “upgraded”) to the new version’s schema and attributes. This means that, using the Microsoft definition, you cannot upgrade SharePoint directly from 2007 to 2013. You have to do the intermediate hop to 2010. The gap between anything other than successive versions is too wide for a Microsoft upgrade to cope with.
Fortunately Microsoft also has a definition for migration. A migration involves copying and moving items from a database but not the database itself. All the unstructured data, structured data, other attributes and important SharePoint “stuff” can be read or copied. Everything is then reproduced in a different database on a new SharePoint farm.
Using a capable product, such as Metalogix Content Matrix, achieves this with no dependencies or limitations related to the SharePoint version being migrated either from or to. A SharePoint migration can also move items in a more granular fashion. These items don’t have to be moved to the exact equivalent location in the new SharePoint target. You are free to exercise your creative nature and your observations of the usage of your existing SharePoint site, and move to a new structure that actually fits how your users wish to use SharePoint to more effectively solve the business problems you’re solving with SharePoint.
In other words, a SharePoint migration leaves the databases in place but everything else is copied and moved. There is now no version gap too wide. You can avoid a completely unnecessary and costly and step.
Still confused? Let's sum it up another way.
If you wish to move to SharePoint 2013, irrespective of your current SharePoint version, come and speak to us. We can get you there in a single, simple hop, and increase your SharePoint usability while you’re at it.