Supported workflows
Miglify supports Supabase, Lovable-connected/GitHub-backed, and Lovable Cloud source workflows into a destination Supabase project.
Supported today
- Supabase → Supabase migration
- Lovable-connected/GitHub-backed → Supabase workflows
- Lovable Cloud → Supabase workflow
- Database migration
- Auth users migration
- Storage migration
- Secret requirement detection and secure configuration workflows
- Edge Function detection and supported deployment workflows
- Live progress
- Selective modules
- Selective rollback
- Verification reporting, and cutover readiness where supported
Supabase → Supabase
Controlled migrations between two Supabase projects for database, auth users, and storage, with validation, live progress, selective modules, and rollback-aware tracking.
Lovable-connected/GitHub-backed → Supabase
Normal Lovable projects connected to a user-owned Supabase project and backed by a GitHub repository can be analyzed and migrated. A connected repository gives Miglify access to Edge Function source code.
Lovable Cloud → Supabase
Lovable Cloud is a distinct workflow from a normal Lovable project connected to Supabase. Miglify provides a dedicated Lovable Cloud migration workflow for moving into your own Supabase project, covering Database, Auth, Storage, Secret requirements, Edge Function readiness, verification, and cutover steps.
Edge Function workflows
Miglify detects Edge Functions and evaluates deployment readiness based on available source code, required Secrets, and Supabase authorization. Supported functions can be deployed through the migration workflow, and any remaining requirements are surfaced before completion.
Coming next
- Backup mode
- Restore mode
- Manual sync
- Scheduled sync
- Bolt
- Replit
- Base44
- Firebase
- Neon
- PlanetScale
What is not fully supported yet
- Non-Supabase destinations
- Cross-region scheduled sync
- Deployment of Edge Functions where no source or required authorization is available