Is Your Municipality Ready for an ERP Project?
Aging finance systems, manual workarounds, reporting that cannot answer the question, and vendors quietly changing their support models. Plenty of municipalities are looking hard at the systems behind finance, payroll, HR, procurement and budgeting, and concluding that the current arrangement will not hold much longer.
A new ERP can fix a lot of that. But most of what determines whether it does gets decided before procurement starts. Municipalities that define their outcomes, involve the right people, get their data in order and understand their own capacity end up buying better and implementing better. Seven questions will tell you where you stand.
1. What do we want the project to achieve?
A clear answer here drives everything downstream: requirements, vendor evaluation, implementation sequencing, and how you will know afterward whether it worked.
Common objectives include cutting manual entry and duplicate work, improving access to financial and workforce information, strengthening reporting and internal controls, expanding employee and manager self-service, and standardizing processes across departments.
The value of writing them down is that every later decision can be tested against them. Without that, decisions get made on preference.
2. Do we have strong corporate ownership?
ERP projects cross every department, which means no single department can carry one. An executive sponsor, a cross-functional steering committee and named process owners give the project the authority to keep moving when departments disagree.
The governance structure needs to settle who makes major decisions, who approves scope changes, which departments own which business processes, and how issues get escalated. It should also be clear who reports progress to senior leadership and council.
The City of Fort Saskatchewan identified governance, clear objectives, internal staff capacity and change management as central to its ERP modernization work, and its 2026 capital budget recognized that the implementation would touch every department.
3. Do we understand how work happens today?
ERP planning is a rare licence to look properly at how finance, HR, payroll, procurement and reporting actually run. Process reviews turn up duplicate entry, approvals nobody can justify, and workarounds that exist because the current system cannot do something. They also turn up practices worth keeping, which matters just as much.
Useful questions: which steps still serve a purpose, where could things be simpler or more consistent, what could be automated or moved to self-service, and where would a shared standard improve reporting?
Doing this work before procurement gives you requirements based on reality rather than assumption. It also gives staff a genuine say in how the future system works, which pays off later during adoption.
4. Is our data ready?
Data preparation is the work most often left too late. Starting during planning gives you time to review what you hold, where it lives, who owns it and what standards will apply going forward.
Typical work includes finding duplicate employee, supplier and customer records, reviewing naming and coding conventions, filling gaps in key fields, assigning ownership, confirming retention requirements, and identifying information currently sitting in spreadsheets outside any system.
The Town of Creston named process alignment, data cleansing and change management planning as specific implementation-readiness activities in its ERP replacement business case.
Beginning early also means vendors get a clearer picture of what they are being asked to migrate, which shows up in the accuracy of their pricing.
5. Do we have the capacity to support the project?
Your staff know how the work actually gets done. Their involvement is what makes requirements realistic, configuration appropriate and testing meaningful. It is also time they do not currently have.
Subject-matter experts get pulled into process reviews, requirements, vendor demonstrations, data preparation, configuration decisions, testing, training and post-launch support. That is a substantial commitment stretched across a long period.
Leadership should identify who is needed, estimate how much of their time, and decide what happens to their regular work during the demanding phases. Then you can judge honestly where backfill, specialized expertise or independent advisory support would help.
6. Are employees prepared for the change?
A new ERP changes how people do their jobs. Self-service replaces requests, processes get standardized across departments that previously did things their own way, and approval structures shift.
MNP's 2026 Municipal Report found change fatigue is already affecting engagement and delivery timelines in a majority of Canadian municipalities. The same research points to leadership communication, training and support programs as the practices that help most.
A workable change approach settles how the project's purpose gets communicated, how employees contribute to process and system decisions, what training each group needs, how responsibilities will shift, and how adoption gets monitored after launch. None of that is expensive. All of it is easy to skip.
7. Are we ready to make clear decisions?
ERP projects generate a steady stream of decisions about scope, configuration, timing and investment. A defined framework for making them keeps the project connected to its objectives and gives you a way through the moments when departments want different things.
Before procurement, leadership should be able to say which requirements are essential, where corporate standards create value, how you will approach configuration versus customization, what belongs in phase one, and how success will be measured.
These get considerably easier once questions one and two are answered. They also help vendors propose something that fits the organization rather than something generic.
Readiness Creates a Stronger Starting Point
Readiness is really about whether the municipality can guide the project: with clarity about what it wants, capacity to do the work, and ownership that holds when things get difficult. A readiness assessment surfaces the gaps while there is still time to close them.
That preparation creates value long before anything goes live. You enter the market with better requirements, have more informed conversations with vendors, and build an implementation approach grounded in how your municipality actually operates.
This fall, Perry Group's ERP Readiness to Results webinar series looks at the decisions to make before procurement, the questions municipal buyers should be asking vendors, and what turns an implementation into lasting results.