Divestiture software licensing for the parent.

Divestiture software licensing for the parent is the exposure the seller retains after selling a business unit, when the contracts, commitments and deployments that were sized for the whole company no longer match the smaller business that remains. Buyers focus on what they are taking on, but the parent has its own licensing problem, and a buyer who understands it negotiates better. Divestiture software licensing for the parent centres on stranded entitlement, residual deployment, pass through exposure under the transition services agreement and the audit risk that follows when entitlement counts no longer match a shrunken estate.

Why divestiture software licensing for the parent is overlooked

The seller side of a separation rarely gets the same attention as the buyer side, yet the parent carries real and quantifiable exposure. Enterprise agreements, volume commitments and capacity contracts were negotiated for the business as it was, including the demand of the unit being sold. Once that unit leaves, the parent keeps paying for entitlement it no longer needs, the mirror image of the stranded cost the new entity tries to avoid. The diagram illustrates the split: the parent holds full entitlement, its demand drops once the divested unit goes, and the gap between the two is stranded entitlement, a commitment that keeps being paid for but is no longer used. For a buyer, recognising this exposure on the other side of the table is a source of negotiating insight, because a parent motivated to shed stranded cost may be flexible on how shared contracts are divided.

The four exposures the parent retains

The parent faces four distinct exposures. Stranded entitlement is the first, where commitments sized for the pre sale business leave the parent over licensed; the response is to renegotiate or true down at the next renewal. Residual deployment is the second, where software belonging to the divested unit is still installed in the parent environment after close, which both wastes spend and, if unsupported, creates risk; the response is to reclaim and decommission once the TSA ends. Pass through exposure is the third, where the parent extends its own licenses to the new entity under the TSA and must hold valid entitlement for that extended use or face exposure itself; the response is to warrant valid entitlement and cap the pass through term. Audit risk on the retained estate is the fourth, where the parent entitlement counts no longer match the smaller business and a publisher review finds a mismatch; the response is to rebaseline entitlement against actual use. The table pairs each exposure with the parent response.

How shared contracts split between parent and unit

The hardest part of divestiture licensing is dividing shared contracts. A single enterprise agreement, volume license or platform subscription often covers both the retained business and the divested unit, and it cannot simply be cut in half. The publisher has to agree how the entitlement divides, which engages the same change of control and assignment clauses that gate the buyer side. As of June 2026, the major publishers, including Oracle, SAP, Microsoft, IBM and increasingly Broadcom for the former VMware estate, treat this division as an opportunity to review usage and terms across both resulting estates, so the split is a commercial negotiation, not an administrative one. This is the parent facing companion to the buyer work in separating shared software licenses, and both sides benefit from a single, evidence based reconciliation of who deploys and consumes what.

What this means for the buyer across the table

A buyer who understands the parent exposure negotiates with more leverage. Knowing the parent will be left with stranded entitlement on a shared contract creates room to argue for the unit to take a fairer share, or for the parent to absorb a transitional cost in exchange for a clean exit. Knowing the parent carries pass through exposure under the TSA strengthens the case for a warranty of valid licensing on every pass through line, which protects the buyer from inheriting the parent compliance gap. And recognising that both sides face audit risk after the split makes a joint, documented reconciliation the obvious path, because it protects both estates at once. This perspective is part of our carve out and TSA separation service and the wider carve out and TSA software playbook, and it connects to carve out software audit risk for both sides. As always, this is commercial and licensing advisory, and the interpretation of any contract clause belongs with each party own counsel.

How a parent reduces its own divestiture exposure

A parent that wants to minimise its retained exposure has a clear sequence to follow, and a buyer benefits from understanding it because the two sides can often align. The parent first quantifies the stranded entitlement by measuring its retained demand against its existing commitments, so it knows exactly how much it will be over licensed once the unit leaves. It then targets the next renewal of each affected contract as the moment to true down, since renewals are the natural point at which a publisher will accept a reduced commitment without penalty. In the interim it uses the transition services agreement to keep the divested unit on the parent licenses, which keeps utilisation high and softens the stranded position until the contracts can be resized.

The parent also has to attend to residual deployment, the divested unit software that lingers in the parent environment after close. Left in place, it consumes entitlement, may fall out of support and can show up in an audit as unexplained usage. A disciplined parent inventories what the unit leaves behind, reclaims the licenses it can redeploy and decommissions the rest once the TSA ends, turning a quiet liability into recovered value. This is the seller mirror of the day one and exit discipline the buyer runs, and it is why a joint plan serves both sides better than two disconnected ones.

For the buyer, the lesson is that the parent priorities are predictable, and predictable priorities are negotiable. A parent eager to true down at renewal may welcome a clean break that lets it resize sooner. A parent worried about residual deployment may accept a faster migration in exchange for certainty. Reading these motivations lets the buyer shape the separation timeline and the contract split in ways that serve its own interests while giving the parent what it needs, which is the essence of a well negotiated carve out.