SAP ECC end of maintenance: 2027, 2030, 2033

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 10 October 2026 · facts checked against the SAP Help Portal and SAP's maintenance pages, October 2026

SAP ECC end of life — strictly, the end of mainstream maintenance — is 31 December 2027 for SAP ERP 6.0 on enhancement packages 6 to 8. Paid extended maintenance lasts until 31 December 2030, and a transition option lets qualifying RISE with SAP customers keep ECC in SAP's private cloud until the end of 2033.

The same deadline is called ECC end of support, ECC EOL, the ECC sunset or, in German, the Wartungsende; all of them point at those dates, which SAP publishes in its maintenance strategy, linked below. This page sets out the dates and the products that retire alongside ECC as of October 2026, what staying on ECC past 2027 involves, the steps of a conversion to S/4HANA, and what the deadline means for the people doing the work.

Is SAP ECC end of life in 2027?

Not quite: on 31 December 2027 mainstream maintenance ends, not the software. SAP stops the standard stream of support packages, legal changes and fixes delivered under the normal maintenance fee; a system does not switch off on 1 January 2028, and nothing in it stops posting. What changes is the contract behind the system. From that day an ECC customer is in one of four positions: it has bought extended maintenance, it has signed up for the RISE path that ends in the 2031–2033 transition option, it has already converted, or it runs with the reduced customer-specific maintenance SAP applies once a maintenance phase has ended.

Two details are routinely misquoted. First, the 2027 date only applies to enhancement packages 6 to 8; systems on anything older left mainstream maintenance at the end of 2025 and are already in customer-specific maintenance. Second, the dates were not always these: SAP moved them in February 2020, when it extended Business Suite 7 maintenance to 2027 and committed to S/4HANA until 2040 (SAP News Center). Anyone planning around an older deadline read an older announcement.

Which SAP products reach end of maintenance with ECC?

Most of the Business Suite 7 landscape around it does: the integration server, the monitoring and change platform, the warehouse and the planning system share its calendar, because SAP aligned SAP NetWeaver 7.5 and the Business Suite 7 applications with the ERP. The table lists only dates SAP has published in its own maintenance pages, news or learning content (SAP's maintenance strategy for Business Suite 7 and S/4HANA).

The "where SAP points you" column is SAP's direction of travel, not a contract: a company can replace its CRM with another vendor's rather than SAP's Sales and Service Cloud and the wider CX suite, or keep its warehouse on a separate system, and many will. Solution Manager is the row most often forgotten in project plans. Its extended maintenance comes free with Business Suite 7 extended maintenance but covers only a limited set of functions, and SAP recommends that customers complete the move to Cloud ALM before the end of 2027 (SAP Solution Manager 7.2), which puts change control, test management and monitoring on the same deadline as the ERP.

Can you keep running ECC after 2027?

Yes: the system keeps running, and SAP sells extended maintenance to 31 December 2030 for customers who need more time; without it, the system falls into customer-specific maintenance, which keeps existing fixes available but delivers no new support packages or legal changes. Extended maintenance buys three more years of broadly the same service, for more money and with a deadline to decide. SAP priced it in 2020 as a premium of two percentage points on the maintenance basis for the Business Suite 7 scope, and describes it as a bridge for customers who cannot finish in time rather than a way to stay. It is ordered as a contract addendum, so the decision lands on a procurement calendar well before 2028, and the programmes that buy it are almost always the ones already mid-flight.

For the people working in those systems the practical effect is a longer tail of ECC support work, not a longer ECC career. Legal changes and fixes keep arriving until 2030; new functionality stopped arriving years ago.

What is the transition option to 2033?

It is a paid, time-bound subscription that keeps ECC running in SAP's private cloud from 2031 to the end of 2033 for customers already on the RISE path. The latest date anyone will quote you — the end of 2033 — belongs to SAP ERP, private edition, transition option: a time-bound subscription for large customers with complex landscapes, and not a general extension. As of October 2026 its conditions, as SAP updated them in August 2025 (SAP News Center), are these:

• The system must already sit in SAP's private cloud. Only systems moved to SAP ERP, private edition before the end of 2030 qualify; an ECC still running in a customer's own data centre in 2031 cannot use it.
• It comes with the max success plan. The transition option is available only in combination with that plan's services for 2031 to 2033, which include transformation support.
• It costs more the later a customer commits. Customers who committed to the private edition by the end of 2025 keep commercially equivalent terms in 2031; those committing during 2026 face a published 20 percent uplift; for commitments from 2027 SAP has not yet disclosed the uplift and says pricing follows closer to 2028.
• It is business continuity, not development. The services cover legal changes, security patches and bug fixing while the move to SAP Cloud ERP Private is completed.

Read it as the tail end of RISE with SAP: a customer using it has already done a technical migration to SAP's cloud and is still redesigning the business on top.

What are the steps of an ECC to S/4HANA conversion?

A brownfield conversion follows a fixed technical sequence, repeated in trial runs on copies of production before it is done for real:

1. SAP Readiness Check for SAP S/4HANA — analyses the production system and reports the simplification items, add-ons, custom code impact and sizing that apply, so the programme can be scoped before anyone commits to a date.
2. Simplification Item Check — the report /SDF/RC_START_CHECK in the source system lists the relevant items and runs the consistency checks that must pass before the conversion is allowed to proceed. Mandatory preparation, such as customer-vendor integration into the business partner, and the target stack calculated in the Maintenance Planner, come out of this step.
3. Custom code analysis — the ABAP Test Cockpit (ATC) with its S/4HANA checks, usually run remotely from a central check system, finds the code the new data model breaks; unused code is retired before anything is fixed.
4. Software Update Manager with the Database Migration Option — SUM performs the technical conversion, and DMO moves the database to SAP HANA in the same run when the source sits on another database.
5. SPDD and SPAU adjustments — dictionary modifications are adjusted in SPDD during the SUM run, and programme modifications and enhancements in SPAU and SPAU_ENH after it; then the ATC findings are worked down and the finance data conversion is completed.
6. Test cycles — each trial conversion is followed by functional, integration and regression testing, and timed, until the downtime fits the window the business can give.
7. Cutover — the final conversion of production over a planned weekend, the go or no-go decision and hypercare, as described in SAP cutover and hypercare explained.

A greenfield reimplementation or a selective data transition skips most of this sequence and loads data into a new system instead, which moves the weight of the work from Basis and code to design and migration.

Which roles does the ECC deadline create?

Four roles are the bottleneck on most programmes: Basis, custom-code remediation, data migration and functional redesign. Every ECC system still live in 2026 has to be converted, reimplemented, replaced or consciously run past its maintenance, and each of those paths staffs a project.

Basis and the conversion runtime

Steps one, two, four and six above are largely Basis work — the checks, the SUM runs, the sizing and the downtime rehearsals — and a Basis consultant who has run several of them is the scarcest person on the plan.

Custom-code remediation

Decades of Z-development meet the S/4HANA data model, from the first ATC run to the last finding closed after the conversion. It is steady, countable work, and the clean-core rules decide which findings are fixed in place and which move out of the core.

Data migration

A greenfield or selective path loads data rather than converting it: object inventories, the Migration Cockpit, mock loads and reconciliation. Even a brownfield conversion carries data work, from customer-vendor integration into the business partner to cleansing the open items nobody wanted to look at. The data migration guide describes the stream and its roles.

Functional redesign

Some changes are mandatory — the business partner, the Universal Journal, new asset accounting, an always-on material ledger, a different credit management — and each has a functional owner who has to explain it to the business. Beyond the mandatory ones, fit-to-standard asks which old processes survive at all, and that is senior functional judgment rather than configuration.

Around those four sit the roles every programme needs anyway, only more of them: regression and integration testing, cutover management, and the integration people moving interfaces off Process Orchestration onto Integration Suite on the same timetable.

What happens to ECC-only skills after 2027 and 2030?

They lose value in steps, not overnight. Until 2027 ECC knowledge is a requirement on every conversion, because somebody has to read the source system. From 2028 to 2030 the work narrows to support on extended maintenance and to the late conversions, which are usually the hardest ones. After 2030 it survives in transition-option landscapes, in customers running outside maintenance, and in AMS contracts nobody else wants — a smaller market, and one that pays for reliability more than expertise.

The loss is concentrated in skills tied to what S/4HANA or its successors replaced: classic and new general ledger design, separate customer and vendor masters, APO planning where the company moved to IBP, PI and PO mapping where the interfaces moved to Integration Suite, Solution Manager change control. Process knowledge — how a close runs, how a delivery becomes an invoice — carries straight across, which is the argument the S/4HANA career guide makes at length.

What should you learn before ECC support ends?

The S/4HANA version of what you already do. A functional consultant learns the simplification items and Fiori apps in their own area, then joins a conversion in any seat. An ABAP developer learns ATC remediation now and ABAP Cloud for what follows (the developer guide). A Basis administrator learns SUM with DMO, HANA operations and how the job changes under RISE. A PI/PO or Solution Manager specialist moves to Integration Suite or Cloud ALM, because their deadline is the ERP's. Newcomers find test, data and cutover seats on conversion programmes open to people without a long history.