No, Oracle EBS is not dying: what the 2037 support extension really means for your customizations

The Oracle EBS end of life story is one of the most persistent myths in enterprise IT. Every year we sit with heads of applications, CIOs, and Oracle programme managers who have been told, usually by someone selling them a migration, that Oracle E-Business Suite is being sunset and that they have to move by some looming date. It is not true, and the latest support announcement makes that unambiguous.

On 25 March 2026, Oracle extended Premier Support for Oracle E-Business Suite 12.2 through at least 2037. That was the ninth consecutive annual extension since Oracle introduced the Continuous Innovation release model for EBS in June 2018. For anyone still hearing that EBS 12.2 has a deadline, the software vendor has just publicly committed to full support for more than another decade.

Premier Support is not a maintenance holding pattern. It is the full tier. That means Oracle continues to ship new functionality, regulatory and tax updates, certifications against new third-party versions, and quarterly Critical Patch Updates for EBS 12.2 through the covered period. Customers on 12.2 remain entitled to the same class of engineering investment that other actively developed Oracle applications receive.

The most recent release update pack, EBS 12.2.15, was released in October 2025 and continued the pattern. It is worth being specific about what Continuous Innovation changes and what it does not. Under Continuous Innovation, Oracle separates the applications code stream from the technology stack. Customers can consume newer technology components, refreshed database and middleware versions, and modern security baselines without being forced through a major applications upgrade. In practical terms, EBS 12.2 is a long lived, still evolving codebase, not a frozen legacy platform waiting for the lights to go out.

This is the single most important distinction to draw when someone quotes a scary support date at you. EBS 12.1 has exited Premier Support and now sits in Sustaining Support. Sustaining Support does not include new updates, new fixes, new tax and regulatory updates, or new certifications. If you are running EBS 12.1 in production today, that is a materially different, and materially more urgent, position than running 12.2. Compliance, patching, and vendor certification will keep getting harder for you, not easier.

If you are on 12.2, you are on a supported enterprise applications platform with a public roadmap through at least 2037. If you are on 12.1, the upgrade to 12.2 is not an optional modernization discussion, it is a support and risk conversation. We see both realities across the GCC, in Saudi Arabia, the UAE and Qatar, and across our client base in the US, UK, Europe and Australia. The right first move depends entirely on which of those two you are actually running.

Here is the honest turn. The 2037 date does not mean you can do nothing for a decade. The support extension changes the deadline, it does not change the debt. The real risks in a mature EBS estate are almost never about Oracle pulling the plug. They are about what has accumulated inside your environment over ten or fifteen years.

• Customization debt in PL/SQL, Forms, Reports, Workflow and BI Publisher that no one currently on the team originally wrote.
• OAF extensions and Forms personalizations that were built against assumptions the standard product has since moved past.
• A technology stack that quietly drifted, WebLogic and Java versions that need to be brought current, database upgrades that keep getting deferred.
• Skills availability, in particular senior OAF and Forms engineers who understand both the framework and the underlying EBS data model.
• Undocumented integrations to downstream systems that only surface when something breaks at quarter close.

None of those get better by waiting. All of them get worse quietly. When a customization finally fails in production, it is almost never because Oracle changed something. It is because a browser, a Java version, a WebLogic patch, a database upgrade, or a business process moved, and the customization was never designed to move with it.

The right way to read the 2037 announcement is not as a reason to relax. It is as a reason to modernize on business merit instead of under a manufactured deadline. When there is no artificial cliff, you get to sequence the work by value and risk, not by fear.

For most organizations we work with, that means three things in sequence. First, do a proper customization audit so you actually know what you own. Second, keep the EBS environment healthy through disciplined patching, technology stack currency and quarterly Critical Patch Updates. Third, retire the worst offending customizations incrementally, usually by rebuilding them as clean APEX applications on the same database, which is a natural evolution rather than a rip and replace.

Our position is straightforward. If you are on EBS 12.2, you have a supported enterprise platform and time to modernize deliberately. That is a good position to be in. We help clients turn that time into a plan.

We start by cataloguing every customization, OAF extension, Forms personalization, custom concurrent program, workflow customization and integration point, and grading them by business impact, technical fragility and cost to maintain. From there we sequence the work. The customizations that hurt the most, usually a handful of high traffic OAF pages, get modernized first, typically by rebuilding them as clean Oracle APEX applications reading directly from the EBS schema. The rest we keep supported and stable, quarter after quarter, through our EBS Care retainer.

The result is a mature EBS estate that continues to run the business today, on a platform that Oracle has publicly committed to through at least 2037, while the customization debt goes down every quarter rather than up. That is the modernization story that actually holds up in front of a board, and it is the one the 2037 extension makes possible.