PostgreSQL Migration Tool

Move schemas and data between PostgreSQL instances or migrate into managed cloud Postgres with sequence checks, SSL defaults, and pgcopydb compatibility.

Cloud PostgreSQL environment checks

  • AWS RDS and Aurora: Enforces sslmode=require and avoids commands requiring SUPERUSER.
  • Supabase: Flags transaction pooler port 6543 and directs DDL and bulk loads to direct port 5432.
  • Neon: Reports managed filesystem capacity honestly as Unknown instead of fabricating free disk bytes.
  • Google Cloud SQL and Azure Database: Checks SSL mode, connection limits, and write privileges prior to table creation.

PostgreSQL-to-PostgreSQL command bridge

For same-engine PostgreSQL transfers, Database Migration Studio generates a verified migration plan plus a ready-to-run pgcopydb clone invocation when native PostgreSQL binary utilities are installed locally.

pgcopydb clone --source "postgres://migrator@pg14.internal:5432/analytics" \
  --target "postgres://postgres@pg16.neon.tech:5432/analytics" \
  --table-jobs 4 --index-jobs 4

Frequently asked questions

Why does the analyzer show Free Space as Unknown on Neon or RDS?

Managed cloud databases often restrict host filesystem statistics from client SQL roles. Showing Unknown prevents false confidence before large transfers.

How are identity and serial sequences handled after data loading?

Stage 7 resets every identity sequence to the maximum inserted key value and records the synchronized sequence counter in the verification report.