SAP Business All-in-One maintenance ends with ECC: the ERPNext path for mid-market SAP sites
Short answer
SAP’s Business Suite 7 maintenance page says SAP will provide mainstream maintenance until the end of 2027 for the Business Suite 7 core applications, “which are also core applications of SAP Business All-in-One”, including the latest three enhancement packages of SAP ERP 6.0. Optional extended maintenance runs from 2028 to the end of 2030 at a premium of two percentage points on the maintenance basis; without it, systems move to customer-specific maintenance (checked Nov 16, 2026). SAP also says ERP 6.0 without an enhancement package or on EHP 1 to 5 left mainstream maintenance on December 31, 2025. SAP’s destination is S/4HANA. For a mid-market All-in-One site with one or a few companies, standard processes and a partner who packaged the system years ago, S/4HANA can be more system than you need. ERPNext is worth pricing in that case; it is the wrong choice if you rely on deep SAP-specific functionality or a group mandate to stay on SAP. SAP is quote-only, so we give no SAP estimate.
Contents
- Who this guide is for
- What SAP actually says about All-in-One
- What customer-specific maintenance means
- Ten questions to put to your SAP partner
- Your options
- When S/4HANA is oversized for a mid-market site
- How SAP ERP areas map to ERPNext
- What a migration from SAP to ERPNext moves
- Costs: what is published
- Where staying with SAP is the better answer
- A practical plan for All-in-One sites
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for finance directors, operations leads and IT managers at small and mid-sized companies that run SAP Business All-in-One: SAP ERP 6.0 sold and implemented for the mid-market, typically by an SAP partner and often with an industry package on top. Many of these systems went live more than a decade ago and have been supported by the same partner ever since.
We implement ERPNext. For some All-in-One sites, staying with SAP is the right answer, and we say where below. For larger, multi-entity ECC estates read our SAP ECC end of maintenance guide; if your system is on enhancement package 5 or earlier, read our SAP ECC EHP 5 guide too. The legacy ERP end-of-support hub lists every vendor date we have confirmed.
Sources, checked on Nov 16, 2026: the SAP Business Suite 7 maintenance page, SAP’s “Maintenance Timelines for SAP ERP 6.0” post on SAP Community, SAP Note 52505 (public PDF copy, version 66, released Aug 19, 2024), the Frappe Cloud pricing page, the ERPNext repository on GitHub and the ERPNext documentation linked below.
What we do not estimate
SAP licences, S/4HANA subscriptions, extended maintenance fees and implementation work are quoted per customer. We give no SAP estimate and no implementation estimate for either path.
What SAP actually says about All-in-One
| Item | What SAP states | Source |
|---|---|---|
| Mainstream maintenance | Until end of 2027 for Business Suite 7 core applications, “which are also core applications of SAP Business All-in-One”, including the latest three enhancement packages of SAP ERP 6.0 | SAP Business Suite 7 maintenance page |
| Extended maintenance | Optional, from beginning of 2028 to end of 2030; premium of two percentage points on the maintenance basis for the Business Suite 7 scope | SAP Business Suite 7 maintenance page |
| Without extended maintenance | Customer-specific maintenance for Business Suite 7 applications | SAP Business Suite 7 maintenance page |
| ERP 6.0 without an EHP or on EHP 1 to 5 | Mainstream maintenance ended December 31, 2025; now customer-specific maintenance | SAP’s “Maintenance Timelines for SAP ERP 6.0” post on SAP Community |
| SAP’s destination | S/4HANA, with an innovation commitment until end of 2040 | SAP Business Suite 7 maintenance page |
In plain terms: an All-in-One system’s maintenance is the maintenance of the SAP ERP 6.0 underneath it. What matters is your enhancement package. SAP’s post explains how to check: open the system status, look at the SAP_APPL component, and read the third digit of the release (617 means EHP 7). On EHP 6, 7 or 8 you have mainstream maintenance until the end of 2027. On EHP 5 or below you are already in customer-specific maintenance.
Partner industry packages and add-ons on top of SAP ERP are a separate question. Their support depends on the partner that sells them, not on SAP’s page. Ask your partner in writing what they will support after 2027.
What customer-specific maintenance means
SAP Note 52505 (public copy, version 66) describes the scope. You keep paying your maintenance fee, and SAP still handles known problems, but:
- No delivery of legal changes, which matters for payroll, tax reporting and e-invoicing.
- No delivery of support packages.
- No guarantee of technology updates, such as new kernel versions for new database or operating system versions, or new patches for non-ABAP components.
- No support of new interfaces.
- New problems not yet known to SAP may be charged, “in particular” for customer-specific enhancements.
- Service level agreements for initial response and corrective measures are no longer delivered.
For an All-in-One site, the legal-change point usually decides the timeline. If your country’s tax or reporting rules change after your system leaves mainstream maintenance, the fix is yours or your partner’s to build.
Ten questions to put to your SAP partner
Most All-in-One customers deal with SAP through the partner that implemented them. Get these answers in writing before you decide; they are the same questions whether you then choose S/4HANA or ERPNext:
- Which SAP_APPL release and enhancement package are we on, and which support package level?
- Are we in mainstream or customer-specific maintenance today, and from what date?
- What would extended maintenance from 2028 cost us under our contract, and by when must we order it?
- Which partner add-ons and industry-package objects do we run, and will you support them after 2027?
- How many custom ABAP objects do we have, and how many are used? (The SAP Readiness Check helps here.)
- Which legal and tax changes do we expect in our countries over the next three years, and who builds them if SAP no longer delivers them?
- What do our operating system and database versions mean for kernel support in customer-specific maintenance?
- What would a move to S/4HANA involve for us: conversion or new implementation, on-premises or SAP’s cloud?
- What are the options for keeping our SAP history available for audits after a move, and what do they cost?
- What is the notice period on our SAP and partner support contracts?
The last two answers matter for an ERPNext plan as much as for an SAP one: you will need history for audits, and you do not want to pay maintenance on a system you have already left.
Your options
| Option | What it involves | Best when |
|---|---|---|
| Upgrade to EHP 8 and buy extended maintenance | Stay on SAP ERP 6.0 to end of 2030, at the premium SAP states | You need time; S/4HANA is the plan but not yet |
| S/4HANA (conversion or new implementation) | SAP’s successor, on-premises or in SAP’s cloud | You want to stay SAP long term and can fund the move |
| Stay in customer-specific maintenance | Keep running with the restrictions above | Short bridge only; check legal-change exposure |
| ERPNext | Reimplement on open source; self-hosted or Frappe Cloud | One or a few companies, mostly standard processes, cost pressure |
SAP recommends running the SAP Readiness Check first; SAP’s post says it is included at no additional cost with your maintenance agreement. Run it even if you are leaning towards ERPNext. It tells you how much custom code and add-on scope you carry, which you need for either decision.
When S/4HANA is oversized for a mid-market site
S/4HANA is SAP’s strategic product and a strong platform. Whether it is right for you depends on what you actually use. Signs that a smaller ERP may serve you better:
- You run one to three company codes, in one or two countries.
- Your users mainly work in finance, sales, purchasing, inventory and straightforward production, with few SAP-specific capabilities in daily use.
- Your custom code is mostly reports, forms and interfaces, not changes to core postings.
- Your SAP partner relationship is the main source of SAP skills; you have no in-house SAP team.
- The cost of the move to S/4HANA is large relative to your IT budget.
Signs that S/4HANA is the right answer: a parent or customers that require SAP, advanced warehouse, planning or production functions in daily use, regulated processes validated on SAP, or many company codes with complex consolidation.
How SAP ERP areas map to ERPNext
| SAP ERP area | ERPNext | What to test |
|---|---|---|
| FI general ledger, AP, AR, asset accounting | Accounting, chart of accounts, payment entries, assets (ERPNext Chart of Accounts documentation, ERPNext Payment Entry documentation, ERPNext Asset documentation) | Your month-end close and statutory reports |
| CO cost centres, profit centres | Cost centres, accounting dimensions, budgets (ERPNext Cost Center documentation, ERPNext accounting dimensions documentation, ERPNext Budget documentation) | Your management P&L by segment |
| SD sales orders, pricing conditions, billing | Sales orders, price lists, pricing rules, sales invoices (ERPNext Sales Order documentation, ERPNext Pricing Rule documentation, ERPNext Sales Invoice documentation) | Reprice 200 historical lines |
| MM purchasing, inventory, valuation | Material requests, purchase orders, receipts, stock ledger (ERPNext Material Request documentation, ERPNext Purchase Order documentation, ERPNext Stock Ledger documentation) | Goods receipt to invoice matching |
| PP BOMs, routings, production orders | BOMs, routings, work orders, job cards (ERPNext Bill of Materials documentation, ERPNext Routing documentation, ERPNext Work Order documentation, ERPNext Job Card documentation) | One product family end to end |
| QM inspections | Quality inspection (ERPNext Quality Inspection documentation) | Incoming and final inspection |
| Batch and serial management | Batches and serial numbers (ERPNext Batch documentation, ERPNext Serial No documentation) | Traceability report for a recall scenario |
| Multiple company codes, intercompany | Multiple companies, inter-company invoices (ERPNext inter-company invoices documentation) | Intercompany sale and elimination |
| Custom ABAP reports and forms | Report builder, print formats, server scripts, custom apps (Frappe Server Script documentation) | Your top 10 reports and forms |
Gaps to look for: country-specific statutory reports and e-invoicing (test them for your countries in a pilot), advanced planning, and any process your partner’s industry package handles that standard ERPNext does not.
What a migration from SAP to ERPNext moves
There is no SAP-to-ERPNext converter we would recommend. A migration extracts data from SAP (standard reports, table downloads or your partner’s extraction tools), transforms it and loads it with ERPNext Data Import (ERPNext Data Import documentation):
- Masters: customers, vendors, materials, BOMs, routings, price conditions, chart of accounts and cost centres.
- Open items: open sales and purchase orders, open AR and AP items (ERPNext opening balance documentation).
- Balances: opening trial balance per company and stock on hand per plant and storage location (ERPNext Stock Reconciliation documentation).
- History: keep SAP read-only, or extract to a reporting database; do not load years of documents into ERPNext.
Plan the archive early. SAP licence and infrastructure for a read-only system cost money; a reporting extract may be cheaper to keep for audit periods. Ask your partner and auditors what they need.
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| SAP extended maintenance | Two percentage points on top of the maintenance basis (SAP’s term); fee quoted per contract | Quoted per contract | SAP Business Suite 7 maintenance page |
| S/4HANA licences or subscription | Quote only; no estimate given | Quote only | SAP or partner |
| ERPNext software | No licence fee (GPL-3.0) | No licence fee | ERPNext repository on GitHub |
| ERPNext on Frappe Cloud, site plans | From $5 per month | About £3.78 (indicative) | Frappe Cloud pricing page |
| ERPNext on Frappe Cloud, dedicated servers | From $40 per month | About £30.22 (indicative) | Frappe Cloud server plans 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 16, 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 16, 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.
For an All-in-One site the comparison is not licence against licence. It is the five-year cost of SAP maintenance plus the S/4HANA move, against an ERPNext implementation, hosting and support, plus the cost of keeping SAP history available.
Where staying with SAP is the better answer
- Your parent company, auditors or key customers require SAP, or you share processes with group SAP systems.
- You use advanced SAP functions daily: complex variant configuration, advanced planning, extended warehouse management or industry-specific processes from your partner package.
- Your processes are validated on SAP for a regulator.
- You have an in-house SAP team and the business case for S/4HANA is already approved.
In those cases, the practical path is usually EHP 8 with extended maintenance as a bridge, then S/4HANA. ERPNext is the better path when you have a small SAP footprint, mostly standard processes, cost pressure and no mandate to stay on SAP.
A practical plan for All-in-One sites
Month 1: find out where you stand
Check SAP_APPL and your enhancement package. Run the SAP Readiness Check. Ask your partner, in writing, what they will support after 2027 and what extended maintenance would cost you.
Months 2 to 3: fit test
Load a copy of your masters into ERPNext and run a month of real transactions: sales, purchasing, production and month-end close. Score each area: standard, configure, build, or no-go.
Month 4: decide
Compare five-year cost and risk for EHP 8 plus extended maintenance, S/4HANA and ERPNext. Include the archive in every column.
Then: implement before your maintenance runs out
Go live at a financial year end if you can, with at least one month-end in parallel. Aim to finish before the end of 2027 if you are on EHP 6 to 8 and do not want to pay for extended maintenance.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| Group or customer mandate for SAP | S/4HANA (EHP 8 + extended maintenance as bridge) | Strategic fit outweighs cost |
| One to three companies, standard processes, no SAP team | Price ERPNext | Smaller system, no licence fee |
| On EHP 5 or below, legal changes needed soon | Decide now | Already in customer-specific maintenance |
| Heavy partner industry package in daily use | Stay SAP or test ERPNext very carefully | Package functions may have no equivalent |
| Need time to plan | EHP 8 + extended maintenance | Maintenance to end of 2030 at the stated premium |
Best for, and wrong choice when
ERPNext is best for
Mid-market All-in-One sites with one or a few companies, mostly standard finance, distribution and discrete manufacturing processes, no mandate to stay on SAP, and a wish to own their system without per-user licences.
SAP (EHP 8 then S/4HANA) is best for
Sites inside an SAP group, with validated or highly SAP-specific processes, or with an in-house SAP team and an approved S/4HANA case.
ERPNext is the wrong choice when
You rely on advanced SAP-only functions or a partner industry package with no ERPNext equivalent, statutory reporting in your countries is untested on ERPNext, or a parent company requires SAP.
Frequently asked questions
When does SAP Business All-in-One maintenance end?
SAP says Business Suite 7 core applications, which are also the core applications of SAP Business All-in-One, have mainstream maintenance until the end of 2027 for the latest three enhancement packages of SAP ERP 6.0, with optional extended maintenance until the end of 2030 (checked Nov 16, 2026).
What if my All-in-One system is on EHP 5 or earlier?
SAP says mainstream maintenance for ERP 6.0 without an enhancement package or on EHP 1 to 5 ended on December 31, 2025. Those systems are in customer-specific maintenance: no legal changes or support packages.
How do I find my enhancement package?
In the system status, check the SAP_APPL component. For ERP 6.0 the third digit of the release is the enhancement package; 616 means EHP 6.
How much does SAP extended maintenance cost?
SAP describes a premium of two percentage points on the maintenance basis for the Business Suite 7 scope. The actual fee depends on your contract; we give no estimate.
Who supports my partner’s industry package after 2027?
That depends on your partner, not on SAP’s maintenance page. Ask them in writing.
Can ERPNext replace SAP for a mid-sized company?
Often, for finance, sales, purchasing, inventory and discrete manufacturing with one or a few companies. Test statutory reporting and any partner-package functions in a pilot first.
What does ERPNext cost?
No licence fee (GPL-3.0). Frappe Cloud lists site plans from $5 a month and servers from $40 a month (checked Nov 16, 2026). Implementation is separate.