# JD Edwards World to EnterpriseOne Migration Readiness Assessment > Source: https://netray.co/tools/jde-world-to-e1-migration-readiness-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Ten questions that show how complicated a JD Edwards World to E1 (or other ERP) move will be, based on customization, data, interfaces and people. ## Category erp-migration ## Erp Oracle JD Edwards World ## Audience - CIO - IT manager - JDE World administrator - ERP consultant ## Tool **Kind:** assessment **Questions:** #### How heavily is your JD Edwards World system modified? **Help:** Count modified standard programs and custom RPG, COBOL or CL programs. **Options:** ##### Close to standard, a handful of custom reports **Score:** 10 ##### Some modified programs and a few dozen custom objects **Score:** 7 ##### Hundreds of custom or modified programs **Score:** 3 ##### Core transactions rewritten, no clear inventory **Score:** 0 #### How well documented are your DREAM Writer versions and processing options? **Options:** ##### Versions and processing options are inventoried and current **Score:** 10 ##### Documented for the key programs only **Score:** 6 ##### Mostly known by a few people **Score:** 3 ##### No documentation, hundreds of unused versions **Score:** 0 #### How many interfaces and file transfers touch the system? **Help:** EDI, bank files, payroll, WMS, ecommerce, FTP jobs, ODBC reports. **Options:** ##### Fewer than 5, all documented **Score:** 10 ##### 5 to 15, mostly documented **Score:** 7 ##### 15 to 40, partly documented **Score:** 3 ##### More than 40 or unknown, including direct file reads **Score:** 0 #### What is the quality of your master data (items, customers, suppliers, chart of accounts)? **Options:** ##### Clean, with owners and clear rules **Score:** 10 ##### Mostly clean with known duplicates **Score:** 6 ##### Significant duplicates and obsolete records **Score:** 3 ##### Unknown quality, never cleansed **Score:** 0 #### How much history must be carried to the new system? **Options:** ##### Open transactions and balances only **Score:** 10 ##### Current plus one prior fiscal year **Score:** 7 ##### Several years of detail for audit or service **Score:** 4 ##### Everything since go-live, no archive plan **Score:** 1 #### Do you have in-house skills in both World and the target platform? **Options:** ##### Yes, both, with business process owners available **Score:** 10 ##### World skills in-house, target skills to be bought in **Score:** 6 ##### One or two key World people close to retirement **Score:** 3 ##### World knowledge sits only with an outsourced vendor **Score:** 1 #### Is there a business driver and executive sponsor? **Options:** ##### Funded project with named sponsor and date **Score:** 10 ##### Sponsor exists, funding pending **Score:** 6 ##### IT wants it, business has not engaged **Score:** 3 ##### No sponsor, driven by support expiry alone **Score:** 1 #### How standard are your processes compared with E1 or the target ERP? **Options:** ##### Willing to adopt standard processes **Score:** 10 ##### Some unique processes that are well understood **Score:** 6 ##### Many workarounds the business does not want to lose **Score:** 3 ##### Heavily bespoke, the system is the process **Score:** 0 #### How is the underlying IBM i platform maintained? **Options:** ##### Supported OS release, current PTFs, tested backups **Score:** 10 ##### Supported but patching is irregular **Score:** 6 ##### Out of support OS or hardware nearing end of life **Score:** 3 ##### Unpatched, no recent restore test **Score:** 0 #### Have you evaluated alternatives to E1, such as staying put with modernization or moving to another ERP? **Options:** ##### Yes, with costed options and a decision record **Score:** 10 ##### Informally compared **Score:** 6 ##### E1 assumed because it is the Oracle path **Score:** 3 ##### No options reviewed **Score:** 1 **Bands:** #### High risk, assess before committing **Min:** 0 **Max:** 39.99 **Verdict:** The system is heavily modified or poorly understood, so a migration project would begin with discovery rather than build. Budget for an assessment phase first. **Recommendations:** - Inventory custom objects, DREAM Writer versions and interfaces before estimating anything. - Identify which processes the business will actually give up and which it will not. - Stabilize the IBM i platform and prove a restore before starting. - Compare staying on World with targeted modernization against a full move. #### Moderate readiness, close the gaps **Min:** 40 **Max:** 69.99 **Verdict:** A migration is realistic but a few weak areas, usually interfaces, data quality or skills, will drive cost and schedule. **Recommendations:** - Clean master data early, it is the cheapest risk to remove. - Document every interface and decide which will be replaced, retained or retired. - Secure World knowledge before key people leave. - Run a conference room pilot on your own data before fixing scope. #### Ready to plan the move **Min:** 70 **Max:** 100 **Verdict:** You have the inventory, sponsor and platform stability that make a migration plannable. Focus on target selection, cutover design and testing. **Recommendations:** - Lock scope with a fit-gap against standard target functionality. - Plan data conversion with reconciliation to the general ledger. - Define a cutover rehearsal schedule and a rollback decision point. - Confirm current support dates with Oracle and IBM for your exact releases. ## Content **Intro:** Moving from JD Edwards World to EnterpriseOne is not an upgrade in the usual sense. World runs on IBM i with RPG, CL and DREAM Writer, while E1 uses a different architecture, a different object model and different tools. This assessment shows how much of that gap is risk in your own system. **Sections:** #### How to use the assessment **Body:** Answer each of the ten questions for your current production World environment, not the system you wish you had. Where you are unsure, pick the more cautious option, because unknowns in customization and interfaces are where World migrations normally go over budget. Ideally the IT lead, a business process owner and the person who maintains the IBM i answer together, since each sees a different part of the risk. The result is a percentage score and a band with recommendations. #### What the questions measure **Body:** Each question maps to a common source of migration effort. Customization and DREAM Writer documentation drive fit-gap and rebuild work. Interfaces and history drive conversion and integration effort. Master data quality drives cleansing time. Skills and sponsorship drive schedule risk. Platform health tells you how much time you have. The weighting is deliberately simple, so you can reason about the score instead of trusting a black box. **Bullets:** - Customization and process fit: questions 1, 2 and 8 - Data and integration: questions 3, 4 and 5 - People and governance: questions 6 and 7 - Platform and options: questions 9 and 10 #### Reading your score and common mistakes **Body:** A low score does not mean you cannot migrate. It means the first deliverable should be an inventory and a decision about scope, not a build plan. A high score does not remove the need for a conference room pilot with your own data. Common mistakes are assuming E1 will behave like World with a new screen, counting only modified standard programs and missing custom files read by outside tools, and treating the migration as an IT project when process owners have not agreed to change how they work. **Cta:** If you want a second opinion on your score or an inventory of custom programs and interfaces before you commit to a path, Netray can review it with you. This is optional, the assessment is complete on its own. **Faq:** #### Is JD Edwards World the same as EnterpriseOne? **Answer:** No. World is the older IBM i based product with RPG programs and green screen interfaces, while EnterpriseOne is a newer architecture with a web interface and a different toolset. Data structures are related, but programs, customizations and reports do not move across automatically. #### Do I have to move to E1 when leaving World? **Answer:** No. E1 is the Oracle path, but some companies move to another ERP, keep World with modernization of the user interface and integrations, or move in stages. The right choice depends on customization, budget and how much the business wants to change. #### How long does a World to E1 migration take? **Answer:** It varies widely with scope. Small, near standard systems can take months, while heavily modified multi-company systems often take well over a year. Discovery, data conversion and testing normally dominate, not the installation itself. #### Can I reuse my custom RPG programs? **Answer:** Generally not directly. Business logic has to be re-implemented using E1 tools or replaced by standard functionality. That is why an inventory of custom objects is the first thing to build, so you can retire what nobody uses. ## Search terms jde world to e1 migration, jd edwards world to enterpriseone upgrade, jde world migration assessment, jd edwards world end of life, migrate from jd edwards world, jde world modernization, world to e1 migration checklist, jde world replacement options --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json