Divestiture License Separation: Buyer's Guide
How to split a shared software estate when a business unit is sold, size the transition service period, and contain the re-licensing cost.
A divestiture forces the separation of a shared software estate under a transition service agreement that typically runs 12 to 24 months, and re-licensing the carved-out business as a standalone entity can cost 20 to 40 percent of its annual IT budget if the separation is not negotiated deliberately. The problem is structural: enterprise licenses are usually held by the parent legal entity and shared across business units, so when one unit is sold, its software does not travel with it automatically. The buyer of the divested unit must obtain its own licenses, the seller must remove the divested usage from its own counts, and both sides face a vendor that sees a re-purchase opportunity. Handled well, separation is an administrative exercise. Handled late, it is a double payment.
This guide explains how to map the shared estate, size the transition service agreement, and contain the re-licensing cost. It builds on our software contract negotiation guide and our licensing advisory practice.
Why shared licenses do not 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.
The transition service agreement
The transition service agreement is the bridge that keeps the divested unit running on the seller's systems while it stands up its own. For software, the TSA 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. This is why the TSA window matters: it is the runway to negotiate standalone licenses for the divested unit, not a permanent solution.
| TSA phase | Duration | Software task |
|---|---|---|
| Stand-up | Months 0 to 6 | Inventory shared use; open vendor conversations |
| Negotiation | Months 6 to 15 | Secure standalone licenses; transfer where assignable |
| Migration | Months 12 to 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. The TSA buys time, but software licensing for the divested unit 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 of the TSA is what prevents a scramble at the deadline.
The double-payment trap: During the TSA the seller still holds licenses sized for the combined business, including the divested unit's usage, while the divested unit begins buying its own licenses. For a window, the same usage is licensed twice across the two parties. The seller should reduce its counts as the divested unit transitions off, and the divestiture agreement should specify who bears the overlap cost. Left unaddressed, both sides pay for the same seats until someone notices, and the vendor has no incentive to point it out.
Mapping shared entitlements to usage
The separation cannot be negotiated without a clear picture of what the divested unit actually uses versus what the parent owns. That is an entitlement reconciliation exercise scoped to the carved-out unit: count the divested unit's real deployments and users, match them against the parent's entitlements, and isolate the portion that must move or be re-purchased. The output 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.
| 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 its 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 |
Whether assignment is even possible is governed by the same terms covered in our change of control clauses guide. A divested unit whose key contracts permit assignment to a successor can often carry its existing rate; one whose contracts prohibit assignment is forced into a fresh standalone deal at a worse tier. This is why the assignment read happens early, not at the TSA deadline.
Negotiating leverage in a separation
The divested unit has more leverage than it usually realizes. A vendor wants to retain the unit as a customer rather than see it migrate to a competitor during a moment of natural disruption, and the carve-out is exactly the moment when switching costs are lowest because 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 leverage 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 own now-smaller estate rather than simply shrink it at the old rate. Both sides of a divestiture should treat the separation as a negotiation event, not a clerical one. Our advisory team works either side of a carve-out, mapping the estate and running the vendor negotiations so the separation does not become a re-purchase.
The seller's side of the separation
The seller in a divestiture has its own work and its own opportunity, because removing the divested unit's usage shrinks the seller's license requirement by the same amount it grows the buyer's. The risk for the seller is paying for licenses it no longer needs: if the seller's contract counts are not reduced as the divested unit transitions off, the seller continues to carry and pay for the divested usage long after the unit has left. The opportunity is that a shrinking estate is a renewal event, a moment to renegotiate the seller's now-smaller position rather than simply let it run at the old rate.
The seller should therefore treat the divested usage as a planned reduction tied to the transition timeline, with each vendor's counts adjusted as the unit migrates off, and should use the reduction as leverage at the next renewal. A seller that lets the divested usage linger on its contracts is funding the buyer's separation out of its own budget. The reconciliation that supports this is the same entitlement reconciliation the buyer needs, run from the seller's perspective.
Cloud and SaaS in a carve-out
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 subscription from day one. Shared cloud tenancy adds a further complication, because the divested unit's data and workloads must be separated from the seller's within the same provider, often under a tight transition 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 is the one that 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 the seller 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.
The separation checklist
A clean carve-out separation runs through five confirmations before the TSA ends.
- Entitlements mapped. The divested unit's actual usage is reconciled against the parent's entitlements, isolating what must move or be re-purchased.
- Assignability read. Every material contract is checked for whether it permits transfer to the buyer or forces a fresh standalone deal.
- Standalone licenses secured. The divested unit holds its own contracts for everything it will keep, negotiated during the TSA rather than at its deadline.
- Seller counts reduced. The seller's contracts are adjusted to remove the divested usage, ending the double payment.
- Cloud commitments allocated. Any shared committed spend is divided so neither party is left short of a minimum.
A separation that clears all five ends with both parties on right-sized contracts and no lingering double payment. One that skips them leaves usage licensed twice, commitments stranded, and a vendor collecting on both. The work is detailed but finite, and it pays for itself many times over against the re-purchase cost of getting it wrong. Our advisory team runs the separation for either side of a divestiture.
The four mistakes that turn separation into a re-purchase
Four recurring mistakes convert a routine separation into an expensive double payment, and each traces to treating the carve-out as a clerical task rather than a negotiation. The first is starting late: a team that waits until the final months of the transition service agreement to address licensing negotiates the divested unit's standalone contracts against a hard deadline the vendor can exploit. The second is failing to read assignability early, so the team discovers only at the deadline that key contracts cannot transfer and must be re-bought at standalone rates.
The third mistake is leaving the seller's counts unadjusted, so the same usage is licensed twice across both parties for months while no one bears responsibility for ending the overlap. The fourth is ignoring committed cloud spend, so a shared multi-year commitment leaves the seller short of a minimum it can no longer reach once the divested consumption departs. Each mistake is avoidable with the early entitlement mapping and assignability read described above, and each is expensive precisely because it surfaces after the deal has closed and the leverage has passed. A separation run as a planned negotiation, with the vendor conversations opened in the first months of the transition window, avoids all four, which is the discipline our advisory team brings to a carve-out.
The bottom line for both sides
A divestiture is a negotiation event for the software estate, not a clerical one, and both the buyer and the seller leave money on the table when they treat it as paperwork. The carved-out unit that maps its usage, reads its assignability early, and negotiates its standalone position during the transition window rather than at its deadline avoids the re-purchase that catches unprepared teams. The seller that reduces its counts in step with the unit's departure and allocates shared cloud commitments avoids funding the separation out of its own budget. Run deliberately on both sides, the separation ends with two right-sized estates and no double payment, which is the outcome our advisory team is engaged to produce.