Migrate Neon database: Relational records · Ample Computer

Migrate Neon database: Relational records

Move PostgreSQL data from Neon database to Ample, one component at a time. Destination verified on Ample: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Source procedure: Take a logical backup with pg_dump -Fc from the primary branch. Move separately: Neon branching is a Neon feature; on Ample the managed database is one instance per app and sleeps when idle, like the app. Cutover: Freeze writes at the source with the user's go-ahead, take the final dump, restore, validate, redeploy the app with the managed DATABASE_URL, keep the Neon project until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

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 Neon database provides beyond the component you are moving. Plan these separately: Neon branching is a Neon feature; on Ample the managed database is one instance per app and sleeps when idle, like the app.

  2. Source step 1. Take a logical backup with pg_dump -Fc from the primary branch

  3. Source step 2. Check the Postgres major version and extensions in use 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/relational-records).

  2. Cut over. Freeze writes at the source with the user's go-ahead, take the final dump, restore, validate, redeploy the app with the managed DATABASE_URL, keep the Neon project 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”
✓ relational-records check from the destination example· http get/p/relational-records → “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 workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true)). The source-side export from Neon database uses the vendor's standard tooling.

Tested examples

What it doesn’t cover