Oracle EBS End of Life: What Happens Next (2026)

Oracle EBS End of Life: What EBS Customers Need to Know in 2026

Updated July 2026 to reflect Oracle's March 2026 announcement extending EBS 12.2 Premier Support to at least 2037.

Oracle E-Business Suite (EBS) is not end of life. Oracle E-Business Suite is Oracle's on-premise ERP suite covering financials, procurement, supply chain, manufacturing, and HR. In March 2026 Oracle extended Premier Support for EBS 12.2—its most widely deployed release—through at least 2037. So the honest framing isn't "the platform is dying"; it's that EBS is a mature, still-supported system, and the real decision is when and how you modernize, not whether you'll be cut off next year.

Key Dates for EBS Customers (as of March 2026):

• EBS 12.2 Premier Support — extended through at least 2037 (ninth annual extension, announced March 2026)
• EBS 12.1 — Premier Support ended in 2014; unsupported for new patches today
• Sustaining Support — the indefinite tier that applies only after Premier Support finally ends (no new security patches, no regulatory updates)

Bottom line: You are not facing a 2031 cliff. You have a long runway—but a full EBS migration still takes 18–36 months, so the planning decision is a 2026–2027 one even if go-live is years out.

If your organization runs Oracle E-Business Suite, you have almost certainly seen headlines calling EBS "end of life." That framing is out of date. Oracle has extended Premier Support for EBS 12.2 annually, pushing the date from 2030 to 2033, 2034, 2035, 2036, and—most recently, in March 2026—to at least 2037. Understanding what each support tier actually means, and why "end of life" is the wrong mental model, is essential for EBS customers making infrastructure and ERP investment decisions in 2026 and beyond.

---

What Is the Oracle EBS Support Timeline?

Oracle structures its support into three phases under the Oracle Lifetime Support Policy: Premier, Extended, and Sustaining. Knowing where EBS 12.2 sits determines what you can expect from Oracle and what risks your organization actually carries. The headline: EBS 12.2 remains in Premier Support through at least 2037, thanks to Oracle's pattern of rolling annual extensions.

Premier Support (EBS 12.2: through at least 2037)

During Premier Support, Oracle delivers the full support experience:

• New functionality updates and patches (EBS still ships continuous-innovation updates)
• Regulatory, legal, and tax updates (payroll tables, VAT changes, country localizations)
• Certified compatibility with new third-party software versions (databases, browsers, OS)
• Access to My Oracle Support (MOS) for technical service requests
• Bug fixes and security patches, including quarterly Critical Patch Updates (CPUs), for all severity levels

Because Oracle has extended this date every year since 2018, EBS 12.2 has effectively stayed in Premier Support continuously. The March 2026 announcement moved the floor to at least 2037—and given the pattern, further extensions are plausible.

If you are still on EBS 12.1 (a small but real population of holdouts), Premier Support ended for that release in 2014. That version—not 12.2—is the one carrying genuine end-of-support risk today.

Extended Support and Sustaining Support

Historically, Oracle's model was Premier Support → a paid Extended Support window (often a surcharge of ~10% of net license fees per year) → indefinite Sustaining Support. For EBS 12.2, Oracle's repeated Premier Support extensions have effectively folded the "Extended Support" step into an ever-lengthening Premier window, which is why you should ignore any source still citing a hard "Extended Support ends 2031" date—it was superseded by the 2026 guidance.

Sustaining Support is the tier that eventually applies once Premier Support finally ends. Under Sustaining Support:

• No new security patches or Critical Patch Updates are produced.
• No new tax or regulatory updates.
• No new certified interoperability with third-party software.
• Existing patches and the My Oracle Support knowledge base remain accessible, but nothing new is created.

Running an ERP system under Sustaining Support—with PII, financial data, and regulatory obligations—exposes your organization to material risk, because frameworks like SOC 2, ISO 27001, and PCI DSS require timely patching of critical vulnerabilities. But for EBS 12.2 customers, that scenario is well over a decade away, not a 2031 emergency.

---

Is Oracle EBS Really End of Life?

No—Oracle EBS is not end of life. This is the single most common misconception among EBS customers, and it is worth answering directly because the "EBS is dead" narrative drives poor decisions.

EBS 12.2 is in Premier Support through at least 2037. Oracle continues to invest in the platform through its Continuous Innovation model, shipping new features (including Enterprise Command Center dashboards and Redwood UI updates) without forcing a major upgrade. Independent ERP advisory firms consistently correct the same confusion: EBS is a mature, fully supported system, not an abandoned one.

So why does "end of life" keep circulating?

• Oracle's cloud-first messaging. Oracle actively steers customers toward Oracle Cloud (Fusion) ERP, which creates the impression that EBS is being retired even though it is not.
• Stale content. Many articles still quote the old 2021/2031 dates and were never updated after Oracle's annual extensions.
• Conflation with EBS 12.1. The 12.1 release genuinely fell out of Premier Support in 2014, and that fact gets mis-applied to 12.2.

The right question is therefore not "Is EBS dead?" but "What is our modernization strategy, and on what timeline?" You are choosing between innovation, total cost of ownership, and cloud capabilities—not racing an imminent support deadline. That reframing changes the urgency from "migrate before the lights go out" to "modernize deliberately, on a business-driven timeline."

---

What Are the Risks of Staying on Oracle EBS?

Even with support secured to 2037, EBS customers face compounding operational and strategic risks that grow each year they remain on the platform. These are cost-of-ownership and opportunity risks, not "you'll lose patches next year" risks—but they are real, and they build a legitimate business case for modernization on your own schedule.

Security and compliance surface

Oracle's quarterly Critical Patch Updates continue for EBS 12.2, so the platform stays patched. But an aging architecture—Forms-based UI, older web-services patterns, and pre-cloud security models—presents a larger attack surface than modern cloud ERP, and each year adds integrations and customizations that widen it.

Integration debt

EBS was designed for on-premise integration: database-level joins, custom PL/SQL packages, and Oracle AIA middleware. As your business adopts SaaS tools—Salesforce, Workday, Coupa, Snowflake—the cost of maintaining brittle EBS integrations grows. Modern ERP platforms offer REST/API-native integration that dramatically reduces this overhead.

Talent scarcity

EBS functional and technical consultants—PL/SQL developers, Forms/Reports specialists, and legacy DBAs—are a shrinking, aging talent pool. Recruiting and retaining specialized EBS talent gets more difficult and more expensive every year, and this risk compounds the longer modernization is deferred.

Customization debt and opportunity cost

Years of CEMLI customizations (Configurations, Extensions, Modifications, Localizations, Integrations) accumulate as "customization debt"—the single biggest variable in any future migration's cost and duration. Meanwhile, EBS can't natively adopt AI-driven automation, embedded analytics, or modern UX. Finance teams on cloud ERP run AI-assisted cash application and anomaly detection on journals; operations teams gain IoT and predictive-maintenance capabilities. Every year on EBS is a year those capabilities go unrealized.

---

What Are Your Migration Options as an Oracle EBS Customer?

Because there is no hard deadline, "migration" for EBS customers in 2026 really means "modernization on your terms." There are four legitimate paths—and one of them (lift-and-shift to OCI) is a bridge that lets you modernize infrastructure now while deferring the SaaS decision.

Option 1: Oracle Cloud ERP (Oracle Fusion Cloud)

The most direct modernization path is Oracle's own preferred route: Oracle Cloud ERP (Oracle Fusion Cloud Applications). Oracle has invested heavily in migration tooling to make the EBS-to-Cloud transition manageable.

• Oracle ERP Cloud delivers financial management, procurement, project management, and supply chain in a unified SaaS platform with quarterly innovation updates.
• CEMLI assessment frameworks help catalog EBS customizations and decide what to retire vs. replicate in Fusion.
• Business Process Reviews and Rapid Implementation templates accelerate configuration for standard processes.

Timeline: EBS-to-Oracle Cloud migrations at mid-market organizations typically run 18–30 months; large, heavily customized environments can take 3–5 years. Cost: implementation services at a ~2,000-employee company typically range from $3M–$8M depending on module scope and customization complexity. Trade-off: significant change management, because the Fusion UI and data model differ fundamentally from EBS. When you reach this stage, find an Oracle implementation partner with verified EBS-to-Fusion references in your industry.

Option 2: SAP S/4HANA

Some EBS customers—particularly in industries where SAP dominates (automotive, chemicals, pharma, aerospace)—migrate to SAP S/4HANA instead. Drivers include industry-specific depth, a desire to de-risk Oracle vendor concentration, and existing SAP usage in subsidiaries. Because there is no shared data model or tooling with EBS, this path is inherently more complex: timelines run 24–42 months and implementation cost $4M–$12M+.

Option 3: Oracle NetSuite

For mid-market EBS customers—typically $20M–$500M in revenue running EBS for finance and light manufacturing—Oracle NetSuite is a faster, lower-cost cloud alternative to Fusion. It offers financials, order management, inventory, and basic manufacturing in a single SaaS platform, with 6–12 month standard implementations and lower TCO. The limitation: NetSuite doesn't match Fusion or S/4HANA for multi-entity global consolidation or advanced manufacturing.

Option 4: EBS on OCI (Lift-and-Shift)

The path most often omitted from "end of life" guides is the one that fits customers who aren't ready to move off EBS: lift-and-shift EBS to Oracle Cloud Infrastructure (OCI). Because EBS 12.2 is supported to at least 2037, you can re-host your existing EBS environment on OCI—retiring on-premise hardware and gaining cloud elasticity, better DR, and lower infrastructure cost—without re-implementing on a new ERP.

• Timeline: typically 3–6 months (a re-host, not a re-implementation).
• Cost: the lowest of the four paths—minimal application re-work.
• Why it matters: it's a bridge. You modernize infrastructure now, keep all your customizations and processes intact, and defer the SaaS decision until the business is ready—all while staying on a fully supported release.

Lift-and-shift isn't a permanent answer to modernization, but for organizations facing a data-center exit or hardware refresh, it removes the false urgency of a "migrate-or-die" deadline and turns the Fusion/S/4HANA/NetSuite decision into a deliberate, well-timed one.

---

How to Build a Migration Business Case

Because there's no support cliff forcing your hand, the business case for EBS modernization is a value-and-risk case, not a deadline case. These are the levers that generate the strongest ROI arguments:

1. Infrastructure and support cost avoidance: Quantify current EBS costs (Oracle support fees, DBA resources, patch labor, hosting). Compare against cloud SaaS fees that bundle infrastructure, patching, and upgrades—or, for a near-term win, against OCI lift-and-shift infrastructure savings.

2. Customization maintenance elimination: EBS organizations commonly carry $500K–$2M per year in custom-development maintenance. Modern ERP eliminates most of it through configuration and SaaS extension models.

3. Finance process efficiency: Cloud ERP customers report 30–50% reductions in period-end close time through automated reconciliations, AI-assisted journal preparation, and real-time consolidation.

4. Headcount reoptimization: Finance transformation typically frees 15–30% of manual processing capacity for higher-value analytical work, or curbs headcount growth as the business scales.

5. Innovation opportunity value: Rather than a "risk premium" tied to a fake 2031 deadline, assign value to the AI, analytics, and UX capabilities EBS can't deliver. For most CFOs, the opportunity cost of not modernizing is now the more honest argument than the compliance-cliff argument.

---

Key Questions to Answer Before You Start

Before committing to a modernization path, work through the following:

• How many CEMLI extensions does your EBS system carry? High counts (200+) sharply increase migration complexity and cost regardless of target platform.
• Which business processes are standard vs. differentiated? Standard processes (procure-to-pay, order-to-cash, record-to-report) should move to SaaS best practices; genuinely differentiated ones may warrant cloud extensions.
• What is your data-cleanup debt? Years of master-data drift make migration an opportunity to rationalize supplier, customer, and chart-of-accounts data—but that work takes time.
• Do you need a bridge first? If a data-center exit or hardware refresh is looming, OCI lift-and-shift may be the right first move before any SaaS decision.
• What is your implementation partner's EBS track record? Ask for EBS-to-target references in your industry and size range.

---

Timeline: What to Do in 2026

There is no 2031 cliff, but full migrations still take 18–36 months, so if a SaaS move is in your future, planning is a 2026–2027 activity. A practical sequence:

The point of starting the assessment now isn't a deadline—it's that a well-run modernization is a multi-year program, and the earlier you understand your customization debt, the more options (including a low-cost OCI bridge) stay open.

---

Frequently Asked Questions

Is Oracle EBS really end of life?

No. Oracle E-Business Suite 12.2 is in Premier Support through at least 2037, and Oracle continues to ship new features via its Continuous Innovation model. The "end of life" label is a misconception driven by Oracle's cloud-first marketing and by outdated articles quoting old 2021/2031 dates. The real decision for EBS customers is modernization strategy and timing, not an imminent support cutoff.

When does Oracle EBS support end?

As of Oracle's March 2026 announcement, EBS 12.2 Premier Support is extended through at least 2037—its ninth annual extension. Oracle has moved this date forward every year since 2018, so further extensions are plausible. EBS 12.1, by contrast, left Premier Support back in 2014.

Isn't Oracle EBS Extended Support ending in 2031?

That date is outdated. Oracle's repeated Premier Support extensions superseded the old "Extended Support ends 2031" guidance; the current floor is at least 2037. Any source still citing a hard 2031 deadline for EBS 12.2 has not been updated since Oracle's recent annual extensions.

Can I lift and shift Oracle EBS to Oracle Cloud Infrastructure?

Yes. Because EBS 12.2 is supported to at least 2037, you can re-host your existing EBS environment on Oracle Cloud Infrastructure (OCI) in roughly 3–6 months without re-implementing. Lift-and-shift retires on-premise hardware, cuts infrastructure cost, and acts as a bridge that lets you defer the Fusion/S/4HANA/NetSuite decision until the business is ready.

What is Oracle EBS CEMLI and why does it matter?

CEMLI stands for Configurations, Extensions, Modifications, Localizations, and Integrations—the catalog of everything customized in an EBS deployment. CEMLI count is the single biggest driver of migration cost and duration: high counts (200+) sharply increase complexity, so cataloging your CEMLI objects is the essential first step in any modernization business case.

How much does an Oracle EBS migration cost?

It depends on the path. An EBS-to-Oracle-Cloud (Fusion) migration at a ~2,000-employee company typically runs $3M–$8M; an EBS-to-SAP-S/4HANA move runs $4M–$12M+; NetSuite is lower (mid-market pricing); and an OCI lift-and-shift is the cheapest option because it re-hosts rather than re-implements. Customization (CEMLI) volume is the largest single cost variable.

---

Next Steps

• Build your ERP requirements with our free wizard — define and prioritize requirements before you issue an RFP.
• Compare ERP vendors side by side — evaluate Oracle Cloud, SAP, NetSuite, and more.
• Compare migration targets in detail — feature and pricing depth on the top three SaaS paths.
• Find an Oracle implementation partner with verified EBS migration experience.