Migrating SharePoint – Agile vs Slow and Expensive in the Cloud Era
You have SharePoint 2013 AND the Cloud looming out there. Once on the Cloud, the SharePoint upgrade cycle accelerates. The Cloud provider does all the back-end preparation for a new SharePoint version and… then what. As we look around at SharePoint programs struggling to get off 2007 for a variety of reasons, custom code and the expense of recoding being one of the big ones, we would like to offer a different approach.
Our team is getting ready to migrate a SharePoint environment with tens of thousands of users and terabytes of data in a complex U.S. Government IT environment for the third time. The last time we did it, the actual migration (cut-over) took four days with no major glitches. Because we had prepared our users for the new features, they were ready to go. Because we had engaged thousands of site owners in cleansing their data, the new environment was more streamlined. Our governance guidelines discourage the use of custom code unless absolutely necessary, and encourage out-of-the-box configuration. As a result, we don’t have massively expensive re-coding (which then is re-coded again, and again…) and costly delays.
This is the result of our tested approach to large-scale SharePoint implementation and adoption. We train embedded users to be the stewards of their own sites and to provide Tier One support. We involve them in migration, starting with early planning all the way through user acceptance testing. Does this take resources and time? Yes, but the alternative looks less appetizing in the quickening pace of updates and network technology.
Call us if you are interested, we’d be happy to discuss our approach and map it to your current situation.