page:migrate:neon database:durable job state

Migrate Neon database: Durable job state

Move PostgreSQL data from Neon database 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 pg_dump -Fc from the primary branch. Not migrated automatically: Neon branching, autoscaling and scale-to-zero semantics have no equivalent; the managed database is one instance per 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.

Representative Queries

• Migrate Neon database: Durable job state
• Where can I host Durable job state?
• I need a component-scoped export/import or reconfiguration procedure for Durable job state, with compatibility checks, verification and rollback.

Resource Requirements

• primitive:postgres

Infrastructure Requirements

• Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

Workload

• Durable job state

Migration Source

• Neon database

Release Status

• Published

Support Status

• Verified

Execution Status

• Unbound

Documentation Only

• Yes

Prerequisites

1. Authorized access to the Neon database source and its export tooling
2. An inventory of every component in scope and out of scope
3. A validated backup or copy before any cutover
4. An Ample account token with servers:write, databases:read

Workflow Steps

1. Inventory the source: List what Neon database provides beyond the component you are moving. Out of scope here: Neon branching, autoscaling and scale-to-zero semantics have no equivalent; the managed database is one instance per 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.
6. 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).
7. 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.
8. Rollback: Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

Examples

• Express pattern fixture (destination): Verified destination basis: durable job state.
  • Source Reference: tests/deploy-canaries/express-patterns

Success Checks

1. Destination app responds on its public URL
   • Kind: http_get
   • Path: /
   • Expect: ample canary express patterns
2. Durable-job-state check from the destination example
   • Kind: http_get
   • Path: /p/durable-job-state
   • Expect: see the pattern fixture checks
3. Data or object counts and checksums match the source
   • Kind: manual
   • Expect: operator comparison before cutover

Limitations

1. Documentation only: nothing is executed automatically and no execution binding is offered.
2. The source-side procedure is documented from Neon database's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
3. No full source-product parity is claimed: Neon branching, autoscaling and scale-to-zero semantics have no equivalent; the managed database is one instance per app.
4. Verified on the node-22 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
5. Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures on the managed side are not verified beyond the pattern checks.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• Basis: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

1. App server: Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
2. Managed PostgreSQL database: Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0

Note: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

Evidence Summary

• 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.
• Observed At: 2026-09-21T02:34:39Z
• Implementation Revision: 1d28ae0-dirty (CLI 0.1.21)
• Expires At: 2027-03-20T02:34:39Z
• Scope: Destination only, Template: node-22

Last Verified At

• 2026-09-21T02:34:39Z

Unknowns

1. Region availability is unknown until a verified region fact is recorded.
2. Compliance attestations are unknown; none are claimed.

Formats

• HTML: Link
• Markdown: Link
• JSON: Link

Next Actions

1. Browse the catalog index
   • Method: GET
   • Relative Path: /v1/catalog
2. Search published recipes
   • Method: POST
   • Relative Path: /v1/catalog/search
3. Prepare a deployment plan
   • Method: POST
   • Relative Path: /v1/catalog/plan
4. Read the existing agent authentication setup
   • Method: GET
   • Relative Path: /mcp/setup
5. Browse Neon database
   • Method: GET
   • Relative Path: /v1/catalog/nodes/migration%3Aneon-database
6. Browse Durable job state
   • Method: GET
   • Relative Path: /v1/catalog/nodes/pattern%3Adurable-job-state
7. Browse Migrate Postgres
   • Method: GET
   • Relative Path: /v1/catalog/nodes/intent%3Amigrate-postgres