Supports custom applications & document types
CERTIFICATES
Content migration to OpenText Documentum
Migrate from more than 15 source systems to OpenText Documentum. Our Documentum importer supports all available features of the platform including the whole stack of its applications and different systems: D2, D2 for Life Sciences, DCM, and xCP. Our inplace migration feature enables you to enhance the existing attribute model, change the folder structure, or rearrange security rules without the need of a classical migration. All of the configurations are applied without additional programming or scripting.
Platform-specific use cases
Webtop to D2 in-place migration
The in-place migration capabilities for OpenText Documentum D2 of migration-center allow clients to migrate Webtop-based objects to D2 applications without moving the content to a new repository. Original object IDs remain unchanged during such an in-place migration approach and all business rules like auto-naming, auto-linking, auto-security etc. are automatically applied to the objects. In addition, cabinets, object types, metadata, folder structures, access rights etc. can be changed as well without executing a classic data migration.
Whitepaper
OpenText Documentum In-place Migration
Repository consolidation
Enterprise information and documents are often spread around diverse IT locations using different OpenText Documentum repositories and some installations are outdated. With migration-center these repositories may be easily consolidated into one in order to maintain critical documents with safety, consistency, and regulatory compliance while reducing maintenance costs substantially.
In-place data cleansing & restructuring
Our in-place migration and cleansing capabilities for OpenText Documentum allow clients to change cabinets, object types, metadata, folder structures, access rights etc. without migrating the objects from one to another repository. This feature is mainly used to clean up or enhance the data quality of an OpenText Documentum repository or simply align existing content with the current business requirements. Original object IDs remain unchanged during such an in-place migration approach.
Whitepaper
Opentext Documentum In-place Migration
Content store & storage replacement
Are you looking for a tool that can move only the content from one storage provider to another without moving the whole objects themself and avoid a time-consuming classic migration? There are some use cases when you need to replace the OpenText Documentum underlying storage and sometimes simply copying the files is not an option. On top of a classic migration from one platform to another, with migration-center you can also do an in-place update and then only change the bits you really need, e. g. only tell the Content Server to move the content from an EMC Centera to a file share.
Blogpost
Moving Your OpenText Documentum Content From Centera To Another File Store
Update or replace OpenText Documentum Server or the underlying database
From time to time and several different reasons the OpenText Documentum platform components may need to change. It could be the server hardware, the operating system, the content server version, or the database (vendor). Some of the operations can simply be done with running the dctm installer, but if that is not sufficient, migration-center can help with a “migration”. With migration-center you may change any underlying component without interrupting the business: It can clone the repository to a newly installed system and migrate documents in the background until the final switch.
Blogpost
Upgrading/replacing a database or OpenText Documentum server
All migration path capabilities in one list
The Connector Matrix allows you to create all currently available migration paths (source system in connection with target system) and to list the supported capabilities and versions.
Source System
Supported versions:
Target System
Supported versions: 5.3 - 20.2
| Feature | Category | Support |
|---|
