① Journal · Corporate events
A divestiture turns one mainframe license position into two, and the contracts almost never split cleanly. Transfer commonly requires the vendor's consent, and the moment a vendor learns a deal is happening, the split becomes a priced event. The protections that matter are the ones negotiated before close.
A divestiture hands the software vendor a moment of leverage the buyer rarely sees coming: a deal with a deadline that needs the vendor's cooperation.
Mainframe license agreements are commonly written so that assignment or transfer to another legal entity requires the licensor's consent. In a divestiture that consent becomes a gate. The seller needs to provide the carved out business with the software it runs on, often through a transition services agreement (TSA) for a defined period, and then a permanent license position for the new standalone entity. If the original agreement does not grant divestiture and TSA rights, the vendor is under no obligation to cooperate on the buyer's timetable, and a deal with a signed close date is a powerful place for a vendor to stand. The pattern commonly observed is that the vendor reads the agreement, finds the rights absent or ambiguous, and treats the split as an opportunity to write new license fees, transition fees, or both. For the contract level mechanics see mainframe contract clauses that cost millions.
The asymmetry is timing again. The corporate deal has a hard close. The software consent does not, unless the contract created one. That gap is where divestiture costs are born, and it is almost always cheaper to close it years earlier, at signature, than under deal pressure. Where the rights were never written, the second best move is to engage the vendor early, on your terms, before the close date becomes the vendor's lever.
| Protection | What it grants | What it prevents |
|---|---|---|
| Divestiture transfer right | Assignment or novation to the carved out entity | Consent used as a fee gate at deal close |
| TSA usage right | The divested unit runs on the license during transition | A separate transition license sold under pressure |
| Capacity split basis | Entitlement divided by an agreed, measured method | Both halves charged as if at full original capacity |
| No double counting | One estate's MSU not billed twice across the split | Seller and buyer both paying for the same capacity |
| New entity pricing floor | Pre agreed rates for the standalone agreement | The smaller entity priced as a fresh, weak buyer |
| Audit standstill | No audit triggered by the corporate event itself | A divestiture used as the pretext for an audit |
Transfer, consent, and TSA behavior described reflects patterns commonly observed in software agreements, not a fixed vendor policy or legal advice. Enforceability and wording vary by contract and jurisdiction; your agreement and counsel govern.
One protection is worth more than the rest: a clean capacity split basis with no double counting. When a single mainframe estate becomes two, the easiest mistake, and the most expensive, is for both the retained and the divested business to end up licensed as if each were running the whole original footprint. Agreeing the measured method that divides the entitlement, before the vendor proposes one, is the difference between paying for one estate and paying for nearly two. The standalone entity also tends to be repriced as a small new buyer with no history; a pre agreed pricing floor stops that. None of this is available once the deal has closed and the leverage has passed. For the broader corporate event lens, see mainframe modernization and your license position.
A divestiture closing and the license split unresolved? We mobilize within 48 hours, before the close date becomes the vendor's lever. Start with mainframe license negotiation.
Every issue of the journal, plus renewal benchmarks we do not publish on the site. No vendor sharing, ever.