Volkswagen Financial Services – SharePoint Migration Project
Founded 81 years ago, Volkswagen has grown to be the largest automotive manufacture in the world producing over 6 million units a year. Based in Wolfsburg and employing 177,400 people worldwide, a strong IT system is key to running their business.
Problems Client Faced
VW already had a SharePoint system; however, It was running on SharePoint 2010 and Windows 2008, which support from Microsoft ended in October 2015, and the products are now officially at end of life for support. Along with having a system no longer supported by Microsoft they also felt the benefits of a newer version of SharePoint would benefit the manufactures rate of productivity within the business.
This project was very different to the majority of our data migration projects. When migrating a system, you need to transfer all the data to the next release of that software, in this case it was from SharePoint 2010 to SharePoint 2013 and then to SharePoint 2016.
We transferred all 9TB of their data from their old system to SharePoint 2013 as a first step, and then to SharePoint 2016 as the final platform. Not only will they get the added benefits of SharePoint 2016, but they will have support from Microsoft until 2026.
How It Works
We needed to build a new SharePoint 2013 environment, fully configured and with enough resources to handle the 9Tb of document content. We then transferred all the data from their SharePoint 2010 site to the new SharePoint 2013. This process involved using the virtual storage management tools in place at VW to be able to snapshot the content databases and easily move them to the new LUN storage.
Once the data was re-located to the new environment, the migration phase could begin which involved upgrading the 2010 databases to 2013, rebuilding the farm and testing it’s usability. This of course, had to be completed in as short a window as possible between staff leaving on a Friday afternoon and the returning to work on Monday morning to access their content seamlessly.
We then repeated this process, moving the data from SharePoint 2013 to SharePoint 2016. whilst migrating we maintained the aesthetic look of the pages and functionality. We then made sure that the current data worked with the additional features of SharePoint 2016.
Request A Call Back