For years, the conversation about Oracle E-Business Suite went like this: support is ending, the cloud is the future, start planning your move to Fusion. That pressure has eased. Oracle has pushed EBS support well into the next decade, and a lot of finance and IT leaders are now asking a more honest question.
Do we actually need to move? And if we do, when?
We’ve worked on Oracle ERP systems since the late 1990s, and we don’t think there’s a single right answer. For some companies, Fusion is clearly the better platform. For others, a well-run EBS 12.2 environment on modern infrastructure will do the job for years. Our advice is to decide on total cost and business fit over the next decade, not on a support deadline. This post walks through the options the way we’d walk through them with a client, with the costs and trade-offs out in the open.
Where EBS support actually stands
In March 2026, Oracle extended Premier Support for EBS 12.2 through at least 2037. It was the ninth year in a row that Oracle has pushed the date out by a year, a pattern that started when it moved 12.2 to a “Continuous Innovation” model in 2018.
In plain terms, if you’re on 12.2 and keeping up with patches, nobody is going to switch you off any time soon. You still get regulatory and tax updates, security patches and new features.
There are two catches. If you’re still on 12.1, you’re already in Sustaining Support, which means no new security fixes or tax updates. That creates a material support and security risk that should be assessed now. And even on 12.2, Oracle expects you to stay at a recent patch level. If you’ve let your environment drift, “supported” may mean less than you think.
So the deadline has mostly gone away. What’s left is a business decision, and that’s harder, because nobody can make it for you.
The three realistic paths
1. Re-implement on Oracle Fusion Cloud
People often call this an upgrade. It isn’t. EBS and Fusion run on different data models, so your custom PL/SQL, Oracle Forms and workflow tweaks don’t carry over. They get rebuilt as Fusion configuration or as extensions built on Oracle Integration Cloud and Visual Builder, or they get dropped. Usually only your setup data, open transactions and a slice of history make the trip. The rest goes into an archive for audit and reporting.
What you get in return is a system that Oracle updates every quarter, with its AI features and analytics built in, and no servers for your team to look after. For a company whose processes have changed a lot since EBS went in, that fresh start is often the real prize.
2. Upgrade to (or stay current on) EBS 12.2
If your EBS system works, your team knows it well and your customizations genuinely reflect how you do business, staying on 12.2 is a perfectly respectable choice. It’s the lowest-disruption option. The money goes into patching, cleaning up fragile customizations and improving the user experience, rather than into a multi-year program.
The trade-off is that you carry the technical debt forward. The people who understand your 20-year-old customizations won’t be around forever.
3. Move EBS to Oracle Cloud Infrastructure (OCI)
This keeps EBS exactly as it is but takes it out of your data center. You stop paying for ageing hardware and gain better disaster recovery, without retraining a single user. Plenty of companies do this first to stop the infrastructure bleed, then plan a Fusion move on their own schedule. It’s a bridge, and a good one, as long as everyone understands that’s what it is.
What each path really costs
Every project is different, but some public figures give a sense of scale. One licensing advisory firm puts Fusion migrations at around $200,000 for a mid-market company with about 500 users, rising to more than $20 million for a global enterprise. It also estimates that implementation services make up 60 to 70 percent of the bill. Oracle’s own conversion credits, which apply your existing EBS licenses against a Fusion subscription, can take a meaningful bite out of year one if you negotiate them before you sign.
The number that gets overlooked is what happens after go-live. With EBS, you own the software and pay annual support. With Fusion, you pay a subscription for as long as you use it, and every quarterly update brings a round of regression testing. In other words, moving to SaaS turns a largely predictable cost into an ongoing, variable one.
That doesn’t make Fusion the wrong call. It means the business case has to compare five to ten years of total cost, not just the project budget. Staying on 12.2 has its own running costs too: specialist staff, infrastructure, and the slow drag of customizations that nobody wants to touch.
How to decide
When we sit down with a CFO and CIO to work this out, the conversation usually comes back to a handful of questions.
How much have your processes changed since EBS went live? If the business has grown into new markets, products or entities and the system has been bent to fit, Fusion’s clean slate is worth a lot. If the processes are stable and the system fits them, it’s worth much less.
How much of your customization is actually valuable? Take an honest inventory. In most EBS estates we review, a small number of customizations do real work, and a larger number exist because of a decision someone made in 2009.
What’s the state of your infrastructure? If a hardware refresh is due in the next 18 months, that’s a natural trigger for either OCI or Fusion. Spending on new servers for EBS is the one option we’d question.
Who will run it in five years? Finding and keeping EBS specialists is getting harder and more expensive. That’s a genuine risk, and it should be priced into the “stay” option.
What else needs to connect to it? If your ERP needs to talk to Salesforce, a data warehouse or AI tools, Fusion’s modern APIs make that easier. EBS can do it too, but usually with more integration work.
Mistakes worth avoiding
The most expensive mistake is treating a Fusion move as a technical migration. Teams that try to recreate EBS screen for screen in Fusion spend a fortune on extensions and end up with the old system’s problems on a new platform. The ones that do well use the move to simplify how they work, and they get finance and operations leaders involved from the first week, not the last month.
The second is skipping the discovery work. You can’t plan a migration, or make a case for staying, without knowing what’s actually in your EBS system: every customization, every interface, every report people rely on. When budgets overrun, the root cause usually goes back to something nobody knew was there.
The third is moving dirty data. Supplier records, customer masters and open purchase orders pile up over years. Cleaning them before the move takes weeks. Cleaning them afterwards takes much longer and costs goodwill.
A sensible first step, whichever way you’re leaning, is a short assessment: an inventory of customizations and integrations, a rough total cost of ownership for each of the three paths, and a view of where your data needs work. That’s usually enough to turn a vague debate into a clear decision.
Where Selectiva fits
We’ve supported Oracle ERP customers since 1999, across Oracle E-Business Suite, Oracle Fusion and NetSuite. Because we don’t only sell Fusion projects, we’re comfortable telling a client that staying on 12.2 is the smarter move when that’s true.
We also build the integrations that connect ERP to everything else, including Salesforce, through Oracle Integration Cloud, MuleSoft and Boomi. That matters whichever path you choose, because your ERP rarely works alone.
Selectiva can inventory your customizations and integrations, compare the five-to-ten-year cost of each path, and tell you which one fits your business. Talk to our team and one of our consultants will get back to you within 24 hours.
