Yes, Oracle Forms is still supported, but there is no single end date, because Forms runs on two different support clocks. Standalone Forms and Reports 12c leave Premier Support in December 2026, a few weeks from now, while Forms running inside E-Business Suite 12.2 is supported through at least December 2037.
Those dates are eleven years apart. Tell an E-Business Suite shop that its Forms lose support in December 2026 and their DBA can show you Oracle's document saying otherwise. Tell a standalone 12c team they have until 2037 and they lose the weeks they needed. So before anyone compares APEX with Java, the first job is to find out which clock each Forms application is on.
- Oracle Forms is still supported. Which dates apply depends on whether a Forms application runs on its own or inside E-Business Suite 12.2.
- Standalone Forms 12c leaves Premier Support in December 2026. Extended Support runs to December 2027, and only for the terminal patch set.
- Forms inside E-Business Suite 12.2 follows the EBS clock, with Premier Support through at least December 2037.
- The size of any move is set by the business rules in the PL/SQL triggers and program units, not by the version number.
Which clock is your Forms application on?
Oracle publishes separate lifetime support policies for its middleware and for its applications. Which one governs your Forms depends on how they're installed, not on how the screens look.
Standalone Forms and Reports follow the Oracle Fusion Middleware Lifetime Support Policy (effective 13 April 2026, checked on 16 October 2026). Its footnotes list Forms and Reports among the products in each Fusion Middleware release. That covers Forms your team built and runs on its own middleware install.
Forms inside E-Business Suite 12.2 follow the EBS clock. Oracle's Lifetime Support Policy for Applications (effective 7 August 2026, checked on 16 October 2026) says:
"Customers running Oracle Fusion Middleware in the Oracle E-Business Suite 12.2 internal technology stack will remain supported on the embedded middleware versions for the duration of the support period for Oracle E-Business Suite 12.2."
That policy gives E-Business Suite 12.2 Premier Support "through at least" December 2037. The latest release, 12.2.15, became generally available in October 2025, and Oracle "currently has no plans to end Premier Support" on the 12.2 Continuous Innovation release.
If you run custom Forms alongside E-Business Suite, that's two estates with two deadlines.
| Question | Standalone Forms and Reports | Forms inside E-Business Suite 12.2 |
|---|---|---|
| Policy that applies | Fusion Middleware Lifetime Support Policy | Lifetime Support Policy for Applications |
| Premier Support ends | 12c in December 2026, 14.1.x in December 2030 | Through at least December 2037 |
| What December 2026 changes | 12c leaves Premier Support | Nothing on the EBS clock |
| Sensible first move | Decide whether to upgrade, rebuild or rewrite | Leave the Forms alone and track EBS 12.2 |
Oracle Forms support end dates, release by release
These come from the Fusion Middleware policy linked above. Some summaries online give 14c dates of December 2029 and December 2032. Oracle's own table says December 2030 and December 2033, so read Oracle's document.
| Release | Premier Support ends | Extended Support ends |
|---|---|---|
| Forms and Reports 11gR2 (11.1.2.x) | December 2016 | December 2018 |
| Fusion Middleware 12c (12.2.x), includes Forms and Reports | December 2026 | December 2027 |
| Fusion Middleware 14.1.x, includes Forms and Reports | December 2030 | December 2033 |
Oracle lists 12c general availability as October 2015 to April 2016, and 14.1.x, which people often call 14c, as December 2024. For both, Oracle lists Sustaining Support as indefinite; check the policy for what it covers.
What ends in December 2026, and what doesn't
Nothing switches off. A Forms 12c application keeps running in January exactly as it did before. What changes is the support behind it.
Oracle's Software Technical Support Policies (effective 9 October 2026, checked on 16 October 2026) say Extended Support "is generally available for three years following the expiration of Premier Support and only for the terminal patchset release of a program." For 12c, that runs to December 2027.
Act on the second half of that sentence. If your 12c installation isn't on the terminal patch set, the last one Oracle releases for the version, getting there belongs in the plan. Ask Oracle what Extended Support means under your own contract before anyone budgets around it. Auditors will ask about support status too; we cover those risks in the risks of running end-of-life software.
What is Oracle Forms used for, and is it still used?
Oracle Forms builds data-entry and query screens over an Oracle Database, with logic in PL/SQL triggers that fire when a user leaves a field or saves a record. It is still used, inside E-Business Suite and in in-house applications built in the 1990s and 2000s for order entry, billing and inventory. Those turn up on almost any list of legacy system examples.
Where the business rules live
This decides the size of any move off Forms. In a typical Forms application the logic isn't in one place. Some sits in database packages. Much of it sits in the form itself: in WHEN-VALIDATE-ITEM and POST-QUERY triggers, in program units inside each .fmb module, and in shared PL/SQL libraries (.pll files). A pricing rule might be enforced on one screen and repeated, slightly differently, on another.
None of that shows up in a count of screens, so two applications with the same number of forms can need very different amounts of work. If one long-serving developer is the person who knows, capture that knowledge now. And before anyone prices a migration, someone has to read the code, as we explain in before you rewrite a legacy system.
Your options: upgrade, APEX, Java, or leave it alone
| Option | What changes | When it fits | Main risk |
|---|---|---|---|
| Upgrade to Forms 14.1.x | Same application on a newer Fusion Middleware release | The application works and the business wants to keep it | Existing debt moves across with it |
| Rebuild the screens in Oracle APEX | New web screens on the same Oracle Database | Your team knows PL/SQL and the data stays in Oracle | Logic in Forms triggers has to be moved or rewritten first |
| Rewrite as a Java or web application | New application on a new stack | The business wants to leave Oracle tooling, or wants the process to change | Every rule hidden in triggers and libraries must be found and coded again |
| Leave EBS-embedded Forms alone | Nothing; follow E-Business Suite 12.2 | The Forms are part of E-Business Suite 12.2 | Treating EBS screens as a custom migration by mistake |
Upgrading to 14.1.x buys time to December 2030, but it doesn't make hard-to-change code easier to change.
Oracle Forms migration to APEX appeals because APEX runs inside the Oracle Database and uses the same PL/SQL. It isn't a straight conversion, though: each screen is rebuilt as an APEX page.
Oracle Forms migration to Java, or to another web stack, has the largest scope, and every rebuilt screen has to be tested against what the old one actually did.
Where the 30-day assessment fits
Whichever option you lean toward, know what's in the Forms estate before you commit. The 30-day assessment is fixed in scope, at a price agreed before we start. Over 30 days we go through the Forms modules, PL/SQL libraries, Reports and database packages, establish which applications run standalone and which sit inside E-Business Suite, and map how they fit together with the database and the systems around them. We find the hidden architectural debt, such as rules duplicated across triggers, and flag the security and compliance gaps.
The report says in plain language what is broken and what it would take to fix it, application by application. Your own team can act on it, or we can do the upgrade or migration as a separate project with its own scope and price. Either way, the report is complete on its own.
Book a scoping call to talk through your Forms estate.