10decodersTwo paths, one deadline, and nobody will commit to either in writing.
Oracle's own position is that Premier Support for Fusion Middleware 12c concludes in December 2026 and Extended Support in December 2027, after which there are no updates and no security fixes. Every vendor you have spoken to agrees you must act. None of them will tell you which way — because that answer requires reading your Forms, and nobody has.
Upgrade to 14c
Cheaper, faster, buys you another support window. Also keeps you on Forms — with the same hiring problem and the same conversation again in a few years.
Migrate off Forms
APEX, Java, or .NET. Ends the dependency permanently. Costs more up front and every quote you have is a range with a ±40% on it.
Decide in December
The default, and the most expensive. Emergency migrations cost more than planned ones, and the runway is not getting longer.
The Proof Sprint is built to answer A-versus-B with evidence rather than opinion — and to do it in 30 days, which is the only reason it is still possible to decide before the deadline.
Find out whether your migration finishes before your support does.
Size your estate the way every vendor sizes it — object counts and a multiplier. Then see two things they never show you: how wide that estimate really is, and where your project lands against Oracle's support dates.
ends Dec 2026Extended
ends Dec 2027
You are on 12.2.1.4 — the release 14c upgrades are supported from. This is the best position to be in when the December deadline arrives, and the cheapest point from which to decide.
You are being asked to approve a $221K decision with a $176K margin of error. The Proof Sprint removes that band for $12,500 — 7.1% of the uncertainty itself.
Model assumptions — read these before you quote anyone
This is an indicative sizing model, not a quote. It is deliberately built the way conventional vendor estimates are built, so you can see how wide they necessarily are. Nobody — including us — can narrow that band without reading your Forms.
- Forms (.fmb): 14 engineering hours each
- Reports (.rdf): 9 engineering hours each
- Libraries & menus (.pll / .mmb): 12 engineering hours each
- Complexity multiplier: 1.0 / 1.35 / 1.8
- Blended delivery rate: $45 per hour
- Squad throughput: 600 engineering hours per month
- Pre-read uncertainty band: ±40%. Post-Sprint band: ±8%
Support dates are Oracle's own: Premier Support for Oracle Fusion Middleware 12c concludes December 2026 and Extended Support December 2027, after which Oracle provides no updates or security fixes. Source: Oracle Help Center, End of Support Notice for Oracle Fusion Middleware 12c.
The effort is never in the forms. It is in the six things nobody counts.
Trigger-level PL/SQL
Business logic spread across form, block and item triggers — thousands of lines invisible to any inventory that only counts .fmb files.
Forms built-ins
GO_BLOCK, SET_ITEM_PROPERTY, EXECUTE_QUERY and the rest. Trivial in Forms. Each one a design decision anywhere else.
WebUtil & client-side Java
File I/O, OLE, host commands, printing. No modern browser equivalent — every usage is a bespoke rebuild.
Oracle Reports
A separate product with its own migration path. Frequently forgotten in scoping, frequently half the surprise.
Base-table block coupling
Forms bound directly to tables, with no service layer between. Decoupling is most of the architecture work.
No regression suite
You cannot prove parity against a system that was never automatically tested. Most Forms estates never were.
Everyone else quotes, then migrates. We migrate, then quote.
We take one of your real Forms — the one you choose — migrate it in 30 days for a fixed fee, run it against a regression suite you approved, and only then put a number on the rest of the estate and a recommendation on upgrade versus migrate.
By the time you make the December decision, you are not reading a proposal. You are using the software.
Eight deliverables. You keep all of them regardless of what you decide.
| Deliverable | Standalone value |
|---|---|
| Forms & Reports inventory with dependency graphEvery .fmb, .rdf, .pll, .mmb, block, trigger, program unit and database object — machine-extracted from your source, not estimated from a workshop. | $2,450 |
| Migration risk registerThe specific objects that will not convert cleanly — WebUtil calls, client-side Java, Forms built-ins with no analogue, base-table coupling, embedded report calls — ranked by effort and published before you sign anything. | $3,500 |
| Upgrade-versus-migrate decision recordBoth paths costed against your actual estate: 14c upgrade effort and the support window it buys, against full migration to APEX, Java or .NET. With the reasoning and the rejected alternatives written down — a decision you can defend to a board. | $7,500 |
| One live form, migrated and runningYou choose the form — we do not. Deployed into your environment, against your data. Your users can open it and use it. | $18,000 |
| Automated regression harnessBuilt for that form, reusable across the entire migration. Yours to keep whether you continue with us or not. | $9,000 |
| Full-estate converter runOur automation-led converter executed across your whole Forms estate. You retain the output. | $6,500 |
| Fixed-price migration proposalOne number. One date. One scope. Not a range, not a time-and-materials rate card. | $4,000 |
| CTO-led readoutEdrin Thomas presents the findings to your engineering team and, if you want it, to your board. | Included |
| Total standalone value | $50,950 |
No discovery phase. Code from week one.
Your team's total time commitment: environment and source access in week one, a QA lead for two sessions in week two, and two hours in the readout.
Extract & inventory
Converter runs across the full estate. Forms, Reports, libraries and trigger PL/SQL mapped into a dependency graph. You pick the proof form from a ranked shortlist we hand you.
Architecture & harness
Upgrade-versus-migrate analysis completed and target architecture documented. Regression suite drafted with your QA lead — and signed by you.
Migrate
Form converted, hand-finished, integrated against your database. Daily build visible to your team.
Prove & price
Regression suite executed. Form deployed in your environment. Fixed-price proposal, decision record and CTO readout delivered.
Two guarantees. Both written into the SOW as milestone conditions.
The Parity Guarantee
You approve the regression suite at kickoff. We run it against the migrated form at the end. If it does not pass at 100%, you pay nothing — full refund, no negotiation, no pro-rating.
You keep the inventory, the risk register, the decision record, the harness and the converter output regardless. Parity is not our opinion; it is the suite you signed, executed on the record.
The Full Credit
Proceed to the full migration within 90 days of the readout and the entire $12,500 is credited against the program fee.
The proof costs you nothing. It is a deduction from a decision the December deadline is going to force anyway — not an additional line item.
There are only three ways this ends. You win two of them outright.
It works, you continue
Fee credited in full against the Exit Program. You started your migration with a proven form, a committed price, and months of runway still on the clock.
Net cost: $0Parity fails
Full refund. You keep $50,950 of inventory, risk register, decision record, regression harness and converted code.
Net cost: $0It works, you walk away
You paid $12,500 for a complete migration blueprint, a costed upgrade-versus-migrate recommendation, a working reference implementation, and a converted estate — usable by any vendor you choose.
Net cost: $12,500Outcome C is the only path where we get paid — and it is still the cheapest way to make a December decision you can defend.
All fixed price. None of them time-and-materials.
| Readiness Scan$2,4505 business days | Most chosenProof Sprint$12,50030 days · credited back | Exit Programfrom $195,0007–10 months · fixed price | |
|---|---|---|---|
| You end up with | A document telling you how bad it is. | Working software on your own Forms — plus a costed answer on upgrade versus migrate. | The whole estate migrated, tested, cut over, supported. |
| Forms migrated | None. | One full production form. | All of them, plus Reports. |
| Upgrade-vs-migrate decision record | A recommendation without numbers. | Both paths costed against your estate. | Already decided. |
| Converter run on full estate | No | Yes — output retained by you | Yes |
| Regression harness | No | Yes — yours to keep | Full suite, whole estate |
| Fixed-price number for the rest | An estimate range. | A committed number and date. | — |
| Guarantee | None. | Refund if parity fails. Credit if you proceed. | Fixed price; rework to UAT sign-off at our cost. |
| Fee credited if you proceed | No | 100% | — |
| Standalone value | $2,450 | $50,950 | Quoted per estate |
The Readiness Scan exists for organisations that need a paper trail before finance will release budget. If you already know you have a deadline, it is $2,450 spent confirming it. The Proof Sprint costs five times more, is the only option that puts running software in front of you, and is refunded either way.
We run four Proof Sprints a quarter.
The deadline is Oracle's, not ours
Premier Support for Fusion Middleware 12c concludes in December 2026 and Extended Support in December 2027. After those dates Oracle provides no updates and no security fixes. That clock runs whether or not you have made a decision.
A sprint uses a full squad
Thirty days of a dedicated migration team, not spare bench capacity. We do not oversell the calendar — which is precisely why the fixed price holds.
Pricing holds until end of quarter
After that the Sprint moves to $18,500. Signed sprints are honoured at the price on the date of signature.
