OpenPass versus Micro Focus ALA carryover.

When a Micro Focus estate converts into an OpenPass agreement, the central question is what carries over. The legacy entitlements you hold today are written under Additional License Authorizations, and those ALAs define rights that an OpenPass contract may or may not preserve. The gap between what the ALA grants and what the new agreement records is where money is quietly lost, and it is the first thing to map before you sign.

The Micro Focus acquisition closed on 31 January 2023, folding security, DevOps, COBOL, and analytics product families into OpenText. Most of those products are governed by Additional License Authorizations rather than the OpenText EULA, and the ALA is the document that actually defines a metric, a capacity, or a bundled right. OpenPass is a forward framework. It does not automatically inherit the precise wording of every legacy ALA. A buyer converting an estate into OpenPass is therefore translating one entitlement language into another, and translations lose things unless they are watched closely.

What an ALA grants that you do not want to lose

An Additional License Authorization is the product specific rulebook for a Micro Focus license. It states the metric, the capacity, the permitted environments, and any bundled components that travel with the entitlement. Over years of purchases, an estate accumulates ALAs with favourable terms: a generous metric definition, a non production allowance, a bundled module, a capacity ceiling set higher than current use. These are real rights with real value, and they exist because they were negotiated or granted at the time of purchase. The risk in conversion is that a forward agreement records a simpler, cleaner entitlement that happens to be worth less than what you already hold.

Reading the ALA correctly is the prerequisite to protecting it. The interpretation traps that make ALAs difficult are the core of our Micro Focus ALA and entitlement review track, and the way acquisitions reshaped the surrounding terms is covered in how acquisitions shaped OpenPass terms.

Where the carryover breaks

Carryover breaks in predictable places. The first is metric translation, where an ALA metric is mapped to an OpenPass metric that counts differently, so the same deployment produces a higher number under the new agreement. The second is bundled rights, where components that travelled free inside an ALA are unbundled and repriced in the conversion. The third is capacity, where an ALA ceiling set above current use is reset to current use, removing headroom you already paid for. The fourth is environment scope, where a non production allowance in the ALA is narrowed or dropped in the new contract.

Each break looks like a tidy simplification and functions as a quiet price increase. The defense is to map every legacy entitlement to its OpenPass equivalent and to insist that the new agreement preserves the more favourable of the two wherever they differ. The mechanics of preserving legacy rights are set out in OpenPass migration rights and legacy entitlements, and the metric arguments themselves are in how to challenge OpenPass metric definitions.

The carryover map you build before signing

Before any OpenPass draft is accepted, build a carryover map. List every product in scope, the governing ALA, its metric, its capacity, its bundled components, and its environment rights. Beside each, record the OpenPass equivalent the vendor proposes. The differences are the negotiation. Where the OpenPass term is more favourable, accept it. Where the ALA term is more favourable, insist the agreement carry it forward. This is not an exotic demand. It is the buyer holding the vendor to the value of entitlements already purchased, and it is far easier to win at conversion than to recover afterward.

Building that map depends on having an accurate estate first. You cannot protect an entitlement you have not documented. The discipline of capturing the estate is in documenting your estate for an OpenPass negotiation, and turning that documentation into a defensible opening position is in building an OpenPass target baseline before negotiation.

Carryover during an active audit

Carryover matters most when the conversion follows a finding. A Micro Focus audit prices overuse against the ALA, and if the resolution converts forward into OpenPass while the ALA rights are being renegotiated, the vendor has an incentive to settle the finding generously and recover the value through a weaker forward entitlement. A buyer who watches only the headline finding can win the visible number and lose the invisible one. The defense is to treat the finding and the carryover as a single negotiation, where a reduction in the finding is not traded for a reduction in legacy rights.

In a recent technology engagement, a Fortify developer seat overclaim opened at $4.5M and settled at $0.9M, an 80 percent reduction, but the more durable win was preserving the favourable seat definition from the legacy authorization into the forward agreement, so the same argument would not have to be made again at the next review. The finding was the visible victory. The carryover was the lasting one. If you are converting a Micro Focus estate under audit pressure, open a case before you accept a forward entitlement that quietly undersells what you already hold.

Carryover is value you have already paid for

The reason carryover deserves this much attention is simple. The entitlements written in your existing ALAs were paid for once. A conversion that fails to preserve them asks you to pay for the same rights again, dressed as a cleaner agreement. OpenPass is a strong framework when it records the full value of what you already own, and a costly one when it records less. Mapping ALA against OpenPass term by term, and holding the line where the legacy right is stronger, is how a conversion becomes a genuine consolidation rather than a hidden repurchase. That work sits at the centre of our OpenPass enterprise agreement negotiation track, and the wider method is in the complete OpenText audit defense playbook.