① Guide · M&A and separation
A divestiture turns one mainframe estate into two licensing problems. Vendors require consent to transfer, open audits in the gap, and quietly bill the same capacity twice. This is the buyer playbook for separating mainframe licenses cleanly, before the deal close hands the vendor the leverage.
The deal team models the business separation. The mainframe license separation is what gets discovered later, at a price.
When a business unit is carved out or sold, its mainframe software does not separate by default. Most licenses are granted to a named legal entity and tied to a specific machine capacity. Move the workload, split the LPARs, or stand the unit up on its own and you have triggered the transfer and assignment terms in every affected agreement. Publishers commonly require consent to transfer, and they grant it on their schedule, with their fees, often alongside an audit that arrives precisely when both sides are least able to push back.
The expensive failure mode is double counting. During the transition the same MSU capacity can be claimed against both the parent and the divested entity, so two organizations pay for one workload. Separating cleanly means reading the assignment and audit clauses early, sequencing consent against the Transition Services Agreement, and building the new entity's baseline before the vendor builds it for you. For the underlying work see mainframe contract review and license negotiation.
Map every mainframe agreement to the entity that holds it and the workload it covers. A divestiture splits along legal lines, so the question is not what runs where, but who is the licensee. Products shared across the retained and divested business are the ones that will cost you.
Each agreement says whether the license can be assigned, whether consent is required, and what a change of control triggers. These terms decide whether the divested unit inherits the license, buys a new one, or runs unlicensed by accident. Read them before the deal terms are fixed.
A Transition Services Agreement keeps the divested unit on the parent's mainframe for a defined window. That arrangement needs explicit vendor use rights, or the parent hosts a company it no longer owns, out of compliance. Line up consent and TSA use rights so neither side is exposed during the gap.
Divestitures invite audits because the disruption is visible and the timing favors the vendor. Build both entities' baselines independently, document the capacity split, and prepare the position before a notice arrives. An audit met with a finished reconciliation is a formality, not a crisis.
Through the transition, confirm that capacity is counted once. Sub-capacity reporting, defined capacity limits, and product entitlements all need to reflect the split, or both organizations pay for the same MSUs. This is the leakage no one models and everyone funds.
The standalone unit is a fresh buyer with its own leverage, and inherited terms are rarely the right terms at its smaller scale. Treat day one agreements as a negotiation, with caps, exit rights, and metrics fit to the new footprint, not a copy of the parent's deal.
| Separation event | The exposure | The buyer move |
|---|---|---|
| License tied to named entity | Transfer requires consent and fee | Negotiate assignment rights early |
| Shared products across units | Both sides claim entitlement | Split entitlement before close |
| TSA hosting on parent system | Parent out of compliance | Secure explicit TSA use rights |
| Capacity split mid transition | Same MSUs billed twice | Reconcile to count once |
| Inherited parent contract | Terms oversized for new unit | Renegotiate at the new scale |
Transfer, consent, and audit behavior described here are patterns commonly observed in mainframe divestitures, not fixed vendor policy. Your agreements and the deal structure govern.
Usually only with vendor consent. Most mainframe licenses are granted to a named legal entity, and a carve-out or change of control commonly requires the publisher to approve the transfer, often with fees or fresh commitments. A carve-out or assignment clause negotiated in advance is what makes a clean separation possible.
A divestiture forces visibility into who runs what, and vendors commonly use the moment to open an audit, since both the parent and the buyer now have reason to true up. The risk is double counting: the same MSU capacity being claimed against both entities at once.
A Transition Services Agreement lets the divested unit keep running on the parent's mainframe and software for a defined period after close. It needs explicit vendor use rights for that arrangement, or the parent risks being out of compliance for hosting an entity it no longer owns.
Audit notice or renewal under 18 months out? We mobilize within 48 hours. Carve-out closing soon? We separate the licenses before the vendor sets the price.
Separate the licenses on your timeline, or fund the vendor's.
Related guides: building your mainframe software inventory, contract clauses that cost millions, and negotiating a multi year mainframe ELA. Explainers: what audit clauses allow and escrow and continuity rights. Commercial: mainframe contract review.