TSA Exit Acceleration
Leave clean, and licensed.
Senior operators on day one. Fixed-fee engagements. The first conversation is always free.
A TSA license true-up reconciles the software the seller has been licensing on your behalf against what you will own after exit, so you neither lose access nor pay for the same product twice. It is a finance and compliance issue hiding inside an IT migration, and it routinely costs buyers real money. Handle it as a defined line in the TSA exit strategy.
While the TSA runs, a lot of the software the carved-out business uses is licensed by the seller, not by you. The seller holds the agreements with the software vendors, pays the fees, and passes some cost to you through the service charges. It is convenient and it is invisible, and at exit it becomes a problem because those licenses do not come with you automatically.
The trap has two jaws. On one side, lose access: a license that was the seller's, switched off at exit, leaves you without software the business runs on. On the other side, pay twice: rushing to buy your own licenses while still paying the seller for the same products through the TSA, so the same software is funded twice for the length of the overlap.
Both outcomes are common because licensing sits between IT and finance and tends to fall down the gap. The technical team migrates the application and assumes the license follows. The finance team sees a service charge and assumes IT has it covered. Neither owns the entitlement, and the result surfaces as a vendor audit, a sudden loss of access, or a bill for software you thought you already had.
Like every other exit workstream, this one starts with an inventory: every piece of software the carved-out business depends on, and for each, who actually holds the license. Some you already own. Some the seller owns and passes through. Some sit in enterprise agreements the seller signed where your usage is bundled invisibly into a larger deal.
The bundled ones are the hard cases. When the seller licenses a product across its whole enterprise and your unit is a slice of that, there may be no clean line showing what is yours. Pulling your true usage out of the seller's agreement, and understanding what you will need to license independently, takes real work with both the IT estate and the contracts behind it.
Capture the commercial terms, not just the product names. For each license you need to know the vendor, the metric it is counted by, the quantity your business consumes, and whether the seller's agreement even permits use by a divested entity. That last point matters: some licenses do not allow a carved-out unit to keep using them at all, which turns a transfer question into a fresh procurement on a deadline.
For each licensed product, there are broadly two paths at exit: transfer the seller's entitlement to you, or procure your own. Which is available depends on the vendor's terms and the vendor's willingness, and neither is automatic. The choice has both cost and timeline consequences, so it needs deciding early rather than discovering itself at the cut.
Transfer is often cleaner where the vendor allows it, because it preserves continuity and may carry favorable pricing already negotiated. But vendors know a carve-out is a moment of weakness and may treat a transfer as a chance to reset terms, audit usage again, or require a new agreement at list price. A transfer that looks simple can become a negotiation, and the buyer needs to be ready for that.
Fresh procurement gives you a clean agreement in your own name but takes time and may cost more than the bundled rate the seller enjoyed. For critical software it must be started early enough that the new license is live before the seller's coverage ends. Treating procurement lead times as part of the exit plan, not an afterthought, is what keeps a license gap from forcing an extension or an outage.
The double pay window opens when your own license goes live while you are still paying the seller for the same product through the TSA. It is easy to fall into, because the safe instinct is to secure your license early, and the TSA charge for that software keeps running until the service is formally cut. For the overlap, the business funds the same product twice.
Close the window by coordinating the license start with the TSA service cut. Your new or transferred entitlement should go live as the corresponding TSA charge ends, not weeks before. That requires the IT migration, the license procurement, and the TSA exit to be sequenced together, with someone tracking the date each software charge stops against the date each new license starts.
Where a short overlap is unavoidable, make it deliberate and brief. A few weeks of double cost to guarantee continuity on critical software can be the right call, but it should be a conscious decision with a known price, not an accident that runs for months because no one was watching the seam. The cost of an uncontrolled overlap across a full license estate adds up quickly.
The true up is the reconciliation that closes the workstream: a final comparison of what the seller was licensing on your behalf, what you have now procured or transferred, and what you are actually using, so nothing is missing, nothing is duplicated, and nothing is left non compliant. It is the moment the messy middle resolves into a clean licensing position you own.
Do it against real usage, not assumptions. Carve-outs are a frequent trigger for vendor audits, because vendors know entitlements get scrambled when a business changes hands. A true up that confirms your actual consumption is covered by licenses in your own name is the best defense against an audit that arrives six months after exit asking awkward questions about the transition period.
Finish with documentation you can stand behind. A clear record of every license, its source, its transfer or procurement, and its alignment to usage is what lets you treat software licensing as settled rather than a lurking liability. A buyer that inventories early, decides transfer or buy deliberately, controls the overlap, and trues up against usage exits clean. Building that reconciliation into the plan is part of our TSA Exit Acceleration work.
It is the reconciliation at exit between the software the seller has been licensing on your behalf, what you have now transferred or procured in your own name, and what you are actually using. The aim is a clean licensing position where nothing is missing, nothing is paid for twice, and your usage is fully covered by entitlements you own.
By securing their own licenses early while still paying the seller for the same products through the TSA service charges. The new entitlement goes live before the TSA charge for that software is cut, so the business funds the same product twice for the length of the overlap. Coordinating each license start with the matching service cut closes that window.
Not automatically. Some vendor agreements do not permit a divested entity to keep using software licensed under the seller's contract at all, which forces fresh procurement on a deadline. Others allow a transfer, but the vendor may use the carve-out to reset terms or audit usage again. You have to check each agreement and decide transfer or buy early, not at the cut.
Because vendors know entitlements get scrambled when a business changes hands, so the transition period is a likely time to find usage that exceeds licenses. A true up that confirms your actual consumption is covered by licenses in your own name, with documentation of every transfer and procurement, is the strongest defense against an audit that arrives months after exit.
Removing every seller identity and access path at exit.
Read the article →Transferring security controls cleanly as the TSA ends.
Read the article →Scripting the repetitive mechanics of a TSA exit.
Read the article →The 90-day governance, IT, finance, HR and procurement separation plan we run on live carve-outs. Get the playbook plus the bi-weekly Day One Letter — short, signal-heavy, buyer-side.
No spam. Unsubscribe in one click. · Read the overview first →
Senior operators on day one. Fixed-fee engagements. The first conversation is always free.
Seven buyer-side moves to exit a Transition Services Agreement on time and below budget. The mark-up, the extension-fee curve, exit sequencing, and the 11-month calendar.
A representative benchmark report on where TSA cost-plus mark-up belongs by service category, how to validate pass-throughs, and where the extension-fee curve becomes a penalty. On a representative $48M-revenue carve-out, reading the price stack the way the seller built it recovers $0.7M the headline discount never touches.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →