TSA Exit Acceleration
The safety net you hope not to use.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
TSA exit rollback planning is the discipline of building a credible reversal path for a cutover before the cutover begins. The rollback is the safety net. Disciplined buyers build it, rehearse it, and define exactly when they would pull the trigger. The rollback plan sits inside the broader TSA exit strategy framework because the right to roll back depends on what the TSA permits and on what the seller agrees to keep running during the cutover window.
Most programs treat rollback as a checkbox in the run book that nobody plans to exercise. The plan is written, signed, and ignored. Then the cutover hits a serious defect at 02:00 on Sunday morning, the program director has to make a call by 06:00, and the rollback plan is read for the first time. By 06:30, the team realizes the plan does not work because the data has already changed in three systems, the bank cutoff has passed, and the seller's environment was decommissioned at midnight.
The rollback plan is real when it has been walked through by the senior team, when the steps have been rehearsed at least once, and when the dependencies on the seller's environment have been preserved. The discipline is to invest seriously in the rollback plan even though everyone expects not to use it. The expectation is that the plan is a true safety net, not a paper artifact for the governance committee.
The rollback plan should be a hard requirement in the cutover go decision. The governance committee should not approve the cutover unless the rollback plan has been walked through, the seller has agreed to keep the source environment available for a defined rollback window, and the data preservation steps have been validated. Without these conditions, the cutover should not proceed. The failure pattern of a cutover with no real rollback option is in TSA exit failure modes.
The right to roll back depends on the seller preserving the source environment during the cutover window. Most sellers want to decommission as soon as the buyer's cutover lands, because the cost of running the legacy environment is real. The TSA should require the seller to keep the source environment available for a defined rollback window, typically 30 to 90 days after the cutover, with the buyer paying any incremental cost.
The preservation scope is defined precisely. What systems remain available. What data remains intact. What integrations remain active. What support remains contracted. The default seller posture is to preserve only the bare minimum. The buyer should negotiate the preservation in the cutover plan, not in the TSA negotiation. The cutover plan is where the operational details land, and where the seller has the most flexibility to commit.
The preservation cost is part of the cutover budget. Running the legacy environment for 30 to 90 days after cutover is not free. The buyer should model the cost, fund it in the cutover budget, and treat it as the insurance premium for the rollback right. The benchmarks for this cost are part of TSA exit cost benchmarks.
Rollback decisions sit at three tiers. Tier one is the partial rollback. A specific workstream rolls back while the others proceed. For example, the payroll workstream rolls back if the first payroll fails while the finance and order management workstreams continue. Tier one rollbacks are common, manageable, and should be planned for as the default contingency.
Tier two is the full rollback. Every workstream returns to the seller's environment. The cutover is reversed, the data is reconciled back to source, and the integrations are restored. Tier two rollbacks are rare and expensive. They are typically only triggered when the defects span multiple workstreams and the business cannot operate on the Newco environment. The decision authority is the executive sponsor, not the program director.
Tier three is the failover. The Newco environment continues to receive new transactions, the seller's environment continues to provide read access to history, and the cutover is partial. Tier three is a hybrid state that buys time to address defects while keeping the business operating. The discipline is to plan for tier three as a deliberate option, not as an accidental result of failed planning.
The trigger thresholds for rollback are defined before the cutover, not during it. The thresholds list the specific conditions under which each tier of rollback is considered. For example, payroll calculation error rate above 2 percent on the first run. Or order capture failure rate above 5 percent in the first 24 hours. Or general ledger trial balance variance above 0.5 percent at end of day one. Each threshold has a defined measurement method and a defined decision time.
The thresholds are not aspirational. They are realistic. They reflect what the team has seen in mock cutovers and what the business can tolerate in production. Thresholds set too tight will trigger unnecessary rollbacks. Thresholds set too loose will tolerate defects that damage the business. The governance committee debates and approves the thresholds before the cutover and locks them in writing.
Decision authority is named, not inherited. The program director can authorize a tier one rollback. The executive sponsor authorizes a tier two rollback. A specific operating committee authorizes a tier three failover. The names and contact details are in the cutover run book. The escalation path is short, and the decision time is bounded. Buyers that leave the authority ambiguous lose hours debating who can decide, which is the most expensive way to lose a cutover window.
A rollback is not a failure. It is an exercise of the safety net. The discipline after rollback is to diagnose the root cause, fix it, and plan the rerun. Most rollbacks reveal a defect that was not caught in mock cutovers because the volume, the data complexity, or the integration timing in production differs from the test environment. The diagnosis takes time. The rerun is scheduled when the team is confident the defect is resolved.
The rerun budget is negotiated with the seller. A second cutover window typically requires the seller to extend the TSA, to provide additional cooperation, and to charge for the extension. The extension fee is the cost of the rollback decision. The buyer's program director should pre negotiate the rerun terms before the cutover, so that if rollback is exercised, the rerun is not blocked by a new commercial negotiation in the middle of a crisis.
The lessons from the rollback feed the rerun plan and any future cutover. The diagnosis is documented. The remediation is documented. The mock cutover gap is documented. The cutover playbook is updated. The next time the team plans a cutover, the lessons reduce the risk of the same defect recurring. The discipline of structured lessons learned is part of our TSA exit acceleration service.
How to plan the cutover from seller systems to Newco target state without breaking month end.
Read the article →When parallel running is worth the cost and when it doubles the bill without buying confidence.
Read the article →The ten failure patterns that derail TSA exits and the disciplines that prevent each one.
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 →
Fixed-fee proposal in 48 hours. Senior team on day one. 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.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →