Centric connect.engage.succeed

SharePoint migraties 

Using Microsoft SharePoint 2007/2010 and want to know if you need to migrate to the 2013 version?

In the 2013 version, Microsoft has implemented a number of technical and functional improvements over the 2007/2010 release.  However, if the functionality in SharePoint 2007/2010 is sufficient for your company then a migration is not necessary. Microsoft will continue to support SharePoint 2007/2010 until 2017.

If you find the options in the 2007/2010 version too limited or a newer version offers functionality that is of major value to your company then of course a migration is worth considering.

There are two technical options for migrating to SharePoint 2013:

  • place upgrade
  • content database upgrade

Centric chooses option two in almost all cases. In the case of a content database upgrade, the new environment is installed alongside the old one. This provides a clean SharePoint installation. Also, the existing environment can remain online during the migration so you are still able to locate data.

Centric performs migrations based on a tried-and-tested migration plan. This plan consists of nine steps:

  1. planning
  2. inventory
  3. clean-up
  4. pre-development
  5. installation (test)
  6. test migration
  7. installation (production)
  8. migration
  9. acceptance and going live

However, no matter how important the technical aspect is, the end user ultimately determines whether a migration is successful. And the criteria are actually quite simple:

  • The information that the user needs must still be locatable.
  • The speed at which the user can operate the system must still be satisfactory.
  • The user must still be able to carry out all the actions that were performed in the old version. 
  • The user must see added value from the new options that the migration has created.

Communication and involvement

During introduction of a new software solution, even if it’s just a new version, it is essential to inform your employees and get them involved in a timely manner.

This might include:

  • Updating all users about the upcoming migration through intranet or e-mail;
  • Forming a key user group which, during several sessions, is informed about the steps being taken for the final migration. What’s expected of them in regard to testing and communication towards other users will also be indicated here.
  • Workshops for key users and end users following the test migration to help them get oriented in the new environment.
  • Keeping everyone informed of the current status during the process.
  • Keeping a migration team on standby during the days after the migration in order to answer questions and solve any problems that might arise.