SAP ECC ends in 2027: what to do with everything you built around it
By Xavier Franco, CEO de Elternativa · Grupo Zemsania
· 7 min read
Written with the help of AI and reviewed by Xavier Franco

In this article
If your company runs SAP ECC, you have probably had this conversation more than once: 2027 is just around the corner, you have to go to S/4HANA, and nobody quite knows what to do with everything that has been built around it over twenty years. I think the question is framed wrongly. The challenge is not the core: it is what sits on top of it. Let me tell you why, and how I would approach it.
The dates, as SAP has given them
It is worth starting with what is certain. In February 2020, SAP announced that it would provide standard maintenance for the core applications of SAP Business Suite 7, which includes ECC, until the end of 2027. From 2028 until the end of 2030, extended maintenance can be purchased, with a surcharge of two percentage points on the maintenance base. And for S/4HANA, the commitment runs to 2040.
In January 2025, SAP added a transition option between 2031 and the end of 2033 for very large and complex customers who sign a cloud migration agreement. But it made clear that this was not an extension: the end of standard maintenance in 2027 does not change.
So the question is not whether you need to move, but how and with what.
In practice: note the date on which your maintenance contract expires and how much the extended-maintenance surcharge would amount to. It is the figure you will compare everything else against.
The core stays
I will start with what does not change, because it is reassuring. Finance, controlling, purchasing and sales (FI, CO, MM and SD) are the heart of SAP and will stay in SAP. The conversion to S/4HANA is done by SAP or its partner. I am not proposing that you change ERP or migrate the core.
What I do propose is to take a calm look at what is around it: the Z transactions and applications, the exits and BAdIs, the ABAP reports, the batch processes, the screens and portals for users who only look things up. That is where the real work is, and also the opportunity.
The problem of the Z layer in S/4HANA
S/4HANA comes with an idea that SAP calls clean core: keeping the core clean, standard and ready to be updated without pain. According to SAP, extensions go outside the core, in BTP, or inside it with the new ABAP Cloud model. The classic Z layer, with its modifications and its exits from twenty years ago, does not fit that model. It has to be emptied before converting.
And here comes the most common temptation: taking everything to BTP, SAP's extension platform, because «that is what you do». BTP can be a good option for some pieces. But it is also paid for, in credits. If you take everything without thinking, you pay again for what you had already built.
My position is simple: BTP is an option, not an obligation. Each piece has to go where it adds the most value.
In practice: ask your SAP team for the list of Z developments and, for each one, whether it has been used in the last year. You will be surprised how many are there just in case.
Piece by piece: what stays, what moves out and what gets switched off
When you take an inventory of what has been built on a SAP system, each piece has one of three destinations:
- It gets switched off. What nobody uses is not migrated. It is the quickest saving and the one with the least risk.
- It moves out. Z transactions and apps can become your own application that talks to SAP through OData, BAPI or IDoc, with the same look and the same security. Batch jobs and ABAP reports can go to your data platform and your dashboards. Extensions go to BTP if you choose, or to your own code, with no credits.
- It stays, if it really has to live inside SAP.
The result is a cleaner SAP, cheaper to maintain and easier to take to S/4HANA. And a part of your business that stops depending on a single vendor.
I say this without being against anyone. SAP remains the core, and done well. What I defend is being able to choose each piece for its value, not out of obligation or habit.
In practice: separate your Z objects into three columns (switched off, moves out, stays) before asking for a conversion quote. It will change the size of the project.
No big bang
Converting a SAP system is delicate enough without adding a big cutover of everything else. That is why what is around it moves piece by piece: each new application or report coexists with the old one and replaces it when it gives the same result with real data. No nail-biting weekend.
What waiting costs
Some companies consider stretching ECC with extended maintenance while they decide. It is a legitimate option, but it is worth knowing what it costs. According to SAP, extended maintenance from 2028 to 2030 carries a surcharge of two percentage points on the maintenance base. And the transition option between 2031 and 2033 is only intended for very large customers who sign a cloud migration agreement.
But the cost of waiting is not only the surcharge. Every year that passes, the Z layer grows a little more, the people who know it are a year closer to leaving, and the conversion gets bigger. And in the meantime you keep paying for screens and portals that are often used only by people who look things up.
That is why my advice is to separate the two decisions. When to convert the core is a decision with SAP and its partner. What to do with what is around it is yours, and you can start today, without waiting for the other. Emptying the Z layer first reduces the risk and the size of the conversion, whatever you decide about the dates.
In practice: put on one sheet the annual cost of your maintenance, the surcharge for extended maintenance and the number of Z developments. They are the three figures your management committee will ask you for.
Where to start
- A read-only inventory of everything built on SAP: what exists, who uses it and which core data it depends on.
- A piece-by-piece verdict: it stays, moves out or gets switched off, with its destination.
- Switch off what is not used, now.
- Move out first what weighs the most, in use or in cost, and validate parity with real data.
- Arrive at the conversion with a Z layer already emptied and a smaller project.
There are a little over twelve months left until the end of 2027. It is enough time if you start with the inventory and not with the tool.
How we help
At ERP and CRM Migration we do not migrate the core: we migrate what has been built on top of SAP, Salesforce, Dynamics 365, Oracle or ServiceNow. On SAP, we empty the Z layer before the conversion and take each piece to the destination you choose (your own application connected through an API, your data platform, your dashboards or BTP), piece by piece and with measured parity.
We do it with the Datagentis migration module: it connects read-only, inventories what you have, flags what is not used and what has a licence impact, and generates the documentation and the plan before anything is moved.
Do you know how many of your Z developments are really used?
In a demo we show you how we take a read-only inventory of what has been built on your SAP and decide, piece by piece, what stays, what moves out and what gets switched off.


