That depends on the type of upgrade, the size of your environment, and the extent of testing required. For a standard tools upgrade, we typically estimate 80 to 100 hours of work, or about 10 to 12 business days. An application upgrade is a different story: the time required depends on your customizations, the volume of your data, and the development work involved. After the impact scan, you’ll know exactly where you stand.
JD Edwards Upgrades. Get more out of your ERP. Upgrade ahead.
An upgrade often feels like a major project. But it doesn’t have to be. JD Edwards EnterpriseOne 9.2 continues to evolve through regular releases. Release 26 is the current version, and Release 27 is on the roadmap. With Release 27, the technical foundation will also change: 64-bit, Oracle WebLogic, and Java 21 will become the standard.
What do we see in practice? Organizations that view upgrades as an integral part of their roadmap stay in control. Those who put it off for years end up with a large and risky project on their hands. With our ERP+ approach, we guide you through your tool and application upgrade—from impact assessment to hypercare. And if you’d like to outsource management afterward, our Managed Services will take care of it all for you, 24/7.
Why upgrade now? Release 27 is coming soon
Release 27 is more than just a new version. Oracle is standardizing the technical foundation of JD Edwards, and that affects nearly every environment:
- WebLogic is the only web server —IBM WebSphere, IBM AIX, Oracle Solaris, and IBM DB2 LUW are transitioning to Sustaining Support.
- Java 21 – Java 8 is moving to Sustaining Support.
- Effective January 1, 2027, new Application ESUs will only be available in 64-bit. The Platform Pack installers will be discontinued.
- Starting January 1, 2028, application updates will only be available as Web PAR.
- There is no longer a direct path from OneWorld Xe —the direct upgrade to 9.2 will no longer be available starting with Release 27.
Does that mean you have to overhaul everything right away? No. But don’t wait until you have to, either. In our experience, it’s precisely these technical dependencies that lead to surprises during an upgrade. Identify them now, and you’ll be the one setting the pace.
Good to know: Premier Support for JD Edwards will continue through at least 2037. This means you’re investing in a platform that’s here to stay. You can read more background information in our article about the JD Edwards roadmap and Release 27.
What upgrade do you need?
No two environments are the same. Where you are right now determines the route:
- Tools Upgrade – You’re currently running version 9.2, but on an older Tools release. You’ll be upgrading to the latest JD Edwards Tools, which include improvements to Orchestrator, UX One, integrations, and security, among other features. Starting with Tools Release 9.2.6, EnterpriseOne is fully 64-bit.
- Application Upgrade – You’re currently on version 9.2, but you’re behind on application updates. We’ll implement ESUs and new features and assess in advance how this will affect your customizations and integrations.
- Upgrade to 9.2 —if you're still on 9.0 or 9.1, this will be a comprehensive process: impact assessment, retrofitting of custom features, testing, and data migration.
- Upgrading from OneWorld Xe – Starting with Release 27, this can no longer be done in a single step. Oracle recommends first upgrading to 9.0.2 or 9.1, and then using One-Click Provisioning to upgrade to 9.2.
Our tip? Start with an impact scan. That way, you’ll know where your customizations, dependencies, and risks lie, and you’ll get a step-by-step plan you can build on.
Our upgrade services for JD Edwards
- Impact scan & roadmap - We identify customizations, links and risks and deliver a concrete roadmap.
- Technical and Functional Upgrade – We perform the tool and database upgrade and implement the new features of the current release.
- Testing and validation - Careful regression testing to keep your processes running smoothly.
- Data migration and integrations - Everything transferred securely and reliably, preserving your data and integrations.
- Hypercare and support - Training, knowledge transfer and optimization after going live for a flawless transition.
Our approach in 5 steps
- Analysis - We examine your current environment and identify dependencies and potential opportunities.
- Roadmap - We determine the strategy together: technical-only or a full upgrade with 9.2 innovations.
- Preparation - We set up a test environment, analyze your data and create a detailed schedule.
- Implementation - The controlled upgrade is performed with minimal downtime and impact on daily operations.
- Optimization & support - We monitor performance after going live and provide support through our team or Managed Services.
After your upgrade: Stay up to date without a second thought
An upgrade isn't the finish line. The real benefit lies in what comes next: staying up to date without every update turning into a project.
- 24/7 Managed Services – We can take over the management of your JD Edwards environment entirely, or supplement your own team. Monitoring, incident response, JDE Tools updates, security patches, and performance tuning: all handled around the clock. This way, you’ll have complete peace of mind after your upgrade, and your team will have time left over for improvement and innovation.
- Code Current – No one-off patches and no major catch-up efforts every few years, but a steady stream of functional and technical updates, including the latest Tools Releases. This keeps your environment secure and lets you benefit immediately from new features.
- PACKMAN – package builds and deployments, fully automated from development through testing, acceptance, and production. Fewer manual steps, fewer errors, and faster deployment of your ESUs and changes.
- Forza TestTool – test suites containing test data and scenarios that the tool runs automatically, for both interactive and batch processes. After every update, you’ll quickly know whether your processes are still running smoothly, allowing you to go live with confidence.
The result? Fewer manual processes. Fewer surprises. An environment that keeps up with the times.
Frequently Asked Questions
How long does a JD Edwards upgrade take?
Should we upgrade to Release 27 already?
Not necessarily right away. But around Release 27, there will be significant changes to the technical foundation: WebLogic only, Java 21, 64-bit ESUs only starting in 2027, and Web PAR only starting in 2028. Our advice? Put Release 27 on your roadmap now, so you can choose the timing—not the deadline.
What is the difference between a tools upgrade and an application upgrade?
A tools upgrade updates the technical layer of JD Edwards: the Tools Release, which includes Orchestrator, UX One, and security. An application upgrade brings new functionality and ESUs to your modules. You often combine them into a single project.
What happens to our custom work?
We fully map this out in the impact scan. Standard solutions where possible, custom solutions where necessary: wherever UDO’s or standard functionality can replace your custom solutions, we’ll recommend that. We’ll carefully migrate and test the rest.
Will you also be able to take over management after the upgrade?
Yes. With Managed Services 24/7, we can take over management entirely—or handle just a portion of it alongside your own team. This includes monitoring, incident response, JDE Tools updates, security patches, and performance tuning.
What immediate benefits does an upgrade provide?
Think of UX One landing pages, watchlists, and simple orchestrations. They immediately provide more insight and reduce manual work.
Wondering which upgrade path is right for your JD Edwards environment?
Schedule a no-obligation session with one of our ERP+ experts.