Transition Services Agreement Cost: The TSA Cost Trap

A transition services agreement is modeled as a known operating expense. It behaves as a variable cost of delay. Seven layers of cost sit behind the fee schedule, and most deal models capture two of them.

Most deal models treat a transition services agreement as a short-term, known operating expense. In practice a TSA is a variable cost of delay, dependency and incomplete separation. Its true cost includes not only service fees, but extension premiums, stranded costs, duplicated technology, internal program spend, lost synergies, management distraction, restricted operating flexibility, and the economic value of decisions deferred.

A TSA is not a contract for back-office services. It is the commercial expression of an unfinished separation.

Why the deal model gets it wrong

• Deal teams model contractual fees, but frequently omit the cost of standing up the replacement capability.
• The base case assumes timelines will hold — despite incomplete system inventories, unresolved data dependencies, vendor-consent requirements and scarce functional resources.
• TSA costs are often allocated to a transaction or transformation budget, rather than linked to operating performance and synergy realization. That accounting choice hides the problem until it is expensive.

The seven layers of TSA cost

• 01

  Contracted service fees

  Periodic charges for finance, IT, payroll, HR, customer support, ERP access and procurement.

• 02

  Markup and overhead allocation

  Cost-plus structures commonly carry the seller’s fully loaded cost plus a margin.

• 03

  Extension premiums

  Fees typically escalate — often sharply — once services run beyond the original term.

• 04

  Replacement-build cost

  New systems, implementation partners, migration support, controls, testing, data cleansing and hypercare.

• 05

  Duplicate-run cost

  Paying for the TSA service and the new target-state capability simultaneously, for as long as cutover is delayed.

• 06

  Stranded-cost exposure

  Seller-side cost that remains after a business exits shared services — a recurring source of tension over scope, pricing and exit timing.

• 07

  Value-delay cost

  Deferred synergies, postponed commercial changes, process standardization that cannot start, and management time diverted from growth.

Total economic exposure

Not every transaction carries all seven. The point is narrower than that: a deal model containing only the first two is describing the invoice, not the economics.

The hidden economics of extension

A ninety-day extension looks like a procurement decision. It is usually a value decision, because it postpones a much larger agenda — ERP consolidation, procurement leverage, pricing harmonization, shared-services redesign, the exit of expensive duplicate systems. A cheap extension can be economically irrational.

The reverse is equally true. An accelerated exit destroys value if it moves a business-critical process before data, controls, training and fallback plans are ready. The question is never simply whether to extend. It is which services to exit, in what order, against which dependencies.

A better model: TSA total cost of ownership

• Build the model by service tower, not as a single aggregate line.
• Track baseline run-rate, contracted fee, exit cost, target-state run-rate, critical dependencies, and the value unlocked by exit.
• Include an extension-scenario waterfall: base case, three-month slip, six-month slip, hard-failure case.
• Assign an accountable executive to each service and each exit milestone. A TSA with no named owner per tower will slip by default.

How to exit in value sequence

Exit services according to their relationship to the investment thesis — not according to which systems are easiest to migrate. Those two orderings are rarely the same, and following the second is how a separation ends up having done the simple work first and run out of time for the work that mattered.

• Early: bounded, low-dependency services — identity, email, devices, expense management, selected HR or payroll functions.
• Late and deliberate: revenue-critical and highly interconnected processes — order-to-cash, ERP, warehouse systems, complex data domains — with rehearsals and rollback plans.
• Throughout: treat each exit as an enterprise milestone inside the separation roadmap, not as an IT task.

The board-level dashboard

Six lines, reported monthly. Anything more is management reporting; anything less is not governance.

• Original versus current exit date, by service.
• Fees paid to date versus plan.
• Extension exposure by service.
• Replacement-capability readiness.
• Synergies unlocked, delayed, or at risk.
• Risks requiring a decision within thirty days.

An illustrative case

On market terms

Published guidance on transition services is consistent about the failure modes: poor scope definition, vague service descriptions, unrealistic timelines and weak governance produce disputes, overruns and integration delay. The recommended counters are explicit service-level pricing, stated markup and overhead allocation, adjustment mechanisms for partial exits and extensions, and integration of TSA milestones into the wider separation plan.

On pricing, cost-plus structures commonly include the seller’s fully loaded cost plus a markup in the region of five to ten percent, and extension terms are often pre-priced at a premium — figures such as 125 percent of base rate in months thirteen to eighteen, and 150 percent thereafter, appear in practice. Actual terms vary materially by transaction, and these should be treated as orientation rather than benchmark.

What Is This Transition Actually Costing?

The assessment asks what has already been attempted, what is still running on a workaround, and which dependency decides the order of everything else.