Oracle Forms
Oracle Forms Migration & Modernization to the Web, with AI
Codikel migrates your Oracle Forms applications to Oracle APEX or to the service architecture of your choice — Angular/React/Vue/Next/etc + Spring Boot/.NET/Express/NestJS/etc — cutting time and cost by 50–90% versus a manual rewrite. We don't transpile screen-for-screen: we build a knowledge graph of your system and re-architect it into a clean service layer.
Get a free assessment →Why migrate Oracle Forms now?
Oracle Forms 12c Premier Support ends in December 2026, and Extended Support in December 2027. After that, staying on Forms means running business-critical applications with no security patches and no vendor support. For most teams the problem isn't technical — it's the calendar: how long a migration takes, and whether it finishes in time.
That's exactly what Codikel solves: it compresses work that takes years by hand into a fraction of the time.
Which architecture should you migrate to?
There's no single right answer — it depends on your team, your stack, and your horizon. Codikel migrates to the three main targets:
| Target | When it fits | What you get |
|---|---|---|
| Oracle APEX | Teams that want to stay inside the Oracle world, low-code | Smaller skills shift, current Oracle support |
| Spring Boot / REST / etc service layer + React / Angular / etc front-end | Java teams, enterprise-scale apps, integration with other systems | Decoupled backend, reusable REST API, free choice of front-end |
| .NET | Microsoft-ecosystem organizations | Modern .NET services, native fit with the Microsoft stack |
How does the Codikel engine work?
Unlike a transpiler that translates each form into an equivalent screen, Codikel works in three steps:
- Knowledge graphWe analyze the whole Forms system — forms, PL/SQL logic, dependencies — and represent it as a graph that captures what the system does, not just how it's written.
- Re-architecture to servicesWe transform the procedural logic into a clean service layer. Stored procedures already living in the database are preserved and reused — we don't rewrite what already works. We develop to your own code, architecture, and security standards.
- VerificationEvery migrated component is validated against the original behavior — unit tests, API tests, functional obligations, and UI tests.
The result isn't a modernized clone of a legacy app — it's an application with an architecture your team can maintain and evolve.
See it in action
Proven at enterprise scale
Codikel migrated the legacy system of Forus — a multinational retailer with 400+ stores across 4 countries — to Spring Boot + React: 500 forms and ~550,000 lines of code in 14 months, work manually estimated at roughly 16 years.
That project was a Delphi modernization. The engine and the approach are the same ones we apply to Oracle Forms: knowledge-graph analysis, re-architecture into a service layer, verification. The scale of Forus is the proof the engine holds up on real enterprise systems.
Choosing to trust Generative AI was the key differentiator. It wasn't about “translating” code, but about understanding the architecture, using knowledge graphs, mapping the dependencies and complex logic — and above all, preserving the DNA of the business.
— Gustavo Rivera Luna, CDTO · CIO, Forus · See the LinkedIn post (translated from the original Spanish)
What gets migrated, and what stays?
- Re-architected: the procedural logic in your forms moves to APEX or a modern service layer.
- Preserved and reused: the stored procedures already living in the database. We don't touch what already works well.
- What Codikel does NOT do (and why that's an advantage): we don't redesign your data model, we don't re-orient the system by domains in the same pass, and we don't change the functional flow your users already know. That keeps the migration bounded, verifiable, and low-risk.
How much does an Oracle Forms migration cost, and how long does it take?
Timeline and cost depend on the size and complexity of the system (number of forms and reports). As a concrete reference point: the Forus system — 500 forms, 550,000 lines — was migrated in 14 months. The starting point is a free assessment: with the number of forms and reports, we quickly give you an estimate of scope, timeline, and cost within 15% variance. If it makes sense, we can run a low-cost POC and use it to finalize the estimate.
Get your free assessment →Frequently asked questions
Can Oracle Forms migration be automated?
Yes. Codikel automates the analysis and re-architecture of the code via a knowledge graph and generative AI. That automation is what delivers the 50–90% savings in time and cost over a manual rewrite.
Migration vs. modernization — what's the difference?
A “migration” that only replicates screen-for-screen leaves you with the same old application on new technology. Codikel modernizes: it re-architects the logic into a maintainable service layer, not a clone with different syntax.
What happens to my PL/SQL code?
Stored procedures that live in the database are preserved and reused. Procedural logic inside the forms is split between front-end and back-end, depending on the type of logic.
What technologies does Codikel migrate to?
Oracle APEX or a Spring Boot/REST service layer, or .NET — whichever best fits your team and stack.
When does Oracle Forms support end?
12c Premier Support ends in December 2026 and Extended Support in December 2027. Always verify the exact dates for your version in Oracle's official documentation.
Has Codikel migrated enterprise-scale systems?
Yes. The largest public case is Forus (500 forms, 550,000 lines, 14 months) — a Delphi modernization done with the same engine we apply to Oracle Forms. We're also migrating one of the largest ERPs in Latin America, with several modules already live in production.
Have Oracle Forms to modernize?
Tell us how many forms and reports you have and we'll give you a real estimate of scope, timeline, and cost. No commitment.
Get a free assessment →