In brief:
For years, the SAP conversation has been shaped by dates. Upgrade regularly, and be ready when standard support is about to end. For many organisations that has felt less like advice and more like a countdown.
The question we put to clients is simpler: what does your business actually need from its ERP, and what would a change genuinely return? If you run a stable system that does its job and rarely needs attention, “support ends on a certain date” is not a business case. It is a deadline, and the two are not the same thing.
In July 2026, the European Commission made binding a set of commitments from SAP on how on-premise maintenance and support is sold and managed. It does not move a single lifecycle date. But it changes the commercial landscape around those dates, and that changes the conversation customers can have, with SAP, with their boards and with their own teams. This article sets out what actually changed, what didn’t, and how we think organisations should respond.
On 9 July 2026, the European Commission made legally binding a set of commitments offered by SAP, following a preliminary assessment it issued in September 2025. The measures took effect on 10 July 2026, apply to customers worldwide for ten years, and are monitored by an independent trustee. They apply to on-premise software licences and their maintenance and support; SAP’s cloud services sit outside them.
It is worth being precise about the nature of the decision. This was a commitments decision, not a finding of wrongdoing. The Commission’s preliminary concerns were about customers being unable to terminate support for licences they no longer needed, fees charged for returning to support after a gap, and repeated extensions of initial contract terms. SAP offered changes to address them, and the Commission accepted.
In practical terms, the main changes for customers are these:
The lifecycle dates are exactly where they were. Mainstream maintenance for ERP 6.0 (EHP 6 to 8) ends on 31 December 2027, with extended maintenance available to 31 December 2030 for an additional fee. Customers cannot now simply drop licences because they are unused: the termination routes are specific and bounded. And splitting a landscape is not free of conditions. Each resulting installation has to operate as a coherent entity in its own right, licences and systems have to line up, and additional licences may be needed. That last point is where much of the real complexity sits, and we return to it below.
Because these are contractual matters, any organisation acting on them should read the Commission’s published commitments and its own contract terms, and take legal advice. This article is general commentary, not legal advice.
The most useful distinction we can offer is between a support deadline and a transformation deadline.
A support deadline is the date a vendor stops providing standard maintenance for a product. A transformation deadline is the point at which your business needs to change its systems whatever the vendor does: because you are growing, acquiring, separating a business, entering new markets, facing new regulation, or want to do something with your data that your current platform cannot support.
The two sometimes coincide. Often they do not. The risk of treating them as one is that the vendor’s date drives the programme, rather than the business’s needs. Three questions help to separate them:
This is often where we start with clients. Separating the vendor’s date from the business’s own takes an honest look at how stable your platform is, how much of your support you actually use, and what you could get from the asset you already have. Our independent review is designed to do exactly that, and we say more under ‘How Helixr can help’ below.
For most SAP ECC customers, the realistic routes fall into four groups. For most SAP ECC customers, the realistic routes fall into four groups. Which one fits best depends on your business:
|
Route
|
Tends to fit when…
|
Watch out for…
|
|---|---|---|
|
1. Move to S/4HANA now |
The business case is already strong: you need capabilities ECC cannot provide, your estate is fragmented, or a transformation window is already open. |
Moving because of the date alone, scope creep, and underestimating data quality and clean-up. |
|
2. Move in phases |
Large or multi-entity estates, where different parts are ready at different times or carry different risk. |
Running two worlds in parallel, integration cost between them, and governance drag. |
|
3. Extend ECC strategically |
The core is stable and extra time would be used for genuine preparation: clean-up, standardisation, an acquisition, a separation. |
Extension as drift, the cost premium of extended maintenance, and the AI and innovation gap (see below). |
|
4. Selective exit or split |
Parts of the estate are stable and low-change, or are being divested, and could take different support arrangements. |
The conditions for splitting, the scope and quality of alternative support, and additional licence needs. |
The thread that runs through all four is integration. Whichever route you take, the question is what sits in the core and what connects to it. Increasingly, the best answer is a stable, well-governed core with specialist capability around it, connected cleanly. That is why we think of the options as stay, move, split, replace and integrate, not as a single choice between “upgrade” and “don’t”.
When a deadline does the persuading, the business case tends to become an afterthought. The commitments do not remove the deadline, but they loosen its grip, and they put the decision back where it belongs: in a comparison of what you spend and what you get.
That cuts both ways. Staying put is not automatically the cheap option. Security exposure, regulatory change, scarce skills, the premium on extended maintenance and the 2030 horizon are all real costs. But migrating because you were told to is not automatically sensible either. A simple test is to ask: would we be doing this programme if the date did not exist?
A credible business case for any route should be able to answer four questions:
If extra time on ECC is part of your plan, treat it as an investment in transformation capacity, not as a delay. The question to ask is what you will have done with the time by the end of it. If the answer is “the same thing, later”, the case is weak. If it is to clean up data, retire custom code, prepare for an acquisition, separate a business unit or build the integration layer you will need either way, that is a different proposition.
Behind the 2027 date sits a bigger question. Will SAP still be the architecture of choice for 2030 and beyond? And if you extend, are you buying time to see how fast-moving AI reshapes the ERP landscape over the next five years?
Nobody can answer that with confidence, and we would be wary of anyone who claims to. There are several plausible futures. In one, SAP remains the system of record and AI is layered on top of it. In another, the ERP core becomes thinner and more standardised, with specialist platforms and AI agents doing more of the work around it. In a third, AI coordinates across many systems, and the ERP becomes one source among several.
Our own view is that AI will change how people work with enterprise software more than it will replace it. But that is a view, not a certainty, and the sensible response to genuine uncertainty is not to bet on one outcome. It is to avoid decisions that only work in one of them.
There is a complication. While the European Commission’s decision provides organisations with greater flexibility in how they manage existing SAP environments, SAP has also indicated that access to some future AI capabilities may be linked to broader cloud commitments. The precise criteria and availability of these capabilities will continue to evolve, but the broader message is clear. Organisations now have more freedom in how they manage their on-premise ERP landscape, while future innovation is increasingly being developed within cloud-based platforms.
The effect is that two forces are pulling in opposite directions. Regulators have widened the choices available to on-premise customers, while SAP is tying some AI capability to cloud commitment. For customers weighing up an extension, that adds a cost to staying that did not exist a year ago, and it sharpens the question: are you buying time to learn, or time to avoid?
Buying time is a legitimate strategy, but only if the time is used on things that pay off whichever way the AI landscape develops:
An organisation with those foundations can adopt S/4HANA, a hybrid model or something quite different, and still be in a strong position. An organisation without them will struggle in every scenario.
The new flexibility rewards organisations that understand their landscape in detail. The most practical starting point is to look at your estate by capability or business area, and for each one ask whether it should be kept, converted, replaced or retired.
|
Decision
|
What it means
|
Typical candidates
|
|---|---|---|
|
Keep |
Leave as it is, with the right support model and light optimisation. |
Stable, low-change processes with a proven track record. |
|
Convert |
Move to a newer SAP platform, using a system conversion, a new implementation or a selective approach. |
Core processes where new capability is needed, or where the estate is due for consolidation. |
|
Replace |
Move the function to a specialist platform outside the SAP core. |
Areas where a specialist tool does the job better, or where SAP’s route is a poor fit. |
|
Retire |
Switch off processes, custom code or licences that no longer earn their keep. |
Unused modules, duplicated functions, legacy interfaces. |
How you carry out the move matters too. A system conversion (often called brownfield) keeps your existing configuration and data, and is typically faster but carries forward whatever is in the system today. A new implementation (greenfield) starts clean and demands more design effort. Selective approaches sit in between, for example moving some entities or data sets and not others. The right choice varies by part of the estate, and it is common for one organisation to use more than one.
This is also where the commitments meet reality. To split a landscape into separate Commercial Installations, each part must be able to operate as a coherent entity, with licences and systems aligned. In a heavily integrated estate, with shared data, shared interfaces and licences spread across many entities, drawing those boundaries is a serious piece of design work. It involves licence mapping, integration analysis, an understanding of shared data and processes, and, if support will come from more than one provider, clear accountability for each part. It also needs to be tested against the contract. Organisations that start this work early will be able to make choices; those that start late will have them made for them.
ERP advice is rarely neutral. Large integrators typically hold deep relationships with major vendors, with commercial incentives built into those relationships. That is not a criticism, simply how the business model works. But it means advice tends to lean towards whatever the vendor wants to promote, and when the vendor’s roadmap and the customer’s interest diverge, that is exactly when independent advice matters.
Helixr is an SAP partner. We are also a partner of other platform providers, and we are system-agnostic. That means we can tell a client when the right answer is S/4HANA, when it is to stay where they are, and when a different tool does a particular job better. Some organisations, for example, look to specialist platforms for functions such as labelling (Loftware), financial consolidation and planning (OneStream) or accounts payable and order-to-cash automation (Esker). These are examples, not recommendations: there are many alternatives in each area, and the right choice depends on the client.
We have seen this in practice. A global organisation we worked with assessed the SAP route for one of its core functions. Working through the options with them, they chose a different platform, and we helped implement it. The decision was theirs, based on a clear view of what each route would deliver, and that is exactly how it should work.
A decision of this size cuts across the organisation, and it goes wrong when it is left to a single function. The board or CEO owns the strategic direction. The CFO owns the return and the licence and contract position. The CIO owns the architecture and the delivery risk. The COO owns operational continuity. Procurement owns the commercial negotiation. If any of these voices is missing, the decision tends to be re-opened later.
We also recommend working with two plans, not one.
Keeping the two separate stops the near-term support question from dictating the long-term architecture, and the other way round. The roadmap between them is where the real work lies.
We can support at whichever stage you are:
A good starting point is a short, independent review and roadmap. It gives you a factual view of where you stand, and a set of options you can take to your leadership team with confidence.
The more complex your situation, the more this matters. Much of our work is in exactly the situations where a standard migration plan breaks down: multi-country rollouts for global brands, carve-outs and separations where a business unit has to leave with its own systems, integrating manufacturing sites under transitional service arrangements, and regulatory programmes such as electronic invoicing in highly specific markets. These are the projects where the quality of the design, the clarity of governance and the experience of the team make the difference between a plan and a delivered outcome.
If you would like help working through them, we would be happy to talk.
|
Question
|
If yes…
|
If no…
|
|---|---|---|
|
Is the core platform stable, with low change and few incidents? |
Staying, or a selective exit, is a credible option. Test the cost of support against what you really use. |
A move may be justified on capability and risk. Define what you need before choosing a route. |
|
Do you depend on SAP-delivered regulatory and legal updates? |
Keep SAP support for those parts, and be cautious about alternatives there. |
Alternative support for those parts may be worth evaluating. |
|
Do you have unused licences, modules or custom code? |
Review them for retirement, and check which contractual routes apply. |
Focus optimisation effort elsewhere. |
|
Are you planning an acquisition, divestiture or separation? |
Factor the new licence and split options into timing, and plan the design early. |
Less urgency; keep it under review. |
|
Do you have a clear AI and data strategy that depends on a specific platform route? |
Check how SAP’s cloud-linked AI conditions apply, and whether alternatives meet the need. |
Build the no-regret foundations first: data, processes and integration. |
|
Does your business case stand up without the 2027 date? |
Proceed, and plan the programme properly. |
Revisit scope, timing or route before committing spend. |
Neil has an astute eye for detail and excels at bringing teams together to deliver results. Always positive in outlook, he combines over 24 years experience in delivering complex business change solutions with natural people skills.
From experience in manufacturing, warehousing and logistics to delivering global ERP solutions, his wide-ranging knowledge combined with his calm, measured approach means he is adept at delivering solutions that work.
Through planning and due diligence to execution and stabilisation
Understanding the levers for successful integration
Expertly navigate the challenges and risks
Unpick the opportunities to drive the bottom line

Disentangling a well-established site from a complex corporate infrastructure-with stringent timelines, local compliance challenges, and a rigid transitional services agreement (TSA) in place.
Expertly navigate the challenges and risks.
Combining processes, systems and people to deliver maximum results
Working with what you've got to make things even better
Making your data work for you to deliver
real insight

How we streamlined and future-proofed, a soon-to-be obsolete labelling solution and a rapid client expansion across multiple new sites.
Enhancing decision making and strategic
alignment to drive performance
Using the latest technology to drive efficiencies, innovation and operational excellence
Meeting local requirements while
delivering smooth cross-border
operations
Simplifying supply chain finance
Improving compliance accuracy and
automation using tax technology