Migration plans list tasks. Sign-off needs evidence. This checklist is organized by phase and written as questions a manager can ask without reading PL/SQL. If an answer is unclear, that phase is not finished.

1. Assessment

  • Is there an inventory of databases, schemas, sizes, growth and peak write volume?
  • Is there a count of packages, procedures, functions and triggers, with unused ones marked?
  • Which Oracle features are in use that have no direct PostgreSQL equivalent: RAC, Data Guard, Advanced Queuing, database links, fast-refresh materialized views, Java stored procedures, APEX, Forms and Reports?
  • Which applications, reports and integrations connect, and who owns each one?
  • When does the Oracle license or support term end, and is the migration date driven by it?
  • What are the agreed recovery time and recovery point objectives on the new platform?

2. Conversion

  • Is every data type mapping that changes behavior recorded with its reason, starting with NUMBER and DATE?
  • Is there a written decision on empty strings and NULL, applied the same way everywhere?
  • Is each PL/SQL unit classified as mechanical, redesign, or move to the application? See PL/SQL to PL/pgSQL conversion.
  • Are package state, autonomous transactions and commits inside loops each listed with a chosen replacement?
  • Are application queries tested against PostgreSQL, including ORM-generated ones and Oracle-specific hints?
  • Do scheduled jobs have a new home and their own alerting?

3. Validation in QA

  • Is data reconciliation repeatable across tables and test cycles?
  • Do tests cover the no-row and error paths, not only the happy path?
  • Has replication been interrupted on purpose and rebuilt without risk to the source?
  • Has performance been measured under representative load, including month-end and batch windows?
  • Which lag, error or mismatch threshold stops the release, and who owns that evidence?

4. Cutover

  • Who has the authority to pause, and who decides between resume and rollback?
  • Are the stop signals and thresholds written down before the window opens?
  • Is the order for stopping writers, batch jobs and integrations documented and rehearsed?
  • Who tells the business what happened, and when?

5. Rollback and licensing

  • Has rollback been rehearsed after PostgreSQL has accepted writes, not only before?
  • What happens to each transaction accepted after cutover if the team has to return?
  • Does the Oracle license and support term cover the whole rollback window?
  • How long did the rehearsal take from decision to validated service, and does that fit the agreed limit?
  • What date or condition closes the rollback path and allows Oracle to be retired?

6. The first ninety days

  • Does alerting watch what fails on PostgreSQL: vacuum health, replication lag, connection saturation?
  • Has the operations team performed a point-in-time recovery on the new platform?
  • Are backup, access, change control and escalation accepted by the receiving team in writing?
  • Are Oracle DBA routines each reviewed: keep, replace, or retire?

How to use this

Put a name and a date next to every question. An item with no owner is not in progress. The phases follow the Production Migration Notes, which explain the reasoning behind each one. The tools guide covers what software can and cannot do for each phase.

Where this leads

Datrick operates Oracle and PostgreSQL in production and delivers Oracle to PostgreSQL migration under a written scope, with named engineers accountable for assessment, conversion, validation, cutover and the operation that follows. The service page describes the delivery model: Oracle to PostgreSQL migration. For a first read of risk and effort, see the migration risk assessment.

Related: Oracle to PostgreSQL migration · migration risk assessment · Oracle DBA services · PostgreSQL DBA services · SQL Server migration checklist