ERP modernization for utilities is increasingly mischaracterized as a platform choice: S/4HANA versus alternatives, Rise versus on-prem, Brownfield, Bluefield or Greenfield. Platform decisions matter, but they are not where programs succeed or fail. The decisive variable is whether leadership treats modernization as a governance and operating-model problem or as a “technology upgrade” executed by IT.
The forcing function is plain: ECC’s post-2027 support trajectory is too risky for utilities running core processes on an aging platform. But operations have also changed. Distributed energy resources (DERs), bidirectional energy flows, dynamic pricing pressures and the emerging “prosumer” model are pushing utilities to modernize.
The grid and the customer relationship have become more dynamic. This means utilities need real-time orchestration across both customer operations and electrical grid interfaces.
Make the “Loss of Control” Explicit and Early
Many utilities are contemplating moving their ECC environments to RISE due to SAP’s strong push and contract incentives. One of the least discussed consequences of moving from on-prem to a managed cloud service is the loss of unilateral control. Historically, utilities avoided downtime during storm season by simply not upgrading. In a managed model, upgrades must be orchestrated on a set cadence with SAP to limit operational risk. The upgrade cadence is not a minor sustainment detail; it is a first-order design input that should influence resilience architecture, release management and business continuity planning from day one.
Utilities that internalize this early design – including the move from on-prem to managed services – differently are better positioned for successful modernization. Some examples are incorporating contingency constructs that enable outage and call-center operations to continue during upgrade windows and adopting a sustainment model that plans further ahead than many legacy IT organizations are accustomed to.
Retire the Myth: “Bluefield Makes Transformation Easier”
A Bluefield strategy can reduce certain migration risks by facilitating the retirement of old customizations, enabling newer features, and more easily utilizing AI capabilities within Joule in the long run. However, it does not completely remove the transformation burden of moving from ECC to S/4HANA in the modern SAP delivery model. User interface changes and replacement of ECC functionality with updated features require justification, control, and change management. Clean-core principles are enforced by platform mechanics, not just by policy. The practical outcome is that migration strategy is not the same as transformation strategy. Assuming they are equivalent, leads programs to underfund change management, data work, and cross-functional decision-making.
The Underused Lever: Design Authority before SI Contracting
A structural cost driver in large utility transformations is unresolved “big rock” decision-making during SI selection and contracting. When core architectural and application decisions are not made, such as what is replaced, what consolidates into SAP, what remains outside, and what customer engagement and reporting patterns look like, system integrators price uncertainty. That is rational behavior, and utilities pay for it.
A more disciplined pattern is to establish a holistic solution design first, often with a Phase 0 initiative that produces a high-level design and roadmap and then procure implementation against that design. This does not eliminate unknowns, since business buy-in can still constrain replacement decisions, but it materially reduces ambiguity, improves commercial leverage, and prevents schedule optimism that collapses once the program hits genuine architectural forks.
“Modern Digital Core” Is an Economic Statement about Integration, Not a Feature Checklist
Utilities have lived the cost of composable ERP implemented as an ecosystem of systems stitched together via asynchronous or batch interfaces: reconciliation overhead, duplicated reporting maintenance, manual workarounds, and slow change velocity driven by customization and technical debt. Modernization is the opportunity to reverse that integration tax by consolidating what belongs together and governing extensions properly.
A pragmatic boundary is clear:
Keep finance, controlling, procurement, asset management, and master data in the core; moving them out is typically an efficiency loss.
Implement customer engagement with cloud capabilities that have out-of-the-box integration patterns.
Put extensions and integrations in a governed platform layer (e.g., BTP) to preserve clean core, rather than modifying the core itself.
Clean core is not dogma. It is the only sustainable mechanism for absorbing SAP’s innovation stream, especially as AI capabilities expand, while avoiding the need to rebuild the fragile, client-specific ERP patterns that utilities are trying to exit.
Real-time Is Selective and the Selection Is the Architecture
Utilities do not need real time everywhere. They need it where the grid and customer relationship now demand it: customer interactions across channels, grid monitoring interfaces, DER applications, and pricing signals (including real-time pricing and tariff-driven calculations). Finance period end closing and much of HR remain largely batch oriented. The point is not technical; it is about governance. Organizations must decide where real-time is necessary and design their integration and data quality strategies accordingly, instead of treating "real time" as a generic program slogan.
The Two Governance Gaps that Quietly Derail Programs
First, data governance. Utilities often discover that their data is less clean than assumed, and that a business-led stewardship model must be formed to standardize data into the formats required by clean-core operations and compliance expectations. This includes customer, product, vendor, and asset data. Often overlooked is the need to rationalize and standardize GIS, especially when multiple systems are present.
Second, AI governance. The practical boundary is straightforward: automate deterministic alerts; keep strategic decisions augmented. What is missing in many organizations is a clear governance model that defines which AI capabilities currently exist, what new ones are on the horizon, and how utility data is used to support these models, rather than defaulting to blanket rejection due to uncertainty.
What Utilities Leaders Should Consider
Utility SAP modernization will not be won by picking the “right” migration flavor or repeating generic cloud narratives. It will be won by leaders who govern the digital core under shifting control: deciding early how the organization will operate with managed upgrade cadence, enforcing clean core as an executive policy, sequencing transformation where change is real (customer and asset, not just ERP screens), and establishing business-led data and AI governance that can sustain continuous evolution without destabilizing operations.
Read the ISG State of SAP Migration Report here.
About the authors
Sandip Tarafdar
Jon Brock
