Migrate Neon database: Multi-tenant relational data · Ample Computer
Migration guide
Migrate Neon database: Multi-tenant relational data
Move PostgreSQL data from Neon database 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 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
- Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
You need
- Authorized access to the Neon database source and its export tooling
- An inventory of every component in scope and out of scope
- A validated backup or copy before any cutover
- An Ample account token with servers:write, databases:read
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
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.
Source step 1. Take a logical backup with
pg_dump -Fcfrom the primary branch.Source step 2. Check the Postgres major version and extensions in use against the managed engine (PostgreSQL 16).
Source step 3. Restore into a scratch managed database first and compare row counts.
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
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).
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.
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
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 Neon database uses the vendor's standard tooling.
Tested examples
- Express pattern fixture (destination). Verified destination basis: multi-tenant relational data.
What it doesn’t cover
- A step-by-step guide: each stage is an ordinary
ample deploy,ample databaseorample bucketcommand you run. - The destination side was verified on Ample with the pattern fixture; the source-side steps use Neon database's standard tooling.
- Plan separately: Neon branching is a Neon feature; on Ample the managed database is one instance per app and sleeps when idle, like the app.
- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector. Back up and restore with pg_dump and pg_restore.