Migrate Supabase Database: Multi-Tenant Relational Data

Move PostgreSQL data from Supabase database 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 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: Multi-tenant relational data
• Where can I host Multi-tenant relational data?
• I need a component-scoped export/import or reconfiguration procedure for Multi-tenant relational data, 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.

Prerequisites

• Authorized access to the Supabase 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

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

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.

Cost Estimate

• Monthly Amount: $10.00 (USD)
  • App server (size: s-1vcpu-1gb): $5.00
  • Managed PostgreSQL database (size: s-1vcpu-1gb): $5.00
  • Note: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

Success Checks

• Destination app responds on its public URL.
• Multi-tenant-relational-data check from the destination example.
• Data or object counts and checksums match the source.

Evidence Summary

Destination side verified: the Express pattern fixture deployed on Ample and its checks passed.

Next Actions

• Browse the catalog index.
• Search published recipes by intent, stack and constraints.
• Prepare a side-effect-free deployment plan for an authorized project.
• Read the existing agent authentication setup.
• Browse Supabase database.
• Browse Multi-tenant relational data.
• Browse Migrate Postgres.