SAP ECC is the operational core for roughly 35,000 large and mid-market organisations worldwide. For most of them, it has been running finance, payroll, procurement, inventory, and compliance reporting for the better part of two decades.
SAP has confirmed it will stop mainstream maintenance on a fixed schedule. The problem is that most public coverage squashes all ECC customers into a single “2027 deadline” — and that framing is wrong. Some companies are already past their deadline without knowing it.
This article answers three things: which deadline actually applies to your system, what operationally changes on the day after that deadline, and why so many organisations are not ready. It is the entry point to the complete SAP ECC end-of-support guide.
What is SAP ECC and why does its 2027 deadline matter at this scale?
SAP ECC 6.0 — also known as SAP ERP 6.0, part of SAP Business Suite 7 — has been the dominant on-premises ERP platform since 2005. It was perpetually licensed: customers paid once and owned the software. That is precisely why moving away from it is so sticky.
Approximately 35,000 enterprises run ECC globally. SAP confirmed in 2023 that there will be no further extensions to the end-of-mainstream-maintenance dates. Once that support gap opens, the operational and regulatory exposure starts to accumulate.
Does the 2027 deadline apply to your SAP system — and what is the EHP version split that most articles miss?
Here is the thing most coverage gets wrong: the “2027 deadline” does not apply to all SAP ECC customers.
SAP ECC 6.0 supports Enhancement Packages (EHP) — incremental add-on releases installed on top of the base system. The EHP version you are running determines your exact end-of-mainstream-maintenance date. Two groups, two different deadlines.
- EHP 0-5: End of mainstream maintenance was December 31, 2025 — already passed.
- EHP 6, 7, or 8: End of mainstream maintenance is December 31, 2027.
SAP’s Arne Schmidthals confirmed this split directly: “For SAP ERP 6 with Enhancement Packages 0-5, mainstream maintenance ends on December 31, 2025. Those still using these versions at that point will automatically transition into Customer Specific Maintenance.”
The split matters beyond the date. Extended Maintenance — the paid option that keeps security patches and legal updates flowing through 2030 — is available only for EHP 6-8 customers. If you are on EHP 0-5, there is no Extended Maintenance option. Your only SAP-supported post-2025 path is Customer-Specific Maintenance, which provides no new security patches and no new legal or regulatory updates.
EHP 0-5 customers can upgrade to EHP 6-8 to push their deadline to December 31, 2027 and gain eligibility for Extended Maintenance. But as Natuvion notes, this “typically makes little sense” — it is time, resources, and money poured into a temporary solution.
To confirm your EHP version, check the SAP Product Availability Matrix or reference SAP Note 2269324.
What does “end of mainstream maintenance” actually stop — and what keeps working?
Mainstream Maintenance is SAP’s full-coverage support tier. Here is what actually changes when it ends.
What stops:
- New security patches for newly discovered vulnerabilities in ECC code
- Legal and regulatory updates (new tax codes, employment law amendments, government reporting changes)
- HR compliance updates
- New SAP Notes for newly discovered bugs
What does NOT stop:
- The ECC system itself keeps running
- Existing SAP Notes remain accessible
- Priority One (critical) support calls are still handled
As Forrester’s Akshara Naik Lopez put it: “Support from SAP is ending for the product, but it does not mean that the ECC environment is, all of a sudden, going to stop working.” The risk is not binary.
What accumulates instead: unpatched CVEs, legal changes not reflected in your software, and — as Natuvion notes — auditors who are “unable to certify the system or requiring significant additional effort to do so.”
One distinction worth being clear on: “end of mainstream maintenance” is not “end of support.” You automatically fall into Customer-Specific Maintenance, which technically continues — but its scope is so narrow that treating the two as equivalent is a mistake.
What happens to an SAP ECC system the day after the 2027 deadline if a company does nothing?
Day one: the system runs exactly as before. Nothing breaks. That absence of immediate failure is precisely why so many organisations treat the deadline as theoretical rather than operational.
From there, the exposure builds. SAP stops issuing new security patches — CVEs discovered after December 31, 2027 will not receive SAP-issued fixes. Tax law changes and payroll legislation amendments stop being incorporated into the software. The audit risk — SOC 2, ISO 27001, financial audit — typically becomes a formal control deficiency in the 12-24 months following the deadline, not on day one.
Rixmind’s analysis captures the trajectory well: companies that delay end up paying for legacy SAP maintenance AND future migration costs at the same time. Not a cliff. A steady grade.
For EHP 6-8 customers who elect Extended Maintenance before 2027, this plays out differently — Extended Maintenance covers security patches and legal updates through 2030. The scenario above applies to those who do neither. For alternatives to SAP’s native options, see our guide to SAP ECC alternatives and third-party support.
Why are 17,000 companies projected to miss the 2027 deadline?
The 17,000 figure comes from Gartner. As of end-2024, only 39% of SAP’s 35,000 ECC customers — roughly 14,000 organisations — had purchased SAP S/4HANA transition licences. Purchasing a licence is a proxy for intent, not completion. Gartner projects 17,000 holdouts by 2027, with more than 13,000 still running ECC in 2030.
Gartner VP Fabio Di Capua was blunt about it: “When SAP tried to make people move to RISE, we told them, ‘You convinced less than half of your clients to migrate in 15 years. How can you think you will migrate the next 50% in five years?'”
The Horváth study (2025) of 200 SAP user companies found projects running 30% longer than planned, only 8% finishing on schedule, and more than 60% exceeding budget. Of those 200 companies, only 37 had actually completed migration. ISG research from February 2026 found nearly 60% of projects delayed and over budget, with two-thirds still in the planning stage.
For a detailed breakdown of why, see why so many SAP migrations exceed budget and schedule.
What are SAP’s official escalation paths after mainstream maintenance ends — and what do they actually cost?
Three options exist. They differ fundamentally in scope, cost, and eligibility.
Extended Maintenance (EHP 6-8 only): January 1, 2028 through December 31, 2030. Includes new security patches and legal/regulatory updates. Adds approximately 2 percentage points to your SAP maintenance fee. Must be elected in advance — it is not automatic.
Customer-Specific Maintenance: The default fallback for all ECC customers after their deadline. You keep access to existing SAP Notes but get no new security patches, no new legal or regulatory updates, minimal bug fixes — at the same cost as mainstream maintenance. That last point is where most of the confusion comes from.
SAP ERP, private edition, transition option: Announced Q1 2025. Available to select large, complex customers who sign a RISE with SAP agreement and commit to migrating their database to SAP HANA by end of 2030. Provides continued ECC support past 2030. Not general availability. SAP has confirmed it is “only centered on ECC 6 and does not include the full scope of Business Suite 7.”
The distinction that matters most here: Extended Maintenance and Customer-Specific Maintenance are not the same thing. Companies who fall into Customer-Specific Maintenance by default receive less coverage at the same cost. That is worth repeating.
For detailed cost modelling see the true cost of SAP S/4HANA migration. For third-party support options see SAP ECC alternatives and third-party support.
What is RISE with SAP and how does it differ from GROW with SAP?
RISE with SAP and GROW with SAP are SAP’s two commercial packages for accessing S/4HANA. The naming is confusing. The distinction matters.
RISE with SAP targets larger, more complex ECC customers migrating to S/4HANA private cloud. It bundles managed cloud infrastructure, migration support tooling, and access to the Private Edition Transition Option.
GROW with SAP targets mid-market customers heading toward S/4HANA Cloud, Public Edition — standardised process fit, limited customisation.
For ECC customers: heavily customised systems typically follow a brownfield path to private cloud via RISE. Simpler environments can use GROW for a greenfield move to public cloud. As Arne Schmidthals at SAP put it: “For customers already using SAP ERP, the private cloud is the usual path.” Neither package is inherently cheaper.
How do you assess whether your SAP ECC environment must migrate before the 2027 deadline?
Here is a five-step framework for arriving at a defensible recommendation.
Step 1 — Confirm your EHP version. Check the SAP Product Availability Matrix or reference SAP Note 2269324. EHP 0-5 means your deadline was December 31, 2025 — already passed. EHP 6-8 means December 31, 2027. Most organisations skip this step. Do not.
Step 2 — Assess your compliance and regulatory exposure. Which legal and regulatory changes must your ECC system incorporate annually — payroll legislation, tax law, government reporting? Estimate the workaround burden if those updates stop. Regulated industries face more exposure here than most.
Step 3 — Run SAP Readiness Check. SAP’s free tool analyses your ECC system for S/4HANA compatibility, identifies custom code volume, and documents database migration requirements. Do this before talking to any consultants.
Step 4 — Assess internal capacity. Do you have a dedicated SAP team or are you relying on external consultants? Do you have budget for a 12-24 month project? The Horváth data points to the biggest failure drivers: lack of IT integration (28%), insufficiently defined processes (24%), knowledge gaps around third-party interfaces (23%).
Step 5 — Model three paths. (a) Migrate at current rates. (b) Elect Extended Maintenance (EHP 6-8 only) and target 2030 — buys time at roughly 2% extra fees, but consulting rates tend to rise as the window narrows. (c) Evaluate third-party support as a deliberate strategic choice — Rimini Street offers support through 2040 at approximately 50% of SAP’s pricing.
There is no universal right answer. The right choice depends on your regulatory exposure, migration complexity, and internal capacity.
For help building the financial model, see the true cost of SAP S/4HANA migration and why so many SAP migrations exceed budget and schedule. Our complete SAP ECC end-of-support guide covers each path in depth.
Frequently asked questions
Can I stay on SAP ECC after 2027 without paying extra?
No. After December 31, 2027, EHP 6-8 customers automatically fall into Customer-Specific Maintenance — same cost as mainstream maintenance, but no new security patches and no new legal or regulatory updates.
Extended Maintenance adds patches and legal updates through 2030 at approximately 2 extra percentage points. It must be elected in advance. There is no free support path after the deadline.
What is the difference between SAP ECC and SAP S/4HANA in plain English?
SAP ECC is the legacy on-premises ERP system — built on traditional relational database architecture like Oracle, MS SQL, or IBM DB2. Perpetual licence, in production since the early 2000s.
SAP S/4HANA is the current-generation platform, built exclusively on SAP HANA in-memory database. Faster, simplified data model, available on-premises or in the cloud. The migration is not a simple upgrade — it requires a database migration and, depending on your approach, business process re-engineering and custom code adaptation.
Does the 2027 deadline apply to all SAP ECC versions?
No. The 2027 deadline applies only to EHP 6, 7, or 8. Customers on EHP 0-5 had an earlier deadline — December 31, 2025 — which has already passed. EHP 0-5 customers have no Extended Maintenance option; their only SAP-supported post-2025 path is Customer-Specific Maintenance.
What is Customer-Specific Maintenance and why does it matter?
It is the default tier after mainstream maintenance expires. Same cost, but: no new security patches, no new legal or regulatory updates, no new HR compliance updates, minimal bug fixes. Organisations relying on it for compliance-critical processes accumulate growing exposure over time.
What is SAP Extended Maintenance and who is eligible?
Extended Maintenance is exclusively for EHP 6-8 customers. It runs January 1, 2028 through December 31, 2030 and includes new security patches and legal/regulatory updates. It costs approximately 2 additional percentage points on top of existing maintenance fees, must be elected in advance, and is not available for EHP 0-5 customers.
What is the SAP ERP private edition transition option announced in 2025?
Announced Q1 2025. Select large, complex customers can continue using ECC past 2030 within an SAP-managed private cloud environment — but only if they sign a RISE with SAP agreement and commit to migrating their database to SAP HANA by end of 2030. Not general availability. Commercial terms require direct engagement with SAP.
Why hasn’t my company moved to SAP S/4HANA yet?
Limited internal SAP expertise, no dedicated migration team, budget constraints, and underestimation of complexity. More than half of surveyed organisations had over-customised legacy ERP to the point where standardisation now feels risky — inertia that blocks decisions.
The Horváth study found more than 60% of migrations deviate significantly from planned budget, schedule, or quality targets, with only 8% finishing on schedule. The challenge is structural, and it is widespread.
How long does an SAP S/4HANA migration actually take?
Projects average 30% longer than planned; only 8% complete on schedule (Horváth, 200 SAP user companies). Gartner has worked with clients anticipating three- to seven-year projects for complex environments.
For organisations targeting 2027 completion, timeline compression is real. Start your readiness assessment now.
What does Gartner say about SAP ECC migration rates?
At end-2024, only 39% of SAP’s 35,000 ECC customers had purchased S/4HANA transition licences — a proxy for intent, not completion. Gartner projects 17,000 holdouts by 2027 and more than 13,000 still on ECC in 2030.
What is third-party SAP support and is it a viable alternative to migrating?
Third-party SAP support replaces SAP’s maintenance contract with an independent provider. Rimini Street offers support for SAP ECC 6.0 through 2040 at approximately 50% of SAP’s pricing, including patches for newly discovered CVEs and legal/regulatory updates that Customer-Specific Maintenance does not cover.
It is a deliberate strategic choice for some organisations — when the migration business case is unclear, when more time is needed, or when the long-term ERP strategy is still being worked out. Not suitable for everyone; it carries commercial and legal complexity worth assessing properly.
Can upgrading my EHP version extend my SAP ECC deadline?
Yes. EHP 0-5 customers can upgrade to EHP 6-8, moving their deadline to December 31, 2027 and gaining eligibility for Extended Maintenance through 2030. An EHP upgrade is not a migration — it does not move you to S/4HANA. Given the 2025 deadline has already passed for EHP 0-5 customers, treat this as an urgent near-term decision.
Where can I find SAP’s official ECC end-of-support dates?
The authoritative source is the SAP Product Availability Matrix (PAM). SAP Note 2269324 in the SAP Support Portal covers ECC 6.0 maintenance end dates and enhancement package distinctions. Seidor’s summary is a well-organised secondary reference.
