TSG has recently enhanced OpenMigrate to add support for migrations to and from Veeva Vault. The OpenMigrate Veeva Target connector enables complex migrations into Veeva Vault to occur through an automated 1-step migration. The 1-step approach provides a huge benefit for regulated life science companies by streamlining validation efforts and eliminating the need for manual intervention.
This post will walk through a simple migration from Documentum to Veeva Vault, demonstrating the benefits of the 1-step migration approach.
Documentum to Veeva – Migration Approach
At a high level, the migration from Documentum to Veeva Vault is accomplished through the following steps:
- The OpenMigrate Documentum Source Connector uses DQL and Documentum APIs to pull a set of documents, extract the appropriate metadata, content, versions, renditions, audit trail data, etc.
- After a set of documents has been extracted, the OpenMigrate Mapping Layer and Listeners are responsible for mapping the metadata from Documentum attribute values into Veeva Vault attributes. For example map the value “SOP-100” stored in the Documentum field object_name to the Veeva field document_number__v. Additional transformations, lookups, data and content manipulations can be performed prior to loading metadata and content into Veeva Vault.
- The OpenMigrate Veeva Target Connector will be responsible for storing the metadata and content into Veeva Vault, specifying versioing, uploading renditions (if required), creating binders, etc.
There are multiple ways to import content into Veeva Vault as discussed in our previous article, Documentum Migraiton to Veeva Vault – Best Practices. Using a 1-step migration is preferred for most life sciences customers for the following reasons:
- Reduces Validation Effort – A one-step migration only requires content and metadata verification once. A multi-step migration requires verification of each step (i.e. Verify Export is successful, Verify Import is Successful).
- Eliminates Manual Errors – If Vault Loader is used, typically both IT and the Business are modifying spreadsheets and the opportunity to inadvertently introduce an incorrect value, delete an entry by mistake, etc. is high.
- Repeatable – 1-step migrations are repeatable whereas manual manipulation and generation of spreadsheets will always be unique.
For other information on migrations, some related links include:
- ECM Migrations – Top Ten Planning Tips for a Successful Migration
- What makes migrating from a Legacy ECM systems so difficult?
Please share with us your thoughts and experiences below.
Leave a Reply