Carve out day one software readiness.

Carve out day one software readiness is the state in which the new entity can operate from the first business day after close, with every user able to log in, every critical application reachable, every license valid and every essential data flow running, whether on standalone systems or on parent services under the transition services agreement. Carve out day one software readiness is not the same as full separation. It is the minimum operating threshold that lets the business run while the longer migration continues, and reaching it is the first hard test of whether the separation plan was built on a real dependency map.

What carve out day one software readiness actually requires

Readiness on day one is measured across five domains, and the business cannot open until all five are green. Identity and access comes first, because if users cannot authenticate, nothing else matters; every standalone user needs to log in to the systems they need from the first morning. Licensing comes second, because every application in use has to be covered by valid entitlement in the new entity name or explicitly under the TSA, or the new entity is out of compliance from day one. Critical applications come third, the finance, ERP and customer systems that the business cannot transact without. Data and integrations come fourth, because the key interfaces have to flow to the right destinations or order to cash and reporting break. Support and run comes fifth, because a live help desk and a named run team are what keep the first weeks from descending into chaos. The dashboard and the checklist table set the day one minimum and the owner for each domain.

The difference between day one and full separation

A common and costly error is to treat day one and full separation as the same milestone. They are not. Day one readiness is about continuity, getting the business operating without interruption, and it leans heavily on the TSA to provide whatever could not be stood up in time. Full separation is about independence, exiting the TSA entirely and running on the new entity own estate. Confusing the two leads buyers either to over scope day one, trying to complete the entire migration before close and missing the date, or to under scope it, declaring readiness when critical flows still depend on undocumented parent services that fail in the first week. The discipline is to define the day one minimum precisely, secure it with the TSA where needed, and treat everything beyond it as planned migration. This is the bridge between mapping software dependencies before a carve out and exiting the TSA cleanly on software.

How licensing fits day one readiness

Licensing is the domain buyers most often misjudge on day one, because an application that runs is assumed to be licensed, and in a carve out that assumption frequently fails. On day one every application in use must be covered either by entitlement that has transferred into the new entity name, or by an explicit license pass through under the TSA where the parent maintains valid entitlement for the extended use. Anything else is unlicensed use from the first business day, which is precisely the exposure that surfaces later as an audit. As of June 2026, the publishers most likely to act on it remain Oracle, SAP, Microsoft, IBM and increasingly Broadcom for the former VMware estate, and the public record, including SAP reportedly pursuing AB InBev for some 600 million dollars and Diageo for some 60 million pounds, shows the scale licensing exposure can reach. Day one readiness therefore includes a licensing checkpoint that confirms valid coverage for every application before cutover, linking to carve out software audit risk for both sides.

Running the day one readiness review

The readiness review is a go or no go gate held in the weeks before close. Each domain owner reports against the day one minimum, evidence is checked rather than asserted, and any amber item gets a clear plan to green or an explicit decision to cover it under the TSA. A short anonymised composite illustrates the value. A buyer standing up a carved out unit of around 900 employees ran a formal readiness gate three weeks before close and found that a payroll integration everyone assumed was ready still pointed at the parent finance system. Because it surfaced at the gate, it was covered by a TSA pass through for two months and migrated cleanly, rather than failing on the first pay run. Running the gate is part of our carve out and TSA separation service within the carve out and TSA software playbook.

Planning beyond day one to a clean exit

Day one readiness buys continuity, but it also creates a clock. Every application running under a TSA pass through, every flow still pointing at a parent system, and every borrowed service is a cost and a risk that runs until the new entity migrates off it. The mistake buyers make after a successful day one is to relax, treating the gate as the finish line when it is the start of the migration. The estate that opened on borrowed services has to be moved to its own footing before the TSA ends, and the work of doing so should be planned and resourced from the moment day one is secured, not improvised as the exit date approaches.

A useful practice is to maintain a running readiness register that tracks each application from its day one state to full standalone independence. For every system the register records whether it is standalone, on a TSA pass through or partially migrated, what remains to be done, who owns it and the target exit date. Reviewed regularly, this register turns the long tail of migration into a managed programme rather than a scramble in the final weeks of the TSA, and it gives the deal team early warning when an application is at risk of overrunning its TSA window.

The financial logic reinforces the discipline. TSA charges typically carry a margin, and a parent has limited incentive to accelerate an exit that earns it revenue, so the new entity that drifts past its planned migration dates pays twice, once for the borrowed service and again for the standalone replacement it is slow to complete. Treating day one readiness as the opening move of a planned exit, rather than a destination, is what keeps the transition on time and prevents the double cost that erodes the value the carve out was meant to create.