Migrate Azure Database for PostgreSQL: Multi-tenant relational data · Ample Computer

Migrate Azure Database for PostgreSQL: Multi-tenant relational data

Move PostgreSQL data from Azure Database for PostgreSQL to Ample, one component at a time. Destination verified on Ample: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Source procedure: Take a logical backup with pg_dump -Fc from an allowed network or private endpoint. Move separately: Microsoft Entra authentication, zone-redundant HA and PITR are Azure features; on Ample the app connects with injected credentials and backs up with pg_dump. Cutover: Freeze writes with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep the Azure server until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Verified November 5, 2026

What it runs on

You need

Exact tested configuration

build npm run build --if-present
install npm install
runtime node
sizes - 1vcpu - 1gb
start npm run start
template node-22

Steps

  1. Inventory the source. List what Azure Database for PostgreSQL provides beyond the component you are moving. Plan these separately: Microsoft Entra authentication, zone-redundant HA and PITR are Azure features; on Ample the app connects with injected credentials and backs up with pg_dump.
  2. Source step 1. Take a logical backup with pg_dump -Fc from an allowed network or private endpoint.
  3. Source step 2. Check the engine major version, extensions and server parameters the app depends on.
  4. Source step 3. Restore into a scratch managed database first and compare row counts.
  5. Provision and restore. Deploy the app once so a managed PostgreSQL 16 database exists (or create one with ample database create --engine postgres), then restore the dump with pg_restore using its connection string; keep migrations idempotent.
   $ ample database create --name <db-name> --engine postgres
  1. Validate before cutover. Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/multi-tenant-relational-data).
  2. Cut over. Freeze writes with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep the Azure server until confirmed.
  3. Rollback. Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

How it was checked

✓ destination app responds on its public URL · http get/ → “ample canary express patterns”
✓ multi-tenant-relational-data check from the destination example · http get/p/multi-tenant-relational-data → “see the pattern fixture checks”
✓ data or object counts and checksums match the source · manual → “operator comparison before cutover”

Evidence

  1. November 5, 2026 · canary run
    Destination side verified: the Express pattern fixture deployed on Ample (npm install, npm run build --if-present, npm run start on the node-22 template) and its checks passed (a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok)). The source-side export from Azure Database for PostgreSQL uses the vendor's standard tooling.

Tested examples

What it doesn’t cover