matomo

TSA Checklist for the IT Carve-out | FHC+P
Practical checklist · IT carve-out

TSA Checklist

Cutting, pricing, and exiting Transitional Service Agreements properly

TSAs decide whether a carve-out runs smoothly or gets expensive: they define which IT services the seller continues to provide after closing. This checklist summarises what no TSA package should be missing from an IT perspective, drawn from FHC+P project practice, and not to be mistaken for legal advice.

1 · Service scope

What exactly is provided during transition?

2 · Commercials

Price, term, extension

3 · Security & data

Access, data protection, responsibilities

4 · Governance & exit

Steering and the planned end

TSA negotiations ahead?

We bring the IT perspective to the negotiating table and steer the scheduled exit afterwards. More on our IT carve-out page.

Questions & Answers

FAQ

Have further questions? Feel free to contact us directly via our contact form or by e-mail.

How long should a TSA run? +

As short as possible, as long as necessary: in practice 6 to 12 months per service is common, with a clearly defined extension option on a rising price ladder. Long comfort terms paralyse the build-up of your own IT and are usually priced expensively by the seller.

What is the most common TSA mistake? +

Blanket service descriptions like "IT operations as before". Without a service catalogue per system, measurable service levels, and defined exit criteria there is no yardstick in a dispute, and the exit drags on because nobody can say when a service may be ended.

Does this checklist replace legal advice? +

No. The checklist covers the IT and project perspective: service scope, service levels, security, governance, and exit. The contractual drafting belongs in the hands of your law firm, with whom we work closely on carve-out projects.