SAP ECC end of maintenance (2027): is ERPNext a realistic S/4HANA alternative for subsidiaries and mid-size manufacturers?
Short answer
SAP’s Business Suite 7 maintenance page says SAP provides mainstream maintenance until the end of 2027 for Business Suite 7 core applications, including the latest three enhancement packages of SAP ERP 6.0 (ECC). After that, customers can buy optional extended maintenance from the start of 2028 to the end of 2030 for a premium of two percentage points on the maintenance basis. Anyone who does not take it moves to customer-specific maintenance (checked Nov 12, 2026). SAP’s answer is S/4HANA, which SAP sells on quote only; we give no estimate for it. Our view: ERPNext is not a realistic replacement for a group-wide SAP core with complex finance, global template governance or deep SAP-specific industry processes. It is a realistic option in a two-tier model: ERPNext runs smaller subsidiaries, plants or sales entities, and the group keeps SAP (ECC under extended maintenance, then S/4HANA) at the centre. It can also suit a 100 to 1,000 person manufacturer whose ECC use is mostly finance, purchasing, inventory and production orders. ERPNext has no licence fee (GPL-3.0), and Frappe Cloud hosting starts at $5 a month for a site and $40 a month for a server.
Contents
- Who this guide is for
- What SAP actually says about 2027 and 2030
- The two-tier model, and why it is the honest place for ERPNext
- Where ERPNext fits a subsidiary or mid-size plant, and where it does not
- Designing the integration back to the SAP core
- What we can and cannot say about cost
- S/4HANA for everything, or two-tier with ERPNext: a decision table
- A pilot plan for one subsidiary
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for CIOs, group finance leads and IT directors at two kinds of organisation. The first is a group that runs SAP ERP 6.0 (ECC) at the centre and has smaller subsidiaries, plants or sales entities on the same system, or on spreadsheets and local packages. The second is a manufacturer of roughly 100 to 1,000 people that runs ECC itself and is asking whether S/4HANA is the only sensible next step.
It is part of our series on legacy ERP deadlines. The legacy ERP end-of-support hub lists every vendor date we have confirmed. If your SAP estate also includes Solution Manager for IT service management, read our SAP Solution Manager ITSM replacement guide too; its 2027 timeline lines up with ECC’s.
Sources: the SAP Business Suite 7 maintenance page for SAP dates and terms; the ERPNext repository on GitHub, Frappe Cloud pricing page, ERPNext inter-company invoices documentation, ERPNext accounting dimensions documentation, ERPNext Bill of Materials documentation, ERPNext Work Order documentation, ERPNext subcontracting documentation, ERPNext Landed Cost Voucher documentation, Frappe Framework REST API documentation and ERPNext Data Import documentation for ERPNext. All checked on Nov 12, 2026.
What we do not do here
SAP does not publish S/4HANA list prices, so we give no S/4HANA estimate and no “savings” figure. We also do not estimate implementation fees for either option. They depend on your entities, modules, integrations and data, and any number we gave without seeing them would be invented.
What SAP actually says about 2027 and 2030
SAP’s Business Suite 7 maintenance page is short and specific. Here is what it states, in plain terms:
| Milestone | What SAP states | When |
|---|---|---|
| Mainstream maintenance for Business Suite 7 core applications | Includes the latest three enhancement packages of SAP ERP 6.0, CRM 7.0, SCM 7.0 and SRM 7.0, and SAP Business Suite powered by SAP HANA. These are also the core applications of SAP Business All-in-One | Until end of 2027 |
| Optional extended maintenance | For customers who need support during longer conversion phases to S/4HANA. Premium of two percentage points on the maintenance basis, for all support offerings in the Business Suite 7 scope | Beginning of 2028 to end of 2030 |
| Customer-specific maintenance | For customers who do not opt for extended maintenance, or once extended maintenance has ended | From 2028 (no extended maintenance) or from 2031 |
| S/4HANA maintenance commitment | SAP states that until 2040 there will always be at least one S/4HANA release in maintenance | Until end of 2040 |
Three practical points follow. First, the 2027 date applies to the latest three enhancement packages of ERP 6.0. For ECC that means EHP 6, 7 and 8. Systems on older enhancement packages are outside this commitment. We cover that case separately in the hub, because SAP’s detail for it sits behind a customer sign-in.
Second, extended maintenance is a bridge, not a destination. SAP frames it as support for “longer conversion phases” to S/4HANA. It buys three years, and the two-point premium applies to your whole Business Suite 7 maintenance basis, not just the parts you still need.
Third, customer-specific maintenance is the fallback. We will not paraphrase what it includes beyond what SAP’s public page says. Get the exact terms from your SAP account team in writing, because they decide how much risk you carry if a conversion slips.
As of Nov 12, 2026, that leaves about 13 months of mainstream maintenance. A group that wants a subsidiary off ECC before 2028 without paying the premium has roughly one planning-and-pilot cycle left. That is enough for a small entity and tight for anything larger.
The two-tier model, and why it is the honest place for ERPNext
Two-tier ERP means running one ERP at the group level (tier 1) and a lighter ERP in smaller subsidiaries, plants or sales offices (tier 2). The two are connected by integrations for financial results, inter-company trade, master data and sometimes orders. Many SAP groups already work this way in practice: the core sits on ECC, and smaller entities run something local because rolling the full SAP template out to a 40-person sales office never made economic sense.
The 2027 deadline forces a decision for every entity on ECC. The default plan is to convert everything to S/4HANA. The alternative is to convert or re-implement the core on S/4HANA, and move smaller entities to a tier-2 ERP instead of carrying them through the conversion. ERPNext is a credible tier-2 candidate for four reasons:
- No licence fee per user or per entity. ERPNext is GPL-3.0. Adding a subsidiary adds hosting and support cost, not a new licence negotiation.
- Multi-company in one site. Several legal entities can run in one ERPNext site, each with its own chart of accounts, and ERPNext supports inter-company invoices between them.
- Manufacturing and stock included. Bills of materials, work orders, subcontracting, batches, serials and landed cost are part of the standard product, not add-ons.
- Open APIs. Every ERPNext document type is exposed through the Frappe REST API, which makes the integration back to SAP a normal integration project rather than a proprietary connector purchase.
Where we draw the line
We do not recommend ERPNext as the tier-1 replacement for a group-wide SAP core with complex finance (group-wide controlling, transfer pricing at scale, multi-GAAP), heavy SAP industry solutions, or thousands of users on a global template. In those estates the real choice is between S/4HANA editions, partners and timelines, and pretending otherwise would waste your time.
Where ERPNext fits a subsidiary or mid-size plant, and where it does not
| ECC area | ERPNext fit for a tier-2 entity | What to test in the pilot |
|---|---|---|
| FI: general ledger, AP, AR, bank, assets | Strong for single-entity and multi-entity accounting | Mapping to group chart of accounts; period close; asset depreciation methods |
| CO: cost centres, profit centres, internal orders | Partial: cost centres and accounting dimensions cover most tier-2 needs | Whether your controlling model needs more than cost centres plus dimensions |
| MM: purchasing, inventory, valuation | Strong | Valuation method, landed cost, approval rules |
| SD: quotes, orders, deliveries, billing, pricing | Strong for standard B2B flows | Complex pricing conditions and rebates |
| PP: BOMs, routings, production orders | Good for discrete manufacturing at small and mid scale | Routing depth, capacity planning, subcontracting flows |
| QM: inspections | Basic quality inspection available | Regulatory quality needs (for example batch release) |
| PM: plant maintenance | Limited; asset maintenance features are basic | Whether a separate maintenance tool is needed |
| WM / EWM: warehouse management | Basic multi-warehouse stock, no SAP-style bin strategies | Pick, put-away and bin logic |
| HR and payroll | Do not assume parity; local payroll is often separate | Country payroll and statutory reporting |
| Industry solutions (IS-Oil, IS-Retail and so on) | Not equivalent | Usually a reason to stay on SAP for that entity |
A pattern we see often: a plant or subsidiary uses a small part of what ECC offers, mainly FI, MM, SD and simple PP, but carries the full SAP support and upgrade cost. That is the entity to pilot first. A plant that depends on SAP-specific warehouse logic, complex variant configuration or an industry solution is not.
Designing the integration back to the SAP core
In a two-tier model, the integration is the project. Get it wrong and finance ends up reconciling two systems by hand every month. These are the flows to design, in rough order of importance:
| Flow | Direction | Typical approach |
|---|---|---|
| Financial results (trial balance or journal summaries) for consolidation | ERPNext to SAP | Period-end summary by group account and entity, mapped from the ERPNext chart of accounts |
| Inter-company sales and purchases | Both ways | Inter-company orders and invoices with matching references on both sides |
| Material and product master | SAP to ERPNext (usually) | Group-owned master pushed to subsidiaries; local items allowed only where the group agrees |
| Customer and supplier master | Depends on ownership | One owner per record; never two systems creating the same customer |
| Exchange rates | SAP or treasury to ERPNext | Daily or monthly rate load into ERPNext currency exchange records |
| Orders to or from group plants | Both ways | Purchase order in ERPNext becomes a sales order in SAP, or the reverse |
On the ERPNext side, the Frappe Framework REST API documentation gives create, read, update and list endpoints for every document type, authenticated with API keys or OAuth. On the SAP side, use whatever your SAP team already supports for inbound and outbound integration. We do not prescribe a middleware product; if the group already runs one, use it.
Two rules save most of the pain. First, decide the system of record for every master before you build anything. Second, consolidate on mapped summaries, not on every ERPNext transaction pushed into SAP. Pushing everything recreates the cost you were trying to avoid.
What we can and cannot say about cost
| Cost line | S/4HANA (converting the entity) | ERPNext (tier 2) |
|---|---|---|
| Software licence | Quote-only from SAP; no published list price | None (GPL-3.0) |
| Maintenance or subscription | Quote-only from SAP | None for the software; optional paid support from Frappe or a partner |
| Hosting | Depends on deployment and contract | Frappe Cloud: sites from $5 / month, servers from $40 / month (USD published); or self-host |
| Implementation | Partner quote | Partner quote |
| Integration to the group core | Usually lower if the entity is inside the same SAP system | A real line item: design, build and run |
| ECC extended maintenance while you move | Two-point premium on the Business Suite 7 maintenance basis, 2028 to 2030, if taken | Same premium applies to the group until all ECC scope is off it |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.75) and servers from $40 a month (about £30.00), checked on Nov 12, 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.3335 per £1 for 10 Nov 2026, the latest published figure when we checked on Nov 12, 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 cost argument for ERPNext in a subsidiary is not “ERPNext is cheaper than S/4HANA”, because nobody outside your SAP contract can quantify the S/4HANA side. The argument is narrower: for an entity that uses a small slice of SAP, you stop paying for the slice you do not use, and the integration cost is the price of that saving. Ask your SAP account team to quote the S/4HANA scope with and without the tier-2 entities. Compare the difference with an ERPNext quote for the same entities, including integration. That gives you a decision based on two real numbers.
S/4HANA for everything, or two-tier with ERPNext: a decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| The entity shares plants, stock and production with the core in real time | S/4HANA (keep it in the core) | Splitting tightly coupled operations creates more integration than it saves |
| The entity is a sales office, small plant or acquired business with its own processes | Two-tier with ERPNext (price both) | Small footprint, local processes, no need for the full template |
| You depend on an SAP industry solution in that entity | S/4HANA | No ERPNext equivalent |
| The group expects acquisitions that need a fast, repeatable ERP template | Two-tier with ERPNext | A light template you can stand up per entity without licence negotiation |
| Group finance insists on one system for audit and controls | S/4HANA | Two-tier needs agreed controls across two systems |
| You are a stand-alone 100 to 1,000 person manufacturer using mainly FI, MM, SD and simple PP | ERPNext worth a pilot (price both) | You may be paying for SAP depth you do not use |
| Your team cannot staff an integration and a second ERP support model | S/4HANA | Two-tier adds a second system to run |
A pilot plan for one subsidiary
| Phase | Work | Done when |
|---|---|---|
| Entity selection (2–4 weeks) | Score entities on SAP usage, coupling to the core, industry solutions and headcount; pick one | One entity and a sponsor agreed |
| Discovery (6–8 weeks) | Map the entity’s FI, MM, SD and PP use to ERPNext; agree system of record for each master; design integration flows | Signed scope, mapping workbook and integration design |
| Pilot build (8–12 weeks) | Configure the entity, load masters and open items, build consolidation and inter-company flows | Entity closes a pilot month in ERPNext and group consolidation accepts it |
| Parallel or dress rehearsal (1–2 cycles) | Trial migration from ECC, reconcile balances and open items | Balances and open items match ECC |
| Cutover (period start) | Close the period in ECC, load openings, go live, switch integrations | First month closed and consolidated |
| Decide the next entities | Review cost, effort and control issues from the pilot | A go or no-go for the next wave, based on your own numbers |
These durations are our planning ranges for a small, loosely coupled entity, not a promise. Starting discovery in early 2027 gives a realistic chance of moving a first entity before mainstream maintenance ends. Anything later probably means at least some extended-maintenance years for the group anyway. That is fine, as long as you plan for it rather than discover it.
Data migration from ECC
Extract masters and open items from ECC with whatever your SAP team already uses for data extraction. Load them with the ERPNext Data Import documentation (CSV or Excel, insert or update). Post opening balances against a temporary opening account, as ERPNext’s opening balance documentation describes. Load open receivables and payables as opening invoices, and opening stock through stock reconciliation. Keep ECC history in ECC or an archive; there is no reason to load ten years of SAP documents into a subsidiary ERP.
Best for, and wrong choice when
ERPNext is a realistic option when
It runs tier-2 subsidiaries, sales entities or small plants that use a fraction of ECC, or a stand-alone mid-size manufacturer whose SAP use is mainly finance, purchasing, inventory, sales and simple production, and you will fund integration and a proper pilot.
ERPNext is the wrong choice when
The entity is tightly coupled to the core in real time, depends on an SAP industry solution or advanced warehouse logic, or group controls require one system. It is also wrong as the replacement for a group-wide SAP core.
Converting everything to S/4HANA is the wrong choice when
Small entities would carry the full SAP template and cost only because they happen to be on ECC today, and nobody has priced the alternative.
Frequently asked questions
When does SAP ECC maintenance end?
SAP’s Business Suite 7 maintenance page says mainstream maintenance for Business Suite 7 core applications, including the latest three enhancement packages of SAP ERP 6.0, runs until the end of 2027. Optional extended maintenance is available from the start of 2028 to the end of 2030 (checked Nov 12, 2026).
What does SAP ECC extended maintenance cost?
SAP states a premium of two percentage points on the maintenance basis for all support offerings in the Business Suite 7 scope, available from 2028 to the end of 2030. The base itself depends on your SAP contract.
What happens if we do not take extended maintenance?
SAP says customers who do not opt for extended maintenance, or whose extended maintenance has ended, receive customer-specific maintenance. Ask your SAP account team for its exact terms in writing.
Can ERPNext replace SAP ECC?
For a group-wide SAP core with complex finance or industry solutions, we do not think so. For subsidiaries, sales entities, small plants or a mid-size manufacturer using mainly finance, purchasing, inventory, sales and simple production, it can, usually in a two-tier model.
How much does S/4HANA cost?
SAP sells S/4HANA on quote only and does not publish list prices, so we give no estimate. Ask SAP to quote your scope with and without the entities you might move to a tier-2 ERP.
How does ERPNext integrate with SAP?
Through the Frappe REST API on the ERPNext side and your existing SAP integration tools on the other. Most two-tier designs exchange financial summaries for consolidation, inter-company documents, masters and exchange rates.
Is ERPNext free?
ERPNext is open source under GPL-3.0 with no licence fee. You pay for hosting (Frappe Cloud lists sites from $5 a month and servers from $40 a month), implementation, integration and support.