Oracle E-Business Suite is not end of life. Oracle has committed Premier Support for EBS 12.2 through at least 2037, a date it confirmed in March 2026, and the same commitment covers JD Edwards EnterpriseOne and PeopleSoft under its Applications Unlimited program (ERP Today, ERP Research). Premier Support is Oracle's full tier: new functionality, regulatory updates, and security patches. The only Oracle date that has bitten recently is EBS 12.1, which left Extended Support in December 2025. That is a version problem, and the fix is an upgrade to 12.2, not a new platform. For the board, the move to Oracle Fusion Cloud ERP, or elsewhere, is a value decision with no external clock.
Oracle has committed Premier Support for EBS 12.2 through at least 2037
The headline date is 2037, and it is not a rumor. Oracle confirmed Premier Support for EBS 12.2 through at least 2037 in March 2026 (ERP Today). Premier Support is Oracle's top maintenance tier, so a company on 12.2 keeps getting new functionality through continuous innovation releases, regulatory and tax updates, and security patches. Nothing in that list is being withdrawn in the next decade.
That matters because the three Oracle support tiers are not interchangeable, and most of the confusion about EBS comes from blurring them. Premier Support is full coverage. Extended Support is full coverage at a premium for a defined window after Premier ends. Sustaining Support is the floor: existing fixes stay available, but there are no new patches and no regulatory updates.
The table below sets the Oracle on-premise products against those tiers as they stand today.
| Oracle product | Support tier today | Committed through | What that includes |
|---|---|---|---|
| EBS 12.2 | Premier Support | At least 2037 | New functionality, regulatory updates, security patches |
| JD Edwards EnterpriseOne | Premier Support (Applications Unlimited) | At least 2037 | New functionality, regulatory updates, security patches |
| PeopleSoft | Premier Support (Applications Unlimited) | At least 2037 | New functionality, regulatory updates, security patches |
| EBS 12.1 | Sustaining Support | Indefinite, but static | Existing fixes only, no new patches, no regulatory updates |
Verify each line on Oracle's Lifetime Support Policy page before you put it in a board paper. Vendors change terms, and a date in a board paper should trace to the vendor's own document, not to a secondary source.
JD Edwards and PeopleSoft carry the same date under Applications Unlimited
EBS is not the only Oracle product in this position. JD Edwards EnterpriseOne and PeopleSoft sit under Oracle's Applications Unlimited program, which carries Premier Support for those products through at least 2037 as well (ERP Today). Applications Unlimited is Oracle's standing commitment to keep supporting and enhancing its acquired on-premise application lines alongside Oracle Fusion Cloud ERP, rather than forcing those customers onto the cloud product on a fixed date.
For a JD Edwards or PeopleSoft customer, the practical reading is the same as for EBS. The vendor is not setting the clock. A company can stay current on its release, take the regulatory updates, and plan a platform change on its own calendar.
This is a stronger position than SAP's ECC customers hold. Our rundown of every ERP support deadline in one place puts the Oracle dates beside SAP's December 31, 2027 mainstream maintenance end and shows how far apart the two situations are. The Oracle customer has more than a decade. The ECC customer has a firm date and a 36-month program to fit before it.
EBS 12.1 is the only Oracle date that has bitten, and the fix is an upgrade
One Oracle date is real and recent, and it is the source of most of the "EBS is dead" talk. EBS 12.1 left Extended Support in December 2025 and now sits on Sustaining Support (ERP Research). A company still on 12.1 is getting no new patches and no regulatory updates. For a finance team, the regulatory gap is the one that forces action, because a tax rate change or a new reporting rule now has to be built by hand or bought from a third party.
The important point is what kind of problem that is. A customer on 12.1 has a version problem, not a product problem. EBS as a product is fully supported through at least 2037. The version the customer is running is the thing that has aged out.
The fix follows from that distinction. An upgrade from 12.1 to 12.2 returns the customer to Premier Support and full regulatory coverage. It is a database and application upgrade on the same product, not a reimplementation on a new platform, so it is measured in months and a fraction of a migration budget. A company that reads "12.1 is out of support" as "EBS is dead" can talk itself into a multi-year tier 1 program when the actual remedy is an in-place upgrade it could schedule this year.
The "EBS is dead" narrative comes from partner marketing, not Oracle's lifecycle page
The claim that EBS is end of life has circulated for years, and ERP Research's correction is blunt: EBS is a mature, fully supported product, and the narrative drives poor decisions (ERP Research). Oracle's own lifecycle policy says the opposite of the narrative.
The narrative persists because someone benefits from it. A systems integrator, a cloud migration specialist, or a reseller earns its fee when an EBS customer starts a move to Oracle Fusion Cloud ERP or another platform. "Your system is dying" is a faster sell than "your system is supported to 2037, so let us build you a value case." An EBS customer should expect to hear the end-of-life line, and should treat it as a sales position until the vendor's lifecycle document says otherwise.
The right response is cheap and specific. Ask for Oracle's Lifetime Support Policy document and find the line that covers your product and version. If a partner cannot point to an Oracle date that applies to you, there is no date. The burden of proof sits with the party claiming the deadline.
A system with no deadline makes the move a value decision
A no-deadline position changes what the board is deciding. When the vendor sets no clock, the move to Oracle Fusion Cloud ERP or to another platform is a business case, judged on cost and capability, not a date. That is a better place to stand than most SAP customers occupy, and the value of it is that it can be spent deliberately rather than under pressure.
The rule we recommend is simple. Do not put a clock on a slide that Oracle has not put on its lifecycle page. A manufactured deadline inside a board paper does two kinds of damage. It pushes the company toward a compressed program, and compression is where tier 1 overruns come from, since the work needs about 36 months from decision to a stable go-live whatever the slide says. It also hands away negotiating leverage, because a vendor and an SI price a customer who believes they are out of time differently from one who is not.
Moving still makes sense under a stated condition, and the condition is capability, not age. The move is worth making when Oracle Fusion Cloud ERP, or another platform, delivers a business capability the current system cannot provide at acceptable cost, and the value of that capability clears the cost and risk of a tier 1 program. A multi-entity company that needs consolidated close, embedded analytics, or a cloud operating model that EBS cannot reach is a candidate. A company whose EBS runs the business and whose customizations still fit is not, and no support date says otherwise before 2037.