In order to migrate enterprise data, organizations must properly evaluate information architecture, content sources, business processes, regulated content and standards for compliance, formatting and templates.
Migrations must be evaluated and planned based on a number of factors.
- The needs of an enterprise.
- The quantity of the enterprise’s source documents and metadata.
- The quality of the data
- The complexity of the legacy and target sources
Equally important is full understanding of the technical requirements for integrating data and any execution requirements for scheduling and timing, as well as the post-migration support needs.
When planning a data migration, enterprises must also consider the security of the data and establish if there is a need for external links and other types of data, as well as the structure of references and data dictionaries, if applicable, and the types of forms, templates, objects and document indices that users will be working with regularly.
With so many different factors to keep in mind when planning for a migration, it’s essential to start with the fundamentals. Many different questions must be asked regarding the scope of the project before it’s possible to move forward, such as:
- How many documents need to be assessed?
- How many different types of documents are being migrated?
- What number of attributes are contained within those different types of documents?
My colleague, Douglas Vargo, Vice President, Information Management, Paragon Solutions, covered much of this in Data Migration 2016: An Enterprise Necessity for Content Management featured on the Paragon Business Solutions Blog. I invite you to review the full article and review related updates by Douglas Vargo on topics ranging from decommissioning legacy applications to information governance and more.
