What to Know About Migrating JD Edwards World Software to EnterpriseOne
Read time: 4.5 min.
91% of companies are running JD Edwards EnterpriseOne, leaving 9% still running on World.* So, if you’re considering a migration project – you’re not alone. And, if you’re ready to migrate to EnterpriseOne, we can help.
Terillium is a global leader in World to E1 migrations. We help clients assess what makes the most sense for their business—whether the answer is staying on the World system or migrating to EnterpriseOne. Learn more about us.
When to Upgrade
Like most big projects, there is usually something that triggers the impetus to make a move. For some, being off support (and the risk associated with that) is keeping executives up at night. For others, it’s a merger or acquisition that prompts the migration process. In other cases, for larger corporations with many locations, the migration is part of a global ERP project rollout.
Other reasons organizations choose to migrate to JDE Edwards E1 from World:
- End user capabilities
- Technology enhancements
- Improved reporting
- New features and functionality
- End of support
- Architecture change
- Cloud hosting
- Business has changed
- Growth – acquisitions or expansions
- Oracle’s investment in JDE
- Improved user interface
- Mobile applications
Building a Roadmap - Planning for the Upgrade
Below are some important areas to keep in mind when planning a World to E1 migration:
- Project Scope
- Tools and Technology
1. Project Scope
The first part of preparing for your 9.2 migration is understanding the type of project you’re planning. You may have heard the term “like for like” or “technical” migration – this is one option. Another is a functional migration, which means that in addition to the like-for-like, there are some process changes or perhaps a new module that is implemented during the project. A transformational migration means essentially starting from scratch.
It’s important to have good leadership on any project – especially your JDE migration. However, leadership can’t do it all – and they don’t have to know it all.
The executive sponsor of an ERP project leads the team and provides guidance – each person on the team has specific tasks they must complete. This executive sponsor should be focused on the project – and very little else. He or she should lead by example and have strong conviction toward completing the project on time, within budget and as close to the original scope as possible.
Over 80% of ERP data is inactive.** For this reason, and many others, how you’ll handle your data is one of the most important aspects of your World to E1 migration. Having the opportunity to put data management best practices in place is also one of the advantages of the project. Below are a few data management aspects to consider:
- Archiving – to improve system performance, among other reasons
- Setting up disaster recovery
- Setting up back-ups
- Purging data to reduce legal risk
- Reducing costs
Preparing for data conversion and data management should be one of the first steps you take in your project planning.
4. Tools and Technology
Cloud vs. On-Premise
JD Edwards EnterpriseOne is a web-based ERP, however you have the choice of whether to deploy JD Edwards E1 on-premise or host in the cloud. Many organizations choose cloud hosting, including Oracle Cloud, Amazon Web Services or Microsoft Azure.
Reducing modifications should be the goal of your World to E1 migration. To determine what JDE customizations are still needed versus what can be eliminated, the first step is document current customizations. From there, a plan of action can be made on how to handle retrofits.
How many interfaces with JDE currently exist within your organization? Below are some steps to take regarding integrations when planning for the 9.2 migration.
- Verify the integration is still supported and works in a web-enabled environment
- Are you changing platforms or going to a cloud/hosted solution? What is the impact of those changes on existing integrations?
- Verify the integration can be used as is
- Review the latest technologies around a service-oriented architecture and JDE BSSV
- Check for a pre-built integration or an option with Cafe One
- Keep in mind that if the integration is not “broken,” the migration project may not be the place to “fix” it (in order to stay within scope, on-time and on-budget)
JD Edwards EnterpriseOne 9.2 has many options for deployment, integrations, and new features and functionality. Research and become knowledgeable in these options, and what might be valuable to your organization. LearnJDE.com is a great resource. Our team can also help you evaluate new functionality.
The short answer is that Oracle licensing can be complicated. Our team, or your Oracle representative, can help you navigate the process. Your team will need to determine if you have the rights to license EnterpriseOne or if you need to re-license.
Oracle JD Edwards EnterpriseOne Features
With a planned product roadmap until 2031 and beyond, Oracle has made significant investments in the JD Edwards EnterpriseOne 9.2 software suite. Recent application enhancements include: capital asset management, human capital management, financials, sales, manufacturing and procurement. Other major product improvements have been made to reporting and the user experience.
Bringing it All Together - Next Steps
- Determine what type of migration you’re planning (technical, functional, transformational)
- Gain internal buy-in
- Begin initial project planning, and building your project team
We can help. Contact us at firstname.lastname@example.org or (513) 621-9500 to discuss your JD Edwards World to E1 upgrade.