Carve Out Software Licensing and TSA Software Separation

Carve out software licensing is where most separations lose time and money. The business being carved out runs on contracts the parent signed, on group wide and enterprise agreements, and on shared platforms that were never designed to split. A transition services agreement keeps it running on the parent's estate for a defined window, but that window is a meter. This guide explains how to map the shared estate, separate the licenses, plan the transition services exit, and stand up the new entity, with links to every detailed page in the cluster.

The stakes fall on both sides. The parent risks stranded cost, paying for capacity the departing business used. The buyer risks either over buying to feel safe or running out of compliance during transition. Both outcomes are avoidable with a sequenced plan built before signing. The page on what a carve out is and why software is the hard part sets the scene, and what a transition services agreement is and how software fits in explains the mechanism.

Why carve out software licensing is so difficult

A carve out has to unwind entitlements that were bought as one. Group wide and enterprise agreements rarely transfer to a new owner without consent. Anti assignment and change of control clauses can block the move entirely or trigger repricing at standalone rates. Shared systems carry data and integrations for both the parent and the departing business. None of this resolves itself, and the transition services clock is running the whole time. Mapping the dependencies first is the only way to avoid surprises, covered in mapping software dependencies before a carve out.

Stranded cost and double licensing

Two mirror problems come from the same cause. Stranded cost hits the parent when shared agreements are not resized to retained consumption after the unit leaves. Double licensing hits the buyer when a new license is stood up while the transition services agreement still bills for the same system. Both are cured by a single shared view of the estate and a sequenced cutover, not by speed. The pages on stranded software costs in a carve out and carve out and the risk of double licensing cover each side.

Deal structure shapes all of it. Change of control and anti assignment clauses bite differently depending on whether the carve out is structured as an asset sale, a share sale of a carved entity, or a hive down followed by a sale. As of 2024, public reporting on disputes such as SAP against AB InBev and Diageo shows how inherited and disputed licensing can reach hundreds of millions, which is why the separation is planned and priced rather than assumed.

Planning the transition services exit

The transition services agreement is a bridge, not a home. Every month the carved out business runs on the parent's contracts is a month of cost and a month of dependence, and a parent holds leverage over any extension. The exit is therefore sequenced by lead time and criticality. Systems with the longest vendor consent or provisioning times go first, alongside the most critical platforms such as identity and productivity. The page on the transition services exit timeline and the software critical path sets out the method, and exiting the transition services agreement cleanly on software covers the finish.

Standing up the new entity estate

For the buyer, the goal is an estate that is independent and compliant from completion, sized to the unit's real consumption rather than to a copy of the parent configuration. Over buying wastes capital. Under buying creates a compliance gap during the most scrutinised period of the deal. New agreements are negotiated on the new entity's own terms and stood up in priority order. The pages on standing up the new entity software estate, re licensing the carved out business from scratch and negotiating software terms for the new entity work through the build.

Negotiating the new entity's terms from strength

The standalone agreements a carved out business signs will set its software cost for years, so they are worth negotiating properly rather than accepting under deadline pressure. The new entity rarely has the volume the parent had, which means it cannot expect the same unit pricing, but it does have choices the parent did not. It can select editions that match real need rather than inherited habit, it can avoid the over deployment that crept into the parent estate over years, and it can structure terms around its own growth plan. The point is to buy what the business actually consumes, on terms that flex with it, not to replicate the parent contract line for line. The page on negotiating software terms for the new entity covers the levers, and re licensing the carved out business from scratch describes the clean sheet approach.

Timing the negotiation against the transition services exit is what gives the new entity leverage. Agreements signed too early lock in terms before consumption is understood. Agreements signed too late force a rushed deal under the pressure of an expiring transition window. The right window is once the real usage is measured and before the transition meter forces a decision, which is exactly what a sequenced exit plan creates. The page on exiting the transition services agreement cleanly on software connects the negotiation to the timeline.

Why independence matters in a carve out

A carve out puts the buyer, the parent and the publishers around the same table, and each publisher has every reason to use the separation to reprice. Independent buyer side advisory matters here more than anywhere, because the adviser's only interest is the acquirer's compliant, correctly sized estate, not a larger contract for a vendor or a reseller. The firm behind this guide is paid only by the acquirer and holds no affiliation with any software publisher or reseller, which is what allows it to push back on a consent driven repricing or a standalone rate that does not reflect real consumption. A clean separation, planned early and defended through consent and audit, is the outcome every page in this guide is built to deliver.

Separating shared software licenses

Shared licenses are the heart of the carve out problem. A single enterprise agreement may cover the parent and the departing business together, with one entitlement, one set of discounts and one renewal. Separation means deciding, system by system, whether to split the existing agreement, assign part of it with the publisher's consent, or re procure entirely for the new entity. Each path has cost and risk, and the right choice depends on the publisher, the metric and the consent terms. The page on separating shared software licenses in a carve out works through the options, and avoiding vendor consent delays covers the approvals that sit on the critical path.

Consent is often the longest pole. A publisher asked to assign or split an agreement has every incentive to take its time and to reprice, and a carve out on a fixed transition timeline cannot afford either. Engaging the publishers early, with a clear and defensible position, is the only reliable way to keep consent off the critical path.

Cloud and SaaS separation in a carve out

Cloud separation carries its own difficulties. Tenancies, identity directories and SaaS subscriptions are frequently shared at the group level, and splitting them means standing up new tenancies, migrating data and re establishing entitlements without breaking access. Subscriptions that auto renew at the group level can lock the new entity into terms it never chose. The page on cloud and SaaS separation in a carve out sets out the sequence, and carve out day one software readiness defines what has to be working from the first day of independent operation.

Day one readiness and the critical path

Day one is the test of the whole plan. The carved out business has to be able to operate from the moment it is independent, which means identity, productivity, finance and the core line of business systems all have to be ready, licensed and compliant. Readiness is engineered backward from day one, with the longest lead items started first. The page on carve out day one software readiness defines the minimum, and mapping software dependencies before a carve out identifies what the day one systems quietly depend on.

Audit risk on both sides of a carve out

A carve out raises audit risk for both the parent and the buyer at once. The parent has changed its deployment and its entitlement and may now be over or under licensed on the remainder. The buyer has stood up a new estate at speed, with the compliance gaps that speed creates. A publisher sees a carve out as two customers to examine rather than one. The page on carve out software audit risk for both sides covers the exposure, and the buyer side and seller side playbooks in carve out software licensing for the buyer and for the seller set out each party's priorities.

The transition services software catalogue and pricing

The transition services agreement should list software services explicitly, with a price and an end date for each, not bundle them into a vague monthly fee. A clear catalogue lets the new entity retire services one by one as it stands up replacements, and it stops the parent from charging for capacity the business no longer uses. The page on the transition services software service catalogue and pricing sets out how to structure it, and negotiating software terms for the new entity covers the agreements that replace it.

The full carve out playbook and the parent view

Bringing it together, the complete sequence runs from dependency mapping through separation, transition services exit and new entity stand up, with consent management and audit defence running throughout. The page on the complete carve out software licensing playbook assembles the steps, and the parent perspective is set out in divestiture software licensing for the parent. The general questions buyers and sellers ask are answered in the carve out and TSA software FAQ.

One final principle holds the whole carve out together. Speed without sequencing creates cost, and sequencing without early mapping is impossible. The teams that separate cleanly are the ones that mapped the shared estate before signing, priced the standalone position honestly, and ran the transition services exit as a managed project with a named owner rather than a deadline everyone hoped to meet. The detailed pages in this guide each address one part of that discipline, and together they describe how a buyer takes a business that was deeply entangled in its parent and stands it up as an independent, compliant and correctly sized software estate, with the parent left whole and the new owner protected from the inherited exposure that a rushed separation so often leaves behind.

Everything in this carve out and TSA guide