--- title: "Migrate Supabase database: Multi-tenant relational data" description: "Move PostgreSQL data from Supabase database to Ample, one component at a time." canonical_url: "https://ample.computer/migrate/supabase-database/multi-tenant-relational-data" last_updated: "2026-09-21" --- # Migrate Supabase database: Multi-tenant relational data Canonical URL: https://ample.computer/migrate/supabase-database/multi-tenant-relational-data Formats: [HTML](https://ample.computer/migrate/supabase-database/multi-tenant-relational-data) | [Markdown](https://ample.computer/migrate/supabase-database/multi-tenant-relational-data.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Amigrate%3Asupabase-database%3Amulti-tenant-relational-data) Recipe ID: `page:migrate:supabase-database:multi-tenant-relational-data` | Revision: `r1` | Catalog revision: `cat_f13ab9a494120b5e` Status: release `published`, support `verified`, execution `unbound` ## Summary 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. Path: [Agent hosting discovery](/discover/discovery) / [Migration sources by component](/discover/migration) / [Postgres sources](/discover/migration/postgres-sources) / [Supabase database](/discover/migration/supabase-database) / [Migrate Supabase database: Multi-tenant relational data](/migrate/supabase-database/multi-tenant-relational-data) ## Infrastructure requirements - [Postgres](/discover/primitive/postgres): verified (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 ## Exact tested configuration - template: `node-22` - runtime: `node` - size: `s-1vcpu-1gb` - install: `npm install` - build: `npm run build --if-present` - start: `npm run start` ## 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. ``` 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 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. ## Tested examples - **Express pattern fixture (destination)** (tests/deploy-canaries/express-patterns): Verified destination basis: multi-tenant relational data. ## Success checks - destination app responds on its public URL (`/` on the live URL, expect ample canary express patterns) - multi-tenant-relational-data check from the destination example (`/p/multi-tenant-relational-data` on the live URL, expect see the pattern fixture checks) - data or object counts and checksums match the source ## Cost estimate Estimated 10.00 USD per month (size prices from pricing.toml at build revision 515b7316fc6e5a81679407ae0c811146ceb2c5c7). - app server x1 `s-1vcpu-1gb`: 5.00 USD - managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample. ## Verification evidence - canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: 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 Supabase database is documented from the vendor's standard tooling and was not executed by this catalog's evidence. (expires 2027-03-20T02:34:39Z) Last verified: 2026-09-21T02:34:39Z ## Execution binding No execution binding. This recipe is documentation only; nothing is executed automatically. ## Next actions - Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false) - Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false) - Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false) - Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false) - Browse Supabase database (GET /v1/catalog/nodes/migration%3Asupabase-database on the api origin; auth: false, approval: false) - Browse Multi-tenant relational data (GET /v1/catalog/nodes/pattern%3Amulti-tenant-relational-data on the api origin; auth: false, approval: false) - Browse Migrate Postgres (GET /v1/catalog/nodes/intent%3Amigrate-postgres on the api origin; auth: false, approval: false) Actions describe possible next steps. They are typed data, not commands, and grant no permission.