Frequently asked questions
Quick answers about the Miglify private beta, supported workflows, secrets, Edge Functions, rollback, and limits.
Is Miglify production ready?
Miglify is currently in controlled private beta. It is ready for guided testing on supported flows, but access is reviewed manually.
What platforms are supported today?
The private beta currently focuses on Supabase-to-Supabase and Lovable/GitHub-backed projects connected to Supabase.
Can Miglify migrate only part of a project?
Yes. Miglify supports selective migration modules for database, auth users, and storage.
Can Miglify migrate Edge Functions?
Miglify can deploy GitHub-backed Edge Functions when source code is available through a connected repository. Supabase-detected-only Edge Functions require manual deployment.
Can Miglify copy secret values from my source project?
No. Secret values cannot and should not be exported from the source project. Miglify detects required secret names and helps users recreate or apply destination values safely.
Does Miglify store Supabase Management Access Tokens?
No. Supabase Management Access Tokens are used as one-time setup tokens and are not stored.
Does Miglify store secret values?
No. Secret values are not stored or displayed after saving.
What does rollback do?
Rollback deletes only supported destination items Miglify created during that migration. It does not delete existing destination data that already existed before the migration.
What are the private beta limits?
Private beta migrations are limited to 100,000 database rows, 10,000 auth users, 10,000 storage files, 5 GB total storage, and 100 MB per storage file.
Should I start with production?
We recommend starting with staging, test, or non-critical projects before using production data.