One global unified research and development solution
Successful content migration providing consistent metadata
Compliance for regulatory requirements
- Source system: OpenText Documentum D2 3.1 production system
- Target system: OpenText Documentum for Life Sciences Research and Development solution
- Product used: migration-center 3.9
A global generic and specialty pharmaceutical company had the challenge to migrate all their submission-based data from their current OpenText Documentum D2 application to the new Documentum for Life Sciences Research and Development solution. The source system support contract was reaching its expiration date and had limited capabilities and functionalities compared to the Research and Development solution. The company also had an initiative to have one centralized global system. The main challenge was that the active source data from the internal submissions system had too many inconsistencies with regards to the metadata. The client had a requirement to enrich the data from a data migration perspective and map the documents accordingly to the target system.
fme’s Migration Services team utilized it’s unique approach to gather the large amount of data from the clients’ internal submissions system and eCTD Manager to be able to map the documents in scope to the target system for Life Sciences Research and Development solution. The clients’ process at that time was to import documents in scope to be submitted to the authorities into their eCTD Manager submission system from the source OpenText Documentum D2 system. In order to migrate all data from the D2 system and the eCTD Manager, fme had to complete additional metadata requirements to then map the documents to the correct document classification (Group, Subgroup, Artifact) and registration forms (Products, Projects, Applications). This was a very tedious process as not all metadata and data classification on the source documents were fully consistent. Therefore it was not possible to just use one attribute to map the data. Various alternate attributes were used to be able to classify the active documents accordingly. Various mapping sheets were generated and verified with the business to map the documents to the correct registration form and also to the new solutions’ classifications. migration-center was used to perform the migration and was leveraged to migrate documents as-is into a legacy and archive area in the solution while preserving the same source folder structure per client’s requirement. Lastly, there was a requirement to set the documents to not in scope to be migrated; as they were not needed by the business. By the completion of the project all documents in scope were migrated successfully.