Portfolio

Seamless intranet asset migration

Supporting transition of ownership with intranet migration

egforit Software helped a global consumer goods company achieve a fast and seamless intranet asset migration.

Executive brief

Supporting asset migration

Our client is a multinational consumer goods company. After selling its beauty division, the company needed help migrating its intranet assets. egforit Software helped the company achieve this through a seamless SharePoint migration. The benefits of this project were:

ability to sell quickly

security kept intact

cost-effective migration

secure intellectual property

Curious about how we achieved this intranet migration? Read on to find out more.

The full story

Purple arrow encouraging readers to scroll down for the rest of the GDPR data solutions case study

The challenge

Dissecting the assets

Our client had recently sold its beauty division and was looking for ways to migrate the intellectual property to the buyer seamlessly. However, the client needed a guarantee that its own employees would not have access to the sites after the transition of ownership. Furthermore, it was important that the data remained intact and uncorrupted during the migration.

 

Additionally, it was essential to the client that the intranet would not crash or be damaged during this process.

 

Upon reviewing the sites and directories, we found over 400 locations to be moved across and have their access rights changed. Lastly, it was important that the sites being moved over remained intact on both the front and back-end.

The solution

Segregating content

The company contacted our intranet experts for help after seeing our many SharePoint successes.

 

Firstly, to make the process as efficient as possible, we started moving the content before the official divestment date. This gave us more room to check that every site’s permissions had changed and the content was migrated over in time. It was important for the client that the buyer could take over the intranet immediately.

 

In order for a smooth transition to take place, we needed to:

 

  • analyse affected areas and directories 
  • rework the existing access rights
  • migrate content from the intranet

The benefits

Smooth segregation

The primary benefit of this portal solution was that the intranet was split quickly and flawlessly. Crucially, the client didn’t have to invest substantial time and money in dividing assets, meaning it could sell the division easily.

 

Following the asset migration there was no damage to the remaining assets, and all permissions were moved in good time. Importantly, the benefits of this project were:

 

  • low costs for the client
  • assets were moved quickly
  • the migration was completed on time

 

We’re helping our client transform business efficiency and productivity in the long term with our SharePoint implementation skills and continued support.

Work with asset migration experts

We provide seamless migration of online assets and continued bespoke support. To find out how we can help you, check out our digital portals page.

Info

21st January 2021
digital portal, staff data, intranet

Privacy Preference Center

Necessary

Advertising

Analytics

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

Other

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_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

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 egforit.
- 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:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress,
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
-id-[app_id],-session-[add-id]

×