Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
Oracle Forms is one of the most widely deployed development frameworks in enterprise IT history. Introduced in the 1980s and reaching maturity through the Oracle Forms 6i and 10g era, it underpins thousands of mission-critical business applications across government, financial services, healthcare, utilities, and manufacturing. Oracle Reports generates the financial, operational, and regulatory reporting output that these organisations depend on daily.
Oracle's official position is that both Oracle Forms and Oracle Reports are on a sunset trajectory. Oracle APEX (Application Express) is Oracle's stated replacement path for Forms applications. Oracle's sales team presents APEX migration as a strategic opportunity. The reality is that APEX migration of a mature Oracle Forms application is a substantial development project — not a migration, but a rebuild — with typical costs of $2M–$15M+ for large Forms estates.
Third-party support for Oracle Forms and Reports changes this calculation. You keep your working Forms applications, eliminate the Oracle sustaining support fee, and make the migration decision on your own commercial timeline — not Oracle's renewal pressure schedule.
Oracle Forms and Reports Version Timeline
| Version | Premier Support End | Extended Support End | Sustaining Support | TPS Viable |
|---|---|---|---|---|
| Forms/Reports 6i | Nov 2010 | Extended ended 2013 | Sustaining only (no patches) | Yes — high demand |
| Forms/Reports 10g (10.1.2.x) | Jul 2010 | Extended ended 2013 | Sustaining only | Yes |
| Forms/Reports 11g (11.1.2.x) | Jan 2015 | Extended ended 2018 | Sustaining only | Yes |
| Forms/Reports 12c (12.2.1.x) | Dec 2022 | Extended ended Dec 2025 | Sustaining only from Jan 2026 | Yes — immediate demand |
| Forms/Reports 14c (14.1.0.x) | Dec 2026 (est.) | TBC | Premier active | N/A (current) |
The immediate TPS opportunity is Oracle Forms and Reports 12c. Extended support ended in December 2025, meaning that from January 2026, Oracle 12c Forms customers are in "sustaining support" — a tier where Oracle provides no new patches, no new security fixes, and no updates. Yet Oracle continues to charge annual support fees at 22% of licence value for this sustaining support tier.
GoVendorFree covers Oracle Forms and Reports versions 6i through 12c under full third-party support. The most active TPS demand is for Forms 12c customers who recently lost extended support access.
The APEX Migration Reality Check
Oracle's APEX pitch is consistent: "Forms is old, APEX is modern, migration is straightforward." Each element of this pitch warrants scrutiny.
Forms is old — this is true in terms of technology vintage. It is not true in terms of functional reliability. Oracle Forms applications deployed in the 1990s and 2000s have run continuously and correctly for decades. The applications work. The business rules embedded in them are accurate. The users who operate them are trained on them. "Old" is not a synonym for "broken".
APEX is modern — also true. APEX is a capable web-based development framework. But APEX and Oracle Forms are not functionally equivalent. Forms applications are typically characterised by complex multi-block forms with tight Oracle database integration, PL/SQL business logic, and Oracle Reports output. APEX handles these patterns differently — in many cases requiring a ground-up redesign of the application logic rather than a code conversion.
Migration is straightforward — this is where Oracle's field sales rhetoric most dramatically diverges from client reality. Organisations that have attempted large-scale Forms-to-APEX migrations consistently report projects running 2–4x their original budget estimates and 1.5–3x their planned timelines. The reason is that Oracle Forms applications accumulated business logic over decades — in triggers, PL/SQL procedures, database packages, and application-level validations — that is not systematically documented and cannot be automatically converted.
Running Oracle Forms 12c or Earlier?
Tell us your current Oracle support contract value. We'll build a TPS cost model showing your annual saving — no commitment required.
Get Oracle Forms Estimate →Oracle Forms TPS Cost Model
Oracle Forms and Reports support fees are calculated as part of the broader Oracle technology licence support contract — typically at 22% of the Forms and Reports licence value, combined with other Oracle technology products (Database, WebLogic, etc.) in a Technical Support Identifier (CSI) structure. Extracting the Forms-specific support cost from an Oracle contract requires analysis of the CSI breakdown, but typical Forms support costs run as follows:
| Organisation Profile | Forms Application Scale | Oracle Annual Support (Est.) | GoVendorFree TPS | Annual Saving |
|---|---|---|---|---|
| Government department | 50–150 Forms modules | $180,000 | $63,000 | $117,000 (65%) |
| Mid-size utilities company | 150–400 Forms modules | $320,000 | $112,000 | $208,000 (65%) |
| Large financial institution | 400–1,000 Forms modules | $680,000 | $238,000 | $442,000 (65%) |
| Healthcare/Insurance enterprise | 1,000+ Forms modules | $1.2M+ | $420,000 | $780,000 (65%) |
Estimates based on typical Oracle contract structures. Actual savings depend on your CSI composition and Forms licence value.
What GoVendorFree Covers for Oracle Forms and Reports
GoVendorFree's Oracle Forms and Reports support covers both the application layer and the underlying technology stack components required for Forms to function. Our Forms support engineers carry deep expertise in Forms PL/SQL development, Forms Builder configuration, Oracle Reports Server, and the WebLogic integration layer used in 11g and 12c deployments.
Oracle Forms Coverage
- Oracle Forms Builder (6i, 10g, 11g, 12c) — application configuration and break-fix
- Oracle Forms Runtime and Forms Servlet configuration
- Forms PL/SQL trigger and procedure support
- Oracle HTTP Server and WebLogic integration (11g/12c)
- Character mode and GUI mode Forms environments
- Oracle Forms Java Bean integration
- Forms performance diagnostics and tuning
Oracle Reports Coverage
- Oracle Reports Builder and Reports Server (all supported versions)
- Oracle Reports scheduling and distribution
- Oracle BI Publisher integration where Reports is used as data source
- Reports output format configuration (PDF, HTML, XML, RTF)
- Oracle Reports security and authentication configuration
Stack-Level Coverage
- Oracle WebLogic Server integration layer (for 11g/12c Forms)
- Oracle HTTP Server (OHS) / Apache integration
- Oracle Database PL/SQL procedures and packages called by Forms
- Security advisory for Forms-related CVEs
Oracle Forms by Sector
Government and public sector: Oracle Forms is particularly deeply embedded in UK central government, European public administration, and US federal/state agencies. Forms applications here are often 15–25 years old, tightly integrated with core financial systems, and subject to procurement rules that make replacement projects slow and complex. TPS provides a cost-effective way to maintain operational coverage while long-term replacement programmes proceed at their own pace.
Financial services: Core banking ancillaries, insurance policy administration systems, and treasury operations applications built on Oracle Forms are still live at tier-1 financial institutions globally. The regulatory change management overhead for replacing these applications makes rapid migration impractical. TPS reduces support cost while the institution determines its long-term application architecture.
Utilities and energy: Customer billing, network asset management, and metering applications built on Oracle Forms are common across utilities. Many of these applications are tightly integrated with Oracle E-Business Suite — which creates an Oracle-wide TPS opportunity rather than a Forms-only engagement.
Oracle E-Business Suite integration: Many Oracle Forms applications are run as extensions to Oracle E-Business Suite — bespoke Forms modules that extend standard EBS functionality. For EBS customers already considering TPS for their main Oracle database and EBS stack, the Forms components are a natural extension of the same engagement. GoVendorFree covers Oracle EBS and custom Forms extensions as part of integrated Oracle TPS support.
Your Four Options for Oracle Forms in 2026
Third-Party Support (GoVendorFree)
Stay on your current Forms version under GoVendorFree coverage. 55–65% cost saving vs. Oracle support. Full Forms runtime and stack coverage. Removes Oracle sustaining support fee with no functional change.
Migrate to Oracle APEX
Oracle's preferred path. Web-based development framework. Not a Forms migration — a Forms rebuild. Budget $2M–$15M+ for large estates. 2–4 year project for complex applications. Justified when Forms functionality genuinely constrains the business.
Upgrade to Oracle Forms 14c
Oracle Forms 14c is the current version. Maintains Forms architecture with WLS integration. Upgrade project required (testing and re-deployment). Does not solve the long-term Oracle support cost issue — you remain on Oracle's 22% support fee model.
Forms-to-Web Commercial Converters
Tools like Entrinsik Informer, LANSA, or Unison for Forms claim to automate conversion. Results vary significantly by application complexity. Partial conversion tools — do not handle complex PL/SQL trigger logic. Useful for simple Forms; not for enterprise-scale estates.
Oracle Support Cost Reduction: The Complete Playbook
24 pages covering Oracle's 22% support fee model, ULA and PULA traps, third-party support economics, and a 12-step renewal negotiation framework. Directly applicable to Oracle Forms and Reports support contracts.
Download Free →Related reading: Oracle Third-Party Support: The Complete Guide · Oracle E-Business Suite TPS · Oracle Database TPS · Oracle WebLogic Support · Oracle Support Services