Platform migration

Project summary

Guiding Europe’s busiest port to CMS modernisation

When a UK port faced uncertainty on how to modernise its outdated SharePoint platform, our consultants stepped in with migration expertise. The key results of this project were:

Clear direction

With a detailed audit, analysis, and report, the port gained a clear view of its migration options.

Engaged users

High adoption was ensured by involving stakeholders across the business in the migration planning.

Efficiency and security

Due to the planning that went beforehand, the company was able to get full value from its new platform.

The full story

1: Needing to get shipshape


As Europe’s busiest ferry port and an award-winning cruise port, our client plays a crucial role in the local and international economy. At the time of contacting us, the port was using SharePoint 2007 as its central document repository. This platform hosted the port’s key workflows and its organisation-wide intranet.


However, the platform was several versions out of date. Issues around performance, functionality, and support had led the port to consider migrating to a modern SharePoint platform.


And on top of that challenge, the port’s efficiency was also hampered by disparate teams using siloed file shares. A SharePoint migration seemed like an opportunity to bring those teams onto a transparent central platform.


The need for change was clear. But lacking the internal expertise, first the port needed guidance on how to proceed for best results.

2: Pre-migration analysis and findings


The port approached Influential Software to benefit from our experience with similar SharePoint migration projects. It was agreed that our consultants would carry out an initial discovery phase to assess the port’s existing content.


This phase consisted of four main elements: a content audit, analysis, report creation, and migration planning.


In the content audit the port’s SharePoint sites were arranged into a thorough inventory with a variety of auditing tools. This provided data for analysis, including internal collating, assumption testing, and planning. And this in turn informed a detailed document on the existing platform and the migration options available, along with their costs and benefits. Finally came the migration planning stage, which took the form of on-site workshops with the port’s stakeholders and IT teams.


As a result of this process, the port’s IT team found itself in a position to perform its long-awaited SharePoint migration. Without the need for further external support, the port followed our detailed recommendations to successfully migrate 10 site collections containing around 600GB of content.

3: Full speed ahead


As any migration expert will tell you, migrating content is the simplest part of the operation. What requires expertise is the auditing, analysis, and planning. And without the clarity provided by this stage, the migration will not be satisfactory.


In the port’s case, the careful pre-migration planning resulted in a modern platform that exceeded users’ expectations. By ensuring all the new features worked flawlessly, the port was able to make SharePoint users’ platform of choice. This resulted in information silos being broken down and increased efficiency across teams.


Is your business stuck with outdated content management?

Our SharePoint consultants will carry you forward.


15th May 2020
SharePoint, migration, CMS

Privacy Preference Center




Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview


WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by Influential.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:

Wordpress, Intercom
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]