Who hasn’t already made the painful experience of how bad communication has led to additional costs and reduced the quality of a project at the same time? We don’t want that to happen at all and therefore most project leaders today are very aware of the importance of communication within their project.
To help keeping your communication straightforward in a migration project, let’s have a closer look at the mapping specification as a crucial document in migration projects.
When introducing new systems or adding new areas to a new system usually data migrations are needed to integrate the data from the old system or other areas into the new system. During such data migrations often a migration tool is used to get the data from the source into the target system. This migration tool transforms the data to be compliant with the new system and imports the data into the system.
In such a scenario generally these questions come up: How to validate the data migration? Do we need to validate the tool itself? Do we need to validate all details of all rules and functionalities that are available in the tool and could be used in theory?
The implementation of a standardized DMS like D2 or the > Dell EMC Documentum Life Sciences Solution Suite requires the migration of documents from the old to the new system or a transforming of the data model within the system in order to work properly with the new application. Often this old data is not fully standardized and structured, but either based on a less controlled system such as Documentum Webtop or on a controlled system with slightly different structures such as CSC FirstDoc or Cara.
Document management is no longer greenfield terrain. By now many companies have already determined their need for a document management system and understand the benefits it offers them, especially in the Life Sciences. For this reason, nearly every company dealing with mission-critical documents has implemented some sort of solution in recent years.
The question that is now more likely to arise is whether the performance level and user friendliness of today’s system are still adequate, and/or capable of meeting growing requirements. And it could be that other providers have developed a newer, more attractive solution.