CivicPlus migration proposals routinely under-price the records-management line by $15,000 to $40,000. Procurement signs the smaller number; municipal ops eats the gap during the FOI request that follows.
If your municipality has fewer than 5,000 published documents in its CMS, this post overstates the risk for your case. This is for mid-size and larger municipalities with FOI exposure and a CivicPlus renewal decision on the table.
Why CivicPlus records matter beyond migration
CivicPlus is genuinely a fantastic tool, and I want to say that plainly before I say the rest: it is also large and cumbersome, with an ecosystem of plugins and add-ons that need constant maintenance to stay upright. The records published through it carry FOI exposure, and migrating away does not lift that obligation; it only changes which platform produces the audit trail. That is exactly why I treat records handling as a first-class line in any WordPress migration rather than a clean-up afterward.
What records management actually includes
When a municipality says “records management,” they mean document version history, disposition schedules, audit logs, retention enforcement, and a search-indexable archive. The catch is that none of those are WordPress defaults, so each one is work you are choosing to do, not a box that comes pre-ticked. The maintenance burden you were trying to escape from CivicPlus does not vanish; it moves, and it has to land somewhere you have actually built for it.
Where the budget surprise hits
The surprise is almost always the same. A CivicPlus migration plan that leaves out records-management implementation under-prices the project by $15,000 to $40,000, because that work is real and somebody has to do it. Procurement signs the smaller, cleaner-looking number, and operations quietly eats the gap later, usually at the worst possible moment.
What an honest scope looks like
An honest scope migrates documents with their provenance preserved, builds retention automation, integrates the audit log, and stands up a disposition workflow. Before cutover, it gets a records-officer sign-off on the destination configuration, not just on the website. It is the same provenance-first approach I describe in moving a publication off emdash onto WordPress.
Three-year money
Records-management implementation as a separate line: $15,000 to $40,000. Ongoing operations: $3,000 to $8,000 per year. Cost of discovering this gap during an FOI response: unbounded plus a council apology.
The Canadian rule that anchors this conversation
Bound by the Municipal Freedom of Information and Protection of Privacy Act (MFIPPA, Ontario) and equivalent provincial municipal-records statutes elsewhere. The records officer signs off on the destination configuration, not the website itself.
Product names referenced on this page — including WordPress — are trademarks or registered trademarks of their respective owners. Training offered here is independent and is not affiliated with, endorsed by, or sponsored by any of these companies.
