Getting started with Miglify

Before you start

• Sign in to your Miglify account.
• Confirm you own or are authorized to migrate the source project.
• Confirm you own or are authorized to use the destination Supabase project.
• Choose the source workflow that matches where your backend currently lives.
• Prepare a clean destination Supabase project whenever practical.
• Review the applicable migration and plan limits before starting.
• Keep an independent backup for business-critical workloads.

Recommended first migration

For your first migration, using a staging, test, or non-critical project is recommended when practical. This lets you become familiar with validation, migration progress, verification, rollback coverage, and cutover before moving a business-critical workload.

Choose a source workflow

Miglify supports Supabase, Lovable-connected/GitHub-backed, and Lovable Cloud source workflows. Choose the workflow that matches where your application backend currently lives.

Prepare a clean destination Supabase project

Use a clean Supabase project as the destination whenever possible. A clean destination reduces conflicts, makes verification easier, and keeps Miglify's rollback behavior more predictable.

Connect credentials

Provide only the credentials and authorizations requested by the selected migration workflow. Miglify validates access before allowing the migration to continue. Never paste passwords, access tokens, service-role keys, or Secret values into support messages.

Select migration modules

Choose the supported modules you want to migrate. Depending on the workflow, this can include Database, Auth users, Storage, and related Edge Function or Secret preparation. Miglify shows the available options before the migration starts.

Review analysis and validation

Miglify analyzes the source, validates destination readiness, and reports detected resources, blockers, and warnings before execution. Resolve blockers and review warnings before continuing.

Configure Secrets if needed

Miglify detects required Secret names and guides configuration according to the selected workflow and available Supabase authorization. When a required value cannot be transferred automatically, Miglify asks you to provide it securely before the dependent Edge Function is considered ready.

Review Edge Function readiness

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, while any remaining requirements are surfaced clearly before completion.

Run migration

Review the final migration summary and confirm when you are ready to start. Miglify processes the selected modules through the worker and reports progress by stage.

Review progress and reports

Follow the job timeline as Miglify progresses through the applicable Database, Auth, Storage, Secret, Edge Function, verification, and completion stages. The exact stages depend on the selected workflow and modules.

Review rollback coverage before cutover

Rollback applies only to supported destination resources created by Miglify during that migration. Review the job's rollback coverage and keep your own backups for resources outside that scope.

Complete verification and cutover

Review the final verification results before switching production traffic or pausing the source system. For workflows that provide Cutover Readiness, complete the required automatic and manual checks before proceeding with cutover.