# Migrate Azure Database for PostgreSQL: Multi-tenant relational data

Move PostgreSQL data from Azure Database for PostgreSQL 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 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.

## 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.  
   ```bash  
   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/multi-tenant-relational-data).

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.

## Success Checks

- **Destination app responds on its public URL**  
  - Expectation: ample canary express patterns.
- **Multi-tenant-relational-data check from the destination example**  
  - Expectation: see the pattern fixture checks.
- **Data or object counts and checksums match the source**  
  - Expectation: 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: Microsoft Entra authentication, zone-redundant HA and PITR have no equivalent on the managed database.
- Verified on the node-22 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
- 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  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components:**  
  - **App server**: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0  
  - **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 (a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok)). 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.  
  **Observed At:** 2026-09-21T02:34:39Z  
  **Implementation Revision:** 1d28ae0-dirty (CLI 0.1.21)  
  **Expires At:** 2027-03-20T02:34:39Z  
  **Scope:**  
   - Checks: /p/multi-tenant-relational-data  
   - Destination only: true  
   - Template: node-22

## Next Actions

- **Browse the catalog index**  
  - Action ID: browse-catalog  
  - Method: GET  
  - Relative Path: /v1/catalog  
- **Search published recipes by intent, stack and constraints**  
  - Action ID: search-recipes  
  - Method: POST  
  - Relative Path: /v1/catalog/search  
  - Parameters:  
    - Body: {"limit":5,"query":"Migrate Azure Database for PostgreSQL: Multi-tenant relational data"}  
- **Prepare a side-effect-free deployment plan for an authorized project**  
  - Action ID: plan:page:migrate:azure-database-for-postgresql:multi-tenant-relational-data  
  - Method: POST  
  - Relative Path: /v1/catalog/plan  
  - Parameters:  
    - Body: {"inputs":{},"projectId":"","recipeId":"page:migrate:azure-database-for-postgresql:multi-tenant-relational-data","recipeRevision":"r1"}  
- **Read the existing agent authentication setup**  
  - Action ID: auth-setup  
  - Method: GET  
  - Relative Path: /mcp/setup  
- **Browse Azure Database for PostgreSQL**  
  - Action ID: browse:migration:azure-database-for-postgresql  
  - Method: GET  
  - Relative Path: /v1/catalog/nodes/migration%3Aazure-database-for-postgresql  
- **Browse Multi-tenant relational data**  
  - Action ID: browse:pattern:multi-tenant-relational-data  
  - Method: GET  
  - Relative Path: /v1/catalog/nodes/pattern%3Amulti-tenant-relational-data  
- **Browse Migrate Postgres**  
  - Action ID: browse:intent:migrate-postgres  
  - Method: GET  
  - Relative Path: /v1/catalog/nodes/intent%3Amigrate-postgres