Government agencies have to modernize while continuing to deliver the services people depend on.
Open cases, historical records, and responsibilities shared across departments can make retiring an old system more complicated than launching its replacement.
Consider an agency introducing a new permitting portal. New applications can come in online, staff have been trained, and the project has reached a major milestone.
But open applications still live in the old system. Historical records need to remain accessible. Another department depends on a report the new platform doesn’t produce yet.
For the employees handling permits, the transition is still very much underway.
This hypothetical scenario illustrates a question worth asking early in government modernization: What will it take for the agency to stop operating the old system?
The answer involves more than a successful launch. It requires decisions about unfinished work, records, reporting, dependencies, and who has the authority to say the old environment can finally be retired.
Retirement deserves a place in the modernization plan
A replacement project naturally draws attention toward what’s being built. There are requirements to gather, configurations to test, and people to train. Getting the new system operational is substantial work.
Planning the end of the old system deserves attention alongside it.
In a July 2025 review, the U.S. Government Accountability Office examined modernization plans for 11 critical federal legacy systems. Only three included all the key elements GAO evaluated: milestones, a description of the modernization work, and details about what would happen to the legacy system.
That finding doesn’t mean every agency had launched a replacement and failed to switch over. It does establish that planning for the legacy system’s future is a recognized part of modernization, and one that can remain incomplete.
For agency leaders, the practical question is whether the plan explains how the organization will become able to end the old operation. A launch date alone won’t provide that answer.
Keeping the old system may be a reasonable decision
An agency may need a period in which old and new environments coexist.
Returning to the permitting example, moving every open application midway through review could introduce complications. An agency might decide to finish those applications in the old system while routing new submissions through the portal.
That can be a deliberate transition strategy. It needs boundaries, though.
Where does an amendment to an existing application go? What happens if an applicant submits information through the new portal for a case in the old system? Where should staff look for the authoritative status?
Without clear answers, employees have to bridge the gap themselves. They may keep spreadsheets, copy information between systems, or contact colleagues to verify which record is current.
Before interpreting those workarounds as reluctance to change, find out what purpose they serve. They may reveal an unresolved dependency that the transition plan needs to address.
Separate access to history from continued operation
“We still need the information” is an important concern. It also needs a more precise follow-up: What do people need to do with it?
Looking up a historical permit is different from editing an active application. Producing a report is different from accepting a new submission. Each need may call for a different arrangement.
The U.S. Fish and Wildlife Service’s decommissioning policy offers a concrete example of the planning involved. It addresses records disposition, data migration, security and privacy tasks, effects on connected systems, resource needs, and stakeholder communication. It also requires formal approval before a system leaves production.
These are that agency’s requirements, rather than a universal checklist for every government organization.
The management lesson is useful beyond that specific policy: retirement planning needs to account for the obligations the old system supports.
For the permitting agency, that means identifying how historical records will remain available and to whom, while separately deciding when active processing can end. Leaving the entire system running indefinitely because someone may need an old record postpones those decisions.
Turn dependencies into work someone owns
A list of reasons the old system must stay is a starting point. Each reason needs an owner, a next action, and a condition that will allow it to be resolved.
If another department depends on a monthly report, who will define and verify its replacement? If open applications must finish in the old environment, who will monitor the remaining workload and address cases that stay open longer than expected?
“Reporting isn’t ready” can keep a system running for months. A named owner working toward an agreed reporting requirement gives the transition a path forward.
The plan should also identify who can approve retirement and what evidence that person needs. Technical staff, program leaders, records personnel, and other stakeholders may each have responsibilities to complete before that decision is possible.
These responsibilities need time and resources. If they remain informal tasks to handle after launch, they compete with daily operations and the next project.
Set conditions for ending the overlap
A target retirement date helps coordinate the work. Pair it with conditions that explain what must be true before the agency can proceed.
For the hypothetical permitting transition, those conditions might include:
- All remaining applications have been completed or moved through an approved process.
- Staff can retrieve the historical records they need through the agreed arrangement.
- Dependent departments have verified replacement reports.
- Connected processes have been tested and unresolved exceptions addressed.
- The responsible officials have completed the necessary reviews and approvals.
The exact conditions will depend on the agency and system. The point is to make them explicit enough to manage.
If a date moves, leadership should be able to see which condition remains unmet, what it will take to resolve it, and who is responsible.
That makes an extension a considered decision with a next step.
Measure progress toward being able to stop
After launch, keep the remaining transition work visible.
How many active cases remain in the old environment? Which reports still depend on it? Where are employees entering information twice? Which unresolved issues prevent a retirement decision?
These measures help leaders determine whether the overlap is shrinking or becoming a permanent part of operations.
A new system can deliver useful capabilities while the transition continues. Realizing the intended benefits also requires attention to the work, costs, and dependencies that remain in the old environment.
Government modernization needs a plan for both. Asking what will make retirement possible gives agencies a clearer way to manage the transition while keeping public services moving.
What’s keeping your agency’s old system in service?
Advisicon has worked extensively with departments of revenue, transportation, energy, and health and human services. We bring that government modernization experience to conversations about how people, processes, and technology need to work together.
If your agency has a replacement underway but unresolved dependencies are keeping the old environment in place, let’s talk about what it will take to move forward.
