County briefed on switching Munis to cloud as vendor ends on‑prem upgrades

Davis County Budget Committee · April 14, 2025

Loading...

AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

Davis County staff said Tyler’s Munis product will stop functional upgrades for on‑premises installations; staff recommended migrating to the vendor's cloud offering and provided estimated first‑year costs and an implementation timeline to avoid budget‑season disruption.

County finance and IT staff told the Budget Committee that the vendor for the county’s Munis financial/Human Resources system will stop delivering functional upgrades for on‑premises installations and is directing development to its cloud product. The change means Davis County will eventually need either to migrate to the vendor’s cloud or select another ERP.

"My recommendation is that we do move to the cloud and that we continue to use Tyler as the kind of the core of our ERP," the controller said during the April 14 meeting. IT and finance staff described the cloud option as less disruptive than switching to a completely different ERP but noted implementation costs and timing constraints.

IT presented cost estimates to the committee. Staff said the county's current annual on‑prem support is about $140,000; migrating to the vendor cloud was estimated at about $260,000 per year, with first‑year implementation costs around $310,000 total. An optional cashiering implementation was discussed as a roughly $60,000 one‑time cost with a modest ongoing license fee of about $6,000–$9,000 annually. Staff cautioned that switching to other ERP platforms (for example Workday, Oracle or PeopleSoft) would likely multiply costs and require significant implementation resources.

Committee members emphasized timing: staff recommended starting implementation after budget season to avoid payroll risk, noting that parallel (dual) runs of on‑prem and cloud systems are costly but reduce the risk of payroll disruption. Staff said a December/January start could aim for a February go‑live, while a full replacement via RFP would likely push a project into 2027.

Next steps: staff will distribute implementation models to department directors, coordinate with administrative officers for departmental feedback, and return with more precise pricing and an implementation schedule.