The 2027 ECC deadline — what it actually means for your plan
SAP ends mainstream ECC maintenance on 31 December 2027. What each date actually obliges you to do, and how to work backwards to a start date.
Written by APx Technology
Two dates get quoted constantly in SAP conversations, usually without much precision about what either one actually requires. Here is the distinction, and what it means for scheduling.
The dates
31 December 2027 — mainstream maintenance ends for SAP Business Suite 7, including ECC 6.0. After this point you no longer receive the standard level of support, and SAP has signalled no further functional updates to ECC.
End of 2030 — extended maintenance ends. This is available at additional cost, and eligibility carries conditions, including in some cases holding a RISE with SAP contract and running on HANA.
Neither date switches your system off. ECC will keep running on 1 January 2028 exactly as it did the day before. What changes is your support position, your compliance exposure, and your access to fixes — including security fixes.
Why 2030 is the wrong date to plan to
It is tempting to treat 2030 as the real deadline and 2027 as a soft one. Three reasons that backfires.
Extended maintenance is a cost, not a reprieve. You pay a premium for a system receiving no functional improvement, while competitors invest the same money in capability.
Eligibility has conditions. Extended maintenance is not automatic and the terms attached to it may themselves require work you have not scheduled.
The resource market does not wait. The scarcity problem peaks well before any deadline. Everyone who left it late is competing for the same consultants in the same window.
Work backwards from the duration
The scheduling maths is the part worth taking seriously.
A focused brownfield conversion on a single, well-understood landscape can complete in six to nine months. A multi-entity programme with significant custom code, heavy integration and a greenfield process redesign commonly runs eighteen to thirty-six months once data, testing and change management are included.
Take the longer figure. Work backwards from December 2027. Add a quarter for procurement and partner selection, which almost nobody includes in their estimate.
The window for starting a large programme comfortably has effectively closed. For a mid-sized one it is closing now. Industry estimates still place well over half of ECC customers at the pre-start stage, which is the part that should concern anyone planning to start late — because that is the cohort you will be competing with for people.
What to do in the next ninety days
You do not need a full programme approved to make progress. You need enough evidence to make the decision defensible.
Run SAP Readiness Check against production. It is free, it takes days rather than weeks, and it produces the simplification item list and custom code inventory that every subsequent estimate depends on.
Inventory your custom code properly. Use ABAP Test Cockpit and the Custom Code Migration app. Most landscapes discover a meaningful share of their Z-objects have not executed in years and can simply be retired — which is the cheapest scope reduction available.
Map your integrations. Every interface in and out, with an owner against each. This is routinely the most underestimated part of a conversion.
Decide the deployment question. On-premise, private cloud under RISE, or public cloud. It changes the shape of everything downstream, so deciding it late forces rework.
Get a costed plan. Not a vendor estimate built from a discovery call — a plan based on your actual readiness output.
The honest summary
If you have not started, you are not unusual. But the organisations that move in the next two quarters will run calmer projects with better people at better rates than those that start in 2027, and the gap between those two experiences is considerable.
The first step is cheap and gives you real information. There is no good argument for delaying it.