Migrate Azure Database for PostgreSQL: Durable job state

Move PostgreSQL data from Azure Database for PostgreSQL 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 an allowed network or private endpoint. Not migrated automatically: Microsoft Entra authentication, zone-redundant HA and PITR have no equivalent on the managed database.

Cutover

Freeze writes with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep the Azure server until confirmed.

Rollback

Keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Prerequisites

• Authorized access to the Azure Database for PostgreSQL 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

Workflow Steps

1. Inventory the source: List what Azure Database for PostgreSQL provides beyond the component you are moving. Out of scope here: Microsoft Entra authentication, zone-redundant HA and PITR have no equivalent on the managed database.

2. Source step 1: Take a logical backup with pg_dump -Fc from an allowed network or private endpoint.

3. Source step 2: Check the engine major version, extensions and server parameters the app depends on.

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  --engine postgres
   

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 with the user's go-ahead, take the final dump, restore, validate, redeploy with the managed DATABASE_URL, keep the Azure server 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

• Destination app responds on its public URL (expect: ample canary express patterns).
• Durable-job-state check from the destination example (expect: see the pattern fixture checks).
• Data or object counts and checksums match the source (expect: operator comparison before cutover).

Limitations

• Documentation only: nothing is executed automatically and no execution binding is offered.
• The source-side procedure is documented from Azure Database for PostgreSQL's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
• No full source-product parity is claimed.
• Verified on the node-22 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.

Cost Estimate

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

Evidence Summary

• Canary run: The Express pattern fixture deployed on Ample and its checks passed. The source-side export from Azure Database for PostgreSQL is documented from the vendor's standard tooling and was not executed by this catalog's evidence.

Last Verified At

2026-09-21T02:34:39Z

Unknowns

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