Migration guide

Oracle to PostgreSQL migration: tools, plan and pitfalls

Move Oracle to PostgreSQL in our cloud, your cloud account or your data center: schema and code with ora2pg, live changes with a change-capture tool.

  • Operated by AceMQ
  • 160+ customers
The migration in phases

Use ora2pg to assess the migration, convert the schema and load the data, then review the converted PL/SQL by hand. ora2pg does the bulk copy. Keeping Oracle live until the switch needs a change-capture tool such as Debezium or AWS DMS. Plan the application changes as well as the data.

Which tools do what

ora2pg is the free converter whose documentation covers the schema, code and data. Its documented features do not include streaming ongoing changes, so a live migration pairs it with a change-capture tool.

ToolWhat it doesBoth sides liveSource
ora2pgConnects to Oracle, scans it and exports structure or data as SQL for PostgreSQL. It covers tables and constraints, views, sequences, indexes, partitions, grants, functions, procedures and packages, with basic PL/SQL conversion, and loads data with COPY or INSERT. It also reports migration cost.No: a bulk copyora2pg docs
Debezium Oracle connectorReads Oracle changes with LogMiner and publishes them as change events through Kafka Connect. A JDBC sink connector can write them to PostgreSQL.YesDebezium docs
AWS DMSA service that can use Oracle as a source, with change capture through Oracle LogMiner or AWS DMS Binary Reader.YesAWS docs

Sources: ora2pg, Debezium and AWS documentation, linked in each row; checked 30 Oct 2026.

How the tools were chosen: ora2pg is the free converter whose own documentation covers Oracle schema, code and data, and the two change-capture tools are documented, work with Oracle as a source and can write to PostgreSQL. Commercial tools are left out of the table and compared in the design review if you already license one.

Pitfalls to plan for

The data is the easy part. The work is in PL/SQL, data types and the SQL inside the application, and ora2pg is open about that.

PL/SQL is reviewed by hand.
ora2pg's own documentation says it does its best to convert automatically but there is still manual work: the code generated for functions, procedures, packages and triggers has to be reviewed to match PostgreSQL syntax (ora2pg docs).
Estimate before committing.
ora2pg can report the migration cost and difficulty of a database, and of PL/SQL code or SQL queries in a file. Its default cost unit is five minutes, and the assessment level changes once the estimate passes a person-days limit (ora2pg docs).
Data types are mapped, not guessed.
The default mapping turns Oracle DATE into timestamp(0), and a DATA_TYPE directive lets you redefine it. NUMBER without precision becomes bigint only if PG_INTEGER_TYPE is true (ora2pg docs). Each mapping is checked against the application.
Objects that change shape.
ora2pg exports synonyms as views and database links as Oracle foreign data wrappers, so these are design decisions, not straight copies (ora2pg docs).
Application SQL.
Oracle-specific SQL in the application is assessed and rewritten. ora2pg can estimate the cost of queries stored in a file.
Prove it matches.
ora2pg has TEST and TEST_COUNT actions that compare Oracle and PostgreSQL contents and row counts (ora2pg docs).

Sources: ora2pg documentation, linked above; checked 30 Oct 2026.

The migration in phases

ora2pg's assessment and conversion run first, with Oracle untouched. Live changes are captured from the start of the bulk load, so Oracle and PostgreSQL stay in step until the switch.

Illustrative: each phase is planned and rehearsed with your team before traffic moves.
  1. Assess

    ora2pg reports the objects, the migration cost and the difficulty level. The PL/SQL and application SQL are sized from that.

  2. Convert

    The schema is exported and loaded into a test PostgreSQL cluster. Functions, procedures, packages and triggers are rewritten and reviewed.

  3. Load and capture

    Change capture starts, the bulk load runs with ora2pg using COPY, and the captured changes are applied after it.

  4. Verify

    ora2pg's TEST and TEST_COUNT actions compare the two databases, and the application test suite runs against PostgreSQL.

  5. Cut over

    Writes to Oracle stop, the last changes apply, sequences are set, and the application connects to PostgreSQL.

The timeline and runbook for Oracle to PostgreSQL migrations are written in the design step, from your data volume, traffic and change windows, and you approve them before the cutover is scheduled.

Cutover and rollback

Without change capture, ora2pg alone leaves a window equal to the final data load. With change capture, the window shrinks to the moment writes pause and the last changes apply, and Oracle stays available until you are sure.

  1. The change stream is caught up and the comparison actions pass.
  2. Application writes to Oracle stop, briefly, and the last changes apply to PostgreSQL.
  3. Sequences are set and the application connects to PostgreSQL.
  4. Oracle stays unchanged as the fallback until PostgreSQL has run normally.

Sources: the ora2pg, Debezium and AWS DMS documentation linked above; checked 30 Oct 2026.

How OSStend runs the move

We run the migration and own the cutover, with both sides live until you switch. Zero downtime is the plan.

Managed PostgreSQL from OSStend is operated by AceMQ engineers, in our cloud, your cloud account or your data center. If Debezium is the change-capture tool, managed Kafka runs the Connect side. A PostgreSQL source such as RDS follows the RDS to PostgreSQL guide. The migration hub lists the other moves.

Operated by AceMQCompany figures, as published on acemq.com
160+customers served by AceMQ, which operates OSStend
10+years running open source data and messaging
24/7on-call engineers, not a ticket queue

AceMQ names a customer only with that customer's written permission, so most of this record stays anonymous. Ask for a similar workload in the 45-minute review.

When this move fits, and when it does not

The move fits when the Oracle estate is moderate in PL/SQL and the business wants off the licence. It does not when the application is built around Oracle-only features that have no PostgreSQL equivalent.

Contact us if

  • The Oracle licence or hardware is the reason to leave.
  • The assessment shows a manageable amount of PL/SQL and application SQL.
  • The business cannot accept a long outage, so change capture is worth setting up.
Talk to an engineer

Not a fit if

  • The application depends on Oracle-only features that the assessment cannot map.
  • A short outage is acceptable and a single bulk load will do.
  • You want to run the move yourselves: ora2pg works without OSStend.

Questions about Oracle to PostgreSQL

Can ora2pg migrate Oracle with no downtime?

ora2pg's documented features cover schema, code and data export and a migration cost report, which makes it a bulk copy. A no-downtime plan adds a change-capture tool such as the Debezium Oracle connector, so changes made during the load are applied (ora2pg docs, checked 30 Oct 2026).

What does ora2pg not convert automatically?

Its documentation says manual work remains, and that the PL/SQL generated for functions, procedures, packages and triggers has to be reviewed against PostgreSQL syntax (ora2pg docs, checked 30 Oct 2026).

How long does an Oracle to PostgreSQL migration take?

It depends on schema size, the amount of PL/SQL and the application changes. ora2pg estimates effort in person-days from the schema, using a default unit of five minutes (ora2pg docs, checked 30 Oct 2026), and the design review turns that into an estimate.

Talk to an engineer

Plan your Oracle move with an engineer

45 minutes with an engineer: the current setup is reviewed against the documented method and the cutover is sketched. No ticket queue.

  • A design sketch for your workload, not a plan menu
  • A zero-downtime cutover path for what you run today
  • A price for that design, after the review
See pricing →

Your request goes to the OSStend team. No newsletter sign-up.

Get a quoteTalk to an engineer
2Engines
3Where should it run?
4What do you need?

Your request goes to the OSStend team. No newsletter sign-up.