Companies planning to replace SAP ECC have less time than the December 31, 2027 deadline suggests. That is when mainstream maintenance ends for SAP ERP 6.0 with enhancement packages 6 through 8. SAP expects customers who want extended maintenance through 2030 to return the signed addendum before the end of 2027. In DSAG’s 2026 investment survey, 54% of respondents still used SAP ECC or the older Business Suite (DSAG, February 26, 2026). At manufacturers, industrial suppliers, intralogistics companies and retailers that use ECC to manage warehouses, run production and keep interfaces working, IT leaders and senior management share responsibility for the decision.
SAP offers extended maintenance for ECC through the end of 2030. The maintenance rate rises by two percentage points, and the extension covers every system under the agreement. Projects take 12 to 24 months, so even a 12-month project must start by the end of 2026 to go live by the end of 2027. For most companies, the deadline that matters comes earlier in 2027, when they need to order extended maintenance in the second or third quarter. Moving warehouse operations, production functions and interfaces out of ECC narrows the scope of the eventual ERP project. The maintenance premium stays the same. We recommend an approach for each area in our three-week ERP options assessment.
SAP’s deadlines for replacing ECC
In 2020, SAP committed to providing mainstream maintenance for SAP ERP 6.0 through the end of 2027. Customers can then opt for extended maintenance through the end of 2030 at a rate two percentage points higher. Customers who have made no choice by the end of 2027 automatically move to customer-specific maintenance (SAP News, February 4, 2020). SAP says that under customer-specific maintenance, it no longer updates the software to reflect changes in legislation and issues SAP Security Notes only in limited cases.
In an October 2026 presentation, SAP says extended maintenance covers the entire commercial installation. Customers cannot exclude individual systems. Coverage always starts on January 1, 2028, and runs for at least one calendar year. Customers must give 90 days’ notice to end coverage at year-end. SAP recommends placing the order in the second or third quarter of 2027 (SAP, October 2026).
SAP says support for third-party databases and for Java 8 on NetWeaver AS Java 7.5 ends in December 2030. After that, SAP will stop issuing kernel security patches for systems running on third-party databases. Support for conversion to S/4HANA also ends at the close of 2030 (SAP News, October 7, 2026).
In SAP’s example, the rate for SAP Enterprise Support rises from 22% to 24%. Under extended maintenance, the higher rate applies to the entire maintenance base.
SAP, October 2026
What the 2027 ECC maintenance deadline means for your business
If you plan to go live by December 31, 2027, you need to start the project now. IBsolution puts the time needed to implement S/4HANA at 12 to 24 months (IBsolution, May 8, 2026). ICB puts ERP projects at 12 to 30 months. If you have yet to define what your future ERP environment should look like, allow another year for preparation (ICB, August 31, 2026). Even a 12-month project would therefore need to start by the end of 2026.
Consider a supplier with two plants, one in Bavaria and one in Upper Austria. All figures in this example are assumptions. The supplier runs ECC on a third-party database. It uses SAP WM to manage the warehouse and SAP PP to manage production. On a maintenance base of €1.5 million to €2.5 million, the supplier pays 22% for Enterprise Support, or €330,000 to €550,000 a year. The extra two percentage points add €30,000 to €50,000 a year. If the new ERP system goes live in mid-2029, the supplier gives notice to end extended maintenance at the end of 2029. The premium for those two years totals €60,000 to €100,000. If the go-live slips to 2030, the total premium rises to €90,000 to €150,000. These figures exclude annual index adjustments to maintenance fees.
Suppose the supplier first moves warehouse control to a dedicated warehouse management system and connects its manufacturing execution system (MES) through a separate integration layer. The maintenance premium stays the same, but the ERP project that follows is smaller and takes less time. Because ECC runs on a third-party database, the supplier must complete any conversion to S/4HANA before the end of 2030. After that, staying with SAP would require a new implementation.
SAP ECC, S/4HANA and the alternatives: how much work does each option involve, and what are the risks?
| Option | Effort | Costs | Risk |
|---|---|---|---|
| Implement S/4HANA from scratch or convert the existing ECC system | 12 to 24 months, according to IBsolution | Implementation or conversion project, plus a new license or subscription agreement | The project must account for custom code. ICB says few consultants will be available during this period. |
| Implement a different ERP system | ICB estimates 12 to 30 months, depending on the sites and legal entities involved | Implementation from scratch, data migration and training | The company must redesign its processes and rebuild the interfaces to its MES and warehouse systems. |
| Extend maintenance through 2030 | Contract addendum. SAP recommends ordering in Q2 or Q3 2027. | Two percentage points added to the maintenance rate across the entire maintenance base | Extended maintenance buys time to decide. SAP support for third-party databases ends in December 2030. |
| Move warehouse operations, production functions and interfaces out of ECC | Months for each functional area | Developing and running custom applications | The surcharge remains the same. The company must operate an additional application. |
| Transition Option from 2031 | Move to SAP ERP, private edition on SAP HANA by the end of 2030 | SAP quotes a 20% subscription premium for contracts signed in 2026. The max success plan costs extra. | Limited to systems of 2 TB or more. Excludes Java functionality. |
| Do nothing | none | unchanged fees | From 2028, SAP will no longer update the software to reflect changes in legislation and will issue SAP Security Notes only in limited cases. |
Read about our approach to legacy modernization and migration planning.
Which option fits your business?
S/4HANA is a good fit if your ECC system has few customizations and you want to keep finance, purchasing and sales in SAP. A different ERP system is worth considering if you use only some of the ECC modules and already plan to change how you work.
If a 2027 go-live is out of reach, we recommend deciding early in 2027 what your future ERP environment should look like. Order extended maintenance in the third quarter of 2027. Once the new system is live, give notice to end coverage at year-end. The premium buys you time to move functions out of ECC. Start where people already work outside SAP, whether they use forklift terminals, record production confirmations on the line or work in supplier portals. You will need those functions whichever ERP option you choose.
You don’t always need an external partner for this. Your IT team can take stock of the system itself if you run a single ECC installation with few customizations, have an in-house SAP team and have already chosen S/4HANA with your current SAP partner. The maintenance section of SAP for Me shows when coverage ends for each production system and whether extended maintenance is available. torck does not carry out S/4HANA conversions or ERP implementations. An independent assessment is worthwhile if you are still weighing the options or want to run warehouse operations, production functions and interfaces in separate applications.
three-week ERP options assessment You receive an inventory of the ECC modules you use, your custom code and the systems that handle warehouse operations, production and interfaces alongside ECC. For each area, we recommend one of four options: S/4HANA, a different ERP system, extended maintenance or a custom application. We estimate the work involved and give you a decision deadline. You can then decide whether to order extended maintenance in the third quarter of 2027 and which functions to move out of ECC first. We review your custom code in a separate assessment.
Frequently asked questions
How much does extended maintenance for SAP ECC cost through 2030?
SAP adds two percentage points to the maintenance rate for all SAP Business Suite 7 core applications. In our example, a maintenance base of €1.5 million to €2.5 million means an extra €30,000 to €50,000 a year.
Can I buy extended maintenance for selected systems only?
No. SAP does say that customers switching to an S/4HANA contract can cancel unused legacy licenses. Your SAP sales representative can clarify the terms.
When do we need to decide what our future ERP environment will look like?
If you plan to go live by December 31, 2027, you need to make that decision now and start the project by the end of 2026. Otherwise, aim to settle on your future ERP setup early in 2027, before ordering extended maintenance in the third quarter.
The next step
For details of our services, see Legacy Modernization. We explain how we assess custom code ahead of an S/4HANA migration in SAP Clean Core before the move to S/4HANA. For a comparison of the options for your warehouse module, see Replacing SAP WM before maintenance ends in 2027. We cover the options for your interfaces in Replacing SAP PO. If you need applications that run alongside your ERP system, we build them as part of our custom software development service. The initial consultation lasts one hour and is free of charge. Schedule an initial consultation.