{"catalogRevision":"cat_726f873af6f566cc","recipeId":"page:migrate:neon-database:relational-records","recipeRevision":"r1","canonicalPath":"/migrate/neon-database/relational-records","label":"Migrate Neon database: Relational records","title":"How to move relational records from a Neon database to Ample","family":"Migration guide","summary":"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.","representativeQueries":["Migrate Neon database: Relational records","Where can I host Relational records?","I need a component-scoped export/import or reconfiguration procedure for Relational records, with compatibility checks, verification and rollback."],"breadcrumbIds":["discovery","migration","migration:postgres-sources","migration:neon-database","page:migrate:neon-database:relational-records"],"breadcrumbs":[{"id":"discovery","label":"Agent hosting discovery","canonicalPath":"/discover/discovery","kind":"root"},{"id":"migration","label":"Migration sources by component","canonicalPath":"/discover/migration","kind":"facet"},{"id":"migration:postgres-sources","label":"Postgres sources","canonicalPath":"/discover/migration/postgres-sources","kind":"group"},{"id":"migration:neon-database","label":"Neon database","canonicalPath":"/discover/migration/neon-database","kind":"atom"},{"id":"page:migrate:neon-database:relational-records","label":"Migrate Neon database: Relational records","canonicalPath":"/migrate/neon-database/relational-records","kind":"recipe"}],"parentIds":["migration:neon-database","pattern:relational-records","intent:migrate-postgres"],"parents":[{"id":"migration:neon-database","label":"Neon database","canonicalPath":"/discover/migration/neon-database","kind":"atom"},{"id":"pattern:relational-records","label":"Relational records","canonicalPath":"/discover/pattern/relational-records","kind":"atom"},{"id":"intent:migrate-postgres","label":"Migrate Postgres","canonicalPath":"/discover/intent/migrate-postgres","kind":"atom"}],"resourceRequirements":["primitive:postgres"],"infrastructureRequirements":[{"primitiveId":"primitive:postgres","label":"Postgres","canonicalPath":"/discover/primitive/postgres","status":"verified","summary":"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."}],"workload":"Relational records","migrationSource":"Neon database","releaseStatus":"published","supportStatus":"verified","executionStatus":"unbound","docsOnly":true,"prerequisites":["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"],"testedConfiguration":{"template":"node-22","runtime":"node","size":"s-1vcpu-1gb","install":"npm install","build":"npm run build --if-present","start":"npm run start"},"inputSchema":null,"outputSchema":null,"workflowSteps":[{"title":"Inventory the source","body":"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."},{"title":"Source step 1","body":"Take a logical backup with `pg_dump -Fc` from the primary branch"},{"title":"Source step 2","body":"Check the Postgres major version and extensions in use against the managed engine (PostgreSQL 16)"},{"title":"Source step 3","body":"Restore into a scratch managed database first and compare row counts"},{"title":"Provision and restore","body":"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.","command":"ample database create --name <db-name> --engine postgres"},{"title":"Validate before cutover","body":"Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/relational-records)."},{"title":"Cut over","body":"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."},{"title":"Rollback","body":"Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation."}],"examples":[{"title":"Express pattern fixture (destination)","description":"Verified destination basis: relational records.","sourceRef":"tests/deploy-canaries/express-patterns"}],"successChecks":[{"description":"destination app responds on its public URL","kind":"http_get","path":"/","expect":"ample canary express patterns"},{"description":"relational-records check from the destination example","kind":"http_get","path":"/p/relational-records","expect":"see the pattern fixture checks"},{"description":"data or object counts and checksums match the source","kind":"manual","expect":"operator comparison before cutover"}],"limitations":["A step-by-step guide: each stage is an ordinary `ample deploy`, `ample database` or `ample bucket` command 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."],"costEstimate":{"currency":"USD","monthlyAmount":10.0,"authoritative":true,"basis":"size prices from pricing.toml (loaded by the API) at build revision 3a3dfe06151688a20d397caac2aa66e562c23eb0","components":[{"name":"app server","size":"s-1vcpu-1gb","quantity":1.0,"monthlyAmount":5.0},{"name":"managed PostgreSQL database","size":"s-1vcpu-1gb","quantity":1.0,"monthlyAmount":5.0}],"note":"Upper-bound monthly price of the tested sizes at the destination."},"evidenceSummary":[{"kind":"canary_run","summary":"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.","observedAt":"2026-11-05T22:38:23Z","implementationRevision":"da3e37255e5a","expiresAt":"2027-05-04T22:38:23Z","scope":{"checks":["/p/relational-records"],"destinationOnly":true,"template":"node-22"}}],"lastVerifiedAt":"2026-11-05T22:38:23Z","mcpBinding":null,"unknowns":[],"formats":{"html":"https://ample.computer/migrate/neon-database/relational-records","markdown":"https://ample.computer/migrate/neon-database/relational-records.md","json":"https://api.ample.computer/v1/catalog/recipes/page%3Amigrate%3Aneon-database%3Arelational-records"},"nextActions":[{"actionId":"browse-catalog","label":"Browse the catalog index","operationId":"catalog_index","method":"GET","relativePath":"/v1/catalog","origin":"api","parameters":{},"requiresAuthentication":false,"requiresApproval":false},{"actionId":"search-recipes","label":"Search published recipes by intent, stack and constraints","operationId":"search_recipes","method":"POST","relativePath":"/v1/catalog/search","origin":"api","parameters":{"body":{"limit":5,"query":"Migrate Neon database: Relational records"}},"requiresAuthentication":false,"requiresApproval":false},{"actionId":"plan:page:migrate:neon-database:relational-records","label":"Prepare a side-effect-free deployment plan for an authorized project","operationId":"plan_deployment","method":"POST","relativePath":"/v1/catalog/plan","origin":"api","parameters":{"body":{"inputs":{},"projectId":"<workspace or server id you own>","recipeId":"page:migrate:neon-database:relational-records","recipeRevision":"r1"}},"requiresAuthentication":true,"requiresApproval":false},{"actionId":"auth-setup","label":"Read the existing agent authentication setup","operationId":"existing_auth_setup","method":"GET","relativePath":"/mcp/setup","origin":"api","parameters":{},"requiresAuthentication":false,"requiresApproval":false},{"actionId":"browse:migration:neon-database","label":"Browse Neon database","operationId":"browse_node","method":"GET","relativePath":"/v1/catalog/nodes/migration%3Aneon-database","origin":"api","parameters":{"nodeId":"migration:neon-database"},"requiresAuthentication":false,"requiresApproval":false},{"actionId":"browse:pattern:relational-records","label":"Browse Relational records","operationId":"browse_node","method":"GET","relativePath":"/v1/catalog/nodes/pattern%3Arelational-records","origin":"api","parameters":{"nodeId":"pattern:relational-records"},"requiresAuthentication":false,"requiresApproval":false},{"actionId":"browse:intent:migrate-postgres","label":"Browse Migrate Postgres","operationId":"browse_node","method":"GET","relativePath":"/v1/catalog/nodes/intent%3Amigrate-postgres","origin":"api","parameters":{"nodeId":"intent:migrate-postgres"},"requiresAuthentication":false,"requiresApproval":false}]}