Pull schema, data, auth users, and storage buckets from a Supabase project and generate nSelf migration artifacts.

nself migrate supabase --project-ref <ref> --supabase-key <key> [flags]

nself migrate supabase connects to a live Supabase project via the PostgREST and Admin APIs, pulls your public schema, auth users, and storage buckets, then generates three migration artifacts: a Drizzle-compatible SQL migration file, a Hasura metadata YAML, and a shell script to import your auth users.

Unlike nself migrate firebase, this command requires live access to your Supabase project. Use NSELF_SUPABASE_SKIP=1 to skip live connectivity in CI environments.

1. Connect to Supabase and pull public schema (tables, columns, RLS policies where accessible)
2. Pull auth users via the Supabase Admin API
3. Pull storage buckets via the Supabase Storage API
4. Generate a Drizzle-compatible SQL migration file
5. Generate Hasura metadata YAML
6. Generate an auth user import script
7. Write all files to the output directory

# Basic migration
nself migrate supabase \
  --project-ref abcdefghijkl \
  --supabase-key eyJhbGci...

# Write artifacts to a named output directory
nself migrate supabase \
  --project-ref abcdefghijkl \
  --supabase-key eyJhbGci... \
  --out ./migration

# CI environment: skip live connectivity
NSELF_SUPABASE_SKIP=1 nself migrate supabase \
  --project-ref ci-project-ref \
  --supabase-key ci-service-key

• Project ref: the alphanumeric ID in your Supabase project URL: https://app.supabase.com/project/<ref>
• Service role key: Supabase Dashboard > Project Settings > API > service_role (keep this secret)

After the command completes, apply the generated files to your nSelf project:

# Apply the schema migration
nself db migrate --file ./migration/supabase-migration.sql

# Apply Hasura metadata (via Hasura console or CLI)
hasura metadata apply --directory ./migration/hasura-metadata.yaml

# Import auth users
bash ./migration/import-auth-users.sh

• Only the public schema is pulled. Tables in other schemas require manual migration.
• Supabase-specific features (Edge Functions, Realtime subscriptions) are not converted.
• RLS policies are pulled where the service_role key has access; review supabase-migration.sql before applying.

• cmd-migrate — v0.9 to v1 project migration
• cmd-migrate-firebase — migrate from Firebase
• cmd-db — run schema migrations on a live project

← Commands | Home →