Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 2 of 6

ECC 6.0 in 2027: extended maintenance and the transition option

10 min

Listen to this lesson

0:00 / 6:53

The ECC clock is really two clocks, one per group of enhancement packages, plus a narrow bridge beyond 2030. In February 2020, SAP announced mainstream maintenance for the core applications of SAP Business Suite 7 until the end of 2027, followed by optional extended maintenance until the end of 2030. The SAP NetWeaver maintenance strategy page spells out the scope: the extra time covers the latest three enhancement packages of SAP ERP 6.0 (EHP 6, 7 and 8) and EHP 2, 3 and 4 of SAP CRM 7.0, SRM 7.0 and SCM 7.0, at a premium of two percentage points on the maintenance base for the extended period.

Your enhancement package decides your clock

Source systemMainstream maintenanceAfter thatAction
SAP ERP 6.0 EHP 0 to 5Ended December 31, 2025Customer-specific maintenance; no extended optionAlready out of mainstream: convert, or upgrade to EHP 8 first if the move is years away
SAP ERP 6.0 EHP 6 to 8Until December 31, 2027Optional extended maintenance to December 31, 2030Plan to be live on SAP S/4HANA before your chosen date
SAP ERP, private edition, on SAP HANA (RISE)Transition option from 2031Time-bound subscription; prerequisites in SAP Note 3591251Only for qualifying RISE customers; confirm terms with SAP
SAP S/4HANA (on-premise, Private Edition)Per release: 7 years from 2023 releasesSAP commitment to at least 2040Plan the first upgrade on SAP S/4HANA too

Which ECC clock applies depends on the enhancement package and the contract.

Contoso's production ECC system EP1 ran ECC 6.0 EHP 8, so its clock was the 2027 / 2030 pair. Grace's Q3 go-live (August 2026) put Contoso on SAP S/4HANA well before the end of 2027. During the program, the risk register still carried "go-live slips past 2027", and its mitigation was a budgeted extended maintenance contract, not a hope.

EHP 0-5 systems are already past mainstream; EHP 6-8 have until 2027, with paid extended maintenance to 2030.
The Sign-Off Table · thesignofftable.com/academy/sap-s4t-104

The SAP ERP, private edition, transition option

In 2025 SAP announced the SAP ERP, private edition, transition option for its largest and most complex ERP customers who cannot finish their move by the end of 2030. SAP News described it as business continuity from 2031 to 2033, with services that cover legal changes, security patches and bug fixing. An update dated October 13, 2026 states that subscriptions may now run until December 31, 2035, with further prerequisites. The prerequisites SAP published in 2025 include:

  • Systems must be migrated to SAP ERP, private edition, on SAP HANA before December 31, 2030. SAP HANA is the only supported database.
  • A minimum system size (SAP's announcement named 2 TB).
  • Mitigation coverage for products that the option does not include; SAP Note 3591251 lists the eligible products and the mitigation requirements.
  • The Max Success Plan for the transition period.
  • Commercial terms that depend on when the customer commits (SAP's announcement described a standard uplift for later sign-ups).

Read the option for what it is: a priced safety net for a subscription customer who is already on SAP HANA in SAP's private cloud. It is not an extension of on-premise ECC maintenance, and it does not apply to an ECC system still on a third-party database in a customer data center, which is exactly where Contoso's ECC sat before the conversion.

  1. Live on SAP S/4HANA before the end of 2027?Yes → no bridge needed; keep a slip contingency · No → next question
  2. Live before the end of 2030?Yes → budget extended maintenance (EHP 6-8 only) · No → next question
  3. On ERP private edition on SAP HANA before the end of 2030, and meeting SAP Note 3591251?Yes → evaluate the transition option with SAP · No → customer-specific maintenance risk; accelerate
Which bridge, if any, a program needs depends on its realistic go-live date.
The Sign-Off Table · thesignofftable.com/academy/sap-s4t-104

What 2027 means for testing

Each bridge has a test cost. Extended maintenance keeps ECC patched, so the ECC regression set must stay alive while a conversion program runs: during Contoso's program, the ECC support team still applied notes in ED1 and EQ1 and tested them through ChaRM. A move to ERP private edition is itself a migration with technical and regression testing, followed later by the real S/4HANA move, so it means testing twice. Customer-specific maintenance shifts work to the business: every tax change must be built and tested as a custom change.

Every route ends in SAP S/4HANA; the later routes add test cycles on the way.
The Sign-Off Table · thesignofftable.com/academy/sap-s4t-104

What would you do?

Early in the conversion program, Contoso's board asks Grace to compare two plans: hold the Q3 go-live, or delay twelve months to add scope and rely on extended maintenance if the new date slips into the following year. Priya is asked what the delay means for testing. What should she say first?

Key points
  • ERP 6.0 EHP 0-5 left mainstream maintenance at the end of 2025 with no extended option.
  • EHP 6-8: mainstream to the end of 2027; optional paid extended maintenance to the end of 2030.
  • The transition option needs ERP private edition on SAP HANA before the end of 2030; since October 2026 subscriptions may run to the end of 2035.
  • Every bridge adds test work: a longer ECC regression or an extra migration to test.

Check your understanding · not graded

Lesson check

  1. 1. Which ERP 6.0 enhancement packages are covered by extended maintenance to 2030?

  2. 2. What must be true before the transition option can apply?

  3. 3. What happened to ERP 6.0 EHP 0-5 at the end of 2025?

  4. 4. Why does choosing extended maintenance add test work?