A conversion into OpenPass goes well when it is rehearsed and badly when it is improvised. The buyers who consolidate their estate on favourable terms are the ones who arrived with a plan: a documented estate, a reconstructed position, a clear sequence, and a list of the protections that matter most. This is how to build that playbook before the vendor sets the agenda for you.
OpenPass is OpenText's enterprise licensing framework, a single contract with a defined term and dual entitlements that support migration. Folding an estate into it is one of the larger licensing decisions an organisation makes, and it is usually made under some pressure, whether a finding, a renewal, or a migration. Pressure rewards preparation. A buyer with a conversion playbook controls the sequence and the terms. A buyer without one accepts the vendor's draft because there is no alternative ready. The playbook is the difference between shaping the agreement and signing it.
Step one: document the estate
Everything begins with knowing what you have. The first section of the playbook is a complete inventory of the estate: every product in scope, the governing agreement or Additional License Authorization, the metric, the entitled quantity, the deployment, and the environments. This is laborious and it is non negotiable, because every later step depends on it. You cannot reduce a finding, map an entitlement, or protect a right you have not recorded. The estate document is the foundation the rest of the playbook is built on. The method for assembling it is set out in documenting your estate for an OpenPass negotiation.
Where the estate includes Micro Focus products, the inventory must capture the ALA terms specifically, because those are the rights most easily lost in conversion. The way legacy authorizations map into a forward agreement is covered in OpenPass versus Micro Focus ALA carryover, and the interpretation work behind it is our Micro Focus ALA and entitlement review track.
Step two: reconstruct the position
With the estate documented, the second section reconstructs the effective license position independently, against entitlements and the ALAs, before any vendor measurement script runs. This is where service and dormant accounts are disqualified, non production environments are separated from production, decommissioned systems are removed, and indirect access is narrowed to what the contract actually supports. The output is a defensible baseline: the number you can prove, not the number the vendor's measurement would assert. Only this baseline should ever reach an OpenPass agreement. The method is in building an OpenPass target baseline before negotiation.
This step is the same reconstruction that underpins any audit defense, and it is the single largest source of reduction. Converting an unreconstructed estate forward locks every inflation into the new baseline. Reconstructing first means the agreement is built on what the business actually runs. The discipline behind the order is detailed in the complete OpenText audit defense playbook.
Document, reconstruct, reduce, then convert. A playbook that follows that order builds the agreement on a defensible number. One that skips a step builds it on the vendor's.
Step three: model the paths
The third section of the playbook is the decision model. Before committing to conversion, set the OpenPass path against the alternatives from the same corrected baseline: a flat true up at list, a straightforward renewal, or a conversion. The model totals each path across the term, prices in the exposure each one leaves behind, and makes the cheaper, safer choice visible. A playbook without this step risks converting when a different path would have served better, or paying a true up when conversion would have cost less. The method for the comparison is in how to model an OpenPass versus true up scenario and the savings case in how much can OpenPass save versus a list price true up.
The model is also where timing enters the plan. A conversion has a natural window, after the position is settled and before the audit or term formally closes, and the playbook should identify that window in advance rather than reacting to the vendor's clock. The timing argument is in how to time an OpenPass deal against an audit.
Step four: list the protections to win
The fourth section names the protections the conversion must secure, ranked by what matters most for your estate. Defined metrics so the unit of measurement cannot be reinterpreted. A measurement and reporting clause that bounds how and when the vendor can audit. A price hold across the term. Capacity allowances for normal growth. Dual entitlements to cover any in flight migration. Listing these in advance turns the conversion from a draft you react to into a set of objectives you pursue. The protections are catalogued in audit protections to negotiate into an OpenPass agreement and the metric definitions in defined metrics in an OpenPass enterprise agreement.
A good playbook also names the clauses to remove from the vendor's draft, not only the ones to add. Broad measurement rights and open ended audit clauses are the most common terms worth striking, and the case for removing them is in what audit clauses to remove from an OpenPass draft.
Step five: plan the life after signature
The final section of the playbook looks past the signing. A conversion is only as durable as the governance that follows it, so the playbook should assign ownership for tracking the license position against the new agreement, set the cadence for reconciling consumption against entitlement, and define how change events will be recorded. This is what keeps the agreement defensible through the term and turns the next review into a confirmation rather than a discovery. The standing discipline is set out in OpenPass governance and license position tracking.
What a complete playbook produces is calm. In a recent insurance engagement, a Documentum seat count finding that opened at $7.2M settled at $1.6M, a 78 percent reduction, precisely because the work of documenting, reconstructing, and reducing was done before the conversion rather than during it. The settled figure, not the opening one, defined the forward agreement. That is the payoff of preparation. If you want to build this playbook against your own estate before any pressure forces a rushed decision, open a case and we will work it with you.
A rehearsed conversion is a stronger one
The vendor designs the audit and the resolution as two phases of one process, and it arrives prepared for both. A buyer who arrives with a conversion playbook meets that preparation with its own. Document the estate, reconstruct the position, model the paths, win the protections, and plan the governance. Follow that order and the conversion becomes a genuine consolidation on buyer side terms rather than a repurchase dressed as a clean agreement. That is the work of our OpenPass enterprise agreement negotiation track, and it is why the strongest conversions are the ones rehearsed long before the draft arrives.
If you have received an OpenText or Micro Focus audit notice, the first seven days shape every 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 $90M in claims against vendor positions. 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.