SAP S/4HANA Migration: Deadlines, Routes and How to Plan

SAP ends mainstream maintenance for ECC 6.0 at the end of 2027. This guide explains the deadlines, the routes to S/4HANA, the deployment choices and how to plan the move.

Abstract illustration of connected modules representing an ERP system

Key points

  • Mainstream maintenance for SAP ECC 6.0 on enhancement packages 6 to 8 ends on 31 December 2027; optional extended maintenance runs to the end of 2030 at additional cost.
  • S/4HANA is a different product, not an upgrade: it runs only on the SAP HANA database and simplifies the data model.
  • The three routes are system conversion (brownfield), new implementation (greenfield) and selective data transition.
  • Lead times are long and specialist capacity is limited, so late starters face higher cost and risk.

SAP ERP Central Component (ECC) has been the operational backbone of thousands of European companies for two decades. Its successor, SAP S/4HANA, was released in 2015. SAP originally planned to end ECC maintenance in 2025; in 2020 it extended the date. With that revised deadline approaching, organisations still on ECC need a firm plan.

The deadlines

Product statusDate
ECC 6.0 on enhancement packages 0 to 5: end of mainstream maintenance31 December 2025
ECC 6.0 on enhancement packages 6 to 8: end of mainstream maintenance31 December 2027
Optional extended maintenance for enhancement packages 6 to 8, at a premiumUntil 31 December 2030
After extended maintenanceCustomer-specific maintenance only: no new legal changes or security patches as standard
As published in SAP’s maintenance strategy. SAP has also offered a transition option to 2033 for certain customers who commit to its private cloud ERP; check the conditions with SAP.

Running unsupported software means no legal or tax updates and no security patches. For a system that produces statutory accounts and VAT filings, and that may fall within NIS2 or DORA obligations, that is not a sustainable position.

What is different about S/4HANA

  • Database. S/4HANA runs only on SAP HANA, an in-memory database. ECC on Oracle, Microsoft SQL Server or IBM Db2 requires a database migration as part of the move.
  • Simplified data model. Finance postings are held in a single table, the Universal Journal, which combines financial and management accounting. Many aggregate and index tables have gone.
  • Mandatory changes. Customers and vendors are managed through the Business Partner model; material numbers can be longer; some ECC functions have been replaced or removed. SAP documents these in its Simplification List.
  • User experience. The SAP Fiori interface is role-based and browser-driven, replacing most use of the classic SAP GUI.
  • Embedded analytics and, in current releases, AI-assisted features that are developed only for S/4HANA.

Three routes to S/4HANA

RouteWhat it involvesSuitsTrade-off
System conversion (brownfield)Technically convert the existing ECC system, keeping configuration, custom code and historyOrganisations with sound processes and a well-maintained systemFastest, least disruptive; carries forward old customisations and complexity
New implementation (greenfield)Build a new S/4HANA system on standard processes and migrate selected dataOrganisations with heavily modified or fragmented systems, or changing business modelsChance to simplify; longest, with the most business change
Selective data transitionCreate a new system and move chosen configuration and data using specialist toolsMergers, carve-outs, consolidation of several ECC systems, phased go-livesFlexible; technically demanding and reliant on specialist partners

Deployment choices

  • S/4HANA Cloud Public Edition. Multi-tenant software as a service with standardised processes and frequent updates. Reached through a new implementation only.
  • S/4HANA Cloud Private Edition. A dedicated instance operated by SAP on a hyperscaler, sold in the RISE with SAP package. Supports conversion of existing systems and more extensive customisation.
  • On-premise S/4HANA. Run in your own data centre or on infrastructure you contract for separately.

SAP promotes a “clean core” principle: keep the standard system unmodified and build extensions alongside it on the SAP Business Technology Platform, so that upgrades remain straightforward. The general arguments are set out in cloud ERP versus on-premise.

Licensing and commercial points

Moving to S/4HANA involves a commercial transaction as well as a technical one. Existing perpetual licences can be converted under SAP’s programmes or replaced by a subscription under RISE. Before negotiating:

  • establish what you own, what you use and which users are inactive;
  • understand how indirect access, known as digital access, is licensed where third-party systems create documents in SAP;
  • model costs over at least five years, including the HANA database, infrastructure and extended maintenance if you intend to rely on it;
  • consider independent licensing advice. User groups such as the UK and Ireland SAP User Group and DSAG in German-speaking countries publish guidance for members.

How to plan

  1. Assess readiness. Run SAP’s Readiness Check to identify affected custom code, add-ons, simplification items and sizing.
  2. Clean up. Retire unused custom code, archive old data and resolve data quality problems. Each reduces the scope of the migration.
  3. Convert customers and vendors to Business Partners in ECC ahead of the main project.
  4. Choose the route and deployment based on the state of the current system and business strategy, not on which is quickest.
  5. Build the business case. A purely technical conversion is hard to justify on return alone; identify process improvements that the move enables.
  6. Secure people. Experienced S/4HANA consultants are in demand as the deadline nears. Book partners and free internal experts early.
  7. Govern it as a business programme. The lessons in ERP implementation apply in full.

Alternatives

  • Extended maintenance buys time to 2030 at higher annual cost, without changing the destination.
  • Third-party support providers offer maintenance for ECC independently of SAP, usually at lower fees. You give up SAP’s own patches and new functionality, and should confirm how legal changes and security fixes will be delivered.
  • Moving to another ERP vendor is a full reimplementation. It is a realistic option mainly for smaller or simpler SAP estates.

Frequently asked questions

Is S/4HANA just an upgrade from ECC?

No. It has a different database, data model and user interface. Even a brownfield conversion is a substantial project.

How long does a migration take?

It depends on size and route. Conversions of mid-sized systems commonly take around a year including preparation; greenfield programmes in large groups run for several years.

Can we stay on ECC after 2027?

Yes, by paying for extended maintenance to 2030 or by using third-party support. Each has costs and limits, and neither removes the need for an eventual decision.

Do we have to move to the cloud?

No. On-premise S/4HANA remains available, although SAP directs most new investment and incentives towards its cloud editions.

The bottom line

For ECC customers the question is no longer whether to act but which route to take and how soon to start. The organisations in the strongest position are those that have already assessed their systems, cleaned their data and reserved the skills they will need.

Sources and further reading

Scroll to Top