Upgrade & Migration

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:

  • Should I upgrade on-premise or is this a good time to move to hosted solution.
    • Office 365
    • SharePoint Online
    • Specialist hosting solution
  • How can I minimise downtime during the migration?
  • Would starting with a clean slate be better?
  • Do I need any third party tools to help with the upgrade?

What if I don't upgrade ?

  • Significant user interface changes can mean retraining and adoption difficulties.
  • Upgrading 3rd party add-ins gets more complicated when skipping versions or falling behind.
  • You'll be missing out on all of the new capabilities and performance improvements.
  • Eventually your version will no longer be supported by Microsoft, which means no more patches or service packs and that means risks to both security and supportability.

Why upgrade to SharePoint 2013 ?

  • Productivity improvements for the user.
  • Drag and drop uploading of documents.
  • Permissions management and sharing has been improved and simplified.
  • Themes and enhancements to customise the look.
  • New and improved search capabilities.
  • Crawl improvements on performance.
  • Cross site collection roll-ups.
  • Browser and mobile solutions.

Our Process

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:

  • Pre-upgrade planning including execution of the pre-upgrade check tool.
  • Estimating new hardware requirements.
  • Installing and configuring new SharePoint environment – on-premise or hosted.
  • Testing the upgrade by backing up the content in the current environment and restoring it to the new SharePoint environment.
  • Performing the real upgrade.
    • Freezing the existing SharePoint environment by setting the databases to read only.
    • Backing up and restoring the content to the new SharePoint environment.
    • Updating all DNS entries to ensure that users are accessing the new environment.

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.