Carve out and TSA software FAQ.

This carve out and TSA software FAQ answers the questions buyers ask most often when separating a business unit, from what is actually licensed and what transfers, through which consents are triggered, to how to reach day one and exit the transition services agreement cleanly. A carve out and TSA software FAQ is useful because the same questions recur on every deal, and the answers connect a chain of decisions that runs from diligence to TSA exit. The lifecycle graphic and the table below show where each question sits and where the work that answers it lives.

The carve out and TSA software FAQ buyers need answered

The questions cluster by stage. In diligence, the buyer needs to know what is genuinely licensed and what entitlement will actually transfer, because a unit running software without complaint is not the same as a unit that is licensed for it. At signing, the question is which consents and contract clauses the deal structure triggers, since change of control and anti assignment clauses can require publisher agreement before a license moves. At close and through the TSA, the question is whether the new entity is ready to operate and what it is borrowing from the parent. At TSA exit, the question is whether everything has migrated and whether any double cost, where both parties pay for the same software, has been closed. Each is addressed in depth across the cluster, and this page links to the detailed treatment of each.

Diligence and transfer questions

Buyers ask first what they are really getting. The honest answer is that inherited software licensing is usually latent and unquantified in standard due diligence, and it lands as a publisher audit after close unless it is measured beforehand. The public record shows the scale: as of June 2026, SAP reportedly pursued Anheuser Busch InBev for some 600 million dollars and Diageo for some 60 million pounds over disputed and inherited licensing, figures widely reported rather than firm confirmed. The work that answers the diligence question is a dependency map and a license reconciliation, covered in mapping software dependencies before a carve out and separating shared software licenses.

Consent, readiness and exit questions

At signing the recurring question is which consents are needed, and the answer depends on deal structure: an asset purchase or carve out into a new entity almost always requires consent, while a stock purchase may not, though it can still trip a change of control clause. Avoiding the delay is covered in avoiding vendor consent delays in a carve out. At close the question is readiness, answered by a five domain day one gate in carve out day one software readiness. At exit the question is whether the migration is complete and double cost is closed, the focus of the TSA exit timeline and software critical path. All of this sits within our carve out and TSA separation service and the broader carve out and TSA software playbook. This page is commercial and licensing advisory, not legal advice; interpretation of any clause belongs with the buyer own counsel.

How the questions connect into one chain

The value of seeing these questions together is that the answers form a single chain, where each decision constrains the next. The diligence reconciliation defines what is licensed and what transfers, which sets the consent list at signing, because only the contracts that move need consent. The consents that land define what the new entity owns on day one, which sets the day one readiness gate, because anything without transferred entitlement has to be covered under the TSA. The TSA scope then defines the exit plan, because every borrowed service is a migration task with a deadline. A buyer that treats these as four separate workstreams loses the thread between them, and the gaps between workstreams are where exposure hides.

This is why the carve out questions are best answered by one team holding the whole chain rather than by specialists who each see a single link. The person who measured the licensing position in diligence knows which consents matter and why, the person who ran the consents knows what the new entity owns on day one, and the person who set the day one gate knows what the TSA has to carry to exit. Continuity of knowledge across the stages is itself a control, because it prevents the handoff losses that turn a mapped risk into an unmanaged one.

For buyers planning a programme of carve outs, the same chain becomes a repeatable playbook. The questions do not change from deal to deal, only the answers do, so a team that has run the chain once can run it faster and more reliably the next time, with templates for the dependency map, the consent register, the readiness gate and the exit plan. Building that institutional capability is often as valuable as the outcome on any single deal, because it compounds across every separation the buyer undertakes.