page:migrate:supabase database:text search over records

Migrate Supabase database: Text search over records

Summary

Move PostgreSQL data from Supabase database to Ample, one component at a time. Destination verified on Ample: a generated tsvector column with a GIN index, ranked websearch queries and a negative query returning nothing (search=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.

Workload

Text search over records

Migration Source

Supabase database

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.
   Command: ample database create --name <dbName> --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/text-search-over-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: text search over records. Source Ref: tests/deploy-canaries/express-patterns

Success Checks

• Destination app responds on its public URL: Expected response: ample canary express patterns
• Text-search-over-records check from the destination example: Expected response: see the pattern fixture checks
• Data or object counts and checksums match the source: Expected action: 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.0
• 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.

Next Actions

• Browse the catalog index
  Method: GET | Path: /v1/catalog
• Search published recipes by intent, stack and constraints
  Method: POST | Path: /v1/catalog/search | Query: Migrate Supabase database: Text search over records
• Prepare a side-effect-free deployment plan for an authorized project
  Method: POST | Path: /v1/catalog/plan
• Read the existing agent authentication setup
  Method: GET | Path: /mcp/setup
• Browse Supabase database
  Method: GET | Path: /v1/catalog/nodes/migration%3Asupabase-database
• Browse Text search over records
  Method: GET | Path: /v1/catalog/nodes/pattern%3Atext-search-over-records
• Browse Migrate Postgres
  Method: GET | Path: /v1/catalog/nodes/intent%3Amigrate-postgres