Frequently asked questions
Quick answers about supported workflows, Secrets, Edge Functions, rollback, verification, and migration limits.
Is Miglify production ready?
Miglify is used for controlled production migrations on its supported workflows. Review destination readiness, migration limits, and rollback coverage before migrating a business-critical workload.
What platforms are supported today?
Miglify supports Supabase to Supabase, Lovable-connected/GitHub-backed projects connected to Supabase, and the dedicated Lovable Cloud to Supabase workflow.
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 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 remaining requirements are surfaced before completion.
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?
Secret values are not displayed after saving and are not exposed in customer-facing logs or migration summaries.
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 limits apply to a migration?
Plan limits, resource limits, and workflow-specific requirements apply. Current numeric allowances are published on the Pricing page, and Miglify reports detected resource counts during preflight analysis.
Should I start with production?
Production migrations are supported. For a first migration, a staging or non-critical project is recommended when practical so you can review validation, verification, and rollback coverage first.