SAP ECC End of Support 2027: Options, Costs and Timelines
Mainstream maintenance for SAP ECC 6.0 ends on 31 December 2027. ECC keeps running, but what SAP covers shrinks step by step until 2030, when database, Java and conversion support end as well. This guide sets out the real dates, the five options and what each means for the finance function.
The dates that matter
At the end of 2024 only 39% of SAP's roughly 35,000 ECC customers had licensed S/4HANA, according to Gartner figures reported by The Register, and half of the German-speaking user group DSAG expects to run ECC past 2027. A full migration typically takes 18 to 36 months, so for many companies the question is no longer whether to bridge, but how.
| Date | What happens |
|---|---|
| 31 Dec 2025 | Mainstream maintenance ended for ECC 6.0 on enhancement packages 0 to 5; these releases are in customer-specific maintenance. |
| 31 Dec 2027 | Mainstream maintenance ends for ECC 6.0 on EHP 6 to 8 and the other Business Suite 7 core applications. Extended maintenance must be chosen by the end of 2027, otherwise the system moves to customer-specific maintenance. |
| 2028 – 2030 | Optional extended maintenance at a premium of two percentage points on the maintenance basis. |
| 31 Dec 2030 | Extended maintenance ends. SAP's reselling and support agreements with third-party database vendors end, NetWeaver AS Java 7.5 support ends, and conversion tooling for Business Suite 7 on a non-SAP database is withdrawn: after that, only greenfield transitions are supported. |
| 2031 – 2033 (up to 2035) | SAP ERP, private edition, transition option: a cloud subscription for large, complex landscapes that moved to SAP ERP, private edition on SAP HANA before the end of 2030. In October 2026 SAP extended the possible term to 31 December 2035, with further prerequisites. |
What actually stops in 2027 and 2030
Nothing switches off. The risk is gradual: each phase covers less, and the customer carries more operational and compliance risk.
- Mainstream maintenance (to 2027): fixes, security patches, legal and regulatory updates.
- Extended maintenance (2028–2030): similar scope for EHP 6 to 8, at a higher fee and with possible technical limitations.
- Customer-specific maintenance: help on known problems, but no new legal changes and new issues may be charged as consulting. For finance this is the critical point: a new VAT rule, an e-invoicing mandate or a change to statutory reporting will not arrive as a standard update.
The 2030 database and Java cut-off matters even for companies planning to stay on ECC: a system on Oracle, IBM Db2 or Microsoft SQL Server loses SAP's end-to-end database support, and a later conversion to S/4HANA is no longer possible from that database.
Five options after 2027
| Option | Best for | Watch out for |
|---|---|---|
| 1. Migrate to SAP S/4HANA or SAP Cloud ERP (greenfield, brownfield or selective) | Companies that want to modernise processes and use the new finance and AI capabilities | 18–36 months; scarce consultants as the deadlines approach; data quality |
| 2. Extended maintenance as a bridge to 2030 | Companies with a migration plan that cannot finish by 2027 | Higher fee; must be chosen in time; the 2030 end date is firm for on-premise systems |
| 3. SAP ERP, private edition and the transition option | Large, complex landscapes that cannot finish by 2030 | Move to SAP HANA and private edition before end-2030; minimum size, readiness checks and a paid success plan; price uplift depends on when you sign |
| 4. Third-party support | Stable systems with few planned changes | Off SAP's roadmap; legal updates depend on the provider; the 2030 database and conversion constraints still apply |
| 5. Change ERP platform | Companies whose ECC no longer fits the business model | A full re-implementation; same timeline pressure |
Two practical bridges are often overlooked by finance teams:
- SAP Central Finance: replicating ECC postings into an S/4HANA finance system gives group reporting, IFRS 18 layouts and new analytics before the operational ECC systems are migrated.
- Separating the decisions: covering the maintenance gap with a bridge and negotiating the migration on a calm timeline, instead of signing under deadline pressure.
What it means for finance
An ECC migration is often run as an IT project, but most of the design decisions land in finance:
- Universal Journal: FI and CO merge into one table (ACDOCA), which changes reconciliation, reporting and the close.
- Ledgers and parallel accounting: the choice between ledger and account approaches for IFRS and local GAAP, and whether to activate document splitting.
- New Asset Accounting: mandatory in S/4HANA, with depreciation areas mapped to ledgers.
- Business Partner: customers and suppliers become business partners (CVI): a master data project in its own right.
- Accounts payable add-ons: solutions such as SAP VIM run on both ECC and S/4HANA, but the migration is the moment to review VIM version, workflow and approval rules, and to move approvers to Fiori.
- Regulatory timing: IFRS 18 applies from 2027 and ViDA e-invoicing from July 2030. Delivering them twice, once on ECC and again on S/4HANA, is the most expensive path.
Planning backwards from 2030
With 18 to 36 months of delivery, a programme that must be live before the end of 2030 needs its decision in 2027 and its start no later than 2028. A practical sequence:
- Now: confirm release, enhancement package and database; inventory every SAP system (ECC, CRM, SRM, SCM); check contract and maintenance terms.
- Within 6 months: run a phase zero: business case, Readiness Check, custom code and data assessment, transition approach.
- By end-2027: decide extended maintenance or another bridge, and sign the migration on terms you have modelled.
- 2028 – 2030: deliver the migration along the S/4HANA implementation roadmap, aligned with IFRS 18 and e-invoicing deadlines.
Sources
- SAPinsider: SAP support deadlines 2027, 2030 and 2033
- SAPinsider: SAP sets 2030 cutoff for third-party database and Java support
- ERP Today: SAP extends ERP private edition transition option to 2035 (November 2026)
- Constellation Research: SAP ERP, private edition, transition option
- The Register: only 39% of 35,000 ECC customers had licensed S/4HANA at the end of 2024
- The Register: half of German-speaking SAP users set to run past the 2027 deadline
- Panorama Consulting: 18 to 36 months for a full S/4HANA migration
- eCorp IT: SAP ECC end of maintenance 2027, summary of SAP's October 2026 announcements
- Eursap: what customer-specific maintenance does and does not cover
SAP's terms change often and some conditions sit in SAP Notes that require a login (for example SAP Note 3591251). Check your contract and the current SAP documentation before deciding.
Deciding what to do with ECC?
Our founder has worked on SAP ECC and S/4HANA Finance since 2014, from ECC roll-outs to S/4HANA implementations and Central Finance. We help you choose the path and plan it around your finance deadlines. See selected projects.
Get in touchIn italiano
Questa guida è disponibile anche in italiano: Fine manutenzione SAP ECC 2027: opzioni, costi e tempi.