• GovCon Weekly
  • Posts
  • The Great Plains Exodus Creates Municipal Gold Rush

The Great Plains Exodus Creates Municipal Gold Rush

Canadian Procurement Pulse: Municipal Technology Spotlight

Canadian municipalities are racing to replace their ERP systems. The trigger? Microsoft sunsetted Great Plains, forcing hundreds of smaller municipalities off a platform they'd relied on for decades. The result is a procurement wave that will continue through 2026.

The Great Plains Problem

Great Plains dominated small and mid-sized municipal ERP for years. Affordable, stable, designed for government financial management. Then Microsoft ended support.

Municipalities between 5,000-50,000 population suddenly faced forced migrations. No patches. No updates. No support. Replace your entire financial system or operate on unsupported software.

This explains why Q3 and Q4 2025 show unprecedented municipal ERP activity. Organizations aren't choosing to modernize. They're being forced to replace working systems on compressed timelines.

What These Contracts Actually Cost

Alberta's procurement transparency reveals real pricing from the past year:

County of Wetaskiwin No. 10 (11,000 population)

  • Winner: MNP Digital

  • Contract: $387,250

  • Scope: Full ERP implementation

Rocky View County (40,000 population)

  • Winner: MNP Digital

  • Contract: $392,050

  • Scope: Requirements definition and readiness assessment ONLY

  • Implementation will cost additional

Town of Okotoks (30,000 population)

  • Winner: Tantus Solutions Group

  • Contract: $85,970

  • Scope: Implementation services

Town of Barrhead (6,000 population)

  • Winner: Catalis

  • Contract: $85,000

  • Scope: ERP software

The pattern reveals several insights:

Requirements definition alone costs $390K+ for mid-sized municipalities (Rocky View). Implementation adds another $500K-$1M on top.

Full implementations for small municipalities run $385K-$400K (Wetaskiwin). This includes software, implementation, training, and go-live support.

Software-only contracts are significantly cheaper ($85K range), but don't include implementation services that municipalities desperately need.

Pricing doesn't scale linearly with population. Wetaskiwin (11K) paid $387K for full implementation. Rocky View (40K) paid $392K just for requirements. Organizational complexity, number of departments, and existing system integrations matter more than citizen count.

Municipal Governments Leading the Wave

British Columbia municipalities particularly active:

District of West Vancouver: Complete ERP system and implementation services (closes December 11)

City of Pitt Meadows: ERP Replacement Readiness Assessment (closes December 1)

  • Smart approach: assess organizational readiness before committing to vendors

  • Avoids Rocky View's situation where requirements consumed nearly $400K

City of Victoria: Two separate NextGen ERP RFPs

City of Surrey: Financial software solution

Town of Blackfalds: ERP software replacement

Ontario municipalities following:

City of Hamilton: Independent oversight consultancy for ERP negotiations (closes December 5)

  • Third-party governance during vendor selection and implementation

  • Learning from others' expensive mistakes

City of Prince Albert: Financial ERP replacement consulting

Nova Scotia:

Nova Scotia Liquor Corporation: Complete ERP implementation replacing legacy systems

  • Finance, HR, supply chain, retail operations

  • Major provincial crown corporation modernization

The concentration in BC and Alberta makes sense. Western Canada municipalities heavily adopted Great Plains. Now they're all migrating simultaneously.

Consortium Purchasing Emerges as Cost Control

Canoe Procurement Group of Canada issued an RFI for municipal ERP implementation services (closes December 8). This Alberta-based group purchasing organization represents multiple municipalities seeking coordinated procurement.

The math makes sense: if Rocky View paid $392K just for requirements definition, spreading that cost across 5-10 municipalities dramatically reduces per-organization expense. Shared implementation also means shared learning as problems emerge.

Watch for more consortium approaches as municipalities realize individual procurement is expensive and risky.

Federal Activity: Beyond Great Plains

Federal departments weren't on Great Plains, so their ERP activity follows different drivers:

Department of National Defence: Cloud-based ERP RFI for Canadian Armed Forces

  • Financial management, HR, supply chain, project management

  • Market research for future major procurement

Department of Indigenous Services: Pharmacy Inventory Management System (closes December 2)

  • Cloud-based inventory for nursing stations

  • Specialized healthcare supply chain ERP

Royal Canadian Mounted Police: Complete ERP system replacement (negotiated RFP)

Shared Services Canada: ERP implementation and operational services

Canada's Drug Agency: Financial Planning and Analysis Software (closes November 26)

  • Replacing spreadsheet-based processes

  • Integration with SAGE 300, SAP Concur, Ceridian Dayforce

Federal opportunities are larger but slower. Municipal forced migrations create urgency. Federal modernization follows normal capital planning cycles.

Education Sector: Consistent Pipeline

Queen's University: Oracle Cloud Financial System implementation (closes December 1)

  • Full financial system implementation

  • Universities favoring Oracle Cloud

School District 37 Delta: Participating in Canoe Procurement Group initiative

School District 57 Prince George: Sparkrock implementation (awarded)

School District 93 Francophone Education Authority: ERP procurement underway

Education generates 2-3 opportunities quarterly. Universities choose Oracle. School districts choose Sparkrock. Different buyer sophistication levels and budget constraints create market segmentation.

Pre-Implementation Services: 

Two distinct service opportunities emerged from municipal ERP chaos:

Readiness Assessments (Pitt Meadows seeking proposals)

  • Organizations want to understand gaps before committing hundreds of thousands

  • Rocky View's $392K requirements bill scared municipalities into planning first

Independent Oversight (Hamilton seeking proposals)

  • Third-party consultants managing vendor negotiations

  • Protecting municipal interests during complex procurements

  • Recognition that municipalities lack internal ERP expertise

These represent new categories as organizations realize ERP implementations fail without proper preparation and governance.

What This Tells ERP Vendors

The municipal pipeline will run for 18-24 months. Great Plains municipalities must migrate. Every 5,000-50,000 population municipality in western Canada is a prospect if they haven't already migrated.

Requirements and readiness services are high-margin opportunities. Rocky View paid $392K just for requirements definition. Implementation will cost additional $500K-$1M. Pre-sales consulting generates revenue before software deals close.

Pricing power exists in forced migration markets. When municipalities have no choice but to replace systems, urgency reduces price sensitivity. Wetaskiwin (11K population) paid $387K because delay wasn't an option.

Consortium deals are emerging. Canoe Procurement Group approach pools multiple municipalities. One large contract rather than many small ones. Different sales strategy required but potentially more efficient. If you get on the Canoe contract, you need to educate municipalities yourself on how they can use the group purchasing vehicle.

Municipal ERP is not dominated by enterprise vendors. MNP Digital, Catalis, Tantus winning contracts. Specialized government-focused vendors competing successfully against SAP, Oracle, Microsoft.

What This Tells Buyers

Budget $300K-$400K minimum for small municipality implementations. Wetaskiwin (11K) and Rocky View (40K) both spent ~$390K, though Rocky View only got requirements definition for that price.

Requirements definition before vendor selection is expensive but necessary. Rocky View spent $392K on requirements. Organizations trying to skip this step to save money typically spend more fixing implementation mistakes.

Our Take:

ERPs are just tables, forms, and business logic transforming data. Not exciting. But they're the bedrock of municipal operations. When your ERP breaks, your organization stops.

This wave of replacements reflects something positive: governments finally investing in better infrastructure and data management after years of neglect.

The problem? They're implementing new but still legacy solutions. While municipalities spend 18-24 months replacing Great Plains with traditional ERPs, the rest of the world is experimenting with AI-native tools that query data in natural language and automate workflows through machine learning.

Municipalities must modernize to survive. But modernizing to yesterday's technology means falling further behind tomorrow's capabilities. (Okay that was a lot of platitudes I apologize.)

What This Means:

We're going to see huge variation in value across these deals. AI has made software development dramatically cheaper, but ERP transformations aren't about building new features. They're about migrating 20-year-old configurations and integrating legacy systems.

Rocky View paying $392K for requirements isn't paying for software. They're paying for someone to understand their ancient Great Plains setup, map it to modern equivalents, and plan data migration. That work doesn't benefit from AI productivity gains yet.

For development shops, this is a golden opportunity. Forced demand, compressed timelines, limited internal expertise, premium rates.

For municipalities, this is risky. Spending $300K-$500K on systems that lock you into 5-10 year vendor relationships right as AI transforms business software means potentially buying obsolescence at a premium.

Procurement Action Item:

ERP vendors: Prioritize Ontario municipalities (5K-500K population) that haven't migrated yet. Focus on requirements services as high-margin pre-sales revenue.

Municipal buyers: Budget $300K-$500K minimum. Consider consortium purchasing to share costs. Most importantly, prioritize vendors offering modern APIs and integration flexibility. You're committing to a decade-long platform while AI transforms business software. Choose systems that can evolve.

Development shops: Municipalities need help migrating complex legacy systems. If you can deliver requirements assessments, data migration, and custom integration, there's 18-24 months of premium-rate work ahead. Build them systems that can adapt, not just systems that work today.

Publicus helps government contractors find, qualify, and win more contracts with less effort. Our AI-powered platform monitors every opportunity across all government levels, with analytics on pricing and competition so you can understand your market like never before.