Migrating off JD Edwards, step by step

Contents

1. What makes a JD Edwards migration hard
2. Step 1: take an inventory before choosing a target
3. Step 2: decide what moves and what does not
4. Step 3: choose the route
5. Step 4: move in phases, and reconcile every one
6. Step 5: plan for running two systems
7. What a finished migration looks like
8. Questions buyers ask
9. Sources

The vendors we reviewed publish no measured JD Edwards migrations, so this guide does not quote timelines or budgets. What it sets out is the order of work that turns one large risk into several small ones.

What makes a JD Edwards migration hard

JD Edwards customers rarely run one module. Oracle's EnterpriseOne page spans finance, asset lifecycle, real estate, project costing, payroll, procurement, logistics, warehouse and manufacturing⁠1JD Edwards EnterpriseOneOracle. Each module brings master data, open transactions, reports and integrations, and each has users who depend on its quirks. Long-running installations add customisations on top.

There is also a version question. Customers on World or EnterpriseOne 9.1 are on Sustaining Support, which brings no new fixes or regulatory updates⁠2Oracle Lifetime Support Policy: Oracle ApplicationsOracle · 7 Aug 2026. Their migration has a deadline set by compliance. Customers on 9.2 can choose their timing, which is an advantage worth protecting.

Step 1: take an inventory before choosing a target

• Modules and companies. Which JD Edwards modules each company and business unit uses, and how heavily.
• Customisations. Every modified object, report and orchestration, with an owner and a reason it exists.
• Integrations. Every system that reads from or writes to JD Edwards: banks, EDI partners, warehouse and shop-floor systems, payroll, reporting.
• Reports the business depends on. Statutory, management and operational reports, and who reads each one.

This inventory is what proposals should be priced against. A bidder that quotes before seeing it is guessing.

Step 2: decide what moves and what does not

Not everything has to move at once, and not everything has to move to the ERP. Three groups help:

1. The book of record: general ledger, payables, receivables, fixed assets, costing. This moves to the new ERP, or stays on JD Edwards.
2. Operational work: order entry, purchasing follow-up, customer questions, collections. This can move to the new ERP, or to a layer beside whichever ERP holds the ledger. OpenLazarus, for example, describes its AI teammates working beside an existing ERP and writing back what changes, while companies keep the ERP for the books⁠34OpenLazarus for manufacturingOpenLazarusOpenLazarus for wholesale distributionOpenLazarus.
3. History: detailed past transactions, which often belong in a read-only archive rather than in the new system.

Separating these groups lets the operational improvements start before the ledger cutover, and keeps the cutover itself smaller.

Step 3: choose the route

For World customers, Oracle's own route is EnterpriseOne 9.2, which it describes as the strategic choice and which can run on premises or in the cloud⁠1JD Edwards EnterpriseOneOracle. Oracle also links a separate route from JD Edwards to Oracle Fusion Cloud ERP⁠1JD Edwards EnterpriseOneOracle. Every other vendor in our ranking is a change of vendor as well as of system.

Whatever the route, the delivery model shapes the years after go-live. The cloud suites take over updates: SAP says it fully manages updates for S/4HANA Cloud Public Edition⁠5SAP S/4HANA Cloud Public EditionSAP, Oracle describes automatic updates for Fusion Cloud ERP⁠6Oracle Fusion Cloud ERPOracle, and IFS publishes two releases a year⁠7IFS Cloud releasesIFS. That removes the upgrade project, and replaces it with a release rhythm the business has to test against.

Step 4: move in phases, and reconcile every one

A phase is finished when

• Opening balances in the new system agree with JD Edwards, account by account.
• Open orders, invoices and purchase orders agree in count and value.
• The reports on the inventory list run, and their readers have signed them off.
• Every integration on the list has been tested with real transactions.
• Users have processed a full period end, not just a demo.

The safest first phase is usually one entity or business unit with representative processes and manageable volume. It gives the team a real reconciliation and real training before the largest entities move.

Step 5: plan for running two systems

During a phased move, JD Edwards and the new system run side by side, joined by interfaces for intercompany and consolidation. Budget for that period explicitly: the interfaces, the double support and the people who reconcile both. Keep JD Edwards on a supported footing until the last entity has closed a period in the new system. For a World customer, that may mean an interim support arrangement, which third-party providers such as Rimini Street sell⁠8Support for JD EdwardsRimini Street.

What a finished migration looks like

The ledger runs on a supported release with an update rhythm the team can sustain. Every entity has closed at least one period in the new system and reconciled it. Integrations, reports and archives are documented with owners. And the operational work that drove the project, such as order entry, supplier follow-up and collections, is measured against the baseline taken in step 1. For the choice of target system, see the ranked JD Edwards alternatives, and for timing, the support timeline.

Questions buyers ask

Sources

1. JD Edwards EnterpriseOne. Oracle. Accessed 8 Nov 2026.
2. Oracle Lifetime Support Policy: Oracle Applications. Oracle, 7 Aug 2026. Accessed 8 Nov 2026.
3. OpenLazarus for manufacturing. OpenLazarus. Accessed 8 Nov 2026.
4. OpenLazarus for wholesale distribution. OpenLazarus. Accessed 8 Nov 2026.
5. SAP S/4HANA Cloud Public Edition. SAP. Accessed 8 Nov 2026.
6. Oracle Fusion Cloud ERP. Oracle. Accessed 8 Nov 2026.
7. IFS Cloud releases. IFS. Accessed 8 Nov 2026.
8. Support for JD Edwards. Rimini Street. Accessed 8 Nov 2026.

Updated 8 Nov 2026: First published.

Further reading

• Buyer's guide · Updated quarterlyThe best JD Edwards alternatives in 2026, compared and rankedOracle still supports JD Edwards EnterpriseOne for years to come, so the question is less whether to leave than what to change first. We compared eight options against seven criteria, using only what each vendor publishes.
• Guide · Upgrade or replaceUpgrade, stay or replace: the JD Edwards decision in four optionsReplacing JD Edwards is one option among four, and rarely the cheapest. Here is how to tell which one the business actually needs.
• Guide · Support datesThe JD Edwards support timeline, and what Oracle's dates mean in 2026EnterpriseOne 9.2 is supported through at least 2037. World is already past Extended Support. Here is what Oracle's policy says, release by release, and what it leaves out.