Pieter BangelsSAP for Utilities TheValueChain logo

Insights · Transformation

Five misconceptions about moving from SAP IS-U to S/4HANA Utilities

The move from IS-U to S/4HANA Utilities is not a technical upgrade. These are the five assumptions I see most often in utility projects, and what to do instead.

Most European utilities still run their customer and billing processes on SAP IS-U on ECC 6.0. The move to S/4HANA Utilities is on every roadmap. In conversations with utilities, the same five assumptions keep coming back.

1. "It is mainly a technical upgrade"

S/4HANA changes more than the database. Business partner becomes the single master data object for customers, and the simplification list contains items that touch utility processes directly. Treat the move as a business project with a technical component, not the other way around.

2. "Our custom code will simply move along"

Twenty years of IS-U usually means a lot of custom code in billing, invoicing and market communication. Some of it is no longer needed, some of it breaks, and some of it should move out of the core. Run a custom code analysis early and decide per object: retire, adapt or rebuild outside the core.

3. "We will start once the market rules settle down"

Market processes in the Benelux and the rest of Europe keep changing. Waiting for a quiet period means waiting forever. Build your migration plan so that market changes can be absorbed along the way.

4. "Greenfield means losing our history"

A new implementation does not have to mean starting from zero. Selective data transition lets you combine a redesigned process landscape with the historical data you really need. The right answer depends on how much of your current design still fits.

5. "Billing will look after itself"

Billing is where customers notice every mistake. Plan parallel billing runs that compare results between the old and the new system, for every rate category that matters. Start testing billing early, not in the last month before go-live.

What to do next

Start with an honest assessment of your current IS-U landscape: custom code, data quality and the processes that differ from the standard. That assessment decides your migration path, not the other way around.

Want to discuss your situation? Get in touch.