When the mayor of a small Texas town started calling about the third water main break on 5th Street in a single month, the Utility Director already knew the answer before picking up the phone: the system, all of it, from the field ticketing to the billing platform to the customer complaint log, was running on software that hadn't been meaningfully updated since 2009. The breaks weren't the real problem. The real problem was that nothing in the technology stack could tell her where the next one was coming from.
If that scenario sounds familiar, you're not alone and you're probably not exaggerating how bad it's gotten. This guide walks through what legacy water utility technology actually costs you, how you know it's time to replace your CIS, and what modernization looks like in practice for a utility your size.
Legacy water utility technology refers to on-premise CIS, billing, and work order software that was not designed for cloud delivery, real-time AMI/MDM integration, or modern cybersecurity compliance. Most US water utilities running legacy systems installed them between 1995 and 2010. These platforms are not just outdated, they actively increase operational cost, revenue leakage, and compliance risk.
Legacy does not simply mean "old." A system becomes legacy when its architecture prevents you from doing things your operation now requires: integrating with AMI meters, automating billing runs, giving customers a self-service portal, or generating the audit trails that EPA and AWIA reporting now demands.
A Customer Information System (CIS) is defined as the core software platform that manages customer accounts, service requests, billing records, and payment history for a utility. When a legacy CIS cannot connect to your billing software, your field work orders, or your AMI data feed without manual data entry, every gap costs you time, money, and accuracy.
Non-revenue water (NRW) refers to water that a utility produces and distributes but does not bill for due to leaks, meter inaccuracies, or billing system errors. Legacy systems that cannot integrate with AMI meter data are a significant contributor to NRW losses, which average 16% of total water produced across US utilities. (AWWA)
Most utility directors know something is wrong long before they can justify a replacement to their board. Here are the five signs that your system has moved past "manageable workaround" into "operational liability."
1. Your billing team manually reconciles meter reads a tend-of-month. If your staff exports CIS data to a spreadsheet to reconcile meter reads, you're operating at a billing error risk of 10–15%. Every billing error that reaches a customer is a complaint, a call, and a delayed payment.
2. Your AMI meters produce data your CIS cannot consume. If your utility has upgraded to AMI meters but your CIS still requires manual read imports, you are paying for smart metering and receiving almost none of its value. Real-time AMI integration is table stakes in a modern platform, your CIS should ingest interval data automatically.
3. Your IT team spends significant time on server maintenance and patching. Utilities running on-premise CIS infrastructure routinely report that one or two IT staff members spend 30–40% of their time on hardware maintenance, backups, and security patching, time that could be redirected to operational improvements. Cloud-native SaaS eliminates on-premise infrastructure entirely.
4. You cannot produce an AWIA-compliant cybersecurity risk assessment from your current systems. The America's Water Infrastructure Act of2018 (AWIA 2018) requires community water systems serving 3,300+ people to certify a risk and resilience assessment to the EPA every five years. Legacy on-premise systems with poor audit trails and outdated security protocols are a direct compliance liability.
5. Your customer service team cannot resolve billing questions in a single call. If your customer service staff needs to navigate multiple disconnected systems to answer one customer question - CIS for the account, billing software for the invoice, a separate portal for payment history, your average call handle time will reflect it. A unified platform reduces call handling time by up to 60%.
The reluctance to modernize is understandable. Utility directors are managing lean budgets, smaller teams than they had five years ago, and a board that wants to see a clear financial case before approving a platform change. But the cost calculation that matters is not "what does modernization cost" — it is "what does staying with your current system cost per year."
Consider the compounding cost of delay across three categories:
Billing inaccuracies on a legacy system do not just generate customer complaints — they represent direct revenue loss. A utility billing 15,000 accounts per month with a 10% error rate is issuing 1,500 incorrect bills per cycle. Some will be overcharges (generating refund costs and complaints), but many will be undercharges that are never corrected. Utilities that modernize their billing platform consistently report 50% improvements in billing accuracy, directly reducing revenue leakage.
The ASCE 2021 Report Card graded US drinking water infrastructure C, and EPA regulatory pressure on water quality reporting, cybersecurity risk assessments (AWIA 2018), and lead service line inventories (Lead and Copper Rule Revisions, 2021) is intensifying. Legacy systems that cannot generate automated compliance reports force manual reporting processes and manual processes introduce the documentation gaps that trigger regulatory scrutiny.
Experienced utility staff are retiring at a rate the industry has not seen before. The knowledge that leaves when a senior billing specialist or field supervisor retires is often locked inside manual workarounds built on top of a legacy system. A modern platform with automated workflows and mobile field tools reduces dependence on individual institutional knowledge, protecting operational continuity when staff transitions occur.
A modern water utility management platform is not a collection of separate tools that need to be integrated. It is a unified cloud-native SaaS system that connects CIS, billing, AMI/MDM integration, work orders, asset management, and a customer self-service portal in a single environment.
Here is what that looks like in practice, compared to what most legacy environments deliver:
The key shift is unification. When your CIS, billing engine, and customer portal share a single data layer, a meter read immediately flows to the bill, which immediately updates the customer's self-service view, which immediately reduces the volume of inbound billing calls. There are no file exports, no manual syncs, and no data gaps between systems.
For a deeper look at what modern water utility management software covers across each operational function, the SMART360 water utilities page walks through each module in detail.
The customer information system for utilities is the foundation of the platform - managing accounts, service history, billing records, and payment processing in one environment rather than three.
Implementation fear is the most common reason utility directors delay a platform decision. And to be fair, the fear is historically justified: large enterprise utility software vendors have built reputations for implementations that run 12–18 months, exceed budget, and require dedicated project management staff to survive. If your only data point on utility CIS replacement is "it takes over a year and disrupts everything," the reluctance to start makes complete sense.
That timeline is not universal and it is not what utilities your size should expect.
Platforms purpose-built for small and mid-sized utilities, those serving 3,000 to 100,000 meters, can be implemented in 12–24 weeks because they are pre-configured for the specific data structures, billing rate types, and compliance workflows that municipal water utilities actually use. There is no enterprise customization backlog. There are no integration consultants billing hourly to build connections your system should have out of the box.
A managed implementation for a small-to-mid water utility typically moves through four phases:
Your existing customer account data, billing history, meter records, and service order history are assessed for completeness and migration readiness. A data migration specialist maps your legacy data structure to the new platform schema. Most utilities have messier data than they realize, this phase finds and resolves data quality issues before they become go-live problems.
The platform is configured to your rate structures, billing cycles, service territory, and workflow rules. Integrations to your AMI meter vendor, GIS system, and payment gateway are activated using SMART360's 25+ pre-built connectors. This is typically where the biggest time savings over enterprise vendors occur, pre-built integrations eliminate months of custom development.
Your team runs both the legacy system and the new platform simultaneously across a full billing cycle. This is the safety net - your staff validates that billing outputs match, customer records are complete, and work order flows work as expected. Any discrepancies are resolved before the legacy system is decommissioned.
The legacy system is retired. Your staff has been trained through the parallel phase, so go-live is not a cold start, it is a transition that billing and customer service teams have already rehearsed. Ongoing operational support is provided post-launch.
A Customer Information System(CIS) manages the full customer relationship - account setup, service requests, payment history, and communication records. A billing system handles invoice generation, meter-to-cash processing, and collections. In legacy environments these are often separate products that require manual data syncing. In a modern utility platform, CIS and billing share a single data layer - a meter read flows directly into a bill without any manual intervention.
Cost depends significantly on pricing model. Enterprise vendors typically charge per-user license fees and implementation consulting costs that can run into seven figures for mid-sized utilities. Purpose-built platforms for small and mid-sized utilities price on a pay-per-meter model — meaning your cost scales with your actual service territory rather than your headcount. This model tends to be substantially more affordable for utilities with lean teams and high meter counts.
A managed migration with a parallel testing phase significantly reduces this risk. The critical protection is the parallel-run period, during which your legacy system and new platform process billing simultaneously and outputs are compared. Any data discrepancies are identified and resolved before the legacy system is retired. No utility should accept a migration plan that does not include a parallel testing phase —this is a non-negotiable step in a safe implementation.
AWIA 2018 requires community water systems serving 3,300 or more people to complete a cybersecurity risk and resilience assessment and certify it to the EPA every five years. It does not mandate specific software. However, utilities running on-premise legacy systems with outdated security architecture, inadequate audit trails, and manual reporting processes will find it significantly harder to achieve and document compliance. Cloud-native SaaS platforms designed for utility operations are built with AWIA-relevant audit trails and security controls by default.
