In 2019 the Government Accountability Office found that about 80 percent of the federal government's more than $90 billion in planned IT spending went to operating and maintaining existing systems, and that the ten most critical legacy systems it examined were 8 to 51 years old. Counties have less money and smaller teams than federal agencies, so the same pressure is usually harder to escape. This post is about how a county can modernize in steps, on its own schedule, instead of in one risky replacement.
An earlier version of this post said "the average county government system was deployed before the iPhone existed." We couldn't find data behind that, so we've removed it, along with a client example we can't document. It also listed FedRAMP as a requirement for county systems. FedRAMP covers federal agencies' use of cloud services; it applies to a county only when a federal agency's use case brings it in.
Why modernization keeps losing to the next patch
County budgets are annual and modernization projects run for years, so the comparison is rarely fair. For example, say a replacement costs $2 million over three fiscal years and a patch costs $200,000 and buys another year. (Those figures are illustrative, not from a real county.) The patch wins each budget cycle, and the bill for the replacement grows every year it's deferred.
Risk aversion is part of it too, and it's rational. When a system runs dispatch, property taxes or child welfare cases, a failed cutover is a public safety problem, not a bad quarter. Staff choose the system they know. Meanwhile, the people who know how the old system works retire, and the documentation rarely captures what they knew.
Vendor lock-in finishes the picture. A platform whose vendor has stopped investing in it still has to be maintained, usually by that vendor, on its terms.
What residents actually run into
Residents meet these systems as delays and dead ends. A permit system built before online submissions forces an office visit or a paper form. A records request that a modern system would answer with a search becomes a manual hunt. Case data stays split across departments because the systems were never meant to talk to each other.
People compare that with their bank and their phone. Every gap between the two is a small loss of trust in the county, and those add up.
Modernize in steps, not one big replacement
A big-bang replacement puts every department's work on one cutover date. An incremental approach replaces one component at a time while the rest keeps running. Here's the order we'd recommend.
- Build the integration layer first. Put APIs in front of the legacy systems so new components can connect to them. When a legacy module is replaced later, nothing else has to change.
- Start with services residents use. Permits, licenses, records requests and payments have clear inputs and outputs, and progress on them is visible, which helps keep budget and political support.
- Migrate data in batches. Run old and new systems in parallel, move data in pieces, and check it as you go, instead of betting everything on one weekend.
- Build compliance in from the start. Retrofitting it costs more than designing for it.
- Train your own team. The goal is a county IT staff that can run what gets built, not a permanent dependency on contractors, including us.
The tradeoff is time. An incremental program takes longer to finish than a replacement promises to, and for a while you run two systems at once. What you buy is that no single day can take the county offline.
Accessibility now has a deadline
Compliance in step 4 now includes a hard date. The Department of Justice's ADA Title II rule makes WCAG 2.1 Level AA the technical standard for state and local governments' web content and mobile apps. After an interim final rule in April 2026, the compliance dates are April 26, 2027 for governments serving 50,000 or more people, and April 26, 2028 for smaller governments and special districts.
A legacy portal that was never built for screen readers or keyboard navigation is now a compliance problem with a date on it, not just a usability complaint. Systems that hold criminal justice or health records carry their own federal security rules on top of that. Meeting all of these in a new component is far easier than retrofitting an old one, which is a good reason to start with the services residents touch.
Start with an honest inventory
The first step isn't a purchase order. It's knowing where you stand:
- Which systems are near end of life or end of vendor support?
- Where does knowledge of a system sit with one or two people?
- Which resident-facing processes cause the most complaints or delays?
- Which compliance requirements, including the ADA web rule, are you meeting through workarounds today?
The answers decide the order of the work, and they let you budget it in pieces that fit an annual cycle.
Sources
- GAO-19-471: Agencies Need to Develop Modernization Plans for Critical Legacy Systems (June 2019)
- U.S. Department of Justice: Fact Sheet on the ADA Title II web and mobile accessibility rule
- FedRAMP: Scope
Last checked November 14, 2026.
Want a structured way to do the inventory? Our IT Modernization Readiness Assessment scores your systems, cloud readiness, security posture and workforce, and turns the results into a phased roadmap. Schedule a briefing to walk through it with our team.
