Choose an OpenText licensing partner for its entitlement archaeology, because an OpenText estate is rarely one contract — it is acquisition layers of Content Server, Documentum and former Micro Focus paper, each with its own metrics, user types and module entitlements. The partner worth hiring can reconstruct what you actually own across those layers, police named-user-type drift before a verification review does, and model a Cloud Editions conversion from your usage data rather than the vendor’s proposal.
Published 23 January 2026 · Last reviewed 26 February 2026
OpenText grew by acquisition, and its customers’ license positions show the strata: Content Server and Extended ECM on OpenText’s own historical paper, Documentum estates carried over from the 2017 Dell EMC deal with order forms sometimes decades deep, and — since January 2023 — the former Micro Focus portfolio (ALM, UFT, LoadRunner, Fortify, NetIQ and more), itself an accumulation of Borland, HPE Software and NetIQ heritage, parts of which have since been divested onward. Each layer carries its own metrics: tiered named-user types and module entitlements in content management, concurrent users and per-core counts on heritage paper, transaction volumes in the B2B network, and subscription terms under the Cloud Editions program.
Two consequences follow for anyone choosing help. First, no single “OpenText metric” exists to be expert in — competence means range across the layers plus the discipline to reconstruct entitlement before debating deployment. Second, the commercial pressure points are predictable: maintenance renewals with uplift, conversion proposals onto Cloud Editions, and license verification reviews that surface user-type drift. The work maps to compliance assessment, renewal negotiation, audit defense when a review is live, and licensing advisory for the right-sizing between events.
General information for buyers, not legal or licensing advice; no firms are named here. The directory, filtered to OpenText, lists the firms covering this vendor — alphabetical, balanced pros and cons, listed not ranked.
Entitlement reconstruction first. The opening deliverable on this vendor is a layered entitlement map: what was bought, under which heritage, with which migration and exchange clauses. A firm that starts from the vendor’s install-base report instead of your order forms has conceded the baseline. Ask for an anonymized example (labelled indicative) of an entitlement rebuild across at least two acquisition layers.
User-type discipline. In Extended ECM and Documentum, the money question is rarely “how many users” but “which type”: full named users against occasional, read-only or external types, each priced differently. The characteristic finding in a review is activity that outgrew the type — plus leavers never deprovisioned and integration accounts with no stated position. A partner should explain exactly how it samples activity logs to defend or rescope a user-type split.
Both heritages, post-2023. The Micro Focus acquisition put testing, security and identity products on the same commercial table as content management, with bundling and co-termination consequences — and the subsequent divestments mean some products’ long-term contract homes deserve explicit treatment at renewal. Fluency across both heritages is now part of the job description; the OpenText vendor hub maps the landscape.
Conversion arithmetic. Cloud Editions proposals repaper perpetual estates onto subscription. The honest evaluation is module-level: measured use, conversion credits, exit terms, and what retiring the perpetual fallback is worth. Insist on seeing that model built from your data — the reasoning parallels the timing rules in when to bring in help.
| Estate layer | Typical meters | Characteristic exposure | What a partner verifies |
|---|---|---|---|
| Content Server / Extended ECM | Tiered named-user types; module entitlements | Occasional or read-only users whose activity matches full users; modules enabled beyond entitlement | Activity sampling against user types; module inventory against order forms |
| Documentum | Named users, CPU/core on older paper | Decades-old order forms nobody can produce; inactive accounts inflating counts | The entitlement rebuild, deprovisioning hygiene, migration-clause rights |
| Micro Focus heritage (ALM, UFT, LoadRunner, Fortify, NetIQ) | Concurrent users, named users, per-core | Concurrent peaks unmeasured for years; license servers misconfigured against contract terms | Measured concurrency against entitlements; which products’ contract homes changed post-acquisition |
| B2B / Business Network | Transaction and document volumes | Volume growth outpacing committed tiers | Actual volumes against tier commitments before the renewal conversation |
| Cloud Editions subscriptions | Subscription per user/module bundle | Paying for bundled modules unused since conversion | Consumption against the bundle; renewal-date leverage and exit terms |
The table is the interview: a candidate firm should be able to talk specifically about whichever layers your estate carries, and say plainly where its experience is thinner.
Dedicated OpenText boutiques are scarce; the vendor is usually one practice within broader SAM and negotiation firms, so the bench question — who has actually done this vendor, on which layers, how recently — matters more than the logo wall. Independent firms take fees from buyers only, which is the clean configuration when the right advice is to drop shelfware support rather than buy more. Resellers and integrators carry real program knowledge, and many OpenText estates were sold and implemented through them — but margin and services revenue grow with your commitment, a factual trade-off that belongs in writing; the protocol is in the independence test. Big Four practices surface when OpenText is a line inside a larger transformation or audit response; ask the alliance-disclosure question. Law firms lead only when a verification review hardens toward dispute — the split is mapped in lawyer or consultant. SAM tooling reads installed components reasonably but maps user types and module entitlements poorly out of the box; treat tool output as raw material.
Fee models are the standard four — fixed-scope, day-rate, retainer, gain-share — and the usual caution applies with extra force: on a vendor where remediation often means rescoping user types rather than cutting spend, “savings” in a gain-share formula needs a precise definition. See fee models explained; no prices are published on this site.
1. “Do you, or any affiliate, earn OpenText channel revenue — resale, implementation, renewal commissions — today?” In writing.
2. “Show us an entitlement rebuild you have done across acquisition layers — what paper existed, what was missing, how you closed it.” (Anonymized, labelled indicative.)
3. “How do you sample activity to defend a user-type split in Extended ECM or Documentum?”
4. “Which of our Micro Focus heritage products have you handled since the 2023 acquisition, and what changed for them?”
5. “Build the outline of our Cloud Editions conversion model: what data do you need, and what would make you advise against converting?”
6. “What terms have you moved at an OpenText renewal — uplift caps, support right-sizing, reinstatement waivers, co-termination?”
7. “Who specifically would staff our work?” The fuller checklist is in 20 questions to ask.
Red flags, OpenText edition: advice that starts from the vendor’s deployment report rather than your entitlements; a conversion recommendation with no module-level usage model behind it; an integrator-advisor who has not disclosed its implementation revenue; user-type opinions offered without an activity-sampling method; and a firm that cannot say which acquisition layers it has actually worked.
Yes — license verification reviews are part of the commercial model, and the Micro Focus side of the house brought its own established compliance program into the 2023 acquisition. Reviews are typically triggered around renewals, migrations the customer declines, or estates that have gone quiet commercially, and they resolve through negotiated true-ups far more often than through formal dispute.
User-type drift in content management estates: people licensed as occasional or read-only users whose actual activity matches a full named user, accounts never deprovisioned after leavers, and system or integration accounts touching the repository without a clear license position. On legacy Documentum and Micro Focus heritage estates, the equivalent exposure is concurrent-use metrics that nobody has measured properly in years.
It widened the table. ALM, UFT, LoadRunner, Fortify and NetIQ products now sit under OpenText commercial management alongside Content Server and Documentum, which creates bundling opportunities and co-termination questions that did not exist before 2023 — and parts of the former Micro Focus portfolio have since been divested, so support and contract continuity for those products deserve explicit treatment at renewal. A partner should be fluent on both heritages before advising on either.
It is a genuine trade-off, not a default. Cloud Editions repaper the relationship onto subscription terms — which can reset pricing and bundle modules attractively, but also retires the fallback position a maintained perpetual license preserves. The decision rests on module-level arithmetic: what you actually use, what the conversion credits, and what the exit looks like. That modelling, from your data, is the first deliverable to ask of a partner.
Letting maintenance lapse usually means reinstatement fees or full re-licensing if you later need support or upgrades, and it weakens your position if a verification review follows. Estates carrying shelfware are better served by right-sizing the support base at renewal — dropping what is documented as unused — than by lapsing coverage on products still in production.
Before a maintenance renewal or Cloud Editions proposal lands; at the first sign of a verification review; and ahead of estate events that move the count — an ECM consolidation, a Documentum migration decision, integrations that put new systems in front of the repository, or divestment questions on former Micro Focus products. The cheapest engagement is the one that reconciles entitlement before the vendor asks.
Adjacent guides and the working pages for this vendor, plus the directory filtered to OpenText.
The full OpenText landscape on this site →
The firms doing maintenance and conversion negotiation →
The firms building the layered entitlement position →
Another portfolio vendor with five meters running at once →
Fixed, day-rate, gain-share — and their incentives →
Every field guide on the site →
Tell us which OpenText situation you are in — a verification review, a maintenance renewal, a Cloud Editions proposal or a Documentum decision — and we will route your brief to firms that genuinely cover it, with each firm’s independence status stated on its profile. Free for buyers, no vendor ever sees your brief, no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.