# 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. Move separately: Supabase Auth, Storage, Realtime and Edge Functions stay on Supabase or move into the app; row-level security tied to Supabase roles is re-expressed with the app's own roles. 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.

**Verified** November 5, 2026

## What it runs on

- [Postgres verified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## You need

- 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

build npm run build --if-present
    install npm install
    runtime node
    sizes-1vcpu-1gb
    start npm run start
    template node-22

## Steps

1. **Inventory the source.** List what Supabase database provides beyond the component you are moving. Plan these separately: Supabase Auth, Storage, Realtime and Edge Functions stay on Supabase or move into the app; row-level security tied to Supabase roles is re-expressed with the app's own roles.

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 <db-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.

## How it was checked

✓ destination app responds on its public URL· http get/ → “ample canary express patterns”  
✓ multi-tenant-relational-data check from the destination example· http get/p/multi-tenant-relational-data → “see the pattern fixture checks”  
✓ data or object counts and checksums match the source· manual → “operator comparison before cutover”

## Evidence

1. November 5, 2026 · canary run
   
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 uses the vendor's standard tooling.

## Tested examples

- **Express pattern fixture (destination).** Verified destination basis: multi-tenant relational data.

## What it doesn’t cover

- A step-by-step guide: each stage is an ordinary `ample deploy`, `ample database` or `ample bucket` command you run.
- The destination side was verified on Ample with the pattern fixture; the source-side steps use Supabase database's standard tooling.
- Plan separately: Supabase Auth, Storage, Realtime and Edge Functions stay on Supabase or move into the app; row-level security tied to Supabase roles is re-expressed with the app's own roles.
- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector. Back up and restore with `pg_dump` and `pg_restore`.
