Miglify Docs
Guides and references for planning, running, verifying, and completing controlled SaaS migrations with Miglify.
Learn how to migrate Supabase, Lovable-connected, Lovable Cloud, and GitHub-backed projects with selective modules, live progress, credential validation, Secrets and Edge Function workflows, verification, and rollback-aware controls.
Migrating a production workload? Review destination readiness, migration limits, credentials, Secret requirements, Edge Function readiness, and rollback coverage before you start.
Choose a starting point
Getting started
Prepare your first migration, connect the required credentials, review preflight checks, and understand the migration lifecycle.
Supported workflows
Compare supported source workflows, migration modules, requirements, and destination expectations.
Supabase to Supabase
Move a Supabase backend to another Supabase project with controlled validation and module-by-module migration.
Lovable to Supabase
Migrate a Lovable/GitHub-backed application connected to Supabase into a destination Supabase project.
Lovable Cloud to Supabase
Migrate from Lovable Cloud into your own Supabase project with dedicated Database, Auth, Storage, Secrets, Edge Function, verification, and cutover workflows.
Migration capabilities
Core capabilities available across Miglify's supported migration workflows.
Learn how Miglify works
Selective migration
Choose supported modules such as Database, Auth users, and Storage before running a migration.
Live progress
Track migration stages, verification status, and completion from the job timeline.
Secrets
Detect required Secrets and complete configuration through the available automatic or guided workflow without exposing values in customer-facing logs or summaries.
Edge Functions
Detect Edge Functions, evaluate deployment readiness, and deploy supported functions when the required source and Supabase authorization are available.
Rollback
Roll back supported destination resources created by Miglify during that migration. Review rollback coverage before relying on it for recovery.
Migration limits
Review plan limits, resource limits, and workflow-specific requirements before starting a migration.