Step two: Leave Oracle
Leave Oracle. Keep your business logic.
Move your database to PostgreSQL and connect your web application to it. Your people see the same screens, and the Oracle database licence ends.
Why keep your logic
The data is the easy part
Moving tables and rows is the easy part of leaving Oracle.
Your business logic lives in your Forms and your database: triggers, program units and PL/SQL written over many years. Rewriting it means rebuilding and testing every rule. If your rules work, keep them.
In step one, Keep Oracle turns your Forms and Reports into a web application, still on your Oracle database. In step two, Forms Migration moves the database to PostgreSQL and connects that web application to it, with all your logic.
On its own, the move ends the Oracle database licence. With step one's browser screens, you stop paying Oracle altogether.
Built on open-source technology.
A silent switch
One switch. Your screens keep working.
Database: Oracle
Move your database to PostgreSQL and connect your web application to it. Your people see the same screens, and the Oracle database licence ends.
Show the engineering
forms-migrate moves your tables, data and PL/SQL code to PostgreSQL. magic-broker sits between your application and the database, so nothing on the screen changes. Written in Rust, and every result is compared with your Oracle before you switch.
In the middle: magic-broker
magic-broker sits between your application and your database. When the database moves to PostgreSQL, it takes care of the differences, so your screens, your reports and your users carry on as before. Move one screen or one database at a time, and switch when you are ready.
It is written in Rust for speed and safety, streams results so memory stays flat on the largest reports, and every result is checked against your original Oracle database before you switch.
The migration report
Every table matched
After moving a real customer database to PostgreSQL, every table, sequence and view came out the same.
The migration report lists tables, sequences, views and code, each compared equal.
What staying on Oracle costs
One highly available Oracle setup, at Oracle list price
Database licences
$760,000
2 servers, 16 cores each
Forms and Reports licences
$184,000
2 servers, 8 cores each
Support, every year
$207,680
22% of the licence price
Five years
$1,982,400
About QAR 7.2 million
With open source, the licence and support lines are zero. You pay only for the servers you choose: your own, in Qatar, or any cloud.
Source: Oracle Technology Global Price List, 15 September 2026. US dollars, before discounts. Processor licences counted as cores × 0.5 (Intel and AMD); the standby server is licensed too. Excludes options such as Partitioning and the Diagnostics and Tuning Packs, and yearly support increases.
Already on AWS? Five years of one highly available database
PostgreSQL on AWS
$108,000
Lowest
No Oracle licence
Oracle Standard Edition 2
$206,600
91% more
Licence included in the AWS price
Oracle Enterprise Edition
$897,000
731% more
Your own licence, plus Oracle support
Same server, same storage. The difference is the Oracle bill.
Source: Amazon RDS price list, 13 November 2026. Bahrain region, on-demand, Multi-AZ, 8 vCPU and 64 GB server. Enterprise Edition: 8 processor licences at Oracle list price (2 vCPUs per licence, standby included), $380,000 once plus $83,600 support a year. Storage, the same for all three, not included.
Work out your own figure
Example figures. Replace them with yours.
Up to 20 years
Paid to Oracle over the period
QAR 1,250,000PostgreSQL has no licence fee
Your own figures. Ask us about Forms Migration's pilot terms.
What you gain
Your database, set free
No lock-in, no audits
Your database, your rules, no contract renewals.
Grows with you
From one server to many as your business grows.
Runs anywhere
Your own servers, a data centre in Qatar, or any cloud.
Easy to staff and connect
A huge community, skilled developers and standard tools.
The money you spent on Oracle goes back into your business. See how it stays up
Carried out for you, one step at a time
- The Forms Migration team carries out the database move as a service.
- Every result is compared with your Oracle before you switch, and the migration report shows the comparison.
- No big-bang switch: one screen or one database at a time.
- magic-broker and the translator then run at your site, for as long as your application runs.
For engineers
Questions engineers ask
Do our screens change?
No. The web application from step one connects to PostgreSQL instead of Oracle. magic-broker sits between the application and the database, so nothing on the screen changes.
What if our database uses a feature that is not supported yet?
You know before you switch. Every Oracle feature your database uses is listed and checked against Oracle itself, and anything not yet proven stays on that list.
Can we go back to Oracle?
Yes, until you switch your Oracle off. Going back means changing one value in a configuration file and restarting, for your Forms and for the browser screens. If you ask for it, every record saved after the move also goes to Oracle, so it is never behind.
Where does it run?
At your site. magic-broker and the translator run there for as long as your application runs, and memory stays flat on the largest reports.