Oracle EBS 11i in 2026: retiring it to ERPNext for a subsidiary or small division
Short answer
Oracle’s Lifetime Support Policy for Applications (effective Aug 7, 2026) shows E-Business Suite 11.5.10: Premier Support ended November 2010, Extended Support ended November 2013, Sustaining Support indefinite. Earlier 11i releases (11.5.1 to 11.5.9) never had Extended Support. Sustaining Support keeps you on My Oracle Support with existing fixes, but brings no new fixes, security alerts, tax, legal or regulatory updates. Oracle’s own upgrade guide says an 11i system must be at 11.5.10.2 (CU2) with the sustaining-support patch baseline, and on database 11.2.0.4 or later, before it can move to Release 12.2, which has Premier Support through at least December 2037. For a subsidiary or small division still on its own 11i instance, a full EBS upgrade is often more project than the business needs. The pragmatic alternative is archive and migrate: freeze 11i as a read-only archive, move masters, open items and balances to ERPNext (open source, GPL-3.0, no licence fee), and report summarised results to the group. Oracle is quote-only, so we give no Oracle estimate.
Contents
- Who this guide is for
- What Oracle’s Lifetime Support Policy shows for 11i
- What Sustaining Support does and does not give you
- Oracle’s path: 11i to Release 12.2
- The archive-and-migrate approach
- Designing the archive: what it must answer
- What moves, and where it lands in ERPNext
- Reporting to the group: running ERPNext as a second tier
- Where ERPNext fits a retiring 11i entity, and where it does not
- A fit test before you choose
- What it costs to run ERPNext
- A phased plan for a subsidiary
- Decision table
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for group finance and IT leaders who still have one Oracle E-Business Suite 11i instance running somewhere in the group, usually for a subsidiary, an acquired business or a small division, and for the finance managers in those entities who live with it. It is common: the group moved most entities to Release 12, to another ERP or to the cloud years ago, but one 11i instance stayed because it worked, the entity was small, or the business case for upgrading never cleared.
We implement ERPNext, so read our view with that in mind. For a large, complex 11i estate that is still the group’s main ERP, the right answer is usually Oracle’s own path or a group-wide replacement programme, and this guide says so. Where ERPNext fits is the smaller case: an entity whose 11i system can be retired rather than upgraded.
If your entity is on 12.1 rather than 11i, read our Oracle EBS 12.1 guide. Other Oracle guides in the series: JD Edwards World and JD Edwards EnterpriseOne 9.1. For the two-tier idea with an SAP parent, see SAP ECC end of maintenance and ERPNext. The legacy ERP end-of-support hub lists every vendor date we have confirmed.
Sources, checked on Nov 20, 2026: the Oracle Lifetime Support Policy for Applications (PDF, effective Aug 7, 2026), the Oracle E-Business Suite Upgrade Guide, Release 11i to 12.2: supported upgrade paths, the Oracle E-Business Suite 12.2 documentation library, 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 Oracle’s Lifetime Support Policy shows for 11i
| Release | GA date | Premier Support ends | Extended Support ends | Sustaining Support ends |
|---|---|---|---|---|
| 11.0.3 | May 1999 | Feb 2007 | Not available | Jan 2009 |
| 11.5.1 to 11.5.6 | 2000 to 2002 | Jul 2006 | Not available | Indefinite |
| 11.5.7 | May 2002 | May 2007 | Not available | Indefinite |
| 11.5.8 | Nov 2002 | Nov 2007 | Not available | Indefinite |
| 11.5.9 | Jun 2003 | Jun 2008 | Not available | Indefinite |
| 11.5.10 | Nov 2004 | Nov 2010 | Nov 2013 | Indefinite |
| 12.2 (Continuous Innovation; latest 12.2.15, Oct 2025) | — | Through at least Dec 2037 | Not applicable | Indefinite |
All dates are from the E-Business Suite tables in the Oracle Lifetime Support Policy for Applications (PDF, effective Aug 7, 2026). The policy says each stage runs through the last day of the month, which is why we show month and year. For 12.2, Oracle says the “Premier Support Through At Least” date may be extended in one-year increments, that it currently has no plans to end Premier Support for the Continuous Innovation release, and that it reserves the right not to extend the date.
What Sustaining Support does and does not give you
Sustaining Support is not “no support”. It is support frozen at a point in time. From the policy:
| Included in Sustaining Support | Not included |
|---|---|
| Technical support and access to My Oracle Support | New updates, fixes, security alerts, data fixes and critical patch updates |
| Fixes, updates and critical patch updates created during Premier and Extended Support | New tax, legal and regulatory updates |
| Upgrade scripts created during Premier Support | New upgrade scripts |
| Major product and technology releases | Certification with new third-party or Oracle products |
| — | 24-hour response commitment for Severity 1 service requests |
For a subsidiary on 11i, the practical consequences are: every tax or statutory reporting change since 2013 has been handled with your own customisations or outside the system; the database, application server and operating system underneath are of the same era and are harder to keep supported; and the people who know your 11i customisations are retiring or have moved on. You also keep paying annual support on licences that deliver less every year.
Oracle’s path: 11i to Release 12.2
Oracle publishes a dedicated Oracle E-Business Suite Upgrade Guide, Release 11i to 12.2: supported upgrade paths. Its supported-paths section says:
- “Upgrades from 11.0 or 11i to Release 12.2 must be from 11.5.10.2.” If you are below that code level, you first patch or upgrade to 11.5.10.2, then to 12.2.
- The starting point is 11.5.10 CU2 with the minimum patch requirements for Sustaining Support (Oracle Doc ID 883202.1).
- The database must be at least version 11.2.0.4 before you begin the upgrade to 12.2.
- A repackaged Rapid Install makes it possible to upgrade 11.5.10 CU2 systems directly to 12.2, with AutoPatch applying the upgrade driver and many manual steps around it.
The guide then runs to product-by-product chapters on functional changes in financials, procurement, projects, HR and supply chain. Release 12 changed a lot of the financial architecture (subledger accounting and the E-Business Tax engine among them), so an 11i to 12.2 upgrade is a real functional project, not only a technical one. That is the main reason small 11i entities have stayed where they are.
For the group’s main ERP, that project may well be worth it: 12.2 has Premier Support through at least December 2037. For a small subsidiary, the question is whether to spend an upgrade budget on a system the entity uses lightly. That is the case this guide is about.
The archive-and-migrate approach
Retiring an old ERP is two separate jobs, and treating them separately is what makes the project small enough for a subsidiary:
Job 1: archive the history
Keep every closed transaction readable for audit and statutory retention, without keeping 11i running as a live system. Typical options: keep the 11i instance read-only on minimal infrastructure for the retention period; extract the history into a reporting database with simple screens and reports; or a combination, with the read-only instance kept for a short overlap and then switched off. Check your Oracle licence and support terms for read-only use before you decide.
Job 2: migrate what is open
Move only what the business needs to keep trading: master data, open documents and balances at a period end. Everything closed stays in the archive. This keeps the migration to a few well-defined loads that can be reconciled line by line against 11i reports.
Done this way, the new system starts clean, the cut-off is a single period end, and auditors get a clear story: history in the archive, balances carried forward, new transactions in ERPNext.
Designing the archive: what it must answer
An archive is only useful if the people who will use it can get answers from it without calling a retired consultant. Before choosing a tool, write down the questions it has to answer. In our experience, these cover most requests from auditors, tax authorities and the business:
| Question | Who asks | What the archive needs |
|---|---|---|
| What was posted to this account in this period, and from which documents? | Auditors, tax authorities | GL journal lines with source references, by period |
| Show me this supplier invoice and how it was paid | Auditors, AP team | AP invoice headers, lines, payments and attachments if held |
| What did we sell to this customer over the last N years? | Sales, credit control | AR invoices and receipts by customer |
| What did this asset cost and how was it depreciated? | Finance, auditors | Asset register with depreciation history |
| What stock movements happened for this item? | Operations, auditors | Inventory transactions by item and period |
| Prove the opening balances in the new system | Auditors | Final 11i trial balance and the reconciliation to ERPNext openings |
If a read-only 11i instance can answer these and your licence allows it, keeping it for the retention period may be the cheapest option. If the infrastructure is fragile, extracting these tables to a modern reporting database, with a handful of saved reports, is usually safer over a multi-year retention period. Either way, test the archive with real questions before you switch anything off.
Do not leave the reconciliation to the end
The single most useful archive document is the reconciliation between the final 11i trial balance and the ERPNext opening balances, by account and dimension, signed off by finance. Build it during trial loads, not after go-live.
What moves, and where it lands in ERPNext
| 11i data | ERPNext target | Approach |
|---|---|---|
| Operating unit, set of books, legal entity | Company (one per legal entity) | Set up first; see the ERPNext Chart of Accounts documentation |
| Accounting flexfield segments | Chart of Accounts plus accounting dimensions and cost centres | Map natural account to account, other segments to dimensions; see the ERPNext accounting dimensions documentation and ERPNext Cost Center documentation |
| GL balances | Opening balances at cutover | Trial balance by account and dimension; see the ERPNext opening balance documentation |
| Open AR invoices | Opening sales invoices | Per document, so customers can be chased and paid against them |
| Open AP invoices | Opening purchase invoices | Per document, for payment runs |
| Customers and suppliers | Customer and Supplier | Clean duplicates first; see the ERPNext Customer documentation and ERPNext Supplier documentation |
| Items and on-hand stock | Item, Warehouse, Stock Reconciliation | Active items only; stock at cutover with the ERPNext Stock Reconciliation documentation |
| Open purchase and sales orders | Purchase Order, Sales Order | Open lines only |
| Fixed asset register | Asset | Cost, accumulated depreciation and remaining life; see the ERPNext Asset documentation |
| Bank accounts | Bank Account with opening balances | Reconcile the first month with the ERPNext bank reconciliation documentation |
| Closed transactions, history | Not migrated | Archive |
Masters and open items load through the ERPNext Data Import documentation, which accepts CSV or Excel templates for both new records and updates. For a subsidiary, the volumes are usually small enough that two or three full trial loads, each reconciled against 11i reports, are realistic.
Reporting to the group: running ERPNext as a second tier
Most 11i subsidiaries belong to a group that runs something else. ERPNext does not need to integrate deeply with the parent. In a two-tier model:
- The subsidiary runs day-to-day finance, purchasing, sales and stock in ERPNext.
- At month end it sends summarised results (trial balance by group account, plus any inter-company detail) to the group ledger, by file or API.
- Mapping from the subsidiary’s chart to the group chart lives in one place and is reviewed each close.
ERPNext supports multiple companies in one site, multi-currency accounting and inter-company invoices; see the ERPNext multi-currency accounting documentation and ERPNext inter-company invoices documentation. Period closing is a standard document; see the ERPNext Period Closing Voucher documentation. If the parent runs EBS 12.2 or Oracle Cloud ERP, the feed is a standard journal import on the Oracle side; if it runs something else, the same principle applies.
Where ERPNext fits a retiring 11i entity, and where it does not
| If the 11i entity uses | ERPNext fit |
|---|---|
| GL, AP, AR, cash management, fixed assets | Good |
| Purchasing, order management, inventory | Good for standard processes |
| Discrete manufacturing (BOMs, work orders) | Good for standard make-to-stock and make-to-order; see the ERPNext Bill of Materials documentation and ERPNext Work Order documentation |
| Projects (costing and billing) | Partial: simple project costing fits; complex contract billing needs testing |
| Public sector or grants accounting, heavy regulatory reporting | Weak; test carefully or stay with Oracle |
| Advanced planning, process manufacturing, service contracts | Weak; usually wrong fit |
A fit test before you choose
Run these with your own data
- List the 11i modules the entity actually uses today, not the ones it licensed.
- List every customisation and report, and mark which are still needed.
- Load one month of the entity’s real transactions into ERPNext and close the month.
- Produce the group reporting pack from ERPNext for that month and compare it with 11i.
- Agree the archive approach and retention period with your auditors before anything else is built.
- Ask Oracle or your Oracle partner to scope the 11i to 12.2 path for this entity, so you have a real comparison.
What it costs to run ERPNext
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 Oracle figure: Oracle support fees, licences, Oracle Cloud ERP subscriptions and upgrade projects are quoted per customer. We also give no implementation estimate for either path. When you compare, include the 11i support fee you would stop paying, the cost of the archive, and the cost of keeping the old infrastructure alive during any overlap.
A phased plan for a subsidiary
| Phase | What happens |
|---|---|
| 1. Scope | Modules in use, customisations, reports, retention rules, archive choice |
| 2. Pilot | One month of transactions and one close in ERPNext |
| 3. Build | Chart and dimension mapping, group reporting feed, integrations, print formats |
| 4. Trial loads | At least two full loads of masters, open items and balances, reconciled |
| 5. Cutover | Go live at a period end; 11i set read-only |
| 6. Archive and switch off | History extracted or retained as agreed; 11i infrastructure retired |
Pick a quarter end or year end for cutover if you can, so that opening balances line up with a reporting boundary the auditors already review.
Decision table
| If this is true for you | Lean towards | Why |
|---|---|---|
| 11i is still the group’s main ERP | Oracle 12.2 or a group-wide programme | Too big and too central for an entity-level fix |
| Small subsidiary, standard finance and distribution | ERPNext, archive and migrate | Small, well-defined project; no licence fee |
| Entity being sold or closed within a year | Stay on 11i, archive later | No new project worth starting |
| Heavy use of advanced EBS modules | Stay with Oracle | No ERPNext equivalent |
| Group already moving entities to Oracle Cloud ERP | Ask Oracle to include the entity | Consistency may outweigh cost |
Best for, and wrong choice when
ERPNext is best for
Subsidiaries, small divisions and acquired businesses still on their own 11i instance, with standard finance, purchasing, sales and stock, where the group wants to retire 11i rather than upgrade it.
Oracle’s path is best for
Entities where 11i is still the main ERP, or where advanced EBS modules, group-wide Oracle standards or complex regulatory reporting make staying in the Oracle family the safer choice.
ERPNext is the wrong choice when
The entity depends on public sector, process manufacturing, advanced planning or service contract modules, the group mandates Oracle, 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 Oracle’s path is the better answer.
Frequently asked questions
When did Oracle EBS 11i support end?
Oracle’s Lifetime Support Policy shows 11.5.10 Premier Support ended in November 2010 and Extended Support in November 2013, with Sustaining Support indefinite. Releases 11.5.1 to 11.5.9 had no Extended Support (checked Nov 20, 2026).
Is Oracle 11i still supported?
Only under Sustaining Support: technical support and existing fixes, but no new fixes, security alerts, or tax, legal and regulatory updates.
Can EBS 11i be upgraded directly to 12.2?
Oracle’s upgrade guide says upgrades to 12.2 must start from 11.5.10.2 (CU2) with the sustaining-support patch baseline, and the database must be at least 11.2.0.4. Earlier 11i releases first move to 11.5.10.2.
What is archive and migrate?
Keep closed history readable in a read-only archive, and move only masters, open items and balances into the new system at a period end. It keeps the migration small and the audit trail clear.
Can ERPNext run alongside a group Oracle system?
Yes, as a second tier: the subsidiary runs in ERPNext and sends summarised month-end results to the group ledger.
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. Oracle is quote-only.