Explainer
I have delivered Oracle finance systems and migrated clients off them. This is a plain account of what Oracle Fusion Cloud ERP is, how it differs from E Business Suite, JD Edwards and PeopleSoft, what Oracle has promised those products, and what an EBS to Fusion move really involves.
By Christopher Fagan, Managing Partner, PEF Consulting Partners
Delivered for and alongside
















In this article
Oracle Fusion Cloud ERP is Oracle’s SaaS enterprise resource planning suite. Oracle also calls it Oracle Cloud ERP, and you will see both names on its site for the same product. It is one pillar of Oracle Fusion Cloud Applications, alongside supply chain and manufacturing, human capital management and customer experience, and Oracle’s pitch is that all of them share a single data model on Oracle Cloud Infrastructure, with AI built into the workflows and, in Oracle’s words, hundreds of new features delivered every three months.
The word SaaS is doing real work there. Unlike E Business Suite, which you install, patch and customise on servers you control or rent, Fusion is run by Oracle. You configure it, extend it within the boundaries Oracle allows, and take the updates when Oracle ships them. That trade is the whole decision: less control over the software in exchange for not owning its upkeep. Oracle positions it to its own installed base as, in the words of its E Business Suite page, one complete solution for Oracle E Business Suite customers, which is a polite way of saying that is where Oracle would like you to go next.
Oracle groups the ERP suite into finance, projects, risk and performance management, with procurement sitting in the supply chain pillar of its suite overview even though every finance led programme buys it.
My advice is to buy by process, not by list. A UK finance function moving off EBS typically needs the ledger and subledgers, Expenses, Procurement and a Planning or Consolidation product, and can leave Joint Venture Management or Narrative Reporting until there is a named owner for them. Every module you licence needs configuration, data, testing and training, so an unused module is never free, even at a deep discount. I set out how to turn a requirements list into a module scope in how to choose an ERP system.
Fusion is updated four times a year. Oracle names the updates by year and letter, so 2026’s are 26A, 26B, 26C and 26D, and each customer sits on one of three update schedules: February, May, August and November; March, June, September and December; or April, July, October and January. Test environments are updated on the first Friday of the update month and production two weeks later on the third Friday. The updates are mandatory and cannot be skipped.
What Oracle does allow is control over the features. Fixes and minor changes arrive switched on. New functionality that materially changes the user experience ships disabled and needs an opt in, though some opt ins expire and become automatic, with at least two quarters’ notice where setup is needed. Oracle’s Cloud Readiness site lists what is in each update and the Cloud Console handles notifications and opt ins.
The operational consequence is a permanent, small programme. Someone has to read the readiness notes each quarter, decide which opt ins to take, run regression tests in the two week window and tell the business what changed. Oracle itself suggests test automation for this. Clients who treated go live as the end of the project and disbanded the team are the ones who ring me a year later with a quarterly update that broke an approval rule nobody owned. Budget for the standing team in the ERP business case from the start, not as a surprise in year two.
E Business Suite, JD Edwards EnterpriseOne and PeopleSoft are the products Oracle built or acquired for the client server era, and they share a model Fusion does not. You run them on your own infrastructure or on Oracle Cloud Infrastructure, you choose when to patch, and you can customise the code. Oracle keeps each on a continuous innovation release rather than a numbered upgrade path: EBS 12.2, whose latest update 12.2.15 was announced in October 2025; JD Edwards EnterpriseOne 9.2; and PeopleSoft 9.2. New features arrive as updates to those releases, so there is no forced reimplementation to stay supported.
Oracle’s support position is clearer than people expect. Under its Applications Unlimited commitment, Premier Support for those releases runs through at least 2037, with Oracle reviewing annually whether to extend by a further year, and its pages state plainly that there are no forced migrations. Oracle adds a footnote that certain specified products are not extended beyond their already committed dates, so confirm your own product line and release rather than assuming.
So the difference is not that the old products are dying. It is that they stay yours to run, while Fusion is Oracle’s to run. EBS can be lifted to Oracle Cloud Infrastructure with the E Business Suite Cloud Manager tool, and Oracle claims total cost of ownership 30 per cent or more lower than on premises for doing so, a figure I would test against your own hosting bill. That lift keeps your customisations and processes intact; it buys time, not transformation. Fusion means new processes, new configuration and a migration of data, which is a different scale of decision. I compare the two big vendors’ roadmaps in SAP versus Oracle.
An Oracle EBS to Fusion migration is not an upgrade. There is no utility that turns a 12.2 instance into a Fusion tenant. It is a fresh implementation of a different product, into which you carry your data, your rules and, if you are wise, as few of your old workarounds as possible. The route in practice looks like this.
When I ran the Oracle to Microsoft Dynamics migration for BP Pulse, the programme finished 39 days ahead of forecast, and the reason was unglamorous: the data decisions were made and owned before the implementer mobilised. The same discipline is what shortens an EBS to Fusion programme, and our data migration consultancy is built around it.
Oracle does what several of its rivals do not and publishes a price list for its cloud applications. The Oracle Fusion Cloud Service Global Price List, in the version dated 8 October 2026 when I checked, prices each cloud service in US dollars per metric per month, with metrics such as Hosted Named User and minimum quantities per service, and states that prices are subject to change without notice. I am not reproducing figures here because the list changes and because almost nobody pays list.
What the published approach tells you is how a quote is built: a monthly fee per named user or other metric for each service you take, multiplied by a committed term, usually with a minimum quantity. The commercial variables are therefore the number of services, the user counts you commit to, the term, the discount and the uplift at renewal. Count users by role from your EBS responsibilities rather than taking the implementer’s estimate, and get the renewal cap in writing before signature, because that is the last moment you have any influence over it. Our ERP pricing in the UK guide sets Oracle’s approach beside SAP’s, Microsoft’s and NetSuite’s.
Fusion suits organisations that want Oracle to run their finance system and will accept the discipline that comes with it: multi entity groups needing consolidation and statutory reporting in one place, project and asset heavy businesses, public bodies with grants and complex approvals, and existing EBS, JD Edwards and PeopleSoft customers who have decided the 2037 horizon is a deadline to plan against rather than a reason to wait. It suits them best when finance leads the programme and is willing to adopt Oracle’s processes rather than rebuild the old ones inside a new system.
It suits less well businesses with a few hundred users or fewer, who will find the standing update workload heavy for their size, and organisations whose edge depends on deeply customised processes that Fusion’s extension model will not carry. For the first group, our view of the UK ERP market covers the alternatives; for the second, an honest look at whether the customisation is really an advantage comes first.
If you are weighing Fusion, lifting EBS to OCI or leaving Oracle altogether, our independent Oracle consultancy is built for exactly that decision, and we have no commercial relationship with Oracle or any Oracle partner that would colour the answer.
Related reading: Independent Oracle consultancy, SAP versus Oracle, ERP pricing in the UK, SAP ECC end of life 2027: the options, Data migration consultancy, How long an ERP implementation takes.
Yes. Oracle uses both names for the same SaaS suite, and you will see Oracle Fusion Cloud ERP, Oracle Cloud ERP and Fusion Applications on its own pages. It is distinct from E Business Suite, JD Edwards and PeopleSoft, which are older products you run yourself, on premises or on Oracle Cloud Infrastructure, and which Oracle continues to support separately.
It has no announced end. Under Oracle’s Applications Unlimited commitment, Premier Support for E Business Suite 12.2, JD Edwards EnterpriseOne 9.2 and PeopleSoft 9.2 runs through at least 2037, and Oracle says it reviews annually whether to extend by another year. Oracle also states there are no forced migrations. Check that your own release and product line are within the commitment, because some specified products are excluded.
A new implementation. Fusion is a different product with its own data model, so EBS configuration and customisations do not carry across. You redesign the chart of accounts and processes, configure Fusion, migrate data through Oracle’s File Based Data Import templates and test from scratch. Oracle Consulting’s Soar offer automates parts of the discovery, configuration and data migration, but the work is still a programme, not a patch.
Oracle publishes a global price list for Fusion Cloud services in US dollars, priced per metric per month, largely per hosted named user with minimum quantities, and notes that prices can change without notice. Actual contracts are negotiated off that list, so the cost depends on the services you take, the user counts you commit to, the term, the discount and the renewal uplift.
Quarterly. Oracle names the updates by year and letter, 26A to 26D in 2026, and applies them to test environments on the first Friday of your update month and to production two weeks later. Updates cannot be skipped, but new features that change the user experience arrive switched off and need an opt in, so you control the pace of change for users while Oracle controls the platform.
Weighing up Oracle Fusion? Talk to someone who has delivered Oracle and has nothing to sell you but a straight answer.
Book a confidential conversation
Independent, client side help across ERP implementation: vendor selection, project management, testing and go live, health checks and programme recovery, on SAP, Oracle, NetSuite, Dynamics 365, Sage, IFS, Odoo, Epicor, Infor and more. Fees are shown plainly on our pricing page.
Written by Christopher Fagan
Managing Partner, PEF Consulting Partners
Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.
Where next