Still on SAP R/3: replacing a legacy SAP subsidiary system with ERPNext

Short answer

SAP R/3 releases from before SAP ERP 6.0 (the R/3 4.x line, including R/3 Enterprise) are long out of mainstream maintenance. SAP’s maintenance strategy pages that list release-specific dates need an SAP sign-in, so we give no end date here. What SAP does publish is the rule that applies once maintenance ends: in SAP Note 52505 (public copy, version 66), a release past mainstream or extended maintenance moves automatically into customer-specific maintenance, which has no legal changes, no support packages, no guaranteed technology updates, and “in some cases no direct upgrade to a current release”. You still pay the maintenance fee. Where an R/3 system is the group’s core ERP, the answer is a group-wide SAP S/4HANA or similar programme. But many surviving R/3 systems run a single subsidiary or a small plant. For those, a multi-step SAP upgrade is often out of proportion. The practical alternative is to archive the R/3 history, migrate open items and masters at a period end, and run the entity on ERPNext (open source, GPL-3.0, no licence fee), reporting summarised results to the group. SAP is quote-only, so we give no SAP estimate.

Choosing a platform? Get a free 30-minute advisory call.

Who this guide is for

This guide is for group CFOs, IT directors and SAP competence centre leads who still have an SAP R/3 system from before SAP ERP 6.0 running somewhere in the group, and for the finance and operations managers in the entity that uses it. These systems are rarer every year, but they survive in predictable places: a subsidiary that was never brought onto the group’s main SAP instance, an acquired company with its own SAP, a plant or regional business that “just works”, or a system kept alive for one country’s statutory books.

We implement ERPNext, so read our view with that in mind. If R/3 is still your group’s core ERP, this is not your guide: you need a group-level programme, and SAP S/4HANA or a comparable platform is the obvious candidate. Where ERPNext fits is the smaller case, an entity whose R/3 system can be retired rather than upgraded.

If you are on SAP ERP 6.0 rather than R/3, read our SAP ECC on EHP 5 or earlier guide or the SAP ECC end of maintenance guide. Mid-market SAP sites on a partner package should see SAP Business All-in-One. The legacy ERP end-of-support hub lists every vendor date we have confirmed.

Sources, checked on Nov 20, 2026: the SAP maintenance strategy page (sign-in required for release detail), 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 Frappe Cloud pricing page and Frappe Cloud server plans page, the ERPNext repository on GitHub, and the ERPNext documentation linked in each section.

What we can say about R/3 maintenance, and what we cannot

SAP publishes release-specific maintenance dates on its customer support website and in the Product Availability Matrix. Note 52505 itself points readers there. Both need an SAP sign-in to see release detail, and we did not find R/3 4.x dates on a public SAP page. So we do not give an end date for any R/3 release, and we do not repeat dates from third-party sites. Your SAP account team or your SAP sign-in will show the exact status of your release.

What SAP does say publicly is enough to plan with:

What SAP publishesWhereWhat it tells an R/3 site
R/3 sits between R/2 and SAP Business Suite 7 on SAP’s own timeline (R/3 shown at 1992)SAP presentation “Managing SAP Business Suite 7 Extended Maintenance”, October 2026R/3 is two product generations behind SAP’s current ERP
SAP ERP 6.0 with enhancement packages 0 to 5 is already in customer-specific maintenanceSame presentationEven R/3’s successor release is past mainstream maintenance at those levels
Business Suite 7 core applications (latest three EhPs) have mainstream maintenance until end of 2027, optional extended maintenance to end of 2030SAP Business Suite 7 maintenance pageThe end of SAP ERP 6.0 itself is now scheduled
After mainstream or extended maintenance ends, a release automatically enters customer-specific maintenance, which has no expiry dateSAP Note 52505R/3 4.x releases, long past mainstream maintenance, fall under this rule

Get a tailored shortlist and pricing review

Share your work email and we'll send you a replacement shortlist and cost review tailored to your user count and requirements. A member of our ERP team prepares it personally.

What customer-specific maintenance means in practice

SAP Note 52505 (“Support after end of mainstream maintenance or extended maintenance”, version 66, released Aug 19, 2024) lists the restrictions. During customer-specific maintenance:

  • No delivery of legal changes. Tax, payroll, statutory reporting and e-invoicing changes are your own problem.
  • No delivery of Support Packages.
  • No guarantee for technological updates, including no new kernel versions to support new database and operating system versions, and no new patches for non-ABAP components.
  • In some cases no direct upgrade to a current release; the upgrade must be performed in several steps. SAP does not usually provide new or additional upgrade paths for a start release in customer-specific maintenance, though paths provided earlier remain available.
  • No support of new interfaces.
  • Customer-specific problem processing. Known problems are still covered; for new problems not yet known to SAP, “the customer may have to pay for the expense of solving” them, especially for customer-specific enhancements.
  • No service level agreements for initial response times and corrective measures.

The note also says you must keep paying the maintenance fee under your contract, and warns that SAP cannot support third-party software (operating systems, databases) that its own maker no longer maintains. For an R/3 system, that last point is often the sharpest: the server, operating system and database underneath may be as old as the application.

Your realistic options for an R/3 entity

OptionWhat it involvesFits when
Bring the entity onto the group’s SAPMigrate the entity into the group S/4HANA or ERP 6.0 system as a new company codeThe group has a current SAP platform with capacity and a template for entities like this one
Multi-step SAP upgradeUpgrade the R/3 system in stages to a current release, then onwardsRarely worth it for a small entity; may be unavoidable if the R/3 system holds unusual, heavily customised processes the group still needs
Retire to ERPNextArchive R/3 history; migrate masters, open items and balances; run the entity on ERPNext as a second tierSmall or mid-size entity with standard finance, purchasing, sales and stock
Keep running R/3Accept customer-specific maintenance and infrastructure riskEntity being sold or closed soon

The first option is often the best one, and it is worth asking the group first. Where the group has no suitable SAP template, or the entity is too small to justify a full SAP rollout, the ERPNext route is worth pricing.

Step 1: archive the R/3 history

Retiring an old SAP system is two jobs. The first is making sure closed history stays available for audit and statutory retention without keeping R/3 alive as a live system.

Archive approachHow it worksWatch for
Read-only R/3 for the retention periodLock users to display access; keep the system on minimal infrastructureLicence and maintenance terms for read-only use; ageing infrastructure
SAP data archiving into archive filesUse SAP’s own archiving objects to move closed data out, with display through SAPStill needs a running SAP system to read the archive
Extract to a reporting databaseCopy the key tables (GL line items, open and cleared items, documents, assets, stock movements) into a modern database with saved reportsNeeds someone who understands the R/3 tables to design the extract once

Whichever approach you choose, write down the questions the archive must answer first: postings to an account in a period with their source documents, a supplier invoice and its payment, a customer’s history, an asset’s depreciation, an item’s movements, and the proof of opening balances in the new system. Agree the list and the retention period with your auditors before anything is built, and test the archive with real questions before R/3 is switched off.

Step 2: migrate open items and masters

The second job is moving only what the entity needs to keep trading. Everything closed stays in the archive.

R/3 dataERPNext targetApproach
Company codeCompanyOne per legal entity; see the ERPNext Chart of Accounts documentation
Chart of accounts and GL accountsChart of AccountsRebuild with group mapping kept in one place
Cost centres, profit centres, business areasCost centres and accounting dimensionsSee the ERPNext Cost Center documentation and ERPNext accounting dimensions documentation
GL balancesOpening balances at a period endTrial balance by account and dimension; see the ERPNext opening balance documentation
Open customer itemsOpening sales invoices per documentSo customers can be chased and paid against them
Open vendor itemsOpening purchase invoices per documentFor payment runs
Customer and vendor mastersCustomer and SupplierClean duplicates and blocked records first; see the ERPNext Customer documentation and ERPNext Supplier documentation
Material masters and plant/storage locationsItem and WarehouseActive materials only; see the ERPNext Item documentation and ERPNext Warehouse documentation
Stock on handStock ReconciliationQuantities and values at cutover; see the ERPNext Stock Reconciliation documentation
Open purchase and sales ordersPurchase Order and Sales OrderOpen lines only
Asset master and valuesAssetCost, accumulated depreciation, remaining life; see the ERPNext Asset documentation
Bills of material and routings (if the entity manufactures)Bill of Materials and RoutingReview before loading; see the ERPNext Bill of Materials documentation
Closed documents and historyNot migratedArchive

Masters and open items load through the ERPNext Data Import documentation from CSV or Excel templates. For an R/3 subsidiary, two or three full trial loads, each reconciled against R/3 reports (trial balance, open item lists, stock values), are usually realistic. The reconciliation between the final R/3 trial balance and the ERPNext opening balances, signed off by finance, is the most important document the project produces.

Running the entity on ERPNext as a second tier

An R/3 subsidiary almost always belongs to a group that runs something else, often a newer SAP system. ERPNext does not need a deep integration with it:

  • The entity runs day-to-day finance, purchasing, sales and stock in ERPNext.
  • At month end it sends summarised results, a trial balance by group account plus inter-company detail, to the group ledger by file or API.
  • Group account mapping lives in one place and is reviewed each close.

ERPNext supports multiple companies, multi-currency accounting and inter-company invoices in one site; see the ERPNext multi-currency accounting documentation and ERPNext inter-company invoices documentation. This is the same two-tier pattern described in our SAP ECC guide.

Where ERPNext fits an R/3 entity, and where it does not

If the R/3 entity usesERPNext fit
FI: GL, AP, AR, asset accounting, bankGood
CO: cost centres, simple profit centre reportingGood, with dimensions and cost centres
MM and SD: purchasing, sales orders, deliveries, billing, inventoryGood for standard processes
PP: discrete production with BOMs and routingsGood for standard make-to-stock and make-to-order; see the ERPNext Work Order documentation
Product costing with full variance analysis, CO-PAPartial; test with real data
Industry solutions, complex variant configuration, heavy EDIWeak; usually stay in SAP
HR and payroll on R/3Outside this guide; plan payroll separately

A fit test before you choose

Run these with your own data

  • List the R/3 modules and transactions the entity actually uses, from usage data if you can get it.
  • List every custom program, user exit and report, and mark which are still needed.
  • Load one month of the entity’s transactions into ERPNext and close the month.
  • Produce the group reporting pack from ERPNext and compare it with R/3.
  • Agree the archive approach and retention period with auditors.
  • Ask the group SAP team or SAP whether the entity can join the group’s current SAP system, and on what terms.

What ERPNext costs to run

ERPNext has no licence fee under GPL-3.0. You pay for hosting and implementation. Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.80) and servers from $40 a month (about £30.42), checked on Nov 20, 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.3148 per £1 for 18 Nov 2026, the latest published figure when we checked on Nov 20, 2026. They are not official UK prices: Frappe does not publish a GBP list price for these plans, and your invoice currency, rate and VAT treatment may differ.

We give no SAP figure: SAP licences, maintenance, S/4HANA subscriptions and upgrade projects are quoted per customer. We also give no implementation estimate on either side. When you compare, include the SAP maintenance fee you would stop paying for the R/3 entity, the cost of the archive, and the cost of keeping old infrastructure alive during any overlap.

A phased plan

PhaseWhat happens
1. ScopeModules in use, custom code, reports, retention rules, archive choice, group option checked
2. PilotOne month of transactions and one close in ERPNext
3. BuildChart and dimension mapping, group feed, integrations, print formats
4. Trial loadsTwo or three full loads, reconciled against R/3 reports
5. CutoverGo live at a period end, ideally a quarter or year end; R/3 set read-only
6. Archive and switch offHistory retained or extracted as agreed; R/3 infrastructure retired

Decision table

If this is true for youLean towardsWhy
R/3 is the group’s core ERPGroup SAP programmeToo central for an entity-level fix
Group has a current SAP template for entities like thisJoin the group SAP systemConsistency and shared support
Small entity, standard processes, no suitable group templateERPNext, archive and migrateSmall, well-defined project; no licence fee
Industry solution or complex variant configuration in daily useStay with SAPNo ERPNext equivalent
Entity being sold or closed within a yearKeep R/3, archive laterNo new project worth starting

Best for, and wrong choice when

ERPNext is best for

Subsidiaries, plants and acquired businesses still on an old R/3 system with standard finance, purchasing, sales and stock, where the group wants the system retired and has no suitable SAP template to move the entity into.

Staying with SAP is best for

Entities where R/3 is the core of the group’s operations, where SAP industry solutions or complex configuration are in daily use, or where the group can absorb the entity into a current SAP system.

ERPNext is the wrong choice when

The entity depends on SAP industry functionality, the group mandates SAP for every legal entity, payroll and HR are tightly bound into R/3 with no plan for them, or nobody in the entity can own the new system after go-live.

Want a second opinion before you commit? Our ERP Engineering practice runs fit tests like the one above on your own data, and we will tell you if SAP’s path is the better answer.

Frequently asked questions

When did SAP R/3 support end?

We do not give a date: SAP’s release-specific maintenance dates are behind an SAP sign-in, and we found no R/3 4.x dates on a public SAP page. SAP Note 52505 says releases past mainstream or extended maintenance move automatically to customer-specific maintenance, which has no expiry date.

What is SAP customer-specific maintenance?

The maintenance phase after mainstream or extended maintenance ends. Per SAP Note 52505: no legal changes, no support packages, no guaranteed technology updates, no SLAs, and possibly no direct upgrade path. You keep paying the maintenance fee.

Can SAP R/3 be upgraded to S/4HANA directly?

SAP Note 52505 says that for releases in customer-specific maintenance there may be no direct upgrade to a current release, in which case the upgrade takes several steps. Ask SAP for the path from your exact release.

What does archive and migrate mean for R/3?

Keep closed history in a read-only R/3 system, SAP archive files or an extracted reporting database, and move only masters, open items and balances into ERPNext at a period end.

Can ERPNext replace an SAP R/3 subsidiary system?

Often, if the entity uses standard finance, purchasing, sales and stock. Run it as a second tier that sends month-end results to the group.

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 (about £3.80 and £30.42 at the Bank of England rate for Nov 18, 2026; checked Nov 20, 2026). Implementation is separate. SAP is quote-only.

Still running a subsidiary on SAP R/3?

We map the entity’s masters and open items from R/3 into ERPNext, run one month-end with your data, and lay out the archive, so you can see the whole retirement before committing.

We'll get back to you shortly. We use your details only to reply to this request.