JD Edwards 9.1 off Premier Support: upgrade to 9.2 or move to ERPNext?
Short answer
Oracle’s Lifetime Support Policy for Applications (effective Aug 7, 2026) shows JD Edwards EnterpriseOne 9.1 left Premier Support in March 2017 and Extended Support in March 2020. 9.0 left Premier in November 2015 and Extended in November 2018. Both are on Sustaining Support, which Oracle offers indefinitely but which brings no new fixes, tax and legal updates or certifications. EnterpriseOne 9.2 has Premier Support through at least December 2037 under Oracle’s Continuous Innovation model. For most mid-size JDE sites, the in-family upgrade to 9.2 is the lower-risk move: your data, your processes and your people stay put, and the main cost is retrofitting customisations. ERPNext (open source, GPL-3.0, no licence fee) is worth pricing when your JDE footprint is small or a subsidiary, the customisations would mostly be rewritten anyway, or the business wants to stop paying for an Oracle licence and support it uses lightly. Oracle is quote-only, so we give no Oracle estimate.
Contents
- Who this guide is for
- What Oracle says about EnterpriseOne support dates
- What Sustaining Support means on 9.1
- What a 9.2 upgrade actually involves
- What a move to ERPNext involves
- How JDE concepts land in ERPNext
- Upgrade vs replatform: side by side
- When ERPNext is the better answer
- A 60-day decision plan
- Questions to ask Oracle and your JDE partner
- Costs: what is published
- Best for, and wrong choice when
- Frequently asked questions
Who this guide is for
This guide is for CFOs, IT directors and JDE application managers at mid-size companies that run JD Edwards EnterpriseOne 9.1 or 9.0 and never made the move to 9.2. Some held back because the upgrade looked expensive at the time, some because JDE was working and nobody wanted the disruption, and some because the business has since shrunk, been sold or become one subsidiary of a larger group.
We implement ERPNext, so read our view with that in mind. For many 9.1 sites the right answer is to upgrade to 9.2, and we say so plainly. This guide is about making that decision with the cost drivers on both sides in view, rather than defaulting either way.
If you run JD Edwards World on IBM i rather than EnterpriseOne, read our JD Edwards World guide. For Oracle E-Business Suite, see Oracle EBS 12.1 on sustaining support. The legacy ERP end-of-support hub lists every vendor date we have confirmed.
Sources, checked on Nov 19, 2026: the Oracle Lifetime Support Policy for Applications (PDF, effective Aug 7, 2026), the Oracle JD Edwards Premier Support and Continuous Delivery FAQ (PDF), Oracle’s “Upgrade from 9.0 or 9.1” instructions (Applications Upgrade Guide, UNIX/Linux with Oracle), Oracle’s technical considerations for upgrading to 64-bit 9.2, the LearnJDE EnterpriseOne Upgrade Resources 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 Oracle says about EnterpriseOne support dates
| Release | General availability | Premier Support ended | Extended Support ended | Sustaining Support |
|---|---|---|---|---|
| EnterpriseOne 9.2 (latest update: Release 26) | Oct 2015 (Release 26: Oct 2025) | Through at least Dec 2037 | Not applicable | Indefinite |
| EnterpriseOne 9.1 | Mar 2012 | Mar 2017 | Mar 2020 | Indefinite |
| 9.1 Technology Foundation (IBM) | Mar 2012 | Sep 2016 | Not available | Indefinite |
| EnterpriseOne 9.0 | Sep 2008 | Nov 2015 | Nov 2018 | Indefinite |
| 9.0.2 | Nov 2010 | Nov 2015 | Nov 2018 | Indefinite |
| 8.12 | Apr 2006 | Apr 2011 | Apr 2014 | Indefinite |
| 8.11 | Dec 2004 | Dec 2009 | Dec 2012 | Indefinite |
Source: the Oracle Lifetime Support Policy for Applications (PDF, effective Aug 7, 2026), checked Nov 19, 2026. Oracle notes that, unless stated otherwise, each support stage runs through the last day of the month. The 9.2 GA date and the Release 26 date come from Oracle’s Oracle JD Edwards Premier Support and Continuous Delivery FAQ (PDF). For release-level detail on 9.0 and 9.1, the FAQ points customers to Oracle Support Document 2251064.1, which needs a My Oracle Support sign-in.
On 9.2, Oracle’s policy says the “Premier Support Through At Least” date may be extended in one-year increments, that Oracle currently has no plans to end Premier Support for the Continuous Innovation release, and that it reserves the right not to extend the date if continuing becomes impracticable. The FAQ adds that the date has moved from 2025 to 2028, 2030 and then year by year to 2037. Two caveats belong in your plan:
- Tools releases expire. The policy says each EnterpriseOne Tools release or update expires six months after a newer one becomes generally available. Staying “on 9.2” means taking Tools updates regularly.
- Some 9.2 products have their own end dates. Oracle’s exceptions table lists Premier Support ending for UPK content (Dec 2022), the In-Memory products (Sep 2023), Environmental Accounting and Reporting (Aug 2026) and the Oracle Application Management Suite for JD Edwards EnterpriseOne (Aug 2026). If you depend on any of them, plan around it.
What Sustaining Support means on 9.1
Oracle’s policy describes Sustaining Support as available for as long as you license the products. It includes technical support, access to My Oracle Support, and fixes, updates and critical patch updates created during Premier and Extended Support, plus upgrade scripts created during Premier Support. It does 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 third-party products or versions, or with new Oracle products
- 24-hour commitment and response guidelines for Severity 1 service requests
For a 9.1 site, the item that bites first is usually tax, legal and regulatory updates. Since March 2020 any change in payroll, tax, e-invoicing or statutory reporting has had to be built locally or handled outside JDE. The next is certification: new database, operating system or browser versions are not certified for 9.1, so every infrastructure refresh is a risk you carry yourself.
What a 9.2 upgrade actually involves
Oracle’s own Oracle’s “Upgrade from 9.0 or 9.1” instructions (Applications Upgrade Guide, UNIX/Linux with Oracle) describe the path. In outline: install with One-Click where your platform supports it, or from the GA media; install the latest Tools release, Planner update, Server Manager and Tools rollup; build packages; and, for a Simplified Upgrade, use Oracle’s scripts to create a standard package for table conversions. During the spec merge, custom business functions are copied forward, and table conversions move your data to the 9.2 structures.
Two technical points shape the cost. First, Oracle’s technical considerations for upgrading to 64-bit 9.2 says 64-bit processing came in with Applications 9.2 and Tools 9.2.5, and from Tools 9.2.6.1 only 64-bit is supported. A 9.1 site moving to current 9.2 therefore also moves to 64-bit, which affects custom C business functions and third-party components. Second, the LearnJDE EnterpriseOne Upgrade Resources page page lists a Decustomizer Analysis Report, an Upgrade Advisor (Oracle Support Doc 2320843.2), and Oracle’s Compare and Merge tools. These exist because retrofitting customisations is the main work in any JDE upgrade.
| Upgrade cost driver | Why it matters | How to size it |
|---|---|---|
| Custom objects | Each modified application, report, table or business function has to be compared, merged and retested | Run the Decustomizer Analysis Report; count objects by type and by how much they are used |
| 64-bit and Tools | Custom C business functions and third-party add-ons must work on 64-bit Tools | List every C BSFN and every third-party product with its 9.2 certification |
| Infrastructure | Database, OS and server versions must be certified for current 9.2 Tools | Check Oracle’s Certifications (Minimum Technical Requirements) |
| Integrations | Interfaces built on old Tools or middleware may need rework | Inventory every interface and its technology |
| Testing and training | Upgraded processes and new UX need regression testing and some retraining | Base it on your module count and number of users |
What an upgrade does not change is just as important: your data stays in JDE’s structures, your chart of accounts and business units stay, your reports mostly survive, and your JDE-skilled staff and partner remain useful. That is why, for a site with years of JDE investment, the upgrade is usually the conservative choice.
What a move to ERPNext involves
Moving to ERPNext is a new implementation, not an upgrade. Nothing about JDE’s object model carries across: you map data, redesign processes in ERPNext’s terms and rebuild reports and interfaces. The cost drivers are different:
| Replatform cost driver | Why it matters | How to size it |
|---|---|---|
| Process design | Business units, AAIs, document types and order activity rules map to ERPNext’s companies, cost centres, accounting dimensions, workflows and settings | Workshops per module; a mapping document signed off by finance and operations |
| Data migration | Address book, item master, branch/plant data and open transactions must be extracted, cleaned and loaded | Data volumes and how many years of history you need live |
| Customisations | Each JDE customisation is either dropped, met by standard ERPNext, configured, or rebuilt | The same Decustomizer list, sorted into those four buckets |
| Reports and integrations | Rebuilt against ERPNext’s data model and REST API (Frappe Framework REST API documentation) | Count reports actually used in the last year; list interfaces |
| Change management | New screens, new terms, new habits for every user | Number of users and sites |
In exchange, you stop paying Oracle licence and support fees for the JDE scope you retire, get a system you can self-host or run on Frappe Cloud, and replace a JDE skills market that gets thinner each year with ERPNext’s, built on Python and JavaScript. Whether that trade is worth it depends on how much of JDE you really use.
How JDE concepts land in ERPNext
| JDE EnterpriseOne | ERPNext | Notes |
|---|---|---|
| Companies and business units | Companies and Cost Centres (ERPNext Cost Center documentation) | Business unit hierarchies usually become cost centre trees plus accounting dimensions |
| Object.Subsidiary account structure, category codes | Chart of Accounts (ERPNext Chart of Accounts documentation) and Accounting Dimensions (ERPNext accounting dimensions documentation) | Redesign rather than copy; most sites simplify |
| Address Book | Customers (ERPNext Customer documentation), Suppliers (ERPNext Supplier documentation), Contacts and Addresses | One address book number may become several records |
| Item master and branch/plant | Items (ERPNext Item documentation) and Warehouses (ERPNext Warehouse documentation) | Branch/plant settings move to item defaults and warehouse settings |
| Sales and purchase order types, order activity rules | Sales Orders (ERPNext Sales Order documentation), Purchase Orders (ERPNext Purchase Order documentation), Workflows (ERPNext Workflows documentation) | Status rules become workflow states and approvals |
| Manufacturing: bills, routings, work orders | BOMs (ERPNext Bill of Materials documentation), Routings (ERPNext Routing documentation), Work Orders (ERPNext Work Order documentation) | Good fit for discrete manufacturing |
| Job cost | Projects (ERPNext Project documentation), Timesheets (ERPNext Timesheets documentation) | Good for project tracking; test complex job cost structures |
| Fixed assets | Assets (ERPNext Asset documentation) | Good |
| Budgets | Budgets (ERPNext Budget documentation) | Good |
| Multi-currency, inter-company | Multi-currency (ERPNext multi-currency accounting documentation), inter-company invoices (ERPNext inter-company invoices documentation) | Good |
Areas where JDE sites should test ERPNext carefully: complex advanced pricing (ERPNext has pricing rules (ERPNext Pricing Rule documentation), but heavily layered JDE price adjustments need a worked test); payroll and statutory reporting for your countries; and any industry-specific JDE modules such as real estate, joint venture or energy accounting, which have no direct ERPNext equivalent.
Upgrade vs replatform: side by side
| Factor | Upgrade to 9.2 | Move to ERPNext |
|---|---|---|
| Support horizon | Premier through at least Dec 2037, per Oracle | Open source; community releases; support from your partner or Frappe |
| Data | Converted in place by Oracle’s table conversions | Extracted, mapped and loaded; history often archived |
| Customisations | Retrofitted with Oracle’s tools | Dropped, configured or rebuilt |
| Skills | Existing JDE staff and partner stay useful | New skills; JDE knowledge needed only for extraction |
| Licence and support | Oracle licence and annual support continue (quote-only) | No licence fee; hosting and support costs |
| Disruption | Moderate: same system, newer release | Higher: new system for every user |
| Best when | JDE is core, broad and well used | JDE is narrow, a subsidiary, or heavily customised in ways you want to drop |
When ERPNext is the better answer
In our experience, a move to ERPNext deserves a full proposal in four situations:
- A subsidiary or divested business. The JDE instance serves one company that no longer shares the group’s systems. A two-tier model, with ERPNext in the subsidiary and consolidated reporting into the group, is often simpler than upgrading a whole JDE stack for one entity.
- Narrow use. You license JDE broadly but use finance, purchasing, inventory and basic manufacturing. That scope maps cleanly to ERPNext.
- Customisations you want to lose. If the Decustomizer report shows hundreds of modified objects and the business would rather adopt standard processes, rebuilding in a new system can cost less than retrofitting.
- No JDE skills left. If your last JDE developer has gone and the partner market is expensive where you are, the upgrade’s main advantage, keeping your people useful, has already gone.
Conversely, if JDE runs most of the business, your team knows it well, and the customisations encode real competitive processes, upgrade to 9.2 and stay current on the Continuous Innovation releases.
A 60-day decision plan
| Weeks | What happens | Output |
|---|---|---|
| 1–2 | Confirm support status and licence position with Oracle; run the Decustomizer Analysis Report | Status letter, custom object list |
| 3–4 | Sort customisations into keep, standard, configure, rebuild; list interfaces and reports in use | Scope document both sides can quote on |
| 5–6 | Get a 9.2 upgrade proposal from your JDE partner; get an ERPNext proposal on the same scope, with a fit test of your top three processes | Two proposals, same scope |
| 7–8 | Compare five-year cost, risk and disruption; decide | Board-ready recommendation |
Questions to ask Oracle and your JDE partner
Get these answered in writing before you compare proposals. They turn a general worry about an old release into figures you can plan with:
- What exactly are we licensed for, and what do we pay in annual support? Many sites license modules they no longer use; that matters for both options.
- What does the Decustomizer Analysis Report show? Ask for counts of modified objects by type, and which of them were used in the last twelve months.
- Which third-party products and C business functions need work for 64-bit Tools? Get a named list, not a percentage.
- What does our infrastructure need to change? Database, operating system and server versions certified for current 9.2 Tools.
- How will we stay current after the upgrade? Oracle recommends taking regular enhancement releases on the 9.2 code line; ask your partner what that costs per year.
Ask the ERPNext side the equivalent: map our top processes in a working system, list every customisation that needs development, show how our address book, items and open orders load, and name who supports it after go-live. If either side cannot answer with your data, the proposal is not ready to compare.
Costs: what is published
| Item | USD (published) | GBP | Source |
|---|---|---|---|
| JD Edwards 9.2 licence, support and upgrade services | Quote only; no estimate given | Quote only | Oracle JD Edwards Premier Support and Continuous Delivery FAQ (PDF) |
| 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.79 (indicative) | Frappe Cloud pricing page |
| ERPNext on Frappe Cloud, dedicated servers | From $40 per month | About £30.29 (indicative) | Frappe Cloud server plans page |
Frappe Cloud publishes USD prices: site plans from $5 a month (about £3.79) and servers from $40 a month (about £30.29), checked on Nov 19, 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.3205 per £1 for 17 Nov 2026, the latest published figure when we checked on Nov 19, 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.
Oracle does not publish JD Edwards licence or support prices on the pages we checked, so we give no Oracle figure. Use your current annual Oracle support invoice, and a written upgrade quote from your partner, as the figures in the “stay” and “upgrade” columns.
Best for, and wrong choice when
Upgrading to 9.2 is best for
JDE sites where EnterpriseOne runs most of the business, the team and partner know it well, and customisations encode processes worth keeping. Premier Support through at least December 2037 gives a long runway.
ERPNext is best for
Subsidiaries, divested units and narrow JDE footprints on 9.1 or 9.0 where the upgrade would mostly retrofit customisations nobody wants, and where dropping Oracle licence and support costs matters.
ERPNext is the wrong choice when
You rely on JDE industry modules with no ERPNext equivalent, you need the least disruptive path in the next year, or nobody in the business can own a 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 the incumbent vendor’s path is the better answer.
Frequently asked questions
When did JD Edwards 9.1 support end?
Oracle’s Lifetime Support Policy (effective Aug 7, 2026) shows EnterpriseOne 9.1 Premier Support ended March 2017 and Extended Support ended March 2020. Sustaining Support is indefinite (checked Nov 19, 2026).
Is JD Edwards 9.0 still supported?
Only on Sustaining Support. Premier Support ended November 2015 and Extended Support November 2018, per the same policy.
How long is JD Edwards 9.2 supported?
Oracle lists Premier Support for EnterpriseOne 9.2 through at least December 2037 and says the date may be extended in one-year increments. Individual Tools releases expire six months after a newer one becomes generally available.
What does Sustaining Support exclude?
New fixes, security alerts and critical patch updates, new tax, legal and regulatory updates, new upgrade scripts, new certifications, and 24-hour Severity 1 response commitments, per Oracle’s policy.
Can you upgrade directly from 9.1 to 9.2?
Yes. Oracle publishes an “Upgrade from 9.0 or 9.1” procedure. Current 9.2 Tools releases are 64-bit only, so plan for 64-bit work on custom business functions.
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.79 and £30.29 at the Bank of England rate for Nov 17, 2026; checked Nov 19, 2026). Implementation is separate. Oracle is quote-only.