SAP ECC End of Support: Extended Maintenance Cost and Runway Calculator
This calculator estimates what SAP ECC 6.0 extended maintenance from 2028 to 2030 will cost on your maintenance base, and how many extended years your migration timeline actually needs. It flags when a plan runs past 2030, where only customer-specific maintenance or a contractual transition option remains.
Your numbers
The value your SAP maintenance percentage is applied to, from your maintenance contract.
From your contract. Enterprise Support is commonly 22%, but use your own figure.
Percentage points added to the maintenance base for 2028 to 2030, per SAP's 2020 announcement.
Optional: hosting, support and licences during dual running.
Your results
Planning estimate only. Your maintenance base, rate and any extended maintenance or transition terms come from your own SAP contract; confirm them with SAP before budgeting.
Implied extended premium vs project duration
Sweeps Migration project duration from today to go-live from 6 to 60, holding your other inputs fixed.
Want a reviewed runway plan for your ECC?
Send us your EHP level, database version and migration timeline and we will check the support dates that apply to your whole stack, not only SAP's.
Optional. The tool and every export work without this. No spam.
The dates and the premium
In February 2020 SAP announced that mainstream maintenance for SAP Business Suite 7 core applications, which includes ERP 6.0, runs to the end of 2027, with optional extended maintenance to the end of 2030 at a premium of two percentage points on the existing maintenance base. This applies to ERP 6.0 on enhancement package 6 or higher; EHP 0 to 5 only had mainstream maintenance to the end of 2025, so a system below EHP6 must first move to EHP6, 7 or 8 to use the 2027 and 2030 dates. After the end of extended maintenance, or after 2027 if you do not take it, a release falls into customer-specific maintenance, with no new legal changes or fixes as standard. In 2025 SAP also announced a transition option for customers moving ECC into SAP ERP, private edition, under a RISE contract, with support to the end of 2033; that is contract specific and not modelled here.
How the formulas work
Standard fee = base x rate / 100. Extended premium per year = base x premium points / 100, paid on top of the standard fee. Runway gap = project months from today to go-live minus months left until 31 December 2027, floored at zero. Implied extended years = the gap divided by 12, rounded up and capped at 3, because extended maintenance ends with 2030. Implied premium = premium per year x implied years. Months beyond 2030 = duration minus months left minus 36. Dual running cost is entered separately because it often exceeds the premium. Note that contracted extended maintenance is usually bought in whole years, which is why the implied years are rounded up.
Worked example
Base $2,000,000, rate 22%, premium 2 points, 14 months left to the end of 2027 and a 24-month programme. Standard maintenance is $440,000 a year. The premium is $40,000 a year. The project runs 10 months past mainstream, which implies one extended year and $40,000 of premium. If the programme slips to 40 months, the gap is 26 months, implying three years and $120,000; at 52 months it overruns 2030 by 2 months, the warning case. The chart sweeps duration from 6 to 60 months to show the steps. In most programmes the premium is small next to the cost of a slip, so use the result to argue for schedule contingency, not to skip extended maintenance.
Common mistakes
Do not apply the premium to the annual fee; it is points on the maintenance base, so 2 points on a 22% rate is a 9% fee increase, not 2%. Do not assume your rate is 22%: Standard Support, Enterprise Support and negotiated contracts differ. Check your enhancement package in System, Status, component SAP_APPL before counting on 2030, and remember that the database and operating system have their own support dates, which can end before SAP's. Finally, extended maintenance covers ECC; separately licensed products such as BW or PI have their own schedules.
Frequently Asked Questions
Is SAP ECC 6.0 still supported?
Yes, ECC 6.0 on enhancement package 6, 7 or 8 is in mainstream maintenance until 31 December 2027. Extended maintenance can be contracted for 2028 to 2030. ERP 6.0 on EHP 0 to 5 left mainstream maintenance at the end of 2025 and needs an EHP upgrade to stay in mainstream.
How much does SAP ECC extended maintenance cost?
SAP announced a premium of two percentage points on the existing maintenance base for extended maintenance from 2028 to the end of 2030. On a $2 million base that is $40,000 a year on top of the standard fee. Your actual base, rate and terms come from your contract.
What happens to SAP ECC after 2030?
After extended maintenance ends, ECC moves into customer-specific maintenance: SAP still answers support messages, but new legal changes and standard fixes are no longer delivered as before. SAP has also announced a contractual transition option for ECC moved into SAP ERP, private edition, with support until the end of 2033.
Do I need extended maintenance if go-live is in 2028?
If production ECC still runs in 2028, even for a few months, you need either extended maintenance for that year or to accept customer-specific maintenance. Include dual running and hypercare: the old system often stays live for months after go-live for audits and open items.
If you will run ECC for several more years, we can add a private AI layer on your own servers that helps your team query and support it while the migration is planned.
Related Tools
SAP ECC EHP8 Upgrade SPDD/SPAU Adjustment Effort and Downtime Simulator
Enter SPDD and SPAU object counts, minutes per object, custom objects to retest and SUM downtime, and get adjustment hours per cycle, total effort and development outage.
SAPSAP ECC AI Assistant Sizing and Value Calculator
Estimate peak concurrent requests, GPUs, tokens per day, index size, hours saved and payback for a private AI assistant on SAP ECC 6.0.
SAPSAP ECC Obsolete Transactions and S/4HANA Replacements
A lookup table of common ECC transaction codes and the transaction or app that replaces them in S/4HANA, for training and role design.
SAPSAP ECC Classic MRP Run (MD01/MDBT) Runtime Simulator
Enter materials in scope, net change share, processing key, measured milliseconds per material and parallel processes to estimate the MRP job runtime and whether it fits the night window.
More SAP tools
See all- SAP ECC Private AI Layer Blueprint Generator
- SAP ECC SD User Exit Forms Reference (MV45AFZZ, RV60AFZZ, MV50AFZ1)
- SAP ECC Customer Exits (SMOD Enhancements) by Module Reference
- SAP ECC Classic BAdI Definitions Reference (MIGO, ME21N, MIRO, Deliveries, PM Orders)
- SAP ECC Background Job Tables Reference (TBTCO, TBTCP, Job Status Codes)
- SAP ECC Output Determination Tables and Codes Reference (NAST, TNAPR, NACE)
- SAP ECC Movement Type Configuration Tables Reference (T156, T156T, T157D)
- SAP ECC Stock Type and Location Transfer Movement Type Matrix
- SAP ECC Movement Type to OBYC Transaction Key and GBB Account Modifier Reference
Keep exploring
Free tools
- SAP ECC 6.0 Enhancement Packages and Maintenance Dates Reference (EHP1 to EHP8, 2027, 2030, 2033)Every SAP ERP 6.0 enhancement package with its NetWeaver basis, SAP_APPL release and the maintenance dates that apply: 2025, 2027, 2030 and the 2033 transition option.
- SAP ECC 2027 Maintenance Exit Path AssessmentTwelve scored questions on EHP level, database, custom code, CVI, add-ons, budget and contract appetite that map your SAP ECC 6.0 system to one of four maintenance exit paths, with the dates that apply.
- SAP ECC AI Assistant Sizing and Value CalculatorEstimate peak concurrent requests, GPUs, tokens per day, index size, hours saved and payback for a private AI assistant on SAP ECC 6.0.
Integrations
- How to connect Claude to SAP ECC 6.0Connect Claude to SAP ECC 6.0 through an MCP connector, the Anthropic API, AWS Bedrock or Google Vertex, and see when an on-prem open model is the better fit.
- How to use ChatGPT with SAP ECC 6.0Using ChatGPT with SAP ECC 6.0: custom GPT actions, exports versus live access, an OData or MCP bridge, enterprise data controls, and when a private model is safer.