Migrate from Supabase

Moving away from Supabase gives you full control over your PostgreSQL instance. ArmorDB provides a high-performance home for your existing data.

1. Handle Supabase Specifics

Supabase adds several internal schemas (like \`auth\`, \`storage\`, \`realtime\`). If you only need your application data, you should target specific schemas using the \`-n\` flag.

pg_dump --no-owner --no-acl \
  -n public \
  -d "postgres://postgres:[email protected]:5432/postgres" \
  -f supabase_export.sql

2. Restore to ArmorDB

Import the resulting SQL file into ArmorDB. Note that ArmorDB uses standard PostgreSQL 17, so any custom Supabase extensions may need to be enabled manually if supported.

psql "postgres://julian:[email protected]:6432/dbname" \
  -f supabase_export.sql

No Lock-in Guarantee

ArmorDB doesn't use proprietary wrappers. Your data belongs to you, and we ensure standard PostgreSQL tools work perfectly for both import and export.