OpenPass versus traditional perpetual licensing

OpenPass and traditional perpetual licensing are two different ways of holding the right to run software, and the difference matters most under audit. A perpetual license is an asset you own. An OpenPass agreement is a defined term commitment you hold for a fixed window. Knowing which model governs each part of the estate, and what each implies for renewal and audit exposure, is the starting point for any conversion decision.

For estates that have run OpenText and Micro Focus products for years, the question is rarely abstract. A perpetual estate exists, an audit arrives, and the vendor proposes converting forward into OpenPass as part of the settlement. Whether that conversion is a good idea depends on understanding precisely what is being traded: an owned asset for a term commitment, with all the consequences that follow for cost, flexibility, and audit risk.

What perpetual licensing actually grants

A traditional perpetual license grants the right to use a specified version of the software indefinitely, once the license fee is paid. Ownership of the right does not expire. What does recur is maintenance and support, paid annually, which entitles the buyer to updates and assistance. A buyer can, in principle, stop paying maintenance and continue running the owned version, accepting that it will no longer receive updates. The perpetual model therefore separates the right to use, which is owned, from the right to support, which is rented.

Under audit, the perpetual model has a specific shape. The vendor checks deployment against the licensed quantities and versions. Because the licenses are owned, the dispute is usually about counts and definitions rather than about the right to run at all. That is also why the deemed acquisition remedy bites: a shortfall against owned entitlements is treated as a new acquisition at then current list price, plus back maintenance, plus the cost of the audit.

What OpenPass changes

OpenPass replaces the owned asset with a defined term commitment. Instead of owning licenses indefinitely, the buyer holds the right to use the covered products for the term of the agreement, under one consolidated contract. The advantages are real: consistent definitions across products, a single renewal to manage, dual entitlements that support migration, and the opportunity to negotiate protections that a patchwork of perpetual schedules never offered. The detail of how the framework works is in what is OpenPass and how does it work.

The trade is that the right to use now has an end date. At the end of the term, the agreement must be renewed or the right lapses. That introduces a renewal event, and renewal is where pricing pressure and audit risk tend to return together, a dynamic examined in OpenPass defined term and renewal exposure. A buyer moving from perpetual to OpenPass is exchanging the permanence of an owned asset for the consolidation and protections of a managed term. Whether that exchange favours the buyer depends entirely on the terms negotiated inside it.

How each model behaves under audit

Under a perpetual estate, the audit question is whether deployment exceeds owned entitlements, and the remedy for a shortfall is the deemed acquisition clause at list price. Under OpenPass, the audit question is whether usage stays within the metrics defined for the term, and the consequence of a gap is reconciled within the agreement, often at renewal. Neither model removes audit risk. They relocate it. The perpetual model concentrates risk in the count against fixed entitlements. The OpenPass model concentrates it in the definitions of the metrics and in the timing of the renewal.

This is why metric definitions matter so much in an OpenPass agreement. A perpetual license counts a defined quantity of a defined version. An OpenPass metric, if loosely defined, can be reinterpreted at audit to count more than the buyer expected. The defense in both cases is precision, but the locus of the precision differs. Pinning down OpenPass metrics is covered in how to challenge OpenPass metric definitions.

Cost over the long run

Cost comparison between the two models is rarely as simple as comparing a one time fee to a recurring one. A perpetual estate carries ongoing maintenance, and over a long enough horizon the cumulative maintenance can rival the original license fee several times over. An OpenPass term spreads cost across the term and can include a held price, but it commits the buyer to continued payment to retain the right to run. The right comparison is total cost over a realistic horizon, including maintenance, growth, and the cost of any true up the model permits. Building that comparison is the subject of how to model an OpenPass versus true up scenario, and reducing total cost through a well structured conversion is covered in reducing total cost with an OpenPass conversion.

Choosing in the context of an audit

In a recent engagement, an estate with a largely perpetual footprint faced a finding and a vendor proposal to convert the whole estate into OpenPass. The right answer was not automatic. The work was to reconstruct the perpetual entitlements accurately, reduce the finding to defensible usage, and only then compare a corrected perpetual position against a properly negotiated OpenPass term. In that case the consolidation and the protections made the conversion worthwhile, but the decision rested on the corrected numbers, not on the vendor's framing. The point is that the choice between the models should be made with an accurate picture of what is owned and what is used, which is the heart of our OpenPass enterprise agreement negotiation work and is set in context in the complete OpenText audit defense playbook.

The decision in summary

Perpetual licensing gives permanence and a count based audit exposure. OpenPass gives consolidation, defined metrics, migration rights, and negotiable protections, in exchange for a defined term and a renewal event. Neither is universally better. The right choice depends on the estate, the horizon, and above all on the accuracy of the position the buyer brings to the table. A conversion decided on the vendor's opening number is a poor decision. The same decision made on a reconstructed position, with the protections negotiated in, can be a strong one. If a conversion from perpetual to OpenPass is being proposed alongside a finding, open a case and decide on corrected numbers.