From Google Cloud SQL

Cloud SQL for PostgreSQL and MySQL move to the matching Databasezy engine, with continuous sync for both.

Coming soon: phase 3

A guided Google Cloud SQL preset ships in rollout phase 3. Until then the steps below run as a generic migration: preflight checks the engine, version and size, but does not add Google Cloud SQL-specific checks or URL rewrites.

Google Cloud SQL migration at a glance, from the migration source catalogue

Status	Coming soon · phase 3
Target engines	PostgreSQL , MySQL
How we read it	Connection string
Continuous sync	Yes, for PostgreSQL and MySQL
Provider preset	None yet (generic)

Before you start

• A Databasezy instance of the matching engine, or use --create.
• A database user with a password and read access.
• A public IP on the instance, or the Cloud SQL Auth Proxy on a machine you control.

Find the connection string

In the Google Cloud console, open the Cloud SQL instance and note its public IP address. Add the egress addresses as authorized networks on the instance’s connections settings, and build the URL from the IP, your user and the database name.

Google Cloud SQL notes

• Add our egress IPs as authorized networks, or run zb migrate --from local through the Cloud SQL Auth Proxy.

Without a public IP, run the Cloud SQL Auth Proxy locally and use zb migrate --from local; it streams a dump and needs no inbound access, but cannot sync.

shell

cloud-sql-proxy my-project:us-central1:my-instance --port 15432 &
PGHOST=localhost PGPORT=15432 PGUSER=migrator PGPASSWORD=pw \
  zb migrate --from local --engine postgres --db app --create

Migrate

Portal

1. Open the target PostgreSQL instance (create one first if you need to) and choose the Migrate in tab.
2. Under Source, pick Connection string and paste the URL.
3. Choose Copy and sync to keep the target current until cutover, or Copy for a one-off copy.
4. Run Preflight and work through the checklist. Blocking items must be fixed before the copy starts.
5. Start the copy and follow Copy and Verify. Mismatches are listed per table or collection.
6. When the sync lag is low, stop writes and choose Cut over. The Report step keeps the timings and verification results.

CLI

shell

# Dry run: print the preflight checklist and the plan, change nothing
zb migrate --from "postgres://migrator:[email protected]:5432/app?sslmode=require" --to inst_abc --mode copy_and_sync --dry-run

# Start it (or use --create --size s1 instead of --to to create the target)
zb migrate --from "postgres://migrator:[email protected]:5432/app?sslmode=require" --to inst_abc --mode copy_and_sync

zb migrate status mig_123
zb migrate cutover mig_123     # when status says ready_for_cutover

API

shell

curl -sS https://api.databasezy.com/v1/orgs/$ZB_ORG/instances/inst_abc/migrations \
  -H "Authorization: Bearer $ZB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "source": {
    "kind": "connection_string",
    "url": "postgres://migrator:[email protected]:5432/app?sslmode=require"
  },
  "mode": "copy_and_sync"
}'

# Follow progress, preflight report and verification
curl -sS https://api.databasezy.com/v1/orgs/$ZB_ORG/instances/inst_abc/migrations/mig_123 -H "Authorization: Bearer $ZB_API_KEY"

# Cut over once the status is ready_for_cutover
curl -sS -X POST https://api.databasezy.com/v1/orgs/$ZB_ORG/instances/inst_abc/migrations/mig_123/actions/cutover -H "Authorization: Bearer $ZB_API_KEY"

For PostgreSQL sync, set the cloudsql.logical_decoding flag to on (the instance restarts) and give the user the REPLICATION attribute. For MySQL sync, the binary log must be on and the user needs REPLICATION SLAVE and REPLICATION CLIENT. Preflight checks each setting.

Verify

Verification runs automatically after the copy and compares source and target: row counts per table, sequence or AUTO_INCREMENT values, the number of indexes and a schema hash. A missing table or a short row count fails the migration and lists what differs. Check the result with zb migrate status <mig_id> or the Verify step in the portal, then run your application’s own smoke tests against the new instance before you switch traffic.

Continuous sync and cutover

With copy and sync, the target keeps receiving changes after the copy. When zb migrate status reports ready_for_cutover (two lag samples in a row under 5 seconds):

1. Stop writes to the source: maintenance mode, scale writers to zero, or revoke the application user.
2. Run zb migrate cutover <mig_id> (or Cut over in the portal). The agent drains the last changes, copies sequence values (PostgreSQL), verifies again and stops replication. If the target cannot catch up in time, the cutover is abandoned and sync keeps running; nothing changes on either side.
3. Point the application at the Databasezy connection string and resume writes. zb migrate status shows the measured downtime.

Schema changes are not replicated, so freeze migrations between the copy and cutover. Details: what happens at cutover.

Roll back

A migration never deletes anything on the source. Until you decommission it, rolling back means pointing the application back at the source.

• Before cutover: cancel with zb migrate cancel <mig_id>. The publication, replication slot or replication channel the migration created is removed.
• After cutover: writes made on Databasezy are not on the source. For PostgreSQL, start the migration with --reverse-sync so the old database keeps receiving them after cutover and stays a valid fallback. Without it, copy the new data back with a migration in the other direction before you switch.

Troubleshooting

Preflight reports pg.wal_level

The cloudsql.logical_decoding flag is off. Turn it on and wait for the restart.

Preflight cannot connect to the source

Check that the source accepts connections from the egress addresses preflight prints, that the host is the public one and that the password has not been rotated. zb migrate --dry-run shows the exact URL that will be used after any rewrites.

Preflight lists blocking items

Each item has a machine code and a fix. Nothing is written to the target until every blocking item is resolved; warnings do not block.

The restore stops on an extension

The source uses an extension Databasezy does not ship. Drop it on the source if it is unused, or exclude the objects that depend on it with --exclude.

Sync is blocked with pg.wal_level or pg.replica_identity

Logical replication needs wal_level=logical on the source and a primary key (or REPLICA IDENTITY FULL) on every published table. Preflight lists the tables.

Sync is blocked on binlog or GTID settings

Continuous sync needs binlog_format=ROW, gtid_mode=ON, enforce_gtid_consistency=ON and a user with REPLICATION SLAVE and REPLICATION CLIENT. Preflight names whichever is missing.

For anything else, zb migrate status <mig_id> shows the failing step and its message. How migrations work describes every step.