Oracle EBS 12.1 on sustaining support: upgrade to 12.2, Oracle Cloud ERP, or ERPNext for subsidiaries

Short answer

Oracle’s Lifetime Support Policy for Applications (effective August 7, 2026) shows Premier Support for E-Business Suite 12.1 ended in December 2021, Extended Support is “Not Available”, and Sustaining Support is indefinite. Under Sustaining Support you keep technical support and existing fixes, but get no new fixes, security alerts, critical patch updates or tax, legal and regulatory updates. Release 12.2 has Premier Support through at least December 2037 (checked Nov 16, 2026). For a group whose core runs on EBS, upgrading to 12.2 is usually the right answer, and Oracle supports a direct upgrade from 12.1. ERPNext fits a narrower but common case: subsidiaries and small divisions that share an old 12.1 instance or need their own system, run as a second tier that sends summarised results to the group ledger. Oracle prices are quoted per customer, so we give no Oracle estimate.

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

Who this guide is for

This guide is for CIOs, group finance leads and IT managers at mid-size organisations still running Oracle E-Business Suite 12.1, and for the finance teams of subsidiaries, divisions and acquired businesses that sit on a group EBS instance or need their own system.

We implement ERPNext. We do not suggest replacing a large group EBS core with it; for that, an upgrade to 12.2 or a move to Oracle’s cloud is the realistic choice, and we say so below. Where ERPNext earns its place is the second tier: smaller entities that need a complete ERP without the cost and weight of the group platform. Our SAP ECC guide covers the same two-tier idea for SAP groups, and our JD Edwards World guide covers another Oracle product on Sustaining Support. The legacy ERP end-of-support hub lists every vendor date we have confirmed.

Sources, checked on Nov 16, 2026: Oracle Lifetime Support Policy for Applications (PDF, effective Aug 7, 2026), the Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2, Oracle E-Business Suite Concepts: online patching, the Frappe Cloud pricing page, the ERPNext repository on GitHub and the ERPNext and Frappe documentation linked below.

What we do not estimate

Oracle support fees, licences, Oracle Cloud ERP subscriptions and upgrade projects are quoted per customer. We give no Oracle estimate and no implementation estimate for either path.

What Oracle’s Lifetime Support Policy shows

ReleaseGA datePremier Support endsExtended Support endsSustaining Support ends
EBS 11.5.10Nov 2004Nov 2010Nov 2013Indefinite
EBS 12 (12.0)Jan 2007Jan 2012Jan 2015Indefinite
EBS 12.1May 2009Dec 2021Not AvailableIndefinite
EBS 12.2 (latest 12.2.15, GA Oct 2025)—Through at least Dec 2037Not ApplicableIndefinite

Source: Oracle Lifetime Support Policy for Applications (PDF, effective Aug 7, 2026). Oracle notes that each support stage runs through the last day of the month shown. For 12.2, which is on Oracle’s Continuous Innovation model, Oracle says the “Premier Support Through At Least” date may be extended in one-year increments, and that it currently has no plans to end Premier Support for these releases, while reserving the right not to extend.

Some 12.2 product families have their own earlier dates in Oracle’s exceptions table; for example, Value Chain Planning and Demantra products end Premier Support in December 2026, and some Sales and Marketing products in December 2027. If you use those, check the table for your products.

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 Sustaining Support does and does not include

Sustaining Support includesSustaining Support does not include
Technical support and access to My Oracle SupportNew updates, fixes, security alerts, data fixes and critical patch updates
Major product and technology releasesNew tax, legal and regulatory updates
Fixes, updates and critical patch updates created during Premier (and Extended) SupportNew upgrade scripts
Upgrade scripts created during Premier SupportCertification with new third-party or Oracle products
—24-hour commitment and response guidelines for Severity 1 requests

Source: Oracle Lifetime Support Policy for Applications (PDF, effective Aug 7, 2026). For a 12.1 site the practical consequences are: no new security patches for the application, no new statutory updates for payroll, tax or reporting changes, and a growing gap between your technology stack and what Oracle certifies. Your system keeps running; the risk sits with you.

The real risks of staying on 12.1

Many 12.1 instances have run on Sustaining Support for years without incident, so it is fair to ask what changes now. The answer is that the risk accumulates rather than arrives on a date:

  • Security. No new security alerts or critical patch updates for the application. Issues found after Premier Support ended do not get new fixes for 12.1, so your exposure depends on what you do around the application: network isolation, access control and monitoring. Expect auditors and cyber insurers to ask.
  • Regulatory change. No new tax, legal or regulatory updates. If a country you operate in changes VAT, sales tax, e-invoicing or payroll rules, the change is yours to build, test and maintain.
  • Technology stack. Oracle’s policy says the Fusion Middleware 10gR2 and 10gR3 components embedded in the 12.1 technology stack stay supported only for the support period of 12.1 itself. Certification with new browsers, operating systems, databases and third-party products is not added under Sustaining Support.
  • People. The pool of consultants who know 12.1 and want to work on it shrinks every year, and the work moves to those who do 12.2 and cloud projects.
  • Severity 1 response. Oracle’s 24-hour commitment and response guidelines for Severity 1 requests do not apply under Sustaining Support.

None of these forces a move this quarter. Together they mean that “stay on 12.1” should be a deliberate, time-boxed decision with an owner, not a default.

Questions to put to Oracle and your partner

  • Which entities, operating units and modules on our 12.1 instance are actually used, and by how many people?
  • What do the online patching readiness reports show for our custom code, and how many objects must change?
  • Which database version are we on, and what is the path to a version certified for 12.2?
  • What would our support fees look like after a 12.2 upgrade, and after removing smaller entities from the instance?
  • What would an Oracle Cloud ERP subscription cost for the entities we keep on Oracle?
  • How do we keep read-only access to history for entities that leave EBS, and for how long?

The answers let you compare like with like: the cost of carrying every entity through 12.2, against upgrading the core and moving the smaller entities to a second tier.

Your options

OptionWhat it involvesBest when
Upgrade to EBS 12.2Oracle supports a direct upgrade from 12.0 and 12.1; Premier Support through at least Dec 2037EBS is your group core and you want to keep it
Move to Oracle Cloud ERPReimplement on Oracle’s SaaSYou want Oracle long term and are ready for SaaS
Stay on 12.1 (Sustaining Support)Keep running without new fixes or regulatory updatesShort bridge only; for an entity being retired or sold
ERPNext for subsidiaries (two-tier)Move smaller entities to ERPNext; summarised results flow to the group ledgerSubsidiaries with simpler processes and their own cost pressures
ERPNext for a stand-alone mid-size businessReimplement the whole business on ERPNextA single-entity EBS site with standard processes

What the 12.2 upgrade involves

Oracle’s upgrade guide for 12.0 and 12.1 to 12.2 sets out the path, including an option to upgrade a 12.1.3 instance to 12.2 on Oracle Cloud Infrastructure. The main steps it lists:

  • Prepare the database: the 12.2 upgrade requires database version 11.2.0.4 or higher; upgrade to a certified version and apply the latest database patches.
  • Lay down the 12.2 file system with Rapid Install and apply application-tier technology patches.
  • Upgrade to 12.2.0 with the consolidated upgrade patch and the merged upgrade driver.
  • Enable online patching: run the online patching readiness reports, fix the custom code they flag, and apply the enablement patch.
  • Move to the latest code level with the latest AD-TXK and 12.2 release update packs.

Online patching is what makes 12.2 different. Oracle’s Concepts guide says use of online patching “is mandatory in Release 12.2”, patches are applied with the adop utility while users stay online, and the upgrade installs a logical view of the data model that all code must use. For a site with years of custom code, extensions and reports, the readiness-report fixes are where most of the effort sits. Ask your Oracle partner to run the readiness reports against your instance before quoting.

The two-tier option: ERPNext for subsidiaries

In a two-tier model, the group keeps its main ERP for the parent and large entities, and smaller subsidiaries run a lighter ERP that sends results to the group. It suits EBS groups where small entities are expensive to carry through a 12.2 upgrade, have processes that do not need the full EBS footprint, or were acquired with their own system that also needs replacing.

Need in a subsidiaryIn ERPNextWhat to test
Local general ledger mapped to group chartChart of accounts per company (ERPNext Chart of Accounts documentation)Mapping table from local to group accounts
Several legal entitiesMultiple companies in one site; inter-company invoices (ERPNext inter-company invoices documentation)Intercompany sale with matching entries
Local and group currenciesMulti-currency accounting (ERPNext multi-currency accounting documentation)Revaluation at month-end
Segment reporting matching group segmentsAccounting dimensions, cost centres (ERPNext accounting dimensions documentation, ERPNext Cost Center documentation)Group segment values on every line
Order-to-cash, procure-to-pay, inventorySales and purchase cycles, stock (ERPNext Sales Order documentation, ERPNext Purchase Order documentation, ERPNext Stock Ledger documentation)A month of real transactions
Period closePeriod closing voucher (ERPNext Period Closing Voucher documentation)Close and reopen controls
Group reporting feedTrial balance by account and dimension, exported or pulled through the Frappe Framework REST API documentationThe journal your group ledger imports

The integration pattern is usually simple: at period end, the subsidiary closes in ERPNext, a trial balance mapped to group accounts and segments is produced, and it is loaded into the group ledger as a summarised journal. Intercompany balances are matched before the load. Keep it simple at first; transaction-level integration can come later if the group needs it.

Where staying with Oracle is the better answer

  • EBS is your group core: many entities, shared services, complex consolidation and procurement. Upgrade to 12.2 or move to Oracle’s cloud; do not split the core.
  • You use EBS modules with no ERPNext equivalent, such as advanced planning, complex projects or industry-specific modules, across the business.
  • Your controls are built around EBS: shared service centres, approval hierarchies and audit evidence that would be costly to redesign.
  • Group policy requires one ERP for all entities.

ERPNext is the better answer for subsidiaries and divisions with standard processes, a local finance team, and their own budget pressure, and for single-entity EBS sites that never used most of the suite.

What moves when a subsidiary leaves EBS

EBS dataERPNextNotes
Ledger, chart of accounts segmentsChart of accounts plus accounting dimensionsDecide which segments become dimensions
Customers, suppliers, sitesCustomers, suppliers, addresses (ERPNext Customer documentation, ERPNext Supplier documentation)Only the subsidiary’s active parties
Items, organisations, subinventoriesItems, warehouses (ERPNext Item documentation, ERPNext Warehouse documentation)Map inventory organisations to warehouses
Open receivables and payablesOpening invoices and balances (ERPNext opening balance documentation)Reconcile to aged reports
On-hand stockOpening stock reconciliation (ERPNext Stock Reconciliation documentation)Agree valuation with group finance
Open ordersSales and purchase orders via Data Import (ERPNext Data Import documentation)Freeze changes during cutover
HistoryStays in EBS (read-only) or a reporting extractAgree retention with auditors

Removing an entity from a shared EBS instance has its own work on the EBS side: end-dating the operating unit, closing its periods and preserving access for audits. Plan it with your EBS team.

Costs: what is published

ItemUSD (published)GBPSource
Oracle support, licences, 12.2 upgrade, Oracle Cloud ERPQuoted per customer; no estimate givenQuoted per customerOracle or partner
ERPNext softwareNo licence fee (GPL-3.0)No licence feeERPNext repository on GitHub
ERPNext on Frappe Cloud, site plansFrom $5 per monthAbout £3.78 (indicative)Frappe Cloud pricing page
ERPNext on Frappe Cloud, dedicated serversFrom $40 per monthAbout £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 a subsidiary, compare the share of EBS support, infrastructure and upgrade cost it carries today with an ERPNext implementation, hosting, support and the group integration. Both columns need real quotes.

A practical plan

Month 1: inventory

List entities on the 12.1 instance, their modules, users, custom objects and interfaces. Run Oracle’s online patching readiness reports to size the 12.2 work.

Months 2 to 3: pilot one subsidiary

Rebuild one subsidiary in ERPNext: chart mapping, a month of transactions, intercompany and the group journal. Score fit: standard, configure, build, or no-go.

Month 4: decide the tiering

Decide which entities upgrade with the core to 12.2 (or move to Oracle’s cloud) and which move to ERPNext. Reducing the number of entities on EBS can also simplify the 12.2 upgrade.

Then: move entities at their year ends

Cut over each subsidiary at a period end, run one close in parallel, and end-date it in EBS.

Decision table

If this is true for youLean towardsWhy
EBS runs the whole group with shared servicesUpgrade to 12.2 (or Oracle Cloud ERP)Premier Support through at least Dec 2037
Several small subsidiaries with simple processesTwo-tier: ERPNext for subsidiariesLighter system, no licence fee
Single-entity mid-size EBS site, standard processesPrice ERPNext against 12.2Both are significant projects
Entity being sold or closed within a yearStay on 12.1, archiveNo new project worth starting
Heavy use of advanced EBS modulesStay OracleNo equivalent in ERPNext

Best for, and wrong choice when

ERPNext is best for

Subsidiaries, divisions and acquired businesses of EBS groups, and single-entity mid-size EBS sites, with standard finance, distribution or discrete manufacturing processes and no mandate to stay on Oracle.

EBS 12.2 or Oracle Cloud ERP is best for

Groups where EBS is the core, with shared services, complex consolidation, advanced modules or controls built around Oracle.

ERPNext is the wrong choice when

You would be replacing a large group EBS core, rely on advanced EBS modules daily, or group policy requires one ERP for every entity.

Frequently asked questions

When did Oracle EBS 12.1 support end?

Oracle’s Lifetime Support Policy shows Premier Support for EBS 12.1 ended in December 2021, Extended Support is not available, and Sustaining Support is indefinite (policy effective Aug 7, 2026; checked Nov 16, 2026).

What does Sustaining Support not include?

New updates, fixes, security alerts, data fixes and critical patch updates; new tax, legal and regulatory updates; new upgrade scripts; certification with new products; and the 24-hour commitment for Severity 1 requests.

How long is EBS 12.2 supported?

Oracle lists Premier Support for 12.2 through at least December 2037, with possible extensions in one-year increments.

Can I upgrade directly from 12.1 to 12.2?

Yes. Oracle’s upgrade guide supports direct upgrades from 12.0 and 12.1 to 12.2, with the database at 11.2.0.4 or higher, and online patching enabled after the upgrade.

What is a two-tier ERP model?

The group keeps its main ERP for the parent and large entities, and smaller subsidiaries run a lighter ERP whose results are sent to the group ledger, usually as a summarised journal at period end.

Can ERPNext replace Oracle EBS?

For subsidiaries and single-entity mid-size sites with standard processes, often yes. For a large group EBS core, upgrading to 12.2 or moving to Oracle’s cloud is the realistic choice.

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.

Running subsidiaries on EBS 12.1?

We map one subsidiary’s chart of accounts, entities and intercompany flows into ERPNext, run a month of its transactions, and produce the summarised journal your group ledger needs, so you can compare with the cost of carrying it through a 12.2 upgrade.

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