At INFOCUS 2026 in Denver, the themes were clear: continuous innovation, enterprise automation, AI enablement, security, modernisation and the next stage of the JD Edwards platform roadmap. While many organisations will focus on visible changes to the user experience, successful adoption depends on the work happening beneath the surface.
For IT and business leaders, the question is not simply, “When should we upgrade?” It is, “Is our
JD Edwards environment ready to adopt change without disrupting the business?”
Release 27 readiness starts before the upgrade project
A successful JD Edwards upgrade is rarely just a technical exercise. It affects integrations, customisations, testing processes, security, infrastructure and—most importantly—the people using the system every day.
Customers that wait until an upgrade becomes urgent often face the same challenges:
Unclear technical dependencies
Custom code and integrations that have not been assessed
Limited time and capacity for testing
Ageing platform components
Uncertainty about how new capabilities will affect end users
A modernisation project that feels disruptive rather than incremental
The better approach is to start with a practical readiness assessment. This gives your organisation time to make informed decisions, reduce risk and create a roadmap that fits your business priorities.
1. Review your platform and 64-bit readiness
One of the most important technical conversations for JD Edwards customers is the transition away from 32-bit components. Oracle’s INFOCUS 2026 overview highlighted the migration timeline and lessons learned as 32-bit JD Edwards moves into sustaining support.
This is not just an infrastructure topic. Unsupported or ageing components can limit your ability to adopt new releases, increase security exposure and make upgrades more complex than they need to be.
A clear platform baseline makes it easier to plan Release 27 alongside broader cloud, security and operational goals.
2. Map customisations and integrations before they become blockers
Most mature JD Edwards environments have integrations that are essential to daily operations. These may connect JDE with CRM platforms, warehouses, banks, manufacturing systems, supplier portals, reporting tools or custom applications.
The key question is not whether an integration exists. It is whether it is documented, supportable and ready to be tested.
A readiness review should consider custom objects and bespoke business logic, Orchestrations and automation workflows, APIs, external integrations, security and access models, batch processes, reports and critical operational jobs.
This is also an opportunity to identify candidates for simplification. Reducing avoidable customisation can lower upgrade effort and make future innovation easier to adopt.
Explore Steltix JD Edwards solutions designed to help organisations automate and improve their core business processes.
3. Treat testing as a business-readiness activity
Testing capacity is often underestimated in ERP modernisation projects.
A technically successful upgrade is not enough if users cannot complete essential business processes with confidence. Finance, supply chain, manufacturing, customer service and IT teams all need to validate the processes that matter most to them.
Rather than leaving this until the final stages, define critical end-to-end processes, identify business owners, review available test data and environments, and plan regression testing for customisations and integrations.
The goal is not to test everything at once. It is to focus effort where disruption would have the greatest operational impact.
4. Prepare users for continuous improvement
Modernisation works best when it is not treated as a one-off event.
New tools, automation and improved user experiences only create value when people understand how and why to use them. A practical adoption plan should include communications, role-based training, user support and a way to gather feedback after changes go live.
This matters particularly as JD Edwards customers explore enterprise automation and AI-enabled use cases. The best opportunities are usually focused improvements to real business processes: reducing manual work, improving visibility, validating data or helping users act faster with the right information.
Steltix supports customers globally through its Global Centre of Excellence, combining JD Edwards expertise with practical delivery and ongoing support.
A practical next step for JD Edwards customers
Release 27 should not trigger a last-minute upgrade project. It should trigger a readiness conversation.
Start by assessing your current platform, technical dependencies, customisations, integrations, testing approach and user-adoption plan. From there, you can build a phased roadmap that protects day-to-day operations while creating room for new capabilities.
At Steltix, we help JD Edwards customers modernise with purpose: strengthening the foundation, reducing complexity and helping teams adopt change without disrupting what already works.
Frequently asked questions about JD Edwards Release 27
What is JD Edwards Release 27?
JD Edwards Release 27 is the next stage of the Oracle JD Edwards EnterpriseOne roadmap. Oracle has shared early direction around platform modernisation, automation, AI enablement and continuous innovation. The precise scope and timing relevant to your environment should be confirmed through Oracle’s official product information and your support channels.
How should organisations prepare for JD Edwards Release 27?
Start with a readiness assessment. Review your platform, any remaining 32-bit dependencies, customisations, integrations, security posture, testing capacity and user-adoption approach. This provides a clearer view of effort, risk and the best sequence for change.
Do customisations need to be removed before a JD Edwards upgrade?
Not necessarily. Many customisations support important business processes. However, each one should be assessed for upgrade impact, ongoing supportability and whether standard JD Edwards functionality or a modern integration approach could now meet the same need.
Why are integrations important for Release 27 readiness?
JD Edwards rarely operates alone. Integrations with CRM, warehouse, banking, manufacturing, reporting and external applications must continue to work reliably after change. Documenting and testing these connections early helps avoid operational disruption and unexpected delays.
Is Release 27 readiness only an IT responsibility?
No. IT leads the technical assessment, but business teams should be involved from the beginning. Finance, supply chain, manufacturing, customer service and operational users are best placed to identify critical processes, testing priorities and training needs.
How can Steltix help with JD Edwards modernisation?
Steltix helps JD Edwards customers assess their current landscape, reduce unnecessary complexity, strengthen integrations and security, and build practical roadmaps for modernisation.