① Guide · M&A and change of control
Most mainframe agreements are non-transferable by default, with assignment and change of control clauses that hand the publisher a consent right. That consent moment is when transfer fees, re-pricing, and template swaps appear. Manage it inside the deal, early, or the vendor manages it for you at the worst time.
A change of control clause is a vendor's invitation to re-price.
In mainframe software, the assumption that licenses travel with the business is wrong often enough to be dangerous. Agreements from IBM, Broadcom (CA), BMC, Rocket Software, Software AG, Compuware (BMC), and Syncsort (Precisely) routinely contain assignment restrictions and change of control provisions: the license cannot move to a new legal entity, or the existing entity cannot change ownership, without the publisher's written consent. That consent is not a formality. It is the vendor's contractual right to be at the table the moment your leverage is lowest, against a closing date you cannot move.
What the vendor does with that right follows a familiar pattern: a transfer or consent fee, a true up to current list pricing, a shift from favorable legacy terms onto the current template, or a demand for a longer commitment in exchange for approval. None of it is automatic, and almost all of it is negotiable, but only if the licensing exposure is mapped and the consents are sought early, while the deal still has room to absorb conditions. Sought late, the same consents become a tax on closing.
| Deal type | What moves | Typical vendor trigger | Primary risk |
|---|---|---|---|
| Stock or share purchase | Entity stays, ownership changes. | Change of control clause. | Consent fee or re-pricing on close. |
| Asset purchase | Licenses assigned to a new entity. | Assignment or anti-transfer clause. | License does not convey; must re-license. |
| Merger | Two estates combine. | Consent plus entitlement overlap. | Duplicate spend, mismatched terms. |
| Divestiture or carve out | One license split between two firms. | Partial assignment, fresh license. | Stranded capacity, lost legacy terms. |
| Transitional service period | Temporary shared use under TSA. | Usage and term restrictions in the TSA. | Runway runs out before re-licensing. |
Patterns commonly observed across mainframe publishers. The actual rights turn on the wording of each agreement and the law governing it, which is why transfer planning starts from the contracts, not the deal summary.
Every mainframe agreement in scope is inventoried and its assignment, change of control, and audit clauses are read against the deal structure. The exposure is known before the vendor raises it, not discovered when consent is requested.
Find the clause before the vendor uses it.
Consents are pursued on a timeline that keeps deal leverage intact, not against a closing deadline. A vendor approached early, with the structure explained, prices consent very differently from one approached the week before signing.
Timing is the whole negotiation.
Consent and re-pricing are separated. A transfer is approval to assign existing entitlements, not an opening to true up to list, swap templates, or extend the term. Favorable legacy terms are defended as part of the transfer, not surrendered for it.
Consent is not a re-purchase.
Where two estates combine, duplicate entitlements and shelfware are surfaced and the combined run rate is right sized. A merger that doubles the contracts is also the moment to consolidate them on your terms rather than the vendor's.
Integration is a consolidation opportunity.
④ What changes with us in the room
A closing deadline is the vendor's best leverage. We take it away by starting early.
Typical renewal reduction
Engagements delivered since 2019
Mainframe spend negotiated on the buyer side
No. Most mainframe agreements are non-transferable by default, with assignment or change of control clauses requiring the publisher's written consent before a license moves to a new entity. Stock, asset, merger, and carve out deals differ in what is legally transferred, but in nearly all of them the vendor has a right to be asked, and that right is where fees originate.
Commonly, where the contract requires consent. Publishers often treat the moment as a re-pricing event: a transfer fee, a true up to list, a template swap, or a longer commitment for approval. The size of the ask turns on timing and leverage, so consent sought early, with structure understood, is far more negotiable than consent sought against a closing deadline.
The harder direction. The divesting entity must split a single license between the business it keeps and the one it sells, and most agreements were never written to be divided. The buyer often needs fresh licenses or a partial assignment; the seller must avoid stranding capacity or losing favorable terms. A transitional service agreement bridges the gap but is temporary by design.
In diligence, not at close. Reading the transfer clauses early surfaces which consents are needed, what each vendor is likely to ask, and how much room the deal has to absorb conditions. Brought in late, licensing becomes a closing tax; brought in early, it is a managed workstream with the leverage still intact.
Related: Contract clauses that cost millions · Audit rights clauses · Building your software inventory · all publisher hubs · contract review service
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →