Migrate Heroku Postgres: Durable job state · Ample Computer

Migrate Heroku Postgres: Durable job state

Move PostgreSQL data from Heroku Postgres to Ample, one component at a time. Destination verified on Ample: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true). Source procedure: Take a logical backup with heroku pg:backups:capture and download it, or pg_dump -Fc against the credentials from heroku pg:credentials:url. Move separately: followers, forks, rollback (PITR) and dataclips are Heroku Postgres features; on Ample back up with pg_dump. Cutover: Put the app in maintenance mode with the user's go-ahead, take the final backup, restore, validate, redeploy with the managed DATABASE_URL, keep the Heroku database 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

Steps

  1. Inventory the source. List what Heroku Postgres provides beyond the component you are moving. Plan these separately: followers, forks, rollback (PITR) and dataclips are Heroku Postgres features; on Ample back up with pg_dump.

  2. Source step 1. Take a logical backup with heroku pg:backups:capture and download it, or pg_dump -Fc against the credentials from heroku pg:credentials:url.

  3. Source step 2. Check the Postgres major version and extensions against the managed engine (PostgreSQL 16).

  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/durable-job-state).

  2. Cut over. Put the app in maintenance mode with the user's go-ahead, take the final backup, restore, validate, redeploy with the managed DATABASE_URL, keep the Heroku database 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”
✓ durable-job-state check from the destination example · http get/p/durable-job-state → “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 jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true)). The source-side export from Heroku Postgres uses the vendor's standard tooling.

Tested examples

What it doesn’t cover