From Prisma Postgres

Prisma Postgres databases move to Databasezy PostgreSQL with a copy. Your Prisma schema and client keep working; only the connection string changes.

Coming soon: phase 2

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

Prisma Postgres migration at a glance, from the migration source catalogue

Status	Coming soon · phase 2
Target engines	PostgreSQL
How we read it	Connection string
Continuous sync	No, copy only
Provider preset	None yet (generic)

Before you start

• A Databasezy PostgreSQL instance, or use --create.
• A direct TCP connection string for the database.
• A short write freeze for the copy.

Find the connection string

In the Prisma console, open the database and create a direct connection string (postgres://...). The prisma+postgres:// URL goes through Accelerate and cannot be used by pg_dump.

Prisma Postgres notes

• Use a direct TCP connection string, not the Accelerate (prisma+postgres://) URL.

After the switch, set DATABASE_URL to the Databasezy connection string and run prisma migrate status to confirm the migration history came across. See the Prisma framework guide.

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. Run Preflight and work through the checklist. Blocking items must be fixed before the copy starts.
4. Start the copy and follow Copy and Verify. Mismatches are listed per table or collection.
5. Point your application at the new instance. 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://user:[email protected]:5432/postgres?sslmode=require" --to inst_abc --dry-run

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

zb migrate status mig_123

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://user:[email protected]:5432/postgres?sslmode=require"
  },
  "mode": "copy"
}'

# 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"

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.

Cutover

This source is copy only. Writes that reach the source after the copy starts are not carried over, so for a database that changes, stop writes before you start the copy (maintenance mode, or scale writers to zero), run the migration, check verification, then point the application at the Databasezy connection string.

Roll back

A migration never deletes anything on the source. Until you decommission it, rolling back means pointing the application back at the source. Writes made on Databasezy after you switched are not on the source; if you need them, copy them back before switching. Cancel a running migration with zb migrate cancel <mig_id>; partially restored data stays on the target, so restart with --drop-target or delete the instance.

Troubleshooting

Preflight rejects the URL scheme

It is the prisma+postgres:// Accelerate URL. Create a direct connection string instead.

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.

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