When organizations take the decision to migrate content to a new, modern system – whether to retire end-of-life legacy systems, or as part of a broader digital transformation journey – the temptation is to view this as a large ‘copy’ operation. The assumption is that all content from the old system will be ported across to the new environment, like for like.
This is not only to vastly over-simplify the undertaking; it also misses the opportunity to rethink the way companies and teams capture and manage content, and to thereby transform business processes.
Underestimating the work involved to deliver successful migration can have a costly and highly disruptive effect on a project. But it can also compromise the strategic outcomes, if not everyone appreciates why a project is happening and what the possibilities are once content is available via a more modern, standardized and probably cloud-based platform.
We recently managed a major content migration project for an energy company which uses contractors to build its plants. Previously, once sites had been built and had entered into operational and maintenance mode all of the associated records, documents and technical drawings from all of the various suppliers and subcontractors would be difficult to track down – despite the fact that plant documentation is highly standardized in line with strict guidelines. This was due to an inconsistent use of content taxonomy – an all-too-common scenario.
Migration to a common digital platform created the possibility for this critical content to be captured, held and accessed in a common way, both retrospectively and in the future. But to get to that point, existing data and documentation needed to be assessed and prepared to support this new scenario.
This involved imposing a consistent data taxonomy and structure, improving the existing data quality, and enriching the associated metadata to make content more easily searchable. The same parameters were then applied to the creation of new documentation.
For organizations embarking on a new systems/content migration journey, maximizing the associated opportunities means looking at the project from all angles before getting started.
The following pointers are relevant particularly for complex consolidation and migration projects involving multiple legacy systems.
- Take the broad view. Content migration is rarely, if ever, a case of simply copying across existing documents and data, or certainly shouldn’t be. Allow the time to properly scope the opportunity to clean up content and make it work harder for the business. Ultimately, a change of systems should deliver something more than a faster user experience that’s easier to support. It should support higher productivity, greater efficiency, lower risk, better customer experiences, etc.
- Let these strategic goals dictate the project scope. Sizing up content migration work is not only about the number of documents or gigabytes of data involved, but rather about the complexity of consolidating and preparing that content for improved ongoing use cases/a modernized or redesigned application landscape (e.g. facilitated by more fluid cloud-based content access).
- Don’t assume existing data quality. Rather than look to simply move all content across from the old systems, irrespective of its currency or current state, assess its inherent value and how to increase this – by raising its quality, and by filtering out or archiving redundant or duplicated assets.
- Let business stakeholders help direct what’s needed. Involve them from the outset, asking about their current points of pain and what would help alleviate them. What is holding them back in their work? What constitutes priority content, and what are the current issues around data/document access and visibility, and data quality and consistency? All of this will help inform the preparatory work in advance of any migration – in terms of what needs to happen to improve data governance, transparency, and so on. This dialogue with the business should be maintained throughout the project.
- Go to the market for a suitable migration tool or service – but only once the true scope of the project, its aims and technical constraints are clear (That is for example, once a pre-study has been conducted to help frame the scope for the project).
In a second blog, we’ll be sharing some specific technical tips for companies preparing to migrate content to Microsoft SharePoint Online. Stay tuned!
To discuss an upcoming content migration project with our experts, just reach out to us.