If you run SAP ECC 6.0 on Enhancement Packages 6 to 8, mainstream maintenance ends on 31 December 2027. You can pay for extended maintenance until the end of 2030, and a small group of large companies can use a RISE with SAP transition option until 2033. For most organisations, the real question is not whether to move to S/4HANA but how to move without disrupting finance, supply chain and payroll.
This article explains the dates, the options, what each costs you in risk and money, and a 12-month plan that gets you to a confident decision.
The dates that matter
| Date | What happens |
|---|---|
| 31 Dec 2025 | ECC on Enhancement Packages 0–5 left mainstream maintenance |
| 31 Dec 2027 | Mainstream maintenance ends for ECC 6.0 EhP 6–8 |
| 2028–2030 | Optional extended maintenance, at a higher fee |
| 2031–2033 | SAP ERP private edition transition option, only for selected RISE with SAP customers already on HANA |
| At least 2040 | Maintenance commitment for SAP S/4HANA on-premise |
SAP describes extended maintenance as available for an additional two percentage points on the maintenance fee, according to IBsolution. The 2033 option is not a general extension: Forrester notes SAP's CEO confirmed it does not prolong mainstream or extended maintenance.
What actually changes after 2027
Your system will not stop on 1 January 2028. What stops is the flow of new support packages, legal and tax changes, and full support coverage under mainstream terms. If you do not buy extended maintenance, you move to customer-specific maintenance, which offers problem analysis but no guaranteed new fixes, security patches or legal updates.
For finance and payroll, legal and tax updates are the biggest exposure. A statutory change you cannot patch becomes a manual workaround, and manual workarounds become audit findings.
Your four realistic options
| Option | Suits | Main risk |
|---|---|---|
| Move to S/4HANA now (brownfield, greenfield or selective) | Most ECC customers | Programme execution |
| Extended maintenance to 2030, then move | Companies needing time for a large programme | Cost and a compressed later deadline |
| RISE with SAP transition option to 2033 | Large, complex landscapes that qualify | Conditions, cost, lock-in |
| Third-party support or another ERP | Stable, low-change processes or a platform switch | No SAP legal updates; migration later anyway |
Brownfield, greenfield or selective?
Brownfield (system conversion) keeps your history and most processes and is usually the fastest route. Greenfield re-implements on SAP best practices and retires custom code, which suits companies whose processes need redesign. Selective data transition mixes both, and is common in mergers, carve-outs and consolidations. The right answer comes out of a readiness assessment of your system, not a slide.
Why waiting is expensive
Migrations of this size usually take 12 to 24 months once data cleansing, custom code, integrations, testing and training are included. Starting in 2027 leaves no room for a failed mock conversion or a delayed test cycle. Waiting also concentrates demand for experienced SAP people into the same period, which raises costs.
A 12-month plan to a confident decision
- Months 1–2: Readiness assessment. Run the SAP readiness check, custom code analysis and simplification item review. Inventory interfaces and data volumes.
- Months 2–3: Business case and approach. Compare brownfield, greenfield and selective options on cost, risk and timeline. Decide on hosting: RISE with SAP, a hyperscaler or on-premise.
- Months 3–5: Prepare. Archive old data, cleanse master data, retire unused custom code and fix open financial reconciliations.
- Months 4–6: Foundations. Set up landing zones and security for the target platform. Stand up the project team and governance.
- Months 6–12: First mock conversion and design. Run a sandbox conversion to find surprises early, then lock the realisation plan.
Throughout, keep ECC stable. An application management service that supports ECC while the programme runs protects month-end, payroll and customer service.
Key takeaways
- 31 December 2027 is firm for ECC mainstream maintenance; 2030 is a paid bridge, not a plan.
- The 2033 option applies only to selected RISE customers on HANA.
- Start with a readiness assessment; the approach decision follows from your system's facts.
- Keep ECC supported and stable while you move.