IBM MQ → RabbitMQ
Phased migration with legacy code refactoring
Legacy messaging replaced in phases while the applications calling it were refactored. No big-bang cutover; each phase reviewed before the next.
Forms applications keep much of their logic in PL/SQL and in triggers on the screens. We find that logic, pin it down with tests, then move it screen by screen.
ORDERS.fmbremovedPKG_ORDERS.pkbremovedOrderService.java+96−0OrderController.java+41−0orders.tsx+128−0Stacks we work in
An Oracle Forms migration moves Forms screens to a Java back end with a web front end, or to Oracle APEX, while the PL/SQL business rules are kept and proven with tests. Ace8 delivers the Java target itself through the AceMQ engineering team. The first phase is an inventory of forms, triggers and PL/SQL units, agreed as a fixed price after a scoping call.
Options
The realistic targets are a Java application with a web front end, Oracle APEX, or a low-code platform. The table shows where each one fits. Which one is right depends on how much logic lives in the screens and how much in the database.
Fits when: Forms are complex, the app must integrate with other systems, you want an open and widely staffed stack
What you get: Business logic in services, screens rebuilt in a web framework, database kept
Watch out for: Largest rebuild effort; every screen is redone
Fits when: Logic is already in the database, the team knows Oracle, screens are mostly forms and reports
What you get: Screens rebuilt in APEX on the same Oracle database, PL/SQL stays where it is
Watch out for: Keeps the application tied to Oracle Database and APEX
Fits when: Simple data-entry screens, few integrations
What you get: Screens assembled in a vendor tool
Watch out for: Platform licence and lock-in; complex triggers do not map cleanly
Fits when: The app is stable and the team can still maintain it
What you get: Current Forms release, no rebuild
Watch out for: Skills and the web client remain a risk
Reasons
Oracle has not withdrawn Forms: it released Forms and Reports 14.1.2 on 19 December 2024, and its Statement of Direction for Forms says further releases are planned, with features depending on market demand. Teams move for other reasons. Oracle's own Fusion Middleware Lifetime Support Policy defines Premier, Extended and Sustaining stages, and the date for your release is in that document, so check it for the version you run.
Few engineers learn Forms, so every change costs more and takes longer.
Running Forms in a browser needs an Oracle middleware stack that must be licensed and patched alongside the database.
Web, mobile and API users expect screens and integrations that Forms was not built for.
Method
We extract the rules from the PL/SQL and the form triggers, then write characterization tests that record what the current system does on real inputs. The new code must produce the same answers before anything is retired.
List every form, block, trigger, program unit, stored procedure and report, with data volumes and who uses each screen.
Separate rules that live in the database from rules that live in form triggers. Database logic is often kept as it is.
Run real cases through the old system, record the results and replay them against the new one.
Move one module at a time into the chosen target, with engineer review of every change. AI-assisted tools can draft code and tests; they do not replace the comparison. See AI-assisted modernization.
How it runs
Ace8 scopes and delivers the move. AceMQ engineers support the new stack 24/7 from day one.
Scope, cost and AI readiness, before any migration starts. Characterization tests and a baseline before we touch a line.
AI-assisted, engineer-verified, one capability at a time. Tools draft the rewrite and a senior engineer signs every change.
Tested, reversible cutover. AceMQ engineers support the new stack from day one. Supported after migration →
Cutover
Each module goes live on its own, while the rest of the application stays on Forms. Users move group by group, and a rollback stays available until a module has run clean. This is the same small-reversible-steps idea as the strangler fig pattern and the Ace8 method.
Order modules by risk and by how many other modules depend on them.
Share one database during the move, so old and new screens see the same data.
Retire Forms only when the last module is live and the tests agree.
Evidence
Ace8 has not yet published an Oracle Forms migration or any figures for one.
Results will be listed here as Pending until we have a run to report. Nothing on this page is a promise of time or cost.
Results publish here when the run completes. No figures until then.
Next step
Book a fixed-price assessment.
It returns the form inventory, a recommended target per module and a fixed price for phase one. For the wider options see Java modernization and legacy application modernization.
Broadcom Expert Advantage Tanzu Services Partner of the Year, AMER, 2025 · awarded to the AceMQ engineering team
Proof
The engineers behind Ace8 are the AceMQ team, and this is work they delivered. Ace8 is the new name for that practice, not a new team.
IBM MQ → RabbitMQ
Legacy messaging replaced in phases while the applications calling it were refactored. No big-bang cutover; each phase reviewed before the next.
FAQ
Short answers to what buyers ask first. Something else on your mind? Ask an engineer.
Tools can convert some screens and code, but triggers, PL/SQL interplay and screen behaviour need engineers and tests. We use tools for the mechanical parts and compare results before retiring anything.
APEX fits when logic is already in the Oracle database and the team is Oracle-centric. Java fits when the app must integrate widely or you want to move off Oracle-specific tooling. The assessment recommends one per module.
It depends on the number of forms, trigger complexity and test coverage. We size it in the assessment and quote a fixed price for the first phase rather than a general figure.
No. Many migrations keep the Oracle database and move only the screens. Moving the database is a separate decision; see database modernization.
Start here
A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.
Get in touch
Tell us what you run today. An engineer, not a sales script, replies within one business day.