An OpenPass agreement is a single contract over a defined term, which makes it durable but also rigid. Business does not stand still for the length of that term. A division is sold, a subsidiary is spun out, headcount falls, a product line is retired. If the agreement has no language for these events, the buyer keeps paying for software attached to a business it no longer owns, and any reduction in scope can be treated by the vendor as a breach rather than a right. OpenPass exit and divestiture provisions are the clauses that let the buyer reshape its commitment when the business reshapes itself, and they have to be negotiated in at signing because they cannot be added later.
These provisions rarely matter at the moment of signing, which is exactly why they get dropped. They matter intensely two or three years in, when the corporate event arrives and the agreement either flexes or becomes a stranded liability.
Why a fixed term agreement needs an exit
The defined term that gives an OpenPass agreement its stability also locks the buyer into a quantity and a price for years. A subscription or perpetual licence tied to a business unit that is later sold does not automatically follow the unit, nor does it automatically shrink when the unit leaves. Without an exit mechanism, the buyer is contractually obliged to keep paying for capacity it no longer uses, and the vendor has every incentive to hold it to the full commitment. The exposure that builds up at renewal when the estate has shrunk but the contract has not is examined in OpenPass defined term and renewal exposure.
The defined term that makes an OpenPass agreement stable also makes it rigid. Exit and divestiture clauses are what let the commitment shrink when the business shrinks, instead of stranding the buyer.
Divestiture and the right to carve out
When a buyer sells a division, two questions arise: can the divested entity take the licences it was using with it, and can the remaining business reduce its commitment by the amount the division consumed. A well drafted divestiture provision answers both. It should permit a defined volume of licences to transfer to the acquirer of a divested unit, or to be used by that unit for a transition period, and it should allow the seller to reduce its own entitlement and spend proportionally. Without this, the buyer either double pays, continuing to license capacity the divested unit still uses, or breaches the agreement by reducing scope it has no contractual right to reduce.
Reduction rights and the true down question
Exit is not only about divestiture. Estates shrink for ordinary reasons too: a migration off a product, a fall in users, a decommissioned system. An OpenPass agreement that only allows the commitment to grow, never to contract, ratchets cost upward regardless of actual use. Negotiating a true down right, a defined ability to reduce licensed quantities at intervals, keeps the commitment aligned with the business. The mechanics of building reduction into the agreement are covered in OpenPass true up and true down provisions. An agreement that can only true up is an agreement designed to overcharge a shrinking estate.
The audit angle on a shrinking estate
Divestiture and reduction create their own audit risk. When a division leaves with software, or when capacity is reduced, the vendor may later assert that the transfer or reduction exceeded what the agreement allowed and treat the difference as unlicensed use. The exit provisions therefore have to be drafted alongside the audit protections, so that a permitted carve out or true down is documented in a way that cannot be reopened as a finding. The protections that keep a legitimate change from becoming the next dispute are set out in audit protections to negotiate into an OpenPass agreement, and the way a single framework limits future exposure is examined in can OpenPass cap future audit exposure.
Assignment, change of control, and merger
Exit works in both directions. A buyer that is itself acquired, or that merges, needs the agreement to assign cleanly to the new entity rather than terminating or triggering a renegotiation at the worst possible moment. Change of control language should permit assignment to a successor without the vendor's consent being unreasonably withheld, and should prevent the corporate event from being used as a trigger to reprice or to open a compliance review. A buyer planning for growth through acquisition should treat assignment rights as part of the same exit conversation.
How this works in practice
In a recent engagement, a buyer that had signed a multi year OpenPass agreement sold a business division eighteen months in and discovered the contract had no divestiture language at all. The vendor took the position that the full commitment survived the sale and that any licences used by the departing division could not transfer. The defense reconstructed which entitlements the divested unit had actually consumed, established the defensible reduction, and negotiated a carve out that let a defined volume transfer to the acquirer while the seller reduced its commitment proportionally, all documented so it could not be reopened as a finding later. The cost the buyer avoided was the years of payment for software attached to a business it no longer owned. The reconstruction discipline behind that outcome runs through the complete OpenText audit defense playbook, and similar results appear across our engagements.
Negotiating flexibility before you need it
OpenPass exit and divestiture provisions are insurance against a business that will not stay the same shape for the life of the term. Negotiate the right to carve out and transfer licences on a divestiture, the right to true down a shrinking estate, clean assignment on a change of control, and audit protection around every permitted reduction. These clauses cost little at signing and save a great deal when the corporate event arrives. This work sits inside our OpenPass enterprise agreement negotiation track. If you are signing an OpenPass agreement and your business may change shape during its term, open a case and we will make sure the exit is written in.
If you have received an OpenText or Micro Focus audit notice, the first seven days carry more weight 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, reduced 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.