ECC 2027

About this guide

An independent explainer of the end of SAP ECC maintenance, written for the finance, IT and operations leaders who have to decide what the company does about it.

Contents
  1. Who it is for
  2. Independence and the SAP name
  3. How it is made
  4. Corrections

Most pages about the 2027 deadline are written by firms that sell the migration. They describe the date as a reason to buy. This guide describes it as a decision with several answers. It quotes SAP's terms from SAP's own pages, puts a price on each option, and includes the option to leave.

Who it is for

Chief financial officers, IT directors and operations leaders at established companies that run SAP ECC. We assume readers know their own system, custom code and contracts far better than any outside party, and need the dates, the published prices and the evidence in one place.

Independence and the SAP name

This guide is independent of SAP SE. SAP, SAP ECC, SAP ERP, SAP S/4HANA, RISE with SAP and Joule are named only to identify the products and programmes discussed. We use no SAP logos, and nothing here implies endorsement by or affiliation with SAP.

How it is made

Dates and terms come from SAP's Support Portal and News Center. Costs and survey findings come from user groups, analysts and trade press, each with a numbered source and the date we read it. Vendor-reported figures are labelled as such. The criteria and the ranking frame are on the methodology page.

We re-check the guide at least once a quarter, and whenever SAP changes a date, a price or a programme. Every page shows its last update and keeps a change log.

Corrections

If a date, a price or a description is wrong, tell us. Verified errors are corrected promptly, and each correction is recorded on the page.

Also in: Deutsch · Français