SAP ECC on EHP 5 or earlier is already in customer-specific maintenance: the ERPNext option for mid-size sites
Short answer
SAP’s own material says mainstream maintenance for SAP ERP 6.0 without an enhancement package, or on EHP 1 to 5, ended on December 31, 2025, and those systems are now in customer-specific maintenance (checked Nov 15, 2026). SAP Note 52505 spells out what that means: no delivery of legal changes, no delivery of support packages, no guarantee of technology updates, no response-time SLAs, and new problems may be charged as consulting. You keep paying your full maintenance fee. Your options are to accept that and plan, upgrade to EHP 6, 7 or 8 to get back inside SAP’s mainstream commitment to the end of 2027, move to SAP S/4HANA (quote-only), or, for a mid-size site with standard processes, reimplement on ERPNext, which has no licence fee. ERPNext is a realistic option for single-country or few-entity manufacturers and distributors; it is the wrong choice for deeply integrated, regulated or global SAP estates.
Contents
- Who this guide is for
- What SAP says about ECC enhancement packages
- What customer-specific maintenance actually means
- First, confirm your enhancement package level
- Your options, from least to most change
- Running safely in customer-specific maintenance while you decide
- What moving an ECC site to ERPNext involves
- How ECC concepts map to ERPNext
- Where staying with SAP is the better answer
- What it costs
- A 90-day plan for EHP 5 and earlier sites
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for CFOs, IT directors and SAP leads at mid-size companies, typically single-country or few-entity manufacturers and distributors, whose SAP ECC 6.0 system never moved beyond enhancement package 5. Often the system works, the original project team has gone, and upgrades were deferred because nothing forced them. Since January 1, 2026, something has.
If you are on EHP 6, 7 or 8, the deadlines are different and our SAP ECC end of maintenance (2027) guide covers them, including the two-tier model for subsidiaries. The legacy ERP end-of-support hub lists every vendor date we have confirmed.
We implement ERPNext, so read our recommendations with that in mind. For many SAP sites an EHP upgrade or S/4HANA is the right call and we say where.
Sources, checked on Nov 15, 2026: SAP’s “Maintenance Timelines for SAP ERP 6.0” post on SAP Community (a post in SAP’s “blog posts by SAP” section, by an SAP product expert), SAP Note 52505 (public PDF copy, version 66, released Aug 19, 2024), SAP presentation “Managing SAP Business Suite 7 Extended Maintenance” (October 2026, PDF), the SAP Business Suite 7 maintenance page, the SAP Security Notes & News page, SAP’s Maintenance & Support Commitments page, the Frappe Cloud pricing page, the ERPNext repository on GitHub and the ERPNext documentation linked below.
A note on sources
SAP’s release strategy pages, the Product Availability Matrix and most SAP Notes need an SAP customer sign-in. We rely on SAP-owned public copies and SAP-published material listed above, and quote them rather than paraphrase where it matters. Confirm the status of your own installation in the Product Availability Matrix or with SAP.
What SAP says about ECC enhancement packages
| ECC 6.0 level | Maintenance status | Source |
|---|---|---|
| No enhancement package, or EHP 1 to 5 | Mainstream maintenance ended December 31, 2025; now in customer-specific maintenance | SAP’s “Maintenance Timelines for SAP ERP 6.0” post on SAP Community; SAP presentation “Managing SAP Business Suite 7 Extended Maintenance” (October 2026, PDF) |
| EHP 6, 7 or 8 (the latest three) | Mainstream maintenance until December 31, 2027; optional extended maintenance January 1, 2028 to December 31, 2030 at an extra two percentage points | SAP Business Suite 7 maintenance page; SAP presentation “Managing SAP Business Suite 7 Extended Maintenance” (October 2026, PDF) |
| SAP S/4HANA | SAP commits to at least one S/4HANA release in maintenance until the end of 2040 | SAP Business Suite 7 maintenance page |
SAP’s October 2026 presentation is explicit that extended maintenance “covers the three most recent enhancement packages”, and shows ERP 6 with EhP 0 to 5 going straight into customer-specific maintenance. There is no paid extension for EHP 5 and earlier.
What customer-specific maintenance actually means
SAP Note 52505 (the public copy is version 66, released August 19, 2024) defines the phase. Customer-specific maintenance starts automatically, does not have to be ordered, has no expiry date, and you keep paying your maintenance fee under your existing contract. The restrictions SAP lists:
- No delivery of legal changes. Tax, payroll and statutory reporting changes after the cut-off are not delivered for your release.
- No delivery of support packages.
- No guarantee for technological updates: for example no new kernel versions for new database and operating system versions, no new patches for non-ABAP components (Java, front end), and no support of new interfaces.
- Customer-specific problem processing. Known problems are still solved with existing SAP Notes, but if the error is new to SAP, “further processing is regarded as a consulting service subject to charge”. SAP says this applies to customer-specific enhancements in particular.
- No service level agreements for initial response times and corrective measures.
- Upgrade paths that existed before still work, but SAP does “not usually provide new or additional upgrade paths” for a release in this phase, and some upgrades may need several steps.
On security, SAP’s Security Notes page says that, as a rule, releases going into customer-specific maintenance are considered in the first 12 months for high-priority notes (CVSS 7.0 or higher), for support packages shipped within the last 24 months (SAP Note 3053725 has the detail). Read with the January 1, 2026 start, that window runs out around the end of 2026 by our reading; confirm the position for your system with SAP.
SAP’s own verdict
SAP’s October 2026 extended maintenance presentation describes customer-specific maintenance as “not suitable for regulated industries or high-compliance environments”. If you are audited on IT general controls, expect that sentence to be quoted back to you.
First, confirm your enhancement package level
SAP’s community post gives the quickest check: log on, open System > Status, open the product version details and find the component SAP_APPL. For SAP ERP 6.0 the first digit is 6 and the third digit is your enhancement package: 605 means EHP 5, 616 means EHP 6. Check every production system; groups often have one plant or subsidiary on an older pack.
While you are there, write down your database and operating system versions and when their vendors stop supporting them. SAP Note 52505 warns that SAP cannot support third-party software its maker no longer maintains, and that newer versions may not be supported for releases in customer-specific maintenance.
Your options, from least to most change
| Option | What it involves | Watch out for |
|---|---|---|
| Stay in customer-specific maintenance | Keep paying maintenance; build legal changes yourself or through a partner; harden and isolate the system | No legal changes, support packages or SLAs; SAP’s own “not suitable” warning for regulated environments |
| Upgrade to EHP 6, 7 or 8 | A technical upgrade puts the system inside SAP’s mainstream commitment to end of 2027, with optional extended maintenance to 2030 | A real project (testing every custom program); it buys time but does not remove the S/4HANA decision |
| Move to SAP S/4HANA or SAP Cloud ERP | System conversion or new implementation; SAP recommends running the SAP Readiness Check, which it says is included with your maintenance agreement at no extra cost | Quote-only; largest change; partner capacity |
| Reimplement on ERPNext | New implementation; migrate masters, open items and balances; archive ECC | Process fit, integrations, statutory reporting in your countries |
| Split the landscape | Under SAP’s July 2026 commitments, customers can split a landscape into Commercial Installations and choose different support models or providers per installation | SAP’s Landscape Split Program conditions; requests handled within six months |
That last row matters for groups. SAP’s Maintenance & Support Commitments page (effective July 10, 2026, following the European Commission decision) says each Commercial Installation can have a different SAP support model, a different provider, or no maintenance at all. It also lets customers terminate licences and maintenance for products where customer-specific maintenance is the only available phase, as listed in the Product Availability Matrix. Whether your installation qualifies is a question for SAP and your contract lawyer; we do not assume it does.
Running safely in customer-specific maintenance while you decide
Most EHP 5 sites will spend at least a year in this phase whatever they choose. Use that year deliberately:
- Own legal changes explicitly. List the tax, payroll, e-invoicing and statutory reporting changes due in your countries over the next 24 months, and assign each one to a named person or partner with a budget. SAP will not deliver them for your release.
- Freeze non-essential change. Every new Z-program adds work to whichever path you take later.
- Apply what is still available. Note 52505 warns that an obsolete support package level makes problems harder or impossible to correct. If support packages for your release exist in the download archive and you have not applied them, test and apply them now.
- Isolate and monitor. Restrict network access to the SAP servers, review users with broad authorisations, and log access. This is what your auditor will ask about.
- Keep the people. Document Basis and ABAP knowledge held by one or two individuals before they leave.
None of these is expensive, and all of them reduce the cost of the eventual move, whether to EHP 8, S/4HANA or ERPNext.
What moving an ECC site to ERPNext involves
A move from ECC to ERPNext is a reimplementation, not a conversion. In our projects the work splits into five streams:
- Design. Map company codes, plants, storage locations, cost centres and profit centres to ERPNext companies, warehouses, cost centres and accounting dimensions. Simplify where the SAP design was driven by SAP constraints rather than the business.
- Masters. Extract customers, vendors, materials, BOMs, routings and price conditions; clean them (SAP systems of this age often hold many inactive records); load through Data Import.
- Open items and balances. Open sales and purchase orders, open AR and AP, stock by warehouse and batch, fixed assets and general ledger balances at cutover.
- Interfaces and outputs. Rebuild IDoc and RFC interfaces against the Frappe REST API, and rebuild invoices, delivery notes and labels as print formats.
- History. Keep ECC read-only for a defined period or extract history to a reporting database, and agree retention with finance and audit before cutover.
How ECC concepts map to ERPNext
| SAP ECC concept | ERPNext equivalent | What to test |
|---|---|---|
| Company codes | Companies, with ERPNext inter-company invoices documentation | Intercompany volume and automation |
| Cost centres, profit centres, internal orders | Cost centres and ERPNext accounting dimensions documentation | Mandatory dimensions and allocation cycles |
| Material master and plants | Items (ERPNext Item documentation) and warehouses as a tree (ERPNext Warehouse documentation) | Units of measure, valuation per warehouse |
| Batch management | Batches with expiry (ERPNext Batch documentation) and serial numbers (ERPNext Serial No documentation) | Batch determination rules |
| Pricing conditions | Pricing rules (ERPNext Pricing Rule documentation) | Your condition records at real volume |
| MRP | Production Plan (ERPNext Production Plan documentation) and Material Requests (ERPNext Material Request documentation) | Lot-sizing and lead-time logic |
| BOMs, routings, work centres | BOMs (ERPNext Bill of Materials documentation), ERPNext Routing documentation, ERPNext Workstation documentation | Alternative BOMs and routing versions |
| Production orders and confirmations | Work orders and job cards (ERPNext Work Order documentation, ERPNext Job Card documentation) | Backflushing and scrap |
| Quality management | Quality Inspection (ERPNext Quality Inspection documentation) | Inspection plans and certificates |
| Subcontracting | Subcontracting orders (ERPNext subcontracting documentation) | Components supplied to vendors |
| Z-programs, user exits, BAdIs | Custom fields, ERPNext Customize Form documentation, ERPNext Workflow documentation, Frappe Server Script documentation and custom Frappe apps | Which Z-objects are still used |
| IDocs and RFC interfaces | Frappe REST API (Frappe Framework REST API documentation) | Every interface partner and volume |
Data moves through ERPNext Data Import documentation, the ERPNext Chart of Accounts documentation importer, ERPNext opening balance documentation and ERPNext Stock Reconciliation documentation. As with any move off SAP, it is a reimplementation: keep ECC read-only or extract history to a reporting store for audit.
Where staying with SAP is the better answer
- Your ECC is the group core, integrated with many SAP and non-SAP systems, and other entities depend on it. Replacing it with ERPNext is not a mid-size project.
- You operate in many countries with SAP-delivered localisations, or in a regulated industry where validated processes and audit trails are built around SAP.
- You rely on SAP-specific depth: variant configuration, complex pricing procedures, advanced planning, warehouse management or industry solutions.
- You can upgrade to EHP 8 quickly and plan S/4HANA calmly. For many sites, the EHP upgrade is the lowest-risk way out of customer-specific maintenance.
ERPNext makes sense when the site is mid-size, processes are close to standard, the Z-program list is mostly reports and forms, and the business is open to a reimplementation rather than a technical conversion.
What it costs
| Item | Price | Source |
|---|---|---|
| ECC maintenance in customer-specific maintenance | Your existing contract fee continues; SAP Note 52505 says new problems may be charged as consulting | SAP Note 52505 (public PDF copy, version 66, released Aug 19, 2024) |
| Extended maintenance (EHP 6 to 8 only) | Two extra percentage points on the maintenance base; SAP’s example: 22% Enterprise Support becomes 24% | SAP presentation “Managing SAP Business Suite 7 Extended Maintenance” (October 2026, PDF) |
| SAP S/4HANA or SAP Cloud ERP | Quote-only; no public price, so no estimate | SAP |
| ERPNext | No licence fee (GPL-3.0) | ERPNext repository on GitHub |
| ERPNext on Frappe Cloud | Sites from $5/month, servers from $40/month (indicative £3.78 / £30.22) | Frappe Cloud pricing page |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.78) and servers from $40 a month (about £30.22), checked on Nov 15, 2026. The GBP figures are indicative conversions, not Frappe prices.
Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3238 per £1 for 12 Nov 2026, the latest published figure when we checked on Nov 15, 2026. They are not official UK prices: the vendor does not publish a GBP list price for these items, and your invoice currency, rate and VAT treatment may differ.
The honest comparison is five-year cost for three scenarios: EHP upgrade then S/4HANA later, S/4HANA now, and ERPNext now. Include your annual SAP maintenance, internal SAP skills, hosting and every partner quote. We cannot give SAP numbers; your account executive can.
A 90-day plan for EHP 5 and earlier sites
Days 1 to 15: establish facts
Confirm SAP_APPL levels on every system, database and OS versions, and your maintenance contract terms. Ask SAP in writing what customer-specific maintenance covers for your installation and whether the July 2026 termination or landscape-split options apply.
Days 15 to 45: inventory
List Z-programs, enhancements, interfaces, forms and reports with usage data. Mark each as keep, replace with standard, or drop. Run the SAP Readiness Check if S/4HANA is on the table.
Days 45 to 75: two quotes and a fit test
Get a partner quote for an EHP 8 upgrade and for S/4HANA. In parallel, rebuild one product line in ERPNext with real data: items, BOMs, routings, a month of orders, pricing and cost centres.
Days 75 to 90: decide
Compare risk, five-year cost and fit gaps. If you choose ERPNext, plan go-live at a period or year end with at least one parallel month-end; if you choose SAP, lock the EHP upgrade dates.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| You need to exit customer-specific maintenance fast and keep SAP | Upgrade to EHP 6 to 8 | Returns you to SAP’s mainstream commitment to end of 2027 |
| ECC is the group core with many integrations | SAP S/4HANA (after an EHP upgrade if needed) | A replacement is too disruptive |
| Mid-size site, standard processes, few countries | ERPNext (price all three) | No licence fee; reimplementation is proportionate |
| Subsidiary on old EHP inside a larger SAP group | ERPNext as a second tier, or EHP upgrade | See our two-tier ECC guide |
| Regulated industry with validated SAP processes | Stay with SAP | Revalidation cost and risk |
Best for, and wrong choice when
ERPNext is best for
Mid-size manufacturers and distributors on ECC EHP 5 or earlier, in one or a few countries, with mostly standard processes, a Z-program list they are willing to cut and no appetite for an S/4HANA programme.
An EHP upgrade or S/4HANA is best for
Sites where SAP is the group core, heavily integrated or regulated, or where SAP-specific functionality such as variant configuration or advanced warehouse management is central.
ERPNext is the wrong choice when
You need SAP-delivered localisations in many countries, validated processes, or deep integration with other SAP systems that would all need rebuilding.
Frequently asked questions
Is SAP ECC on EHP 5 still supported?
It is in customer-specific maintenance. SAP says mainstream maintenance for SAP ERP 6.0 without an enhancement package or on EHP 1 to 5 ended on December 31, 2025. You can still raise support cases and receive known fixes, but SAP Note 52505 says legal changes and support packages are no longer delivered.
What is customer-specific maintenance?
SAP’s final maintenance phase. Per SAP Note 52505 it starts automatically, has no end date and you keep paying your maintenance fee, but there are no legal changes, no support packages, no guaranteed technology updates and no response-time SLAs, and new problems may be charged as consulting.
Can I buy extended maintenance for EHP 5?
No. SAP’s optional extended maintenance from 2028 to 2030 covers only the three most recent enhancement packages, EHP 6, 7 and 8.
How do I check my enhancement package?
Open System > Status, view the product version details and find SAP_APPL. The third digit is the enhancement package: 605 is EHP 5, 616 is EHP 6.
Does upgrading to EHP 8 help?
Yes, as a bridge. Systems on EHP 6 to 8 are inside SAP’s mainstream maintenance commitment to December 31, 2027, with optional extended maintenance to 2030. It is a technical project with full regression testing.
How much does SAP S/4HANA cost?
SAP does not publish S/4HANA prices, so we give no estimate. Ask SAP or a partner for a quote on your scope.
Can ERPNext replace SAP ECC?
For a mid-size, single-country or few-entity manufacturer or distributor with standard processes, often yes, as a reimplementation. It is not a like-for-like replacement for a global, integrated or regulated SAP core.