Getting started with Miglify

Before you start

• Confirm you have private beta access and can log in.
• Choose a source project you own or are authorized to migrate.
• Have a clean destination Supabase project ready.
• Keep your own backups. Do not rely on a single tool for recovery.

Recommended first test

Start with a staging, test, or non-critical project. This lets you validate the flow end to end without production risk.

Create or choose a source project

Miglify supports Supabase and Lovable/GitHub-backed projects as sources. Pick one small enough to fit within private beta safety limits.

Prepare a clean destination Supabase project

Use a fresh Supabase project as the destination whenever possible. Miglify only removes items it creates during rollback, so starting clean makes recovery predictable.

Connect credentials

Provide source and destination credentials in the Start Migration flow. Miglify validates them before continuing.

Select migration modules

Choose which modules to include: database, auth users, and storage. You must select at least one.

Review analysis and validation

Miglify inspects the source and reports detected resources plus any warnings. Review these before continuing.

Configure secrets if needed

Miglify detects required secret names. You can apply destination values manually or use the automatic flow with a one-time Supabase Management Access Token.

Review Edge Function readiness

GitHub-backed Edge Functions can be deployed automatically. Supabase-detected-only functions require manual deployment.

Run migration

Confirm the migration to start. Progress is shown live per stage.

Review progress and reports

Watch the timeline update through discovery, schema, data, storage, auth, and verification stages.

Test rollback only on non-critical projects first

Rollback deletes only items Miglify created during that migration. Practice on test data before considering it for production.