Migrate from PostgreSQL v1 to v2
PostgreSQL v2 is in General Availability (GA), offering region-specific endpoints, a redesigned cluster resource model, and a structured cluster lifecycle. IONOS CLOUD automatically migrates all v1 clusters to v2. For more information, see Automatic migration. If you prefer to migrate proactively before the automatic window, see Manual migration.
Automatic migration
IONOS CLOUD automatically migrates all DBaaS PostgreSQL v1 clusters to the v2 infrastructure. Migrations start on July 29, 2026 and complete within four weeks.
What to expect
Temporary downtime: Your cluster is unavailable during the migration. Downtime is typically between a few seconds and a few minutes.
Schedule: Migrations run Monday through Thursday. IONOS CLOUD notifies you of the exact migration time before migrating your cluster.
No endpoint change: Your cluster connection endpoint stays the same. Applications reconnect automatically once the migration completes.
Required action
If you do not manage your clusters programmatically, or already use token authentication, no further action is needed.
Manual migration
To migrate your cluster before the automatic window, follow the steps in this guide. The process covers provisioning a target v2 cluster, transferring data using pg_dump and psql, and executing a controlled cutover of your application.
Phase 1: Target cluster provisioning
Provision a v2 cluster
To create a v2 cluster, see Deploy a PostgreSQL Cluster.
Phase 2: Schema preparation and script architecture
Recommendation: Use the native pg_dump to export database structure and data. It automatically handles sequences, views, extensions, and object dependencies.
Extract data from v1
Use pg_dump to create a consistent export of your v1 cluster:
pg_dump -h <v1-endpoint> -U <username> -d <dbname> -f v1_dump.dumpFor a performance-optimized restore, dump the table structure and data separately and disable triggers (this also deactivates foreign key checks during import):
# Database structure
pg_dump -h <v1-endpoint> -U <username> -d <dbname> -s -f v1_schema_dump.dump
# Database contents
pg_dump -h <v1-endpoint> -U <username> -d <dbname> -a --disable-triggers -f v1_data_dump.dumpPhase 3: Migration execution
Schedule a maintenance window for your application to avoid data drift or split-brain scenarios. Do not run the migration during the scheduled maintenance window of either your v1 or v2 cluster.
Validate data integrity
Compare row counts for your most critical tables to confirm consistency across clusters:
Run
SELECT count(*) FROM <table_name>;on both the v1 and v2 databases and compare the results.For tables with high-frequency updates, compare
MAX(id)or the most recentcreated_attimestamp to confirm the data is current.
Last updated
Was this helpful?