Why ERP replacements fail in local government
Municipal ERP is the highest-stakes software a city operates — and the failure pattern is remarkably consistent. Here's what actually goes wrong.
A failed ERP implementation is the most politically visible disaster in local government IT: payroll that misses a cycle, vendors who go unpaid, a general ledger that won't close, all of it playing out in public council meetings. The systems are replaced once in a generation, so the people running the project have almost never run one before. The failures are not random — they cluster around a handful of causes that are predictable, and therefore avoidable.
Cause 1 — paving the cow paths
The most common failure is insisting the new system replicate every quirk of the thirty-year-old system it replaces. Decades of workarounds get re-implemented as 'requirements,' configuration balloons, and the project collapses under customization that no longer matches any vendor's standard product. A successful ERP replacement is as much a business-process redesign as a software purchase — and governments that won't change a single process should expect to pay for that refusal in time and risk.
Cause 2 — staffing the project off the side of a desk
ERP implementations need the city's best finance and HR people assigned to the project, not added on top of their day jobs. Cities that try to run a multi-year replacement with no backfill get the predictable result: the subject-matter experts are too busy keeping the old system running to configure the new one, decisions stall, and the integrator fills the vacuum with assumptions that surface as defects at go-live.
Cause 3 — underestimating data and change management
Chart-of-accounts conversion, position-budget history, and vendor master data are where timelines quietly slip. The other quiet killer is change management: hundreds of end users across departments who were never trained, never bought in, and revert to spreadsheets the week after go-live. Budget for both as first-class workstreams, not afterthoughts.
The buyer-side lesson is the same one that runs through every category: the vendor matters less than the buyer's own readiness. Pick a viable product, then spend your energy on process redesign, staffing, and data — because that is where these projects are actually won or lost.