eDOCS DM versus Documentum metric comparison

eDOCS DM and Documentum are both OpenText content platforms, but they were never licensed the same way, and an audit that treats them as interchangeable will produce a finding that overstates one or both. Understanding where the metrics diverge is the first defense against a count that borrows the harsher definition from the wrong product.

When a single estate runs both eDOCS DM and Documentum, the audit team often reaches for a single user model and applies it across the board. That convenience favors the vendor. eDOCS DM grew out of the legal and professional services world, where the document management metric is built around the practitioner who files and retrieves matter content. Documentum grew out of enterprise content management, where the named user and consumer definitions attach to the repository and its server deployments. The two products count different things, and a defensible position begins by keeping them apart. Because the OpenText EULA makes compliance the sole responsibility of the licensee, the burden of showing which metric applies to which product sits with the buyer, but that burden is also where the reduction is found.

Why the eDOCS metric and the Documentum metric are not the same

The eDOCS DM license is organized around the people who use the document management system to do legal or professional work. The metric tends to follow the practitioner population, the lawyers, paralegals, and support staff who create, file, and retrieve documents in the system. Documentum, by contrast, is licensed against named users and, depending on the entitlement, server deployments and repository access, with a consumer definition that the audit applies to anyone or anything touching the repository. The risk in a mixed estate is that the Documentum consumer definition, which is broad, gets applied to the eDOCS population, or that an eDOCS practitioner headcount is mapped onto Documentum named user pricing. Either substitution inflates the finding, and neither is supported by the entitlements.

The point to hold is that each product carries its own licensed unit, and the unit is defined in that product's entitlement, not in whichever definition produces the larger number. A comparison done correctly assigns every account and every system to the right product, then applies that product's own metric.

Where the comparison matters in a finding

User population overlap

Staff who appear in both systems can be counted twice if the products are merged into one metric. A practitioner who files in eDOCS DM and also holds a Documentum account is one person, but a careless count lists two chargeable users. Separating the populations, and reconciling the overlap, is the same discipline set out in how to challenge a Documentum repository headcount.

Consumer and read only definitions

The Documentum consumer definition is broad, and the eDOCS model does not share it. Applying the Documentum consumer reach to eDOCS users, or counting read only eDOCS access as a chargeable Documentum consumer, overstates the finding. The boundary is the one explained in Documentum read only users and the consumer definition.

eDOCS specific counting

The eDOCS population has its own counting traps in regulated professional environments, set out in eDOCS user counting in legal and professional services. Those traps do not transfer to Documentum, and the two should be argued on their own terms.

How we defend a mixed eDOCS and Documentum finding under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. In that window we take over the single controlled channel and ensure that the extracts are captured separately for each product, because once the data is merged into one spreadsheet the metric separation becomes much harder to prove.

Reconstruct. We build the effective license position for each product independently, mapping every account and system to eDOCS DM or to Documentum and applying that product's own entitlement and metric. The reconstruction is what keeps the broader definition from contaminating the narrower population.

Rebut. We challenge any line where the audit has applied the wrong product's metric, removed the double counted users who appear in both systems, and held each consumer definition to its own product. The finding falls by the value of every account assigned to the correct, and usually cheaper, metric.

Resolve. We settle on the separated position and, where it serves you, convert forward into an OpenPass agreement that records how eDOCS and Documentum are each measured, so the next review starts from a defined basis rather than a merged extract.

An anonymised outcome

The reason metric separation is worth the effort is the remedy that sits behind the count. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost OpenText incurs performing the audit, so every user assigned to the cheaper correct metric removes that fourfold charge. In our anonymised insurance engagement, case file E-01, a Documentum centred ECM finding fell from $7.2M to $1.6M, a 78 percent reduction, in part because accounts had been swept into a single broad definition that the entitlements did not support once each product was measured on its own terms.

Compare before you concede

The lasting lesson is that two products are two metrics, and a finding that collapses them into one is a finding built for the vendor's convenience. A buyer who insists that eDOCS DM be measured as eDOCS DM and Documentum as Documentum, with the overlap reconciled and each consumer definition held to its own product, removes a layer of inflation before the substantive arguments even begin. To prepare that separation, read how to reconcile Documentum entitlements before an audit, and to see how it fits the wider defense, read our ECM and Documentum audit defense track. For the full method, read our complete OpenText audit defense playbook for 2026. If your estate runs both products and the finding has merged them, open a case.

A practical sequence for a mixed estate

The order of work matters. We begin by inventorying which systems are eDOCS DM and which are Documentum, because a single label applied to the whole estate is where the merged metric takes hold. We then pull the user population for each product separately and identify the people who hold accounts in both, since those individuals are the most common source of double counting. Only after the populations are separated and reconciled do we apply each product's own metric, eDOCS DM against its practitioner based model and Documentum against its named user and consumer definitions.

This sequence keeps the broader Documentum consumer definition from leaking onto the eDOCS population, and it keeps an eDOCS practitioner headcount from being priced as Documentum named users. The discipline is the same one that underlies a clean Documentum entitlement reconstruction: separate the products, document the populations, and let each entitlement govern only what it was written to cover.