Supabase to Supabase migration
Use this guide to understand how Miglify helps move supported resources between Supabase projects.
What can be migrated
- Database schema and rows
- Auth users
- Storage buckets and files
- Secret names (values are provided by you at the destination)
- Edge Functions — deployed automatically when GitHub-backed, otherwise manual
Database schema and rows
Miglify inspects source tables and moves supported schema and rows into the destination project during the database module.
Auth users
Auth users are migrated when the auth module is selected. Existing destination users are not overwritten.
Storage buckets and files
Storage buckets and files are copied to the destination project when the storage module is selected.
Secrets
Source secret values cannot be exported. Miglify detects required secret names and helps you configure destination values safely.
Edge Functions
GitHub-backed functions deploy automatically. Supabase-detected-only functions require manual deployment.
Before migration checklist
- Destination project is fresh or intentionally prepared.
- Credentials validated in Miglify.
- Selected modules are the ones you want to move.
- Detected resource counts fit private beta limits.
Running the migration
Confirm the job to start. Miglify runs each selected module in sequence and shows live progress.
Reviewing progress
Use the job detail page timeline to see each stage: discovery, schema, data, storage, auth, and verification.
Rollback behavior
Rollback removes only supported destination items Miglify created during that migration.
Known beta limits
See the private beta limits page.