Migration Guides
Step-by-step guides for moving your project's backend infrastructure to your own cloud accounts — database, storage, auth, and edge functions included.
Migrate from Lovable Cloud to Supabase
Move your Lovable app's Supabase backend — database schema, edge functions, storage buckets, and auth configuration — to your own Supabase project. Avoid vendor lock-in and keep full ownership of your data.
→Migrate from Bolt.new to Supabase
Move your Bolt-generated app's Supabase backend — database schema, data, edge functions, auth configuration, storage buckets — to your own Supabase project.
→Migrate from Base44 to Supabase
Extract your Base44 project's auto-generated Supabase schema, RLS policies, auth configuration, and storage buckets into a fully owned Supabase project.
Migrate from Firebase to Supabase
Move your Firebase app's backend — Firestore collections to PostgreSQL, Firebase Auth users, Cloud Functions to Edge Functions, and Firebase Storage — to your own Supabase project.
Migrate to a Self-Hosted Supabase via Downloadable Package
Target Supabase isn't reachable from the internet? Staticbot runs discovery + export, hands you a password-protected ZIP, and Claude Code (or Codex/Gemini) applies it locally. Nothing reaches into your VPC.
Back Up Your Lovable Project — Download Everything in One ZIP
Not ready to migrate, but want an offline copy in case Lovable changes pricing or you lose access? Pull schema, table data, edge functions, storage files, auth users, OAuth identities, secrets, and cron jobs into one password-protected ZIP.
Coming soon
v0 → Supabase
Transfer your v0 project's Supabase backend to a fully owned environment.
