flagship ⭐
Oracle to PostgreSQL migration, with a capped price.
You stop paying Oracle licensing without betting your operation. Our own method, a parallel run and a reversible cut: Oracle stays alive until PostgreSQL proves it responds the same or better.
the method
Six steps. None gets skipped.
Automated inventory
Our toolkit walks your database and builds the full object inventory: tables, views, PL/SQL, triggers, jobs, types and dependencies. You know exactly what has to move before moving anything.
$ dbx inventory --db=ORCL --out=inventory.jsonConversion
We convert schema and logic to PostgreSQL. What translates automatically, translates; what needs human judgment —complex PL/SQL, partitions, engine dependencies— is done by hand and documented.
$ dbx convert --schema --plsql --reportRow-by-row integrity check
Running is not enough. We compare source and target row by row and checksum by checksum. If a single value does not match, we do not move on.
$ dbx verify --rowcount --checksum --strictParallel run
Oracle and PostgreSQL run in parallel for an agreed window. We compare results under real load until we have evidence PostgreSQL responds the same or better.
$ dbx parallel-run --window=14d --compareReversible cutover
The final cut has a tested path back. If anything is off at cutover, it rolls back to Oracle with no data loss. Reversibility is not theory: it is tested first.
$ dbx cutover --plan --rollback-testedHypercare
After the cut we do not disappear. We stay with the operation the first days, tune what real load reveals, and leave the system stable before closing. This is usually where the retainer starts.
$ dbx hypercare --days=15 --tunestaged pricing · capped
You pay per stage, with a result in each one.
Object inventory, compatibility and risk matrix, effort estimate and pilot plan.
USD $1,950 – 2,500
Schema converted, first critical objects converted and validated, parallel environment set up.
from USD $7,500
All logic migrated, row-by-row validation, parallel run under real load.
in stages
Reversible cut, production support and a monthly-operation proposal.
up to USD $25,000+ by scope
// Prices in USD, invoiced from the US LLC (CFDI in MXN also available).
FAQ
What a skeptical director asks first.
What about my PL/SQL? Is it lost?
No. PL/SQL is converted to PL/pgSQL. What translates directly is automated; what depends on Oracle specifics is rewritten by hand, tested and documented. The initial inventory tells you, up front, what percentage is direct and what needs manual work.
How long does a migration take?
It depends on the number of objects and PL/SQL complexity, which is why it starts with an assessment: first we measure, then we commit to a staged plan. A mid-size database usually goes in phases over several weeks, with the parallel run going while Oracle stays in production.
What risk does my operation run?
Oracle stays in production until PostgreSQL proves, under real load and in parallel, that it responds the same or better. Cutover only happens once row-by-row validation passes and rollback is tested. We never turn something off hoping the new thing works.
What if the cutover fails?
It rolls back to Oracle. The cutover plan includes a rollback tested before cutover day; going back is a rehearsed procedure, not improvisation.
Why PostgreSQL and not stay on Oracle?
Because for most workloads PostgreSQL covers what Oracle covers without the licensing cost or audit exposure. It is not absolute: if your case truly needs Oracle, we tell you. Technical honesty comes before the sale.
Who owns the result?
You do. The converted schema, scripts, documentation and data stay in your hands. No licenses tie you to us, no proprietary pieces only we can maintain.
next_step
Before you migrate, measure. Then decide.
The Migration Assessment gives you the object inventory, the risk matrix and the real effort, with a pilot plan. It is the base the capped-price project is quoted on — and if you move ahead, it credits in full.