### Migrate Supabase Database: Relational Records

Move PostgreSQL data from Supabase 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` using the direct (non-pooled) connection string. Not migrated automatically: Supabase Auth, Storage, Realtime, Edge Functions and row-level security policies tied to Supabase roles are not migrated by a database move.

**Cutover:** Freeze writes at the source with the user's go-ahead, take the final dump, restore, validate counts and checksums, redeploy the app with the managed DATABASE_URL, keep the Supabase 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 Supabase 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.

### 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
- Relational records
- Migration Source: Supabase database
- Release Status: published
- Support Status: verified
- Execution Status: unbound

### Prerequisites
1. Authorized access to the Supabase 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.

### Tested Configuration
- **Template:** node-22
- **Runtime:** node
- **Size:** s-1vcpu-1gb
- **Install:** npm install
- **Build:** npm run build --if-present
- **Start:** npm run start

### Workflow Steps
1. **Inventory the Source**  
   List what Supabase database provides beyond the component you are moving. Out of scope here: Supabase Auth, Storage, Realtime, Edge Functions and row-level security policies tied to Supabase roles are not migrated by a database move.

2. **Source Step 1**  
   Take a logical backup with `pg_dump -Fc` using the direct (non-pooled) connection string.

3. **Source Step 2**  
   Check extensions and Supabase-managed schemas (`auth`, `storage`, `realtime`) in the dump; only your application schema moves.

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/relational-records).

7. **Cut Over**  
   Freeze writes at the source with the user's go-ahead, take the final dump, restore, validate counts and checksums, redeploy the app with the managed DATABASE_URL, keep the Supabase 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: relational records.

### Success Checks
1. **HTTP Get:** Destination app responds on its public URL (Path: `/`, Expect: `ample canary express patterns`).
2. **HTTP Get:** Relational-records check from the destination example (Path: `/p/relational-records`, Expect: `see the pattern fixture checks`).
3. **Manual Check:** 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 Supabase database'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: Supabase Auth, Storage, Realtime, Edge Functions and row-level security policies tied to Supabase roles are not migrated by a database move.
- 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.00
- **Authoritative:** true
- **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.00)
   - Managed PostgreSQL database (Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00)
- **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 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 Supabase database 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/relational-records'], Destination Only: true, Template: node-22.

---

### Next Actions
- **Browse the Catalog Index:** GET /v1/catalog
- **Search Published Recipes:** POST /v1/catalog/search (Body: {"limit":5,"query":"Migrate Supabase database: Relational records"})
- **Prepare a Deployment Plan:** POST /v1/catalog/plan (Body: {"inputs":{},"projectId":"","recipeId":"page:migrate:supabase-database:relational-records","recipeRevision":"r1"})
- **Read Existing Agent Authentication Setup:** GET /mcp/setup
- **Browse Supabase Database:** GET /v1/catalog/nodes/migration%3Asupabase-database
- **Browse Relational Records:** GET /v1/catalog/nodes/pattern%3Arelational-records
- **Browse Migrate Postgres:** GET /v1/catalog/nodes/intent%3Amigrate-postgres