Contact us
Start building

Move Oracle Forms to Java

Generating the Java is the easy part. Our first AI run reported every one of 183 form elements migrated and nothing dropped, and the screen was still wrong. The hard problem is proving a migration is faithful, and that is what we are building in the open.

READ THE EXPERIMENT TALK TO US ABOUT YOUR APP
Oracle Forms featured image - Vaadin

First, the three routes we don't sell

Premier Support for Forms 12c ends in December 2026; on 14.1.x you have until 2030. The date is rarely what forces a migration. PL/SQL developers get harder to hire every year, and decades of validation and workflow logic sit inside forms nobody wants to open.

Upgrade in place to 14.1.2

The cheapest way to make the date go away, with your code and your architecture untouched. You buy four years and defer the same decision.

Run Forms in the browser

Third-party bridges run Forms server-side and stream the UI to a browser, usually with no code change. That fixes the client. Your logic still lives in Forms.

Move to Oracle APEX

Same PL/SQL, same database, no WebLogic licence, free for existing Oracle Database customers. Complex modules resist automatic conversion, and you stay on Oracle.

The fourth route:
move the application to Java

Forms is in Oracle's plan for Fusion Middleware 27, so nobody is forcing you off it. The question is whether you want to be hiring for Forms in 2030.

Target
Forms-shaped, but modern

Vaadin lets you build data-heavy, form-driven business apps entirely in Java: grids, validators, master-detail layouts, the patterns Forms developers already think in. No JavaScript, and no jumping between front-end and back-end stacks.

Method
Decisions before code

First a plain inventory of what your form contains, with no opinion about Java yet. Then your architecture choices turn that into a spec, the spec becomes small tickets, and code comes last. The rules behind it are public.

Evidence
One form, end to end

Oracle's Summit ORDERS form: 183 elements, 45 PL/SQL triggers, four blocks, migrated twice. The layout errors from run one became checks the build now has to pass. Summit's PL/SQL is simple, so this is a starting point.

Built to still be here in 2040

Vaadin has been building Java web frameworks since 2000 and maintains each major release for 15 years. Dynasoft used it to move Tosca, their 450-module Swiss ERP, off Oracle Forms, keeping the PL/SQL business logic rather than rewriting it in Java.

25 y

Building Java web frameworks
since 2000

85%
Of code automated in past migrations
(up to; Vaadin 7/8, Java Swing)
15 y

Maintenance per major release
from its announcement

Trusted by enterprise Java teams
lufthansa
hsbc
rockwell
jnj
festo
lufthansa
hsbc
rockwell
jnj
festo

Try it, or talk to us

Run our migration process on one of your own forms and tell us how it went. It's all public and free to use. Would rather not do it yourself? We sell commercial support, up to running the whole migration.

What you get:

  1. The migration process, rules and agent skills on GitHub, free to run against your own forms.

  2. 30 minutes with the engineer and product manager behind the migration work.

  3. Which of the four routes fits your application.