Yes, but not on its own. Standard Microsoft Dynamics 365 cannot replace SAP IS-U out of the box, because it lacks utility billing, meter data and market processes. A utility-specific solution built natively on Dynamics 365, such as MECOMS 365, can. For utilities planning an SAP IS-U replacement in 2026, the real question is which layer sits on top of the Microsoft foundation.
Below, we answer the questions that decision-makers ask most often, from why utilities are leaving SAP IS-U to how long the move takes and which risks to assess first.
Why are utilities moving away from SAP IS-U?
Utilities are moving away from SAP IS-U mainly because of rising maintenance costs, SAP’s announced end of mainstream maintenance timelines, a shrinking pool of specialist skills and difficulty supporting smart meters, prosumers and new tariff models. Staying put increasingly means paying more for less flexibility.
Beyond those headline drivers, several practical pressures push organisations towards an SAP IS-U migration:
- Heavy customisation: Decades of bespoke development make upgrades slow, risky and expensive.
- Skills scarcity: Experienced IS-U consultants and ABAP developers are harder to find and retain.
- Integration limits: Point-to-point interfaces struggle to connect with IoT platforms, smart meter data and modern customer channels.
- Customer expectations: Self-service, omnichannel engagement and faster product launches are difficult on rigid legacy architecture.
- Cost model: Cloud subscription pricing is more predictable than ongoing licence, hosting and specialist support costs.
Because SAP’s support timelines can change, always confirm the current dates directly with SAP and your implementation partner when building your business case.
What utility functionality is missing from standard Dynamics 365?
Standard Dynamics 365 lacks the utility-specific logic that energy and water companies depend on. It has no native meter data management, no consumption-based tariff engine, no market switching or settlement workflows, and no preconfigured regulatory processes. It provides a strong enterprise foundation, but not a ready-made utility CIS.
What Dynamics 365 does well is worth recognising. Its financial management, accounts receivable, customer service tooling, workflow automation through Power Automate, Azure scalability and enterprise security are all genuine strengths. The gaps appear where utility billing begins:
- Ingesting and validating smart meter interval data
- Calculating tariffs for consumption-based and multi-commodity pricing
- Handling estimated reads, meter replacements and retroactive billing adjustments
- Supporting switching, settlement messaging and market communications
- Managing prosumers, net metering and bi-directional energy flows
Building all of this through custom development is technically possible, but it is costly, hard to maintain across Microsoft updates and rarely matches the depth of a purpose-built solution.
How does a utility-specific layer on Dynamics 365 close the gap?
A utility-specific layer closes the gap by adding industry billing logic, meter data management and regulatory workflows directly onto the Dynamics 365 platform. Utilities keep Microsoft’s enterprise reliability and gain domain functionality from day one, without the cost and risk of custom development.
A well-designed layer typically includes:
- A tariff and pricing engine for consumption-based and multi-commodity billing
- Meter data management that validates, estimates and processes smart meter reads at scale
- Automated billing runs with management by exception, so teams review anomalies rather than every account
- Market integration for switching, settlement and regulatory reporting
- Preconfigured processes for electricity, gas, water and district heating
The architecture matters. A solution built natively on Dynamics 365 shares Microsoft’s release cycle, so platform updates do not break the utility layer. A solution connected through middleware can fall out of sync and require costly remediation. Certification under Microsoft’s ISV Connect programme is a useful signal of ongoing platform alignment.
What is the difference between SAP IS-U and a Dynamics 365-based CIS?
The key difference is architecture. SAP IS-U is a mature, heavily customised on-premise or hosted system within the SAP ERP landscape, while a Dynamics 365-based CIS is a cloud-native platform running on Microsoft Azure. This changes maintenance, integration, smart meter readiness and cost of ownership.
Comparing the two side by side:
- Maintenance: IS-U upgrades are projects in their own right. A native Dynamics 365 solution receives regular, managed cloud updates.
- Integration: IS-U often relies on brittle point-to-point interfaces. Dynamics 365 connects natively to the wider Microsoft and Azure ecosystem.
- Smart meter readiness: Many legacy billing designs were not built for interval data at volume. Azure-based platforms handle this by design.
- User experience: Legacy screens usually demand specialist training. Dynamics 365 offers a familiar, modern interface that shortens onboarding.
- Cost model: Legacy ownership carries high ongoing maintenance costs. Cloud platforms move towards predictable subscription pricing.
A modern utility customer information system also lets you keep existing Dynamics 365 finance or HR modules rather than replacing them, which avoids data silos and reduces integrations.
How do you migrate from SAP IS-U to Dynamics 365?
Migrating from SAP IS-U to Dynamics 365 is a phased programme covering strategy, data cleansing, mapping, configuration, parallel validation, testing and cutover. Data migration is usually the most critical workstream and should be planned well before technical go-live.
The main steps are:
- Define the migration strategy: Agree scope, commodities, markets, sequencing and the target operating model.
- Audit and cleanse data: Review customers, contracts, meter history and open balances, and remove duplicates and inconsistencies.
- Map legacy structures: Translate IS-U data models into the new platform’s structure, including tariffs and contract logic.
- Configure and integrate: Set up billing, market processes and interfaces with surrounding systems.
- Run parallel validation: Compare bill results between old and new platforms until accuracy is proven.
- Migrate in phases and cut over: Move data in waves to reduce risk, then switch with a clear fallback plan.
Each legacy environment brings its own extraction and transformation challenges, so choose a partner with proven tooling and experience in SAP IS-U specifically. Experienced implementation services make a measurable difference to risk.
How long does an SAP IS-U replacement usually take?
An SAP IS-U replacement typically takes from several months to a couple of years, depending on customer volume, number of commodities, market complexity and how heavily the legacy system has been customised. There is no universal timeline, so any estimate should come from a scoped assessment.
The factors that most influence duration are:
- Data quality and volume: Cleansing and reconciling decades of data often takes longer than expected.
- Customisation depth: Highly bespoke processes need more analysis and redesign.
- Scope: Single-commodity, single-market programmes move faster than multi-commodity, multi-country ones.
- Phasing approach: Migrating in waves lowers risk but extends the overall programme.
- Organisational readiness: Decision speed, resource availability and change management all affect pace.
Using a preconfigured utility solution instead of building billing logic from scratch usually shortens the path, because core processes are available from day one.
Which risks should be assessed before replacing SAP IS-U?
Before replacing SAP IS-U, assess data migration risk, regulatory and market compliance risk, billing accuracy, business continuity during cutover, vendor and architecture risk, and change management. These areas cause the most delays and cost overruns in utility CIS migration programmes.
Key areas to examine:
- Data migration: Meter history, open balances and contract structures can derail go-live if underestimated.
- Evaluating on ERP capabilities alone: Judging a platform by general ERP features rather than utility requirements hides the real gap.
- Regulatory updates: Check how the vendor handles market rule changes after go-live.
- Upgrade alignment: Confirm whether the solution is native to Dynamics 365 or loosely integrated.
- Billing continuity: Plan parallel runs, fallbacks and clear exception handling for the cutover period.
- People and process: Teams used to IS-U need training and clear ownership of new ways of working.
- Multi-jurisdiction needs: Ask vendors to demonstrate live references in each relevant market.
A useful exercise is to map your regulatory and operational requirements for the next five years against what your current platform can realistically deliver. The gaps usually make the timing decision straightforward.
How Ferranti helps with SAP IS-U replacement
We help energy and utility companies replace SAP IS-U and other legacy CIS and billing environments with MECOMS 365, a platform built natively on Microsoft Dynamics 365 and Azure. As a Microsoft premium ISV Connect partner, we combine Microsoft’s enterprise foundation with the utility depth you need from day one.
Here is what we bring to your migration:
- Integrated billing and CIS: A unified engine for complex tariffs, interval data and high-volume invoicing, without manual workarounds.
- Native meter data management: Smart meter ingestion, validation and processing that feeds billing directly, with no custom middleware.
- Management by exception: Automated workflows that flag anomalies so your teams focus on higher-value work.
- Cloud security and compliance: Enterprise-grade controls and audit logging on Azure, ready for evolving market rules.
- End-to-end migration support: Strategy, data migration, implementation, testing, cutover and ongoing support.
- Proven experience: More than 54 clients across over 18 countries, giving us the knowledge to manage complex migrations with minimal disruption.
If your current platform is creating the risks described above, we would be glad to help you understand your options. Contact us to start a conversation about what a move to MECOMS 365 could look like for your organisation.
Veelgestelde vragen
Where should we start if we're considering an SAP IS-U replacement?
Start with a scoped assessment rather than a vendor shortlist. Document your current IS-U customisations, commodities, markets, data volumes and integrations, then map your regulatory and operational needs for the next five years against what your platform can realistically deliver. This gives you a factual baseline for the business case, a realistic timeline estimate and a clear requirements list to test vendors against in demonstrations.
Can we keep our existing Dynamics 365 Finance or other Microsoft modules when we move to a Dynamics 365-based CIS?
Yes, and this is one of the main advantages of choosing a solution built natively on Dynamics 365. Existing finance, HR or customer service modules can stay in place and work alongside the utility layer, which avoids new data silos and reduces the number of custom interfaces. During evaluation, ask the vendor to show how the CIS shares data with your current Dynamics 365 modules.
How do we make sure billing stays accurate during the cutover?
Run parallel billing, where bills are calculated on both the old and new platforms and the results compared until differences are explained and resolved. Define acceptance thresholds in advance, such as the percentage of accounts that must match, and agree a documented fallback plan if issues appear after go-live. Migrating in waves also limits the number of customers affected by any problem.
What data cleansing should we do before migrating from SAP IS-U?
Focus first on duplicate customers and premises, inconsistent or missing meter history, incomplete contract and tariff assignments, and unreconciled open balances. Agree which historical data must be migrated and which can be archived, because moving less data usually lowers risk and effort. Start cleansing early, ideally before configuration begins, since it often takes longer than expected.
What questions should we ask a vendor to confirm their solution is truly native to Dynamics 365?
Ask whether the utility logic runs inside the Dynamics 365 and Azure platform or connects through external middleware, and how the vendor handles Microsoft’s regular release waves. Request evidence of Microsoft ISV Connect certification, a clear update policy and live customer references that have already gone through several platform updates. If the answers rely on custom connectors or separate databases, expect higher remediation costs later.
How do we prepare our IS-U team for the change?
Involve key IS-U users early as process owners and testers so their domain knowledge shapes the new design. Plan role-based training before cutover and keep experienced staff available for hypercare after go-live. Because Dynamics 365 uses a familiar Microsoft interface, onboarding is typically quicker, but teams still need clear ownership of new workflows such as management by exception.
Should we migrate all commodities and markets at once or in phases?
In most cases a phased approach is safer, for example starting with one commodity, region or customer segment and then migrating further waves. Phasing lowers risk and lets you refine data mapping and processes, although it extends the overall programme and means running two systems for longer. A big-bang approach can suit smaller, single-commodity utilities with clean data and strong testing capacity.
Gerelateerde artikelen
- What is the ROI of moving to a cloud utility CIS?
- How can utilities reduce vendor lock-in when replacing their CIS?
- Why is software integration so difficult for energy suppliers?
- What is the total cost of ownership of a legacy billing system in the energy sector?
- How do you improve utility billing accuracy with smart meters?
- Which mistakes do energy companies make when switching to a new billing system?
- How do you scale utility billing operations across multiple markets?
- Which billing models are most commonly used by energy suppliers?
- What is a meter data management system and why does it matter for billing?
- Can billing software handle multiple energy commodities at the same time?
- Is Dynamics 365 suitable for utility billing out of the box?
- How do you implement CIS utility software?
- How do you minimize disruption during a CIS rollout?
- How does a CIS support self-service portals for energy customers?
- What are the benefits of CIS utility software?