Utilities running SAP IS-U on ECC have to decide how they will get to SAP S/4HANA Utilities. The question usually arrives as "brownfield or greenfield", but there are three paths, and the right one depends less on preference than on what is already in your system: how much custom billing code you carry, how clean your master data is, and how much process change the business is ready for.
SAP publishes maintenance dates for ECC-based releases and the options for extending them. Check the dates that apply to your release and contract with SAP directly, and plan backwards from them.
System conversion (brownfield)
A system conversion takes your existing ECC IS-U system to S/4HANA Utilities in place. Configuration, custom code and history come with it. Billing documents, contract accounts and device history stay where they are, which is often the deciding factor for a utility with years of consumption history and open receivables.
The cost is that you also bring your problems. Billing schemas, custom function modules and enhancements that should have been retired come along unless you deal with them during the project. A conversion is also a technical project with its own prerequisites, including the database move to SAP HANA and customer/vendor integration with the business partner for FI customers and vendors.
New implementation (greenfield)
A greenfield project builds a new S/4HANA Utilities system and loads data into it. It is the cleanest way to drop old customizations and adopt standard processes, and it lets you redesign rate structures and billing processes that no longer fit.
It also means migrating utilities master and transaction data: business partners, contract accounts, connection objects, premises, installations, devices, meter reading results, and open items in FI-CA. Billing history is usually summarized or kept in an archive rather than moved in full. Plan for repeated mock loads and a long reconciliation phase.
Selective data transition
A selective data transition builds a new target system shell and moves a chosen subset of configuration and data, for example by company code or by time slice. It can keep the history you need while leaving behind what you don't. It depends on specialist tools and services, so it is worth scoping with whoever will provide them early.
What to check in your own system first
- Run the SAP Readiness Check for S/4HANA against a copy of production, and read the simplification items for utilities that apply to your target release.
- Inventory custom billing code: variant programs, function modules in billing schemas, user exits and enhancements. Mark each one keep, rebuild or retire.
- Profile master data: business partners without contract accounts, devices without installations, open items with no owner. These turn into load errors in a greenfield and into defects in a conversion.
- List every interface around IS-U, including meter data management, bill print, payment providers, the portal and the contact center, and note which ones will change.
- Decide how you will prove billing parity: which portions, which rate categories, and what difference counts as acceptable.
How billing parity gets proven
Whatever the path, the business will judge the project on whether bills are right after go-live. The practical way to show it is billing parallel runs: bill the same portions in the old and the new system, compare the results line by line, and explain every difference before cutover sign-off. Start these early. The differences they find are often design decisions nobody wrote down.
A note on scope
The utilities-specific workstreams (billing, devices, FI-CA and data migration) are often a small part of a larger S/4HANA program, but billing errors are the ones customers see. If a system integrator is leading the program, it is reasonable to ask who will own those workstreams and what they have done on IS-U before.