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

Lesson 1 of 6

Why the move, and when

7 min

SAP ECC (SAP ERP 6.0) has run a large share of the world's manufacturing, distribution and finance for two decades. SAP S/4HANA is its successor: a new product built on the SAP HANA in-memory database, with a simplified data model and a new user experience. For business users, the important point is that S/4HANA is not just an upgrade. Some screens look familiar, but objects, tables and in places processes have changed. This course explains what changes in daily work and what the business must do to make the move safely.

The maintenance timeline

The deadline that drives most programs is SAP's maintenance commitment for ECC. For the most widely used enhancement packages (EHP 6 to 8), mainstream maintenance ends on December 31, 2027. Customers can buy extended maintenance, for an additional fee, until the end of 2030. In 2025 SAP also announced a transition option for qualifying customers moving to SAP's private cloud offering, which covers ECC in a private edition through 2033. Contract details vary, so treat these dates as the outer edges of planning, not targets.

  1. 2015SAP S/4HANA launchedFirst on-premise edition; the simplification list starts to grow with each release
  2. Late 2025SAP S/4HANA 2025The release this course is written for (on-premise and Cloud Private Edition)
  3. Dec 31, 2027ECC mainstream maintenance endsFor enhancement packages 6 to 8
  4. Dec 31, 2030Optional extended maintenance endsAvailable at extra cost
  5. 2031–2033Private edition transition optionOnly for qualifying customers under specific contract terms
Key dates for an ECC customer. Check your own contract for what applies to you.

What actually changes

It helps to separate three kinds of change, because each needs a different response from the business:

Technology changeNew database (SAP HANA), new data model, new technical tools. Mostly invisible to business users, but it is why some reports and custom programs must change.
Functional changeSimplification items: an object replaced (business partner), a component replaced (credit management), a mandatory feature (material ledger, new asset accounting). Visible in daily work.
Experience changeSAP Fiori apps and the launchpad, role-based access, embedded analytics. SAP GUI still exists on-premise and in Private Edition, but new functions increasingly arrive as Fiori apps.
Three layers of change in a move from ECC to SAP S/4HANA.

What stays the same

It is just as important to know what does not change. The organizational structure (company codes, plants, sales organizations, purchasing organizations) carries over. The core document chains you know from ECC (sales order, delivery, billing; purchase order, goods receipt, invoice) still exist with the same logic. Many familiar SAP GUI transactions such as VA01, ME21N, MIGO and MIRO still work on-premise and in Private Edition. That continuity is good news for users, and a trap for testers: because screens look the same, people assume results are the same.

Why companies move now

Maintenance dates are only part of the reason. SAP's new functions, including embedded analytics, new Fiori apps and AI features, are delivered on SAP S/4HANA and its cloud offerings, not on ECC. Finance teams want faster closes and line-item reporting without reconciliation. And the pool of skills and partners is moving with SAP. For a business user, the practical question is not whether the move happens but how well the business prepares for it.

A note on Public Edition

SAP S/4HANA Cloud Public Edition is a standardized SaaS offering. You cannot convert an ECC system into Public Edition; moving there is always a new implementation, using SAP's standard processes and extensibility rules. Everything in this course about conversion applies to on-premise and Cloud Private Edition.

What would you do?

A Contoso sales manager says: "It's just an upgrade, IT can do it over a weekend and we'll carry on as usual." How should a key user respond?

Key points
  • SAP S/4HANA is a new product with a simplified data model, not just an upgrade.
  • ECC mainstream maintenance (EHP 6 to 8) ends December 31, 2027; extended maintenance runs to the end of 2030 at extra cost.
  • Change comes in three layers: technology, functional (simplification items) and experience (Fiori).
  • Public Edition is reached only by new implementation, not by conversion.

Check your understanding · not graded

Lesson check

  1. 1. When does ECC mainstream maintenance end for enhancement packages 6 to 8?

  2. 2. Which statement about SAP S/4HANA Cloud Public Edition is correct?

  3. 3. Which layer of change includes the business partner replacing customer and vendor masters?

  4. 4. Is SAP GUI still available in SAP S/4HANA on-premise and Private Edition?