Maintaining older versions of technology like SharePoint can be challenging and risky. Once SharePoint takes hold, it continues to spread through the organisation and becomes critical to your operations. We can provide the answers to some of your most critical SharePoint upgrade questions:
What if I don't upgrade ?
Why upgrade to SharePoint 2013 ?
When it comes to upgrading we have two options: Upgrade using Database Attach or migrate the content using 3rd Party Software.
Upgrading using Database Attach
A database attach upgrade means that we will stand up new SharePoint 2013 hardware and perform a cutover upgrade by moving your data to the new platform during an outage window. The database attach method is used for upgrading "as-is" so if you need to reorganise content, we recommend that you look at our 3rd party software approach. Database attach does not support skipping versions, which means that if you're on SharePoint 2007 you first need to upgrade to SharePoint 2010 to begin with.
Here's what a typical upgrade project looks like:
Migrate using 3rd Party Software
The benefit of using 3rd party software is that you can reorganise the content during the migration. You may decide that your SharePoint platform has a lot of non-critical documents, duplicate content or just a lot of junk. This approach means that we can pick and choose what to migrate and leave a lot of that content behind.
The process for 3rd party software migration looks similar except that after we get the new hardware set up we will typically run both environments in parallel while we are moving content over because reorganisation efforts typically have a longer transition period.