EN
Insight

SAP ECC end of support 2027: what to decide now

For SAP ECC with enhancement packages 6 to 8, mainstream maintenance ends on December 31, 2027. This date is often called the SAP ECC end of support. If you start today, typical project durations put your go-live in 2028 or 2029. So decide in the coming months on your path to SAP S/4HANA and on how to bridge the time until go-live.

Martin Hörnig6 min read

In brief
  • For EHP 6 to 8, mainstream maintenance runs until December 31, 2027. After that, optional extended maintenance runs until December 31, 2030, at a premium of two percentage points on the existing maintenance basis.
  • For EHP 0 to 5, mainstream maintenance expired at the end of 2025. Extended maintenance is not available for these packages.
  • The transition option runs from 2031 to the end of 2033, and under further conditions until the end of 2035. It requires a move to “SAP ERP, private edition” by the end of 2030 and is aimed at large systems of 2 TB or more.
  • With typical durations for decision, partner selection, and implementation, a start today leads to a go-live in 2028 or 2029.

The deadlines at a glance

SAP ERP 6.0, commonly called ECC, is maintained by enhancement package (EHP). Your IT team can see which package you run under System → Status in the component information.

CasePeriodWhat it means
SAP ERP 6.0 with EHP 6 to 8Mainstream maintenance until December 31, 2027Legal changes, corrections, and Support Packages as before
SAP ERP 6.0 with EHP 0 to 5Mainstream maintenance ended on December 31, 2025Customer-specific maintenance since 2026; extended maintenance is not possible
Extended maintenanceJanuary 1, 2028, to December 31, 2030, only for EHP 6 to 8Optional, at a premium of two percentage points on the existing maintenance basis
Customer-specific maintenanceAfter the applicable maintenance endsNo more legal changes and no new Support Packages; fixes for new problems only for a fee
SAP ERP, private edition, transition option2031 to the end of 2033; since October 13, 2026, under further conditions until the end of 2035Time-limited cloud subscription: move to SAP ERP, private edition, on SAP HANA by December 31, 2030, system size of 2 TB or more, with the Max Success plan

As of November 16, 2026, including SAP’s update of October 13, 2026, on the transition option. Your maintenance contract and SAP Notes 1648480 (maintenance for SAP Business Suite 7) and 3591251 (transition option) are binding.

What you lose from 2028

On January 1, 2028, your system keeps running. What changes is what SAP still delivers for it. Without extended maintenance, customer-specific maintenance applies.

  • Legal changes are no longer delivered by SAP, for example for e-invoicing. In Germany, companies with prior-year revenue above €800,000 must issue electronic invoices for domestic B2B transactions from 2027, and all companies from 2028. Any later change to formats or procedures would be up to you.
  • Support Packages are no longer released. SAP fixes new, previously unknown problems only for a fee.
  • SAP commits to security fixes for newly discovered critical vulnerabilities during mainstream and extended maintenance. If you run without that commitment afterward, systems with external interfaces carry a growing risk.
  • Technical updates for new database, operating system, and browser versions are only available to a limited extent.

Extended maintenance buys three years. It pays off if the project is approved and only the timeline is too tight. If you buy it without a decision, you face the same question in 2030, with less time.

Independent providers also offer third-party support. Legal changes must then be covered in the contract with that provider. Check the scope and the contractual consequences before you terminate maintenance with SAP.

Work backward from go-live

A common planning mistake is to count forward from today and hope for a suitable date. Working backward from the target go-live is more reliable.

StepPlanning assumptionNote
Readiness assessment and decision2 to 4 monthsInvolves the executive team, budget, and the maintenance question
Partner selection2 to 6 monthsFor public-sector clients, the procurement procedure sets the duration
Implementation to go-live12 to 24 monthsDepending on path, scope, and data
Hypercare4 to 8 weeksThen handover to operations

Use your own values for your project; the calculation stays the same.

Take mid-range values. If you start in December 2026, you decide by March 2027 and have a partner in July 2027. After 18 months of implementation, go-live falls in January 2029.

In this case, your ECC system needs a maintenance solution for 2028 and early 2029. Include its cost in the plan right away.

A go-live at the start of the fiscal year simplifies the fixed asset migration, but it coincides with year-end closing.

Which path fits

Brownfield (conversion of the existing system), greenfield (new implementation), or selective data transition: the choice of path depends mainly on four questions.

  1. Do your current processes hold up? If so, there is a strong case for brownfield. If they are to be redesigned anyway, greenfield is the likelier fit.
  2. How much custom code is in the system? In a conversion, every custom development still in use must be checked and often adapted.
  3. How much history do you need in the new system? A conversion carries over all documents. A new implementation usually takes only master data, open items, and balances.
  4. How good is your data? In a conversion, errors carry over; in a new implementation, the data must be cleansed before the migration. Poor data creates work either way.

If you use WM: check the compatibility scope

If you use classic Warehouse Management (WM) in ECC, clarify the target design for your warehouse early. In SAP S/4HANA on-premise, WM is part of the compatibility scope (SAP Note 2269324).

Usage rights for most compatibility packs ended on December 31, 2025. In December 2025, SAP announced a final transition period, which ended at the end of May 2026. Systems under a cloud contract have their own deadlines.

Without compatibility rights, Stock Room Management remains available, a functionally reduced part of WM. It lacks, among other things, Task and Resource Management, Wave Management, Cross-Docking, Yard Management, and Decentralized WM.

For extensive warehouse processes, SAP Extended Warehouse Management (EWM) is the target solution, ideally as a subproject with its own schedule.

The next 90 days

These steps cost little and lay the groundwork for any decision.

  • Run SAP Readiness Check. SAP’s free analysis tool shows affected functions (simplification items), custom code, add-ons, and future sizing.
  • Measure how custom code is used. Collect usage data over several months, ideally across a year-end close. Custom code that nobody runs does not need to move.
  • Check data quality. Look for duplicate suppliers and customers (both become business partners in S/4HANA), incomplete material masters, and assets in the wrong asset classes.
  • Put a number on maintenance from 2028. Ask for a quote for extended maintenance and weigh its cost against the project budget.
  • Name the decision-making body. Who decides on path and budget, and by when? Without a deadline, the analysis never ends.
  • Prepare partner selection. Criteria and requirements come before the first meetings. Public-sector organizations align the procedure with their procurement office.

How we help

In a readiness assessment, we evaluate your system, data, processes, and interfaces. From that we derive the path, a high-level plan, and the maintenance needed until go-live.

Initial call: 30 minutes, free of charge.

Tell us about your system landscape and timeline. We will tell you where we see risks and whether we are the right fit.

Initial call Call