Utilities should choose SAP S/4HANA when SAP is already their strategic enterprise backbone and they can fund heavy customisation. They should choose a dedicated, cloud-based utility CIS when they need faster delivery, lower complexity and better support for smart meter growth. For many suppliers replacing SAP IS-U in 2026, the dedicated CIS route carries less risk. This article compares both routes, from migration effort to IoT readiness.

Why are utilities reconsidering SAP IS-U as support ends?

Utilities are reconsidering SAP IS-U because its mainstream maintenance window is closing, which forces a decision about the platform that runs billing and customer operations. Staying put means growing risk and cost, so most organisations must now choose between a move to S/4HANA or a new, purpose-built utility CIS.

The end of maintenance is only part of the story. Many IS-U estates carry years of custom code, bespoke interfaces and heavily modified billing logic. Every change request becomes slower and more expensive, while the market demands the opposite: dynamic tariffs, prosumer billing, electric vehicle charging and large smart meter volumes.

This is why the deadline is better treated as a trigger for review than as a simple upgrade task. A like-for-like technical move can preserve the same constraints you were hoping to leave behind. The useful question is whether your current model still supports where the business is heading.

How do S/4HANA and a dedicated CIS compare?

SAP S/4HANA for utilities is a broad enterprise suite with utility functionality added through industry solutions, while a dedicated CIS is built around the meter-to-cash process from the start. The first offers enterprise breadth and a single vendor; the second offers utility depth, faster configuration and lower change effort.

The differences become clear when you compare them side by side:

  • Scope: S/4HANA covers finance, supply chain, HR and more. A dedicated CIS focuses on customers, contracts, tariffs, billing and meter data.
  • Time to value: S/4HANA programmes are typically large, multi-year transformations. A dedicated cloud CIS can usually be configured and rolled out in a more phased way.
  • Flexibility: Complex tariff and market changes in a suite often need development effort. In a utility-specific platform, they are more often handled through configuration.
  • Total cost of ownership: Licences, infrastructure, custom code and specialist skills all add up over a 10 to 15 year lifetime, so compare the full picture rather than the upfront price.
  • Ecosystem: A suite favours organisations already standardised on SAP. A dedicated CIS built on a different platform may integrate more naturally with Microsoft-based tools.

It is also worth separating the CIS from the ERP. A CIS knows who the customer is, what they have agreed to and what they consume. An ERP tracks the ledger, payments and reporting. Some utilities combine both in one system, while others keep them separate and integrate them through APIs, so decide which model suits your operating structure before you compare vendors.

What does each route mean for data migration?

Data migration is the largest risk in either route, because years of IS-U data must be cleansed, mapped and validated before go-live. Moving to S/4HANA often means restructuring that data into a new model, while a dedicated CIS requires mapping it into a new utility-specific schema.

Neither path lets you simply copy the old database across. Legacy systems usually contain inconsistent contract records, duplicate business partners, outdated tariffs and incomplete meter histories. Cleansing this data early is what protects billing accuracy later.

Whichever route you take, plan for these essentials:

  1. Profile and clean source data well before the migration window opens.
  2. Agree a clear mapping between legacy objects and the target data model.
  3. Run multiple trial migrations with reconciliation against real billing results.
  4. Keep parallel billing runs and a read-only legacy archive for historical queries.
  5. Define cutover, rollback and support plans before the final weekend, not during it.

A phased migration, moving customer segments or commodities in waves, lowers risk in both cases and is easier to manage than a single big-bang cutover.

Which route is better for smart meter and IoT growth?

A dedicated, cloud-native CIS generally handles smart meter and IoT growth better, because it scales processing on demand and is designed around high-volume meter data. S/4HANA can support these volumes, but usually needs additional components, integration work and capacity planning.

Smart meter rollouts can multiply data volumes by orders of magnitude compared with monthly manual reads. That affects ingestion, validation, estimation and exception handling, not just storage. A strong platform treats meter data management as a core capability and resolves exceptions automatically rather than leaving them in queues.

Look closely at how each option copes with the following:

  • Interval data ingestion at scale, without hardware procurement cycles.
  • Open APIs for connecting AMI networks, EV charging and home energy systems.
  • Configurable tariffs for time-of-use, community energy and dynamic pricing.
  • Management by exception, so teams only handle the readings that need attention.

Cloud elasticity matters here. Peak billing runs and large meter deployments are far easier to absorb when capacity scales up and back down, rather than being sized permanently for the busiest day.

When does a cloud CIS on Microsoft Dynamics 365 make sense?

A cloud CIS on Microsoft Dynamics 365 makes sense when you want a utility-specific platform without managing infrastructure, and when your organisation already uses Microsoft tools such as Azure, Power Platform or Microsoft 365. It suits utilities seeking faster delivery and lower customisation overhead than a suite rebuild.

The strongest cases tend to share a few traits. You want to retire a heavily customised legacy environment. Your IT team would rather focus on improvement than patching and hosting. You expect growth through smart metering, acquisitions or new service lines. And you value a single, familiar user experience for customer service, billing and field teams.

Building on a mainstream enterprise platform also helps with security, regular updates and a long product roadmap. Microsoft partnerships in the utility space show how this combination can support billing, customer engagement and meter data in one integrated environment. Real-world examples include water utilities that have moved to the cloud, such as the story of Waternet and its cloud journey.

If your estate is deeply embedded in SAP finance and asset management, with strong in-house SAP skills and a mandate for one enterprise vendor, S/4HANA may remain the more natural fit. The right answer depends on your context, not on a universal ranking.

How should utilities decide between the two routes?

Utilities should decide by scoring both routes against a short list of criteria: strategic fit, total cost of ownership, time to value, data migration risk, smart meter readiness and internal skills. A structured comparison over a 10 to 15 year horizon is more reliable than comparing upfront licence prices.

A practical decision process looks like this:

  1. Define the business outcomes first. Faster tariff launches, lower cost to serve and better customer experience should drive the choice, not the technology label.
  2. Map your real requirements. List regulatory needs, commodities, market processes and integrations, then test each option against them using your own scenarios.
  3. Model total cost of ownership. Include implementation, customisation, hosting, support, upgrades and the cost of future change.
  4. Assess your capability. Be honest about the SAP or cloud skills you can retain and the change capacity your teams have.
  5. Test the vendor and partner. Ask for utility references, a clear migration approach and a credible plan for training and ongoing support.
  6. Start with a phased scope. Prioritise the area causing the most friction, then expand once the foundation is stable.

Involving compliance, finance and customer service early prevents surprises later. Treat the decision as an operating model choice, because the platform you select will shape billing, data and customer operations for years.

How we help with an SAP IS-U replacement

We help energy and utility companies replace or modernise legacy CIS, billing and meter data environments with MECOMS 365, a utility platform built on Microsoft Dynamics 365 and Azure. With more than 45 years of sector experience, we support the full transformation lifecycle:

  • Migration strategy: a practical roadmap and phasing plan tailored to your estate.
  • Data migration: cleansing, mapping, trial runs and reconciliation to protect billing accuracy.
  • Implementation: configuration, integration, testing and cutover through our implementation services.
  • Utility capabilities: an integrated customer information system, billing, meter-to-cash processes and meter data management in one platform.
  • Ongoing support: post-go-live assistance so your teams stay confident as the platform evolves.

Our solutions serve energy suppliers and utilities across electricity, gas, water and heat. Ready to compare routes with experts who know both worlds? Contact us and we will help you map a practical path away from SAP IS-U.

Veelgestelde vragen

How do I get started with planning an SAP IS-U replacement?

Begin with a discovery phase before you talk to vendors. Inventory your custom code, interfaces, tariffs and billing exceptions, then document the business outcomes you want, such as faster tariff launches or lower cost to serve. This gives you a factual baseline to test both S/4HANA and a dedicated CIS against your own scenarios, and it usually reveals how much of your customisation you actually still need.

How long does an SAP IS-U replacement typically take?

Timelines vary with the size of your customer base, the number of commodities and the amount of custom logic. Large S/4HANA transformations commonly run multiple years, while a phased cloud CIS rollout can deliver value in stages, often starting with one customer segment or commodity. Ask each vendor for a phased plan with clear milestones and reference projects of a similar size, and build contingency into your schedule for data cleansing and trial migrations.

What are the most common mistakes when migrating away from IS-U?

The biggest mistakes are starting data cleansing too late, trying to replicate every legacy customisation in the new system, and planning a single big-bang cutover with no rollback option. Another common error is underestimating testing, especially reconciliation of migrated data against real billing results. Challenge each legacy customisation and ask whether standard configuration or a simplified process can replace it.

What if we have limited time before IS-U maintenance ends?

Consider a phased approach rather than a full cutover. You can prioritise the segments, commodities or processes causing the most risk, migrate those first, and keep the remaining estate on the legacy system for a limited, planned period. Also check what extended maintenance or support options are available to you, and make sure any interim arrangement has a firm end date so it does not become a permanent workaround.

Can we keep our SAP ERP and still move to a dedicated CIS?

Yes. Many utilities keep SAP for finance, asset management and supply chain while moving customer, billing and meter data processes to a dedicated CIS. The two are connected through APIs, with the CIS passing financial postings and reporting data to the ERP. The key is to define clear system boundaries and data ownership early, so you avoid duplicated master data and unclear responsibilities.

How should we build the business case and compare total cost of ownership?

Model costs over a 10 to 15 year horizon rather than comparing initial licence prices. Include implementation, data migration, custom development, hosting or cloud consumption, specialist skills, upgrades and the cost of each future tariff or regulatory change. Then add the benefits side, such as faster time to market, fewer manual exceptions and lower support effort, so the comparison reflects both cost and business value.

How do we prepare our teams for the change?

Involve billing, customer service, finance, compliance and IT from the start, and nominate business owners for data quality and process decisions. Plan role-based training before go-live and keep experienced IS-U users involved in testing so they can validate that real-world scenarios work. After cutover, arrange hypercare support so teams stay confident while the new platform stabilises.

Gerelateerde artikelen