Inventory the application before assessing a converter
Record the Webtop release, Documentum Server version, custom actions, layouts, object types, workflows, scripts and integrations. Include authentication, browser dependencies and the roles that use each feature. Separate configuration from custom code and record which functions are still needed.
Choose the target release only after reviewing vendor compatibility and your entitlements. A user-interface transition and a repository migration are different changes. Define whether content, versions or audit history will move, or whether the new client will use the existing repository.
Ask for evidence of conversion coverage
For any proposed converter, obtain the supported source and target matrix, eligible conversion items, exclusions and output format. Run an assessment against a copy of your configuration. Ask the supplier to identify the remaining work and the conditions under which the generated output is supported.
- Which actions, forms and configurations are translated?
- Which extensions require redesign or replacement?
- How are unsupported items and errors reported?
- Can changes be traced back to the original configuration?
- What must be retested after a target-release update?
This guide does not assume a particular converter or promise that custom code can be moved automatically.
Validate business behavior and security
Test the journeys that matter to the business, including document creation, metadata, search, viewing and workflow completion. Use both permitted and prohibited actions to prove access controls. Test integrations with realistic responses and failures, not only successful calls.
Compare the results with an approved source baseline. Reconcile counts and metadata when content moves, then sample revision chains and related records. The Documentum migration validation guide provides a structured approach to that evidence.
Rehearse cutover and hand over support
Freeze or track configuration changes, rehearse deployment and agree the conditions that trigger a rollback. Confirm backups, restoration steps and who can authorize go-live. Train users around changed tasks and keep a clear route for reporting discrepancies.
Retain the configuration inventory, gap register and acceptance results with the operational runbook. Discuss the target architecture and delivery scope with TechTiera’s Documentum team. Read the D2 and Smart View comparison when selecting the user experience.
