For thousands of European companies, SAP ECC 6.0 is still the system that runs finance, procurement, manufacturing and logistics. On 31 December 2027, SAP’s mainstream maintenance for SAP ERP 6.0 and the core Business Suite 7 applications ends. That is now less than 14 months away.
The deadline does not switch systems off, but it changes the cost, the risk and the regulatory exposure of staying put. This guide sets out the dates, what each support phase includes, the options available and how to decide between them. It reflects SAP’s published policy as checked on 7 November 2026.
Key takeaways
- 31 Dec 2027: mainstream maintenance ends for SAP ERP 6.0 (enhancement packages 6 to 8) and core Business Suite 7 applications.
- 2028–2030: optional extended maintenance is available for a premium of two percentage points on the maintenance basis.
- 2031–2033: an ERP private edition transition option is available only to customers that move to SAP’s private cloud by the end of 2030 and meet other conditions.
- After support ends: customer-specific maintenance gives limited help and generally no new legal or regulatory updates, a serious issue as e-invoicing mandates spread across Europe.
- The real choice is between migrating to S/4HANA (on-premise, RISE or GROW), buying time with extended or third-party support, or moving to another ERP.
In this guide
The key dates
| Date | What happens |
|---|---|
| End of 2025 | Mainstream maintenance ended for older ERP 6.0 enhancement packages (EHP 0 to 5) |
| 31 December 2027 | Mainstream maintenance ends for SAP ERP 6.0 EHP 6 to 8 and core Business Suite 7 applications (CRM 7.0, SCM 7.0, SRM 7.0) |
| 1 Jan 2028 – 31 Dec 2030 | Optional extended maintenance, at an additional two percentage points on the maintenance basis |
| By 31 December 2030 | Deadline to move to SAP ERP, private edition, to qualify for the transition option |
| 2031 – 2033 | ERP private edition transition option: a paid subscription allowing continued use of ECC-based processes in SAP’s private cloud |
| Until at least 2040 | SAP’s stated maintenance commitment for S/4HANA |
What each support phase means
| Phase | Fixes and patches | Legal and regulatory updates | Cost |
|---|---|---|---|
| Mainstream (to end 2027) | Yes | Yes, within SAP’s standard scope | Standard maintenance fee |
| Extended (2028–2030) | Yes | Yes, within SAP’s standard scope | Standard fee plus 2 percentage points |
| Customer-specific (after support ends) | Only existing fixes; new problems solved case by case, often at extra cost | Generally no | Standard fee, with limited value |
| Transition option (2031–2033) | As defined in the subscription | As defined in the subscription | Subscription, with a published 20% uplift for customers signing in 2026; terms for later sign-ups not yet disclosed |
The transition option comes with conditions. According to SAPinsider’s analysis of SAP’s terms, customers must move to SAP ERP, private edition, on SAP HANA before 31 December 2030, take SAP’s separately priced “max success” plan, and check coverage of CRM, SCM and SRM components against the relevant SAP note. It is designed as a bridge for large customers already committed to RISE, not as a general extension.
Why regulation makes 2027 matter more
The biggest risk of staying on an unsupported ECC system is not technical; it is regulatory. Between 2026 and 2030, European tax authorities are rolling out the most significant changes to invoicing and VAT reporting in decades:
- Germany: mandatory B2B e-invoice issuing from 1 January 2027 for larger businesses and from 2028 for all. See our Germany guide.
- France: e-invoicing and e-reporting through approved platforms since September 2026, with SMEs following in 2027. See our France guide.
- Spain: B2B e-invoicing from October 2027.
- United Kingdom: mandatory e-invoicing from April 2029.
- EU-wide: ViDA digital reporting for intra-EU trade from July 2030.
Most of these changes need updates to the ERP’s invoicing, tax and reporting logic. Under customer-specific maintenance, those updates generally stop coming from SAP. Companies then either build them themselves, rely on a third-party provider or bolt on external e-invoicing tools. All three are possible, but each adds cost and risk. For the full picture, see our European e-invoicing mandates guide.
Your options compared
| Option | Advantages | Disadvantages | Best for |
|---|---|---|---|
| Migrate to S/4HANA on-premise | Full control; supported to at least 2040; reuse of existing licences may be possible | Significant project; you run the infrastructure; SAP’s newest innovations increasingly target cloud editions | Organisations with strong internal IT and data-residency requirements |
| RISE with SAP (S/4HANA private cloud) | One contract for software, infrastructure and services; access to the transition option; SAP’s strategic path | Subscription cost; less flexibility to change providers; contract terms need careful negotiation | Large, complex enterprises |
| GROW with SAP (S/4HANA public cloud) | Standardised processes; continuous updates; faster implementation | Limited customisation; may not fit highly bespoke processes | Mid-sized companies willing to adopt standard processes |
| Extended maintenance to 2030 | Buys three years; keeps SAP support and legal updates | Higher fees; still requires a migration later | Companies whose migration is planned but will not finish by 2027 |
| Third-party support | Lower annual fees; support for customised code; can extend ECC life well beyond 2030 | No new SAP product releases; you depend on the provider for regulatory changes; may complicate a later return to SAP | Stable systems with low change needs and a clear exit plan |
| Move to another ERP (e.g. Microsoft Dynamics 365, Oracle, Infor, Odoo) | Chance to reassess cost and fit; modern cloud platforms | Full re-implementation; data migration and retraining risk | Companies where SAP is oversized or poorly aligned with the business |
S/4HANA migration approaches
- Greenfield (new implementation): start with a clean system and standard processes, migrating only necessary data. Offers the most simplification but carries the most change for users.
- Brownfield (system conversion): convert the existing ECC system, keeping configuration, custom code and history. Faster and less disruptive, but carries existing complexity forward.
- Selective data transition (sometimes called “bluefield”): a hybrid that rebuilds some areas and moves selected data and processes. Often used by groups with several ECC instances or carve-out needs.
Whichever route you take, the critical path is usually data quality and custom code, not the technical conversion. Analysing custom code early and cleaning master data before the project starts are the two steps most likely to protect the timeline.
How to decide: five questions
- How much is your ECC system customised, and how much of that custom code is still used?
- Which countries do you invoice in, and what e-invoicing and reporting deadlines apply between 2027 and 2030?
- What does your current SAP contract allow in terms of licence conversion credits, RISE incentives and maintenance-fee terms?
- Do you have the internal capacity, and access to an implementation partner, to run a migration in your preferred window?
- What is your total cost of ownership over 7 to 10 years for each option, including infrastructure, support, regulatory work and change management, not just licence fees?
Implementation partner capacity is a real constraint. With many organisations facing the same deadline, experienced S/4HANA consultants are in high demand. Starting procurement early typically gives you more choice and better terms.
Frequently asked questions
Will my ECC system stop working on 1 January 2028?
No. The software continues to run. What changes is the level of support, patches and legal updates you receive from SAP, and the fees you pay for them.
Can I get extended maintenance beyond 2030?
Not as standard. After 2030, the options are customer-specific maintenance, the transition option if you qualify, or third-party support.
Is third-party support legitimate?
Yes. Independent providers offer support for SAP systems under your existing licences. The trade-offs are that you no longer receive SAP’s own updates and must rely on the provider, or your own team, for regulatory changes.
What is the difference between RISE and GROW?
RISE with SAP centres on S/4HANA in a private cloud edition, usually for large and complex organisations. GROW with SAP centres on the public cloud edition, which offers more standardisation and faster implementation, typically for mid-sized companies.
How long does an S/4HANA migration take?
It varies widely with scope, approach and data quality, from under a year for smaller, well-prepared brownfield conversions to several years for multi-country greenfield programmes. Starting now still leaves limited room before the end of 2027.
Conclusion
The end of mainstream maintenance in 2027 is less a cliff edge than the start of a more expensive and riskier period, made sharper by the wave of European e-invoicing and digital reporting mandates. Whichever option you choose, the decision is best made with a clear view of regulatory deadlines, contract terms and total cost of ownership, and made soon enough to secure the implementation capacity you will need.
Sources
- SAPinsider, SAP support deadlines: 2027, 2030 and 2033
- Rimini Street, No extension to ECC 6 and Business Suite 7 mainstream maintenance end dates
- The Register, SAP extends support deadline (January 2025)
This article is general information and not procurement, legal or licensing advice. SAP maintenance terms depend on your individual contract; confirm dates and costs with SAP or a licensing adviser. Product names are trademarks of their respective owners. Last checked: 7 November 2026. See our Disclaimer.