Oracle Forms Migration Service
To .NET (Windows Forms), with your current screens and reports intact.
Migrate before Oracle Forms 12c Extended Support ends in December 2027 — without rebuilding.
The deadline is already visible
Oracle Forms 12c Premier Support ends in December 2026 and Extended Support in December 2027. Moving to 14c means replacing the whole infrastructure.
To .NET without rebuilding
Screens (FMB) and triggers are converted into Windows Forms and C# with our own tool. The database is used as is, without schema changes.
Core business systems
We have migrated production systems with 253 FMB and 253 SQR programs, and 632 FMB with about 326,000 lines of trigger code.
Support deadlines around Oracle Forms
- Dec 2018Oracle Forms 11g Extended Support ended
- Jun 2022Internet Explorer 11 support ended — launching applets in a browser can no longer be assumed
- Dec 2024Oracle Forms / Reports 14c (14.1.2) released — the successor to 12c, with prerequisites
- Oct 2025Windows 10 support ended
- Dec 2026Oracle Forms / Reports 12c Premier Support ends
- Dec 2027Oracle Forms / Reports 12c Extended Support ends — patches and security fixes stop
- From Jan 2028Market Driven Support only for 12c (scope and cost unannounced)
Sources: Oracle, “Oracle Fusion Middleware — End of Premier and Extended Support”; Oracle Forms 14.1.2 Release Notes (as of September 2026)
The state of Oracle Forms — four points
The deadline is December 2027
Oracle Forms 12c is part of Fusion Middleware 12c. Extended Support lasts only one year.
Upgrading to 14c means a whole new stack
WebLogic 14.1.2, JDK 17 / 21 and Oracle Database 19.23 or later are prerequisites. Forms cannot be upgraded on its own.
Oracle Reports is deprecated
Deprecated since 12.2.1.3.0, with nothing added since. Your reporting needs a separate plan.
Clients still require a Java runtime
Java must be distributed and maintained on every client through Java Web Start or Forms Standalone Launcher.
Oracle Forms will not stop working. The burden grows because the prerequisites for keeping it running keep increasing.
Four migration options
Stay as is
Cost: low
Pros
- No further investment now
- No impact on operations
Cons and risks
- No patches after Dec 2027
- Cannot fix faults or law changes
- Engineers harder to find
Upgrade to Oracle Forms 14c
Cost: medium
Pros
- Forms assets reused as is
- Back under Oracle support
Cons and risks
- WebLogic, JDK, DB replaced too
- Java dependency remains
- Reports stays deprecated
Rebuild from scratch
Cost: high
Pros
- Business processes revisited
- Latest architecture available
Cons and risks
- Design documents required
- Largest effort and time
- Same behaviour hard to assure
Tool-assisted .NET migration
Cost: medium
Pros
- Spec carried over to .NET
- DB schema unchanged
- No WebLogic or Java
- Maintained in Visual Studio
Cons and risks
- Screen details need individual tuning
Move to .NET first to cut the dependency on Oracle middleware, then rebuild only what needs it — a two-step approach is the realistic one.
Target architecture
| Today | After migration | |
|---|---|---|
| Screens | FMB / FMX / MMB / MMX | Windows Forms |
| Logic | Triggers / PLL | C# |
| Reports | RDF / SQR | ActiveReports / C# |
| Development | Oracle Forms Builder | Visual Studio |
| Runtime | WebLogic + Java | .NET (no WebLogic, no Java) |
| Database | Oracle Database | Used as is (PostgreSQL etc. possible) |
Architecture after migration
1. Code converted from your assets
Screens (FMB), menus (MMB), shared PL/SQL (PLL), reports (RDF), OracleWrapper (stored procedures and types)
2. Compatibility libraries (ours)
OnDemandOne.OracleForms: built-ins, SYSTEM variables, triggers, MDI and DB access / OnDemandOne.OracleReports: the report engine
3. Standard technology
.NET / C#, Windows Forms, ODP.NET, ActiveReports (RDLX), NLog
The structure and naming of Oracle Forms are preserved. FormModule / Block / Item / Trigger become C# classes with the same names.
Desktop (ClickOnce) or Web (Blazor)
Windows Forms + ClickOnce
Microsoft’s standard way to distribute and update. On launch the app checks the server and fetches the latest version. Users without admin rights can install it, and no Java has to be maintained on clients.
- For core systems with many screens
- Prints directly to printers
- Uses local files and devices directly
Web version (Blazor Server)
Converted forms run on the server and the browser receives their appearance. The converted code is not rewritten — it is the same source as the Windows Forms version.
- Nothing to deploy to PCs; works remotely and across sites
- Input fields are native browser fields
- Requires a Windows server; recommended up to about 50 users
Migration process — four steps
Conversion
FMB / FMX, PLL, menus (MMB) and RDF are converted into C# and Windows Forms with our tool.
Embedded programs
Triggers and built-in functions that cannot be converted automatically are handled individually.
Unit testing
Using your current test cases, we check that the behaviour matches. This is our standard delivery scope.
Acceptance testing
You compare screens and reports with the current system; we fix any differences you point out.
With our AI-driven approach, issues are fixed once — in the conversion tool or the compatibility library — and reflected on every screen. About AI-driven modernization →
Reports, SQR and more
Oracle Reports
RDF layouts and output logic become ActiveReports for .NET report definitions, maintained in Visual Studio with PDF and Excel output.
SQR
SQR is converted to C# with an SQRP replacement. Batch design is reviewed as needed, so we check volume and processing up front.
Oracle UDT
Wrappers for user-defined types are generated automatically by our tool — no manual work per type.
Embedded Java
Java Beans / PJCs are analyzed and converted to C#, callable as Windows Forms controls in the same way.
Screen fidelity
Layout preserved
Control positions, sizes and tab order match the current screens.
Operation preserved
Function keys and focus movement stay the same, so procedures on the floor don’t change.
Low training cost
Because screens don’t change, users need almost no retraining.
Project examples
Core business system
Oracle Forms + SQR → Windows Forms + C#
484,957 lines converted in total. Performance issues in converted SQR were solved by redesigning the batch processing.
Production control
Oracle Forms + Reports → Windows Forms + ActiveReports
About 49,854 lines of triggers. Order-dependent processing was reproduced faithfully, and Java extensions were migrated.
Public sector system
Oracle Forms + Reports → Windows Forms + Microsoft Report
Included 39 production batches. Differences found in acceptance testing were handled individually.
Customer management (insurer)
Oracle Forms + embedded Java → Windows Forms + ActiveReports
326,221 lines of triggers and 104,697 built-in calls. Scope included 20 embedded Java classes and a Java web app update.
How we estimate
You don’t need to send us your source code. We are happy to sign an NDA first.
Share extracted XML
Send us the XML extracted from FMB / MMB / PLL / RDF with Oracle’s own tools (we’ll guide you). We analyze screens, trigger volume and built-in usage and present an approach and estimate.
Tell us the rough size
Tell us your Oracle Forms version, the number of FMB files, and whether you use Oracle Reports / SQR, and we will reply with an initial range.
What drives the estimate
- Number of screens (Canvas / Block)
- Trigger volume (lines)
- Built-in function usage
- Types of controls used
- Number of Reports / SQR
- Interfaces with other systems
Project phases
Survey and rough estimate
Led by us / 1–2 weeks
Inventory of volume, built-ins and controls; approach and rough estimate.
Conversion and unit testing
Led by us / by size
Conversion, handling of embedded programs, screen-level unit tests and a conversion report.
Acceptance and cutover
Shared / by size
Comparison with current screens and reports, integration and system tests, cutover.
Deliverables
- Complete Visual Studio solution (screens, logic, reports, compatibility libraries)
- Test results (screen-level screenshots and comparison with current screens)
- Operations documents (library guide, screen flow, troubleshooting guide, build and ClickOnce steps)
Optional services
Just tell us your Oracle Forms version and number of screens to start
Tell us the platform version and the number of screens, and we will send an initial answer. We are happy to sign an NDA first.
TEL +81-3-5962-3776