Skip to content
Global expertise. Practical outcomes.
Talk to an Expert ↗
TechTiera
Documentum D2 vs Smart View: plan the right transition
Content & Document Management

Documentum D2 vs Smart View: plan the right transition

Compare the user experience and the work required to preserve your business processes.

Short answer

Documentum D2 and Smart View should not be treated as two unrelated repositories. Start with the deployed client, configuration and server versions. Compare the business journeys users need, identify configuration and extension gaps, then prove the target behavior in a representative pilot.

Understand the product and client names

Older documentation uses D2 Classic and D2 Smart View terminology. OpenText’s release resources also use Documentum Smart View, formerly D2 Smart View. Names alone do not establish compatibility or licensing. Record the exact client, configuration, server and integration versions in your estate.

A client transition changes how users reach and act on governed content. It does not automatically mean the repository must be moved. Separate client modernization, server upgrades and content migration into explicit workstreams, with their own dependencies and acceptance criteria.

Compare business journeys, not screenshots

Choose scenarios that represent real work: importing a document, applying metadata, finding the correct revision, completing a review and sharing an approved output. Include administrators, occasional users and users with restricted access. Record what each role must see and what it must be prevented from doing.

  • Check navigation, search, metadata forms and document actions.
  • Test workflow assignments, delegation, notifications and exceptions.
  • Review document viewing, annotations and external integrations.
  • Verify permissions with positive and negative test cases.
  • Check accessibility and the devices people actually use.

Inventory configuration and extensions

List D2 configuration, custom dialogs, widgets, scripts, authentication dependencies and integrations. For each item, decide whether the target provides an equivalent configured behavior, needs an extension or allows retirement of an unused feature. Confirm support against the documentation for your selected release.

Keep the source configuration under change control during the pilot. A configuration import or successful login is not proof that the original business process works. Record gaps, owners and the evidence needed to close them before expanding the rollout.

Pilot the transition and retain a recovery route

Use representative content, accounts and workflows in an isolated environment. Compare results against an approved baseline, including failed actions and restricted documents. Resolve discrepancies before the business signs off. Rehearse restoration of configuration and the operational steps required if cutover must stop.

Plan training around changed tasks, then hand over monitoring and incident ownership. For technical scope, explore Documentum consulting and modernization. Use the Documentum upgrade checklist for the surrounding release work and the migration validation guide when content is also moving.

Sources and further reading

Continue your research

Continue planning

Connect the assessment to implementation and acceptance evidence.

How can we help?

Complete the form to contact our team.