Divestiture license separation: the carve-out playbook.
When a business unit is sold, its software does not travel with it. Enterprise licenses sit with the parent entity, so the carved-out unit must re-establish its own position while the seller unwinds its own counts — all inside a transition window a vendor is happy to run out. This note maps how to separate a shared estate without paying for the same usage twice.
A divestiture is a negotiation event for the software estate, not paperwork. Re-licensing a carved-out unit as a standalone entity can cost 20–40% of its annual IT budget if separation is left to the deadline. The disciplines that contain it — entitlement mapping, an early assignability read, and standalone deals negotiated inside the TSA — also protect the seller from paying for usage it no longer runs.
01 Key findings
Enterprise licenses are held by the parent, not the unit. Most agreements license software to a single legal entity and its affiliates. Once sold, the divested unit is no longer an affiliate, so its right to use the seller's licenses ends at separation unless the contract provides otherwise.
The TSA is a runway, not the answer. A transition service agreement of 12–24 months keeps the unit running on the seller's systems, but most vendor contracts do not permit a seller to license a third party. Standalone licensing must be solved inside that window.
Assignability decides the price. A unit whose key contracts permit transfer to a successor can often carry its existing rate; one whose contracts prohibit assignment is forced into a fresh standalone deal at a worse volume tier, list-anchored.
Double payment is the default failure mode. During the TSA the seller still holds counts sized for the combined business while the unit begins buying its own. The same usage is licensed twice until someone reduces the seller's counts — and the vendor has no incentive to point it out.
Both sides hold leverage they underuse. Switching costs are lowest during a carve-out because the unit is rebuilding anyway; the seller's shrinking estate is a renewal event. Treated as clerical, both are surrendered.
02 Why shared licenses don't travel
Most enterprise agreements license software to a single legal entity and its affiliates. A divested business unit, once sold, is no longer an affiliate of the seller, so its right to use the seller's licenses ends at separation unless the contract or the deal specifically provides otherwise. The carved-out unit therefore needs a fresh license position, and the vendor is under no obligation to extend its existing discount to the new standalone entity.
The smaller the divested unit, the worse its standalone volume tier, and the larger the re-pricing gap versus the rate it enjoyed under the parent. Whether assignment is even possible is governed by the same terms covered in our change of control clauses guide, and by how the parent agreement defines an affiliate — the subject of our affiliate definition clauses note. Those two reads, done early, determine whether the unit transfers at rate or re-buys at list.
03 The transition service agreement
The TSA is the bridge that keeps the divested unit running on the seller's systems while it stands up its own. For software, it must address whether the seller can lawfully continue to provide access under its existing licenses — and most vendor contracts do not permit a seller to license a third party. That is why the window matters: it is the runway to negotiate standalone licenses, not a permanent solution.
| TSA phase | Duration | Software task |
|---|---|---|
| Stand-up | Months 0–6 | Inventory shared use; open vendor conversations |
| Negotiation | Months 6–15 | Secure standalone licenses; transfer where assignable |
| Migration | Months 12–24 | Cut the unit over to its own contracts and systems |
| Exit | By TSA end | Confirm seller usage reduced; close shared access |
A common error is treating the TSA as the answer rather than the runway. It buys time, but the licensing has to be solved within it, because most vendors will not allow the seller to keep serving a former affiliate indefinitely. Building the vendor-negotiation track into the first six months is what prevents a scramble at the deadline.
04 Separation-task matrix
Separation cannot be negotiated without a clear picture of what the divested unit uses versus what the parent owns — an entitlement reconciliation scoped to the carved-out unit. That baseline tells the seller how much it can release and the buyer how much it must acquire, and it anchors both vendor conversations in usage data the vendor cannot inflate. Each entitlement then follows one of four separation paths.
| Separation path | When it applies | Cost effect |
|---|---|---|
| License transfer | Contract allows assignment to the buyer | Lowest: existing rate may carry |
| New standalone contract | No assignment right; unit re-licenses | Highest: standalone tier, list-anchored |
| Buyer absorbs into own agreement | Acquirer already licenses the product | Low: fold into acquirer volume tier |
| Seller retains, unit migrates off | Unit moves to a different product | Migration cost, no re-license |
During the TSA the same usage is licensed twice. The seller still holds counts sized for the combined business, including the divested unit's usage, while the unit begins buying its own licenses. For a window, both parties pay for the same seats. The seller must reduce its counts as the unit transitions off, and the divestiture agreement should specify who bears the overlap cost. Left unaddressed, both sides pay until someone notices — and the vendor has no reason to say anything.
05 Cloud & SaaS carve-outs
Cloud and SaaS agreements separate differently from perpetual on-premise licenses, and in a carve-out they are often the harder problem. A perpetual license can sometimes be transferred or split; a subscription is tied to the contracting entity and its committed term, and the divested unit usually needs its own from day one. Shared tenancy adds a further complication, because the unit's data and workloads must be separated from the seller's within the same provider, often on a tight timeline.
| Asset type | Separation difficulty | Key issue |
|---|---|---|
| Perpetual on-premise license | Moderate | Assignability and counts |
| SaaS subscription | High | New contract, committed term, data export |
| Cloud platform commitment | High | Tenancy split, committed spend allocation |
| Shared data platform | Highest | Data separation under TSA deadline |
The committed-spend question surprises sellers most. A multi-year cloud commitment signed for the combined business may carry a minimum the seller cannot meet once the divested unit's consumption leaves, exposing it to a shortfall charge. The divestiture agreement should allocate that commitment between the parties, so neither is left holding a minimum it can no longer reach.
06 Leverage during separation
The divested unit has more bargaining power than it usually realizes. A vendor wants to retain it as a customer rather than watch it migrate to a competitor during a moment of natural disruption, and the carve-out is exactly when switching costs are lowest — the unit is already rebuilding its systems. A standalone entity that credibly evaluates an alternative platform during separation can often hold close to the parent's rate rather than reset to standalone list. This is the same vendor negotiating power dynamic that drives any renewal, sharpened by the fact that the unit is migrating anyway.
The seller has leverage too: removing the divested usage reduces its counts, which is a renewal-timing opportunity to renegotiate its now-smaller estate rather than simply shrink it at the old rate. A seller that lets the divested usage linger on its contracts is funding the buyer's separation out of its own budget. Both sides should treat separation as a negotiation event, not a clerical one.
07 Separation framework
Four checks govern whether a carve-out separates cleanly or turns into a re-purchase. Run them in the first months of the transition window, while bargaining power is still live.
Entitlement baseline
Reconcile the divested unit's actual deployments and users against the parent's entitlements, isolating what must move or be re-purchased. No negotiation is anchored until this exists.
Assignability read
Check every material contract for whether it permits transfer to the buyer or forces a fresh standalone deal. Done early, it decides the price; done at the deadline, it is a surprise.
Seller count reduction
Adjust the seller's contracts to remove the divested usage in step with migration, ending the double payment rather than paying for seats that have left.
Committed-spend allocation
Divide any shared multi-year cloud commitment between the parties, so neither is left short of a minimum it can no longer reach once consumption departs.
08 Our recommendation
Map your usage, read assignability early, and negotiate the standalone position during the transition window, not at its deadline. Use the migration moment as leverage to hold close to the parent's rate.
Treat divested usage as a planned reduction tied to the timeline, cutting each vendor's counts as the unit migrates off. Use the shrinking estate as a renewal event rather than funding the buyer's separation.
Put the overlap cost and any shared committed spend in the divestiture agreement itself. What the contract leaves silent, both parties pay for — and the vendor collects on both.
09 Negotiation sequencing
The single highest-value process choice in a carve-out is when the vendor conversations begin:
Early & concurrent Recommended
Open vendor conversations in the first six months, running the assignability read and entitlement baseline in parallel. The unit negotiates with time in hand and a credible migration alternative, and the seller reduces counts on schedule.
Deadline-driven Weaker
Wait until the final months of the TSA. Standalone contracts are negotiated against a hard deadline the vendor can exploit, assignability surprises surface too late to fix, and the double payment runs unbroken until exit.
Separate the estate without re-buying it
We map shared entitlements to the carved-out unit's real usage and run the vendor negotiations for either side of the deal.
The Licensing Edge
Weekly vendor and licensing intelligence for enterprise IT leaders. 3,000+ subscribers.