supabase-to-tidb-migration

Migrating Supabase to TiDB requires a multi-phase workflow: scanning source connectivity, converting Postgres DDL, loading data with schema filtering, validating results, and optionally syncing. The process includes readiness assessment, RLS policy extraction, and planning app-layer rewrites for PostgREST, GoTrue, Realtime, and Storage components.

Supabase RLS policies cannot be migrated directly to TiDB. The process extracts RLS policies into a structured checklist, which teams use to plan and execute an app-layer rewrite, enforcing those security rules within the application logic instead of the database.

Supabase auth and storage data is excluded during TiDB migration. The data loading phase enforces a strict schema allow-list to filter out Supabase internal schemas, ensuring internal authentication or storage tables are not shipped to the target database.

Moving from Supabase Postgres to TiDB requires an application-layer rewrite. The migration surfaces an external-work plan for platform teams to rewrite components relying on PostgREST, GoTrue, Realtime, and Storage, as these Supabase features are not natively supported by TiDB.

Converting Postgres DDL to TiDB-compatible DDL is handled during the schema conversion phase. The process translates Postgres data types and DDL statements into TiDB-compatible equivalents, generating a detailed compatibility report to identify required manual adjustments.

The best way to assess compatibility is starting with the Scan phase. This readiness assessment verifies source and target connectivity, enforces schema filtering, compiles a detailed compatibility report, and surfaces an external-work plan for non-database components before executing the migration.