Content migration

Post-divestment content migration

1: Protecting intellectual property


Our client, a multinational consumer goods corporation, was about to undertake a divestment that would change the status of intellectual property within their SharePoint system.


The new owner of the intellectual property had to be able to access only the correct content, while other content had to be protected within our client’s system.

2: Content analysis and migration


Our team started by analysing the affected SharePoint sites and directories. This allowed us to classify the user base and access rights that would change following the divestment. Next we carried out an effective migration of the relevant content. Finally, we updated the user access rights and permissions to reflect the new structure.

3: Restructured and protected systems


The client received an effective separation of protected and externally accessible intellectual property. This allowed the divestment to take place without being impeded by any content-related issues.


Systems not flexible enough for your content?

Our development team will provide a solution.


15th May 2020
content migration, CMS, consumer goods, SharePoint

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]