OpenPass Dual Entitlements During Migration

The single most attractive feature of an OpenPass enterprise agreement is also the one most often written loosely: the right to run a legacy deployment and its replacement at the same time. OpenText calls this dual entitlement, and it exists to remove the migration penalty that buyers have suffered for years, where moving from one product generation to the next briefly doubled the licensed footprint. Used well, OpenPass dual entitlements let you stand up the new environment, validate it, and retire the old one without ever appearing out of compliance. Written carelessly, the same clause becomes the exact surface a compliance review uses to manufacture a finding two years later.

This article explains how dual entitlement is supposed to behave during a migration, where the overlap window quietly creates exposure, and what to fix in the contract language before you sign. If you are reading this while still inside an active audit, begin with our complete OpenText audit defense playbook, then come back to plan the forward agreement. The conversion is where the real money is won or lost, and the dual entitlement clause is its center of gravity.

What dual entitlement actually grants

OpenPass is OpenText's enterprise licensing framework: one contract, a defined term, and consolidated entitlements that, during a migration, allow concurrent use of both the source product and its target. The premise is simple. If you are moving from an older content repository to a newer one, or from a perpetual deployment to a subscription footprint, you cannot flip a switch overnight. Data has to be migrated, integrations rebuilt, users retrained, and the old system kept live for cutover and rollback. Dual entitlement says that during this period both systems are licensed under the single agreement, so the temporary overlap does not count as overdeployment.

The grant sounds unconditional, but it never is. Three variables decide whether it protects you: the duration of the overlap window, the scope of products it covers, and the metric definitions applied to each side. Get any of the three wrong and the protection you negotiated evaporates precisely when you rely on it. Most Micro Focus products are governed by Additional License Authorizations, the ALAs, and those authorizations control how each product is counted even inside an OpenPass wrapper. Reconciling the ALA definitions with the dual entitlement language is the work that separates a clean migration from a future finding.

Where the overlap window becomes exposure

The first trap is duration. Vendors prefer a short, fixed overlap, often expressed as a number of months from the agreement effective date rather than from the start of each product migration. Real migrations slip. A repository move that was scoped for six months runs nine because a downstream integration was more entangled than anyone realized. If the dual entitlement clock started at signature and expired on a calendar date, the legacy system that you are still decommissioning is now, on paper, unlicensed. The next compliance review measures it, counts it at then current list price, and adds back maintenance. The overlap window must run from the start of the actual migration of each product, and it must be extendable on notice rather than on renegotiation.

The second trap is scope. Dual entitlement is frequently drafted to cover a named pair of products, the specific source and target you described during the sale. But enterprise migrations rarely move in clean pairs. A content platform migration pulls along connectors, archive tiers, and capture components, each of which may be a separately counted product under the ALAs. If the clause only protects the headline products, every adjacent component running in parallel becomes a measurable overlap. The fix is to define the overlap by environment and migration program, not by a fixed product list.

The third trap is the metric mismatch. The legacy product may have been licensed by named users while the target is licensed by a capacity or consumption metric. During the overlap, a single human being can appear as a named user on the old side and as consumption on the new side, and a naive measurement counts both. Dual entitlement should explicitly state that the same underlying usage is not counted twice across the source and target during migration. Without that sentence, the very people you are migrating become a double charge.

How we defend the overlap

Our method applies the same four operations to a conversion that it applies to an audit. We Respond by taking control of the conversation before commitments harden. We Reconstruct your effective license position independently, mapping every product in the migration program against its ALA definition so we know exactly what is moving, in what metric, and for how long. We Rebut the vendor's preferred overlap language, replacing fixed calendar windows with migration anchored windows and replacing named product lists with environment level coverage. We Resolve by writing the dual entitlement clause so the overlap is defined, extendable, and free of double counting, and so the agreement carries audit protections forward.

The reconstruction step is where exposure is found before the vendor finds it. A migration program almost always touches more counted components than the sales narrative admits, and each of those components is a line a future review can inflate. Building the entitlement baseline first, against the authorizations rather than against the vendor's measurement script, means you enter the negotiation knowing your real position. For the mechanics of that baseline, see how we approach establishing your entitlement baseline for OpenPass and how to keep the defined metrics working in your favor.

A migration overlap, defended

In a recent engagement, a buyer converting after an audit settlement was offered an OpenPass agreement with a twelve month dual entitlement window measured from signature. The migration program covered a primary content repository plus four adjacent components, none of which were named in the draft overlap clause. Had the agreement been signed as written, the four components running in parallel would have been fully measurable the moment the calendar window closed, and the migration was already tracking past twelve months. We reconstructed the program, rewrote the overlap to run from each product's migration start with extension on notice, and defined the coverage by environment so every component in the program was protected. The finding that would otherwise have surfaced at the next review simply never existed, because the parallel running systems were licensed exactly as the migration required.

That outcome is consistent with the pattern across our practice. We have defended more than 200 OpenText and Micro Focus audits and reduced the average opening finding by 68 percent, and a large share of forward exposure is removed not in the audit itself but in the conversion that follows it. The case files behind these numbers, including the insurance Documentum reduction from a 7.2 million dollar finding to 1.6 million settled, are summarized in our engagements.

What to lock down before signature

Before you sign an OpenPass agreement that relies on dual entitlement, confirm the overlap window runs from the migration start of each product, not from the effective date. Confirm it is extendable on notice. Confirm coverage is defined by migration environment and program rather than by a fixed product list. Confirm the agreement states that the same underlying usage is never counted twice across source and target. And confirm each side's metric is defined precisely enough that no reviewer can reinterpret it later. These same disciplines carry into the audit protection clauses you should demand, the term length you negotiate, and the price protection you secure, covered in audit protection clauses to demand in OpenPass, negotiating the right OpenPass term length, and price protection and caps in OpenPass.

Dual entitlement is a genuine improvement over the old migration penalty, but only when the clause is written to match how migrations actually behave. The vendor drafts it for the clean, on time, two product migration that almost never happens. Your job, with the right defense beside you, is to draft it for the real one. To pressure test your dual entitlement language before you sign, open a case and we will review the draft against your migration program.

If you have received an OpenText or Micro Focus audit notice, the first seven days decide more than any week that follows. OpenText Audit Defense is an independent, buyer side practice founded in 2020 by former vendor compliance leadership. We have defended more than 200 audits, cut the average finding by 68 percent, and mitigated more than 90 million dollars in claims. We do not resell OpenText software and we are not affiliated with OpenText Corporation. To open a case, use the contact form on this site.