If you're running JD Edwards World, Oracle stopped releasing new patches for your system in April 2025. Extended Support for JDE World A9.4 ended. The system is now in Sustaining Support — Oracle's final, minimal-maintenance phase.
Thousands of organizations are still running World. Many of them do not have a concrete plan. If that describes your environment, this is what you need to understand.
What Sustaining Support actually includes
The term "Sustaining Support" sounds more substantial than it is. What it includes: access to previously released patches, access to existing knowledge base documentation on My Oracle Support, and the ability to log Service Requests. Oracle will respond to SRs, but their response is limited to directing you to existing resources — they will not write new patches or fixes in Sustaining Support.
What it does not include: any new fixes of any kind. If a new security vulnerability is discovered in JDE World after April 2025, Oracle will not patch it. If the IRS announces a payroll tax change, Oracle will not update World to comply. If a state revises its sales tax structure, Oracle will not release an update. Your team is responsible for any required changes to a codebase that Oracle no longer maintains.
This is meaningfully different from the "end of mainstream support" transitions many organizations have navigated before. In Extended Support, Oracle still patched. In Sustaining Support, they don't.
The compliance risk
Tax and regulatory environments don't stand still because Oracle stopped patching. This is the risk that matters most for organizations planning to remain on World for any significant period.
Depending on your industry and jurisdiction, the regulatory exposure from running a system that cannot receive updates may include payroll tax miscalculations, sales tax reporting errors, industry-specific regulatory non-compliance (FDA, DOT, OSHA, state-level equivalents), and financial reporting discrepancies where regulatory standards have updated since April 2025. For manufacturing and distribution organizations — which represent a substantial portion of the World install base — these are not edge cases. They are the normal course of regulatory life.
An audit that surfaces compliance gaps tied to an unsupported system creates exposure that extends beyond the tax or regulatory finding itself. Auditors ask follow-up questions about IT governance when they see a system in Sustaining Support. Those conversations are not comfortable.
Three paths forward
No path is easy. Each has honest tradeoffs.
Path A: Migrate to EnterpriseOne 9.2
Staying in the JDE ecosystem gives you access to Release 26 capabilities, Orchestrator, the web-based administration improvements, and Premier Support through at least December 2037. For organizations with deep JDE process investments, the familiarity of the platform reduces retraining burden.
The honest challenge: World and EnterpriseOne are architecturally different. This is not an upgrade in the way that moving from one EnterpriseOne release to another is an upgrade. It is a re-implementation. Business processes mapped in World do not translate automatically to EnterpriseOne. Data migration requires careful transformation work. The project scope is more similar to a new ERP implementation than to a patch cycle.
Path B: Migrate to a modern SaaS platform
Oracle Fusion, NetSuite, SAP S/4HANA, Microsoft Dynamics, and others all represent a path that leapfrogs the on-premises ERP generation entirely. Modern SaaS platforms are receiving active AI investment, continuous feature development, and infrastructure improvements that on-premises platforms cannot match.
The honest challenge: this is the longest and most expensive path. The timeline from decision to operational go-live on a major SaaS ERP is measured in years for organizations of meaningful complexity. Running your World environment during an extended implementation period compounds the compliance and security risk described above. The "dual-run" period — maintaining World while building the new environment — places significant strain on a core team that is already stretched.
Path C: Stay on World and self-support
Some organizations will choose to remain on World and manage the risk internally. This means handling regulatory and tax changes through manual configuration or custom development, managing security posture without vendor-supplied patches, and maintaining the system on institutional knowledge alone.
The honest challenge: this path is viable only if you have the internal expertise to execute it, and that expertise is becoming genuinely scarce.
The talent problem is worse for World
If EnterpriseOne talent is contracting — and it is — World talent has effectively vanished from the hiring market. There are essentially no new JDE World practitioners entering the field. The training infrastructure does not exist. Universities do not teach it. Oracle's own World certification programs are in decline. The people who know World are the people who learned it when it was the current product, and they are moving toward the end of their careers.
Every World practitioner who retires or moves on takes irreplaceable institutional knowledge with them. The configuration decisions made years ago — the ones that explain why a particular business process works the way it does, or why a specific customization exists — are often undocumented. When the person who made those decisions is gone, troubleshooting becomes archaeology.
If you are staying on World for any period, the most urgent action is knowledge capture. Document the configuration, the customizations, the workarounds, and the institutional knowledge that exists only in people's heads. This is not glamorous work, but it is the difference between an operational environment and a fragile one.
What to do this quarter
Three actions worth taking before you complete your next planning cycle.
Run a compliance audit. Identify every tax, regulatory, and security requirement that applies to your business where World can no longer satisfy through Oracle patches. The gap between your current system and your current compliance obligations is growing every month. Measuring it is the first step to managing it.
Map your key-person dependencies. Who are the two or three people who carry the institutional knowledge of your World environment? What happens to operational stability if one of them leaves in the next twelve months? This is not a comfortable question, but it is the question that most determines your near-term operational risk.
For teams that decide to stay on JDE, a named Allari team can hold World and EnterpriseOne Run on consumption pricing — JD Edwards support that automates the recurring work down, keeps every ticket auditable in OpenBook®, and leaves you free to stop us the day you want.
The support calendar moved in April 2025. The question now is whether your planning is moving with it.
