Lovable to Supabase migration
Miglify supports Lovable/GitHub-backed workflows connected to user-owned Supabase projects.
How Lovable/GitHub-backed workflows work
Lovable projects that are connected to a user-owned Supabase project and backed by a GitHub repository can be analyzed by Miglify.
What Miglify can analyze
- Repository structure through GitHub OAuth
- Supabase database schema, storage, and auth
- Edge Function source code when available in the repo
- Required secret names
What can be migrated
- Database, auth users, and storage from the connected Supabase project
- GitHub-backed Edge Functions
GitHub repository connection
Use the GitHub OAuth flow to pick the exact repository backing your project. Miglify only accesses what you authorize.
Supabase destination setup
Prepare a destination Supabase project and connect it in the Start Migration flow.
Secrets and environment variables
Miglify detects secret names used by Edge Functions. You provide destination values directly.
Edge Functions
Functions with source code in the connected repo deploy automatically. Functions only visible via Supabase detection require manual deployment.
Manual fallback cases
- Repository not connected or not accessible
- Function present in Supabase but missing from the repo
- Secrets that must be created by hand at the destination
Recommended test flow
Start with a test Lovable/GitHub-backed project connected to a fresh Supabase destination to validate the workflow end to end.