Contact us
Oracle 19c, 21c and 23ai, to PostgreSQL on-prem or in the cloud

Move your Oracle database to PostgreSQL.
Leave the licence fees behind.

We migrate tables, data, indexes, views and grants, then compare every value with Oracle.
You cut over when the comparison shows no differences.

Ask about an assessmentHow validation works
Why move

Oracle support renews every year, at about 22% of the licence

Oracle Enterprise Edition lists at USD 47,500 per processor.
PostgreSQL has no licence fee.

The worry is the cutover: an amount rounded, a row lost or a timestamp shifted, and nobody notices until month-end.
The validation step is built to catch those, and you see it catch planted ones before the real run.

How it works

Four steps

Step 1, same day

Assess

You run one read-only script.
You receive a readiness report and a fixed quote.

Step 2

Migrate

We build the PostgreSQL schema, load the data, and write the cutover runbook, including how to fall back to Oracle.

Step 3

Validate

A separate checker compares both databases value by value.
Each difference is fixed, or listed for you to accept.

Step 4

Cut over and tune

Cut over once the report is clean.
Four weeks later we tune the settings based on your production load.

What we move

  • Tables and partitions, with every row of data
  • Indexes, keys and constraints
  • Views and sequences
  • Roles and grants; roles cannot log in until you enable them
  • A cutover runbook, with a rollback plan to Oracle

What stays with your team

  • PL/SQL packages, procedures, functions and triggers.
    The readiness report lists each one with its size and the tables it uses, so your developers can estimate the conversion.
  • Your applications: the connection settings and any SQL inside them.
  • Oracle features with no direct PostgreSQL match, each named in the readiness report with the usual PostgreSQL route.
Validation

How the data is validated

The checker reads Oracle and PostgreSQL directly and shares no code with the migration tooling.

Value-by-value comparison

All columns of all rows are read from both databases and compared, down to numeric precision and timestamps.

Planted faults

We plant faults to verify the checker scripts before launch.

After the moveOne tuning pass, four weeks after go-live, is part of the migration.
Ongoing tuning, backups with a restore test and monthly support are on the PostgreSQL page.PostgreSQL DBA support →
Launch discount: 25% offIn return for an anonymous case study.
Questions

Before you ask

Do you need access to our production database?Not for the assessment: you run one read-only script and send us its output.
For the migration, access is agreed before we start, and Oracle stays untouched as the rollback target.
How long does it take?The assessment takes one day.
A migration takes days to a few weeks, depending on size; the quote gives the timeframe.
What about our PL/SQL?Your developers convert it; it is not part of the migration.
The readiness report gives them every package, procedure, function and trigger to plan from.
Which PostgreSQL can we move to?Your own servers, or Amazon RDS and Aurora.
What if a check fails?We fix the cause and run the checker again.
Any difference left must be accepted by you in writing before cutover.

Talk to us about your database

Send a short message through the contact form.
We reply within one business day to set up a call.

Ask about an assessment