Oracle's own answer to Forms is now "rebuild it." The question is where, and with what proof it went right. Marcus — Kinetech's AI Mendix developer — reads your Forms modules and PL/SQL directly, turns each one into a specification you approve, and rebuilds it in Mendix with evidence at every gate.
01 · The clock
Oracle Forms 14c is supported — Premier Support to December 2030, Extended to roughly 2032 under the lifetime-support revision Oracle published in February 2026. That's runway, and it's real. What it isn't is a future: 12c is already past Premier Support, and every upgrade cycle is a forced WebLogic-and-Java infrastructure project just to stand still.
Since the browser Java plugin died, running Forms means the Forms Standalone Launcher on every desktop and a WebLogic stack behind it — an infrastructure tax on an application layer that isn't gaining features. And the people who built your forms are leaving the workforce faster than replacements arrive.
The fact that settles the strategy question: Oracle desupported its own Forms-to-APEX migration tooling as of APEX 21.1, saying automated conversion wouldn't deliver a complete migration — and now recommends rebuilding Forms applications from scratch (per Oracle's APEX blog). Even the vendor says it's a rebuild. The only open question is which platform you rebuild on, and how much of the work — and the risk — you carry by hand.
02 · The unlock
A Forms application is not a mystery to be re-discovered in workshops. It's a set of machine-readable artifacts — and Marcus reads them at the source, using Oracle's own export tooling, before anyone schedules a requirements meeting.
| Your artifact | What Marcus extracts | Where it lands in Mendix |
|---|---|---|
| .fmb modules via Oracle's own Forms2XML / frmf2xml |
Blocks, items, canvases, LOVs, record groups — and every trigger, with its full PL/SQL body | Entities & associations, pages and data grids, reference selectors, microflows |
| Database schema + ALL_SOURCE | Tables, constraints, and the stored PL/SQL packages where much of the real logic lives | The domain model — with heavy packages left in the database, called through the database connector |
| .pll libraries & menu modules | Shared procedures, menu structure, menu-level security | Reusable microflows, navigation, user roles |
| Oracle Reports .rdf | Report queries and layout intent | Modern generated PDF documents (see section 05) |
An honest caveat: Forms logic is scattered by design — item-level, block-level, and form-level triggers, plus attached libraries and menus. Extraction finds all of it, but deciding what each fragment means is judgment work. That's exactly why the output of extraction is a written specification your team approves — not code that appears by magic.
03 · How a migration runs
The same governed delivery discipline Kinetech applies to its own regulated-industry work, with four gates held by you:
Each form's extracted specification — data, rules, roles, screens — in plain English, approved before a line of the model is written.
Your Forms and menu security matrix, restated as Mendix roles and entity access, signed off by you — not inferred silently.
Styled design directions derived from your brand before pages are generated. You pick; Marcus builds to it.
A rebuilt app reaches you only after all quality gates pass — and cuts over only when you accept it, evidence in hand.
04 · The date
Here is the commitment we will put in writing. The assessment does not end with a range — it ends with a date, sized from your actual extracted complexity. Miss that date and the assessment fee comes back. We can promise a date because we never quote a calendar before reading your source.
The assessment names the date. Miss it, and the assessment fee comes back.
That is a real term, not a slide. It is affordable to us for one reason: the clock below starts only when a complete artifact pack is in our hands, and it pauses only for your own approval gates.
| One Forms module set | Complete artifact pack → UAT-ready |
|---|---|
| Compact — ≤15 forms, ≤10 reports, logic mostly in PL/SQL packages | 2–3 weeks |
| Departmental — 15–40 forms, 10–30 reports, 2–4 integrations | 4–6 weeks · ~30 days typical |
| Load-bearing — 40+ forms, heavy form-level PL/SQL, custom .pll libraries, a Reports estate | 8–12 weeks |
| Each further module in the same estate | 30–40% faster |
Sizing model, not a price list — the assessment reads your actual source and returns one date. Bands assume a single rebuild boundary agreed at the scope gate.
The date is only honest if the inputs are complete, so here is the whole list up front. Nothing on it is unusual, and most of it exists already.
Three approval gates are yours: scope, permission ratification, design sign-off. We answer each within three business days. Time beyond that on your side moves the date by exactly that much — and nothing else does.
Production cutover on your change calendar. SSO and network provisioning by your IT. Third-party licenses or vendor contracts we don't control. Remediation of source-data quality problems the assessment flagged. Anything added after the scope gate.
Functional parity against the approved specification, running on your migrated data in a parallel environment, with production security enforced and tested per role, all nine quality gates green, and documentation published. Your users click through it.
Forms migrations run faster than they look, for one reason: a large share of the business logic already sits in PL/SQL packages in the database, and it can stay there — Mendix calls it. What moves the date is logic that lives in form-level triggers instead, Reports output that has to be reproduced exactly, and .pll libraries shared across modules you were not planning to touch.
05 · The platform question
APEX is Oracle's recommended destination, it's included with the database, and if your organization intends to be all-Oracle forever, it's a reasonable choice. We'd rather concede that up front than pretend otherwise.
Here's the case for rebuilding on Mendix instead:
06 · Straight talk
07 · Quality & security
Watch real build evidence land on the live Build Console, and see the delivery lifecycle at our interactive explainer.
08 · Engagement & pricing
We take your Forms2XML exports and schema access, and return a scored inventory: what to retire, what to rebuild, in what order — with a per-app fixed-bid quote and a rebuilt sample of one representative form as proof.
Each app rebuilt from its approved specification for the price quoted in the assessment. Tested per role, documented, evidence published, accepted by you before cutover.
For estates measured in dozens of forms: Priced on what the work is, how many lanes run in parallel, and how fast you need it — always (a Kinetech engineer reviews every release, with an SLA). The instance works your migration backlog continuously.
Prefer to pay for AI usage directly? Bring your own Claude access — a direct Anthropic API key or Claude through your AWS Bedrock / Google Cloud commitment — and take roughly 15–25% of the monthly off either instance plan, with per-build costs visible on your Console.
Pilot-program pricing, subject to a signed order form; heavy build months on bundled plans may incur metered usage beyond the stated allowance.
09 · The questions you should ask
For your heads-down data-entry users — yes, at first, and we won't pretend otherwise. Expect a period of weeks, not days, before they match old speeds. What we do about it: keyboard shortcuts, inline grid editing, and focused task pages designed in a UX-parity workshop with your power users before design sign-off — not after go-live complaints. The trade is real: a learning curve for them, versus an application the rest of the organization can finally reach from a browser, a tablet, or the field.
No — and you shouldn't want us to. Mendix calls your existing packages and views through its database connector, so proven logic keeps running exactly where it is on day one. Logic migrates into microflows incrementally, where it improves maintainability — and some of it, particularly bulk batch work, should stay in the database permanently. The assessment tells you which is which, in writing.
If the license fee were the whole cost, APEX would win — we concede that. The real cost is the rebuild itself (which Oracle says you're doing either way), the ongoing lock-in (APEX lives inside the Oracle database; Mendix runs anywhere), and the capabilities your backlog actually needs — workflow, task management, native mobile, offline. Price the rebuild plus five years of platform strategy, not the license line alone.
Agreed — the record is poor, and Oracle retiring its own converter is the proof. The difference is what gets automated. Marcus doesn't transpile Forms code into generated spaghetti; it reads the exports, produces a plain-English specification per app, and only after you approve that spec does it build — natively, in Mendix, through the same 9 evidence gates as any Kinetech delivery. The automation is in the reading and the rebuilding; the judgment stays human and on the record.
They're rebuilt as documents generated inside the application — server-rendered PDFs from your data, matched against your real report samples during the assessment so fidelity is judged on evidence, not promises. Oracle Reports is itself end-of-life, so this work is owed to you regardless of which platform you choose.
Because 2030 is a runway, not a destination — and the constraint that bites first isn't the support date, it's people. Forms expertise is leaving the workforce, and every infrastructure refresh between now and then is money spent standing still. Starting now means migrating a few forms a month calmly, on your schedule, with the old system fully alive as the safety net — instead of a forced march later.
Yes. Standard Mendix models in your Team Server repository, validated with Mendix's own checker, fully documented in-model, openable and extendable in Studio Pro by any Mendix developer. If you stop working with us, you keep everything — that portability is the proof the work is real.
10 · Next step
Pick one simple form, one typical one, and the one everybody's afraid of. The assessment returns a scored inventory, per-app quotes, and one of the three rebuilt in Mendix — with the evidence — so you judge this on proof, not slides.
Marc Lehane · Solutions Architect / CTO, Kinetech · [email protected]
Kinetech Cloud · San Antonio, TX · How we deliver · Live Build Console
You are reading Your platform — deeper detail on step 4, Why now?.
That is the pressure. What it costs to answer it is not one number — three things move it.