Federal IT Contracts Need an Exit Plan for the Old System
A GAO audit of 11 critical systems shows why Congress should follow replacement contracts all the way to retirement.
A federal agency can buy a new computer system, launch it on schedule and still pay to run its predecessor for years. That is an easy expense to overlook at a ribbon cutting. It is also one reason the Government Accountability Office treats a plan for retiring the old equipment as a basic ingredient of modernization. The purchase order for the replacement tells Congress only half the story.
In its July 2025 audit, GAO reviewed 69 federal legacy systems and identified 11 as most in need of modernization. Ten agencies operated them. At the time of the review, plans for just three of the 11 contained all the elements GAO looked for. Agencies responsible for the other eight had work to do on their documentation. The finding describes the audit period. It does not establish that every weakness persisted into the next budget year.
Paying for two generations
Running two systems side by side can be a responsible choice. A benefits office needs to know that records transferred correctly and that a family receives the right payment before it shuts down the old service. Payroll, tax collection and public benefits all leave little room for a trial run that loses transactions. Someone must nonetheless define the point at which the trial ends.
Consider the incentives facing a program manager. Keeping the old platform available gives staff a fallback if the replacement encounters trouble. Turning it off creates a visible moment of risk, while the savings may accrue elsewhere in the department. Unless one official owns the decision and a budget line exposes the continuing expense, a temporary precaution can quietly become the operating model.
GAO’s full report provides a useful historical check. Of ten systems flagged in an earlier 2019 review, agencies had completed three modernizations by February 2025. The two groups come from different reviews and should be kept separate. Taken on its own terms, the older group illustrates the distance between identifying an aging system, writing a plan and bringing the replacement effort to a close.
There is a simple way to test the savings claim. Ask finance staff which invoice disappears, in which quarter, when the older service closes. If no one can identify it, the proposed saving may depend on a contract change that procurement staff have yet to negotiate.
What appropriators can verify
The next funding request ought to name the functions that must move, the official authorized to accept the transfer and the evidence required before the old contract ends. A migration involving financial records might require reconciled balances and an auditable archive. A public-facing application might need a period of demonstrated service under real demand. The thresholds should fit the mission and appear before bids are evaluated.
A contractor also needs to know what the government will supply. If an agency cannot deliver clean records or identify the owner of a disputed process, a deadline alone gives bidders little reason to quote a competitive price. Disclosing dependencies lets firms price actual work and makes it harder for either side to bury an avoidable delay in a change order.
Members of Congress do not need to select software architecture to exercise oversight. They can ask when parallel operation began, what it costs per month and what still stands in the way of retirement. An agency with a sound answer may deserve more time. An agency without one should explain why taxpayers are financing two generations of technology with no dated decision about the first.