PostgreSQL Migration Tool
Convert and sync PostgreSQL databases without writing migration scripts.
What the PostgreSQL migration tool does
A desktop tool that moves a whole database - or selected tables - into or out of PostgreSQL: schema, data types, indexes, and keys included.
Targets: on-prem PostgreSQL and managed Postgres on Amazon RDS / Aurora, Azure Database for PostgreSQL, Google Cloud SQL, and Supabase.
One-time and repeatable migrations run in DBConvert; to keep PostgreSQL and another database aligned after the move, use DBSync.
Source
Any supported database
SQL Server, MySQL, Oracle, Access, PostgreSQL, and more.
DBConvert
Configure and run the migration
Select objects, review settings, then transfer the data.
Target
Any supported database
PostgreSQL can be source, target, or both.
Key capabilities
What the PostgreSQL tools handle
Schema and data migration
Move tables and rows into or out of PostgreSQL.
Type mapping
Review how source types land on the target side.
Indexes and keys
Carry core structure along with the data transfer.
Pre-transfer checks
Catch schema and mapping issues before the run.
PostgreSQL schema migration
Migrate the Postgres schema first - review and adjust the type mapping per column before any rows move, so defaults, precision, and identity/serial choices land the way you want.
What it does not do: stored procedures, triggers, and functions written in source-specific SQL are not rewritten into PL/pgSQL - treat that as a separate engineering task.
Migrate to and from PostgreSQL
PostgreSQL can be either side of the migration. Pick a direction to open the exact DBConvert or DBSync tool for that source and target.
Common directions
- Into PostgreSQL: SQL Server, MySQL, Oracle, Access, Firebird, FoxPro, and other sources.
- Out of PostgreSQL: reverse the direction when PostgreSQL is the source.
- Postgres to Postgres: use PostgreSQL as both source and target.
Pick the matching pair from the tools list to open the exact DBConvert or DBSync tool.
PostgreSQL-family targets
The same workflow can move data between PostgreSQL-family systems:
When migration becomes synchronization
Use DBConvert for the initial move. Use DBSync when PostgreSQL and another database must keep exchanging changes after that move is complete.
DBConvert or DBSync?
Use DBConvert for migration
- One-time source-to-target moves.
- Repeatable test loads during a migration project.
- Saved sessions you can run again from the scheduler or CLI.
Use DBSync for ongoing alignment
- Scheduled sync after the first migration.
- Trigger-based insert, update, and delete tracking.
- Selected bidirectional workflows when both systems keep changing.
Cloud synchronization
Sync PostgreSQL databases with Amazon RDS, Aurora, Azure Database for PostgreSQL, Google Cloud SQL, or another PostgreSQL-compatible target while keeping data consistent across staging, production, and reporting systems.
Bidirectional replication
DBSync supports selected bidirectional replication workflows when both systems continue to receive changes and need to stay aligned.
Need CDC, cross-platform desktop, or AI-assisted data workflows?
DBConvert Streams is the separate product for teams that need more than a classic desktop migration wizard.
Log-based CDC
Capture ongoing database changes for pipeline-style movement.
Multiplatform desktop
Work across Windows, macOS, and Linux instead of a Windows-only wizard.
Cross-database workspace
Inspect databases, files, and object storage in one SQL environment.
AI-assisted work
Use it when validation, exploration, and pipeline setup matter as much as migration.
Configuration Resources
Guides for PostgreSQL deployment, hosted services, and managed infrastructure.
Choose your PostgreSQL pair
Open the exact DBConvert or DBSync tool for your source and target.
