Article
The 21 Municipal ERP Success Factors
What helps a municipal ERP project succeed? Drawing on interviews with 11 vendors and implementers, Perry Group identifies 21 success factors covering leadership, preparation, procurement, people, implementation and ongoing operations. Use this practical guide to assess your municipality’s readiness and identify where to focus next.
These 21 factors come from interviews with11 vendors and implementers working in the municipal ERP space, combined withour own advisory experience on both sides of the table.
We asked them a simple question: what separatesthe municipal ERP projects that go well from the ones that struggle? Theiranswers were remarkably consistent. Very little of it was about software. Mostof it was about leadership, preparation, people and follow-through.
The factors are grouped into four stages ofthe journey. Each one includes a short explanation and, where we have one, aquote from the interviews so you can hear it in their words. We kept theinterviews anonymous so vendors and implementers could share their honest,unfiltered feedback, and the quotes are shared the same way.
Stage 1: Define it and own it
1. A senior leader is in charge
An ERP replacement should be led by asenior leader, such as the CAO or a department head, not by IT. These arebusiness decisions that affect the whole organization, and they need someonewith authority to make them stick.
Whatwe heard: In one Ontario city, the CAO, theDirector of Corporate Services, the CFO and IT all sat on the steeringcommittee. Implementers credited the project's success largely to the CAOstaying involved.
2. It's treated as an organizational change
A new system only delivers"better" if people change how they work. Many municipalities pay foran implementation but expect a transformation. Plan for the change, not justthe technology.
3. You know why an ERP is necessary
Be clear on the problem you're solving andwhat "ERP" means for your organization, including which functions arein and which are out. Without that, scope creeps, budgets grow, and departmentsend up disappointed.
4. You know what "better" looks like
If the goal is for the new system to dowhat the old one did, that's replication, not modernization. Define theimprovements you expect before you go to market.
"They don't necessarily look at how muchbetter it can be."
5. The budget covers the full life of the system
Cost the system over its whole life, notjust the first two or three years. Include backfilling staff on the project andcontingency for surprises like messy data.
6. Change management is funded
Change management needs its own protectedbudget and skilled people. It's often the first line cut, and it rarely worksas someone's side job.
"I don't think you can just appointsomeone in-house to say you are the change manager for this massivetransformation."
Stage 2: Prepare and buy well
7. Your systems and integrations are mapped
Know which systems you have, which you'llkeep or replace and why, and how they connect. Every system you keep is anintegration someone must build and maintain.
Whatwe heard: One RFP listed 25 interfaces when only 15were actually needed.
8. You've engaged the vendor market
Talk to peers, run a simple RFI and usecooperative purchasing vehicles to learn the market before you write an RFP.Done fairly, this is education, not pre-procurement.
"We would much rather you tell us we'renot a good fit than have us both invest months finding that out the hardway."
9. You understand your data
Know where your data lives, how clean it isand who owns it. Messy data is the most common surprise once a project starts.
10. You've planned for vendor capacity and procurementtimelines
Many municipalities are going to market atonce, and some vendors can take on only 10 to 15 conversions a year. A clear,well-prepared RFP helps you stand out, and starting early gives you morechoice.
11. Requirements flow from your goals
Define the outcomes you want and a shortlist of must-haves for each business area, demonstrated live. Thousands ofrequirements make evaluation impossible, and vendors increasingly answer themwith AI tools.
Watch the price weighting too. Heavyweighting means only the lowest bidders can realistically win, and missingpieces come back later as change requests.
"When price is scored at 30% or more, itmight as well be 100%."
12. The scope is realistic
Buy the right size of solution for yourorganization and be explicit about the modules, interfaces and services you'rebuying. A list of requirements isn't a scope of work.
Whatwe heard: One implementer puts the tipping pointfor the largest platforms at about 40,000 to 50,000 residents, partly becausesome have minimum user counts for HR and payroll.
13. You have experienced ERP advisors
Most procurement teams have never run aproject this big. An experienced advisor and procurement specialist shouldsimplify the process, not add layers to it.
Whatwe heard: One implementer described municipalities"choking procurement to death" out of fear, with processes sorestrictive that vendors can't propose a better approach.
Stage 3: Get the right people
14. You've chosen the right implementation partner
You're buying a team, not a logo. Ask tosee the specific people who will work on your project, check that theyunderstand municipal finance, tax, utilities and procurement, and write namedkey personnel into the contract.
"They're not asking to see what theproject team is going to look like, which is a little bit crazy."
"You can't successfully implement andchange procedures if you don't understand the work in the first place."
15. Your best people are on the project, and backfilled
The municipality owns the project, not thevendor. Assign your own project manager and your strongest staff and backfilltheir day jobs so they can focus.
Whatwe heard: Backfilling a key role can take three tosix months. Side-of-desk resourcing slows decisions and is one of the leadingreasons municipalities aren't ready at go-live.
Stage 4: Deliver and keep it going
16. The rollout is phased
Break the implementation into manageablephases, with each one fitting a clear picture of your whole back office.Phasing reduces risk and gives staff time to adjust.
17. Processes are standardized
Adopt standard processes wherever you can,rather than rebuilding old workarounds in a new system. Give someone with realauthority the call on when processes change.
18. Governance and escalation are clear
Set up a steering committee with theauthority to decide, and keep executives involved in the big calls. Decidequickly and stick to it. Change requests will come from both sides; manage themthrough governance rather than trying to prevent them.
Whatwe heard: Revisiting decisions is one of the mostexpensive patterns implementers see, in cost, time and frustration on bothsides.
19. Testing is business-owned
The people who will use the system shouldown testing, with clear go/no-go criteria agreed in advance.
20. Data is cleansed and migrated with care
Start cleaning data early and assignbusiness owners to it. Plan migration as its own workstream, not anafterthought.
21. There is an owner and operating model after go-live
Go-live is the beginning, not the end.Decide before you procure who will handle updates, testing and brokenintegrations, and plan for stabilizing, enhancing and continuous improvementwith a named owner and budget.
Whatwe heard: Lack of operational readiness is the mostcommon reason clients end up unhappy, and the implementer often gets the blame.