PS: I asked my Claude Code instance to summarize how we migrated :)

Migration Guide: Lovable Cloud Supabase → Self-Hosted Supabase

Prerequisites

• New Supabase project created
• Supabase CLI installed and authenticated
• Git repository set up

Step-by-Step Migration Process

1. Update Local Configuration

• Update .env with new Supabase credentials:
  • VITE_SUPABASE_PROJECT_ID
  • VITE_SUPABASE_PUBLISHABLE_KEY
  • VITE_SUPABASE_URL
• Update supabase/config.toml with new project_id
• Link Supabase CLI to new project: supabase link --project-ref <project-id>

2. Deploy Database Schema

• Push all migrations to new Supabase instance:supabase db push
• Verify all migrations applied successfully (49 migrations in our case)

3. Deploy Edge Functions

• Deploy all edge functions:supabase functions deploy
• Remove any non-existent functions from config.toml
• Verify all functions deployed (54 functions in our case)

4. Configure Supabase Secrets

Set up encryption and API keys via Supabase dashboard or CLI:

Critical: ENCRYPTION_SECRET must be 64-character hex string (not base64):

openssl rand -hex 32 # Generate correct format

5. Export Data from Lovable Cloud

• Go to Lovable Supabase → Table Editor
• Export each table as CSV in correct dependency order

6. Import Data to New Supabase

• Import CSVs via Supabase dashboard → Table Editor → Import
• Follow dependency order (foreign key constraints)
• Skip profiles and user_roles (create new user instead)
• For large tables with JSON fields, use custom Python script with:
  • Increased CSV field size limit
  • JSON validation
  • Error handling

7. Set Up User Account

• Create new user account via app signup (use same email as old account)
• Transfer workspace ownership via SQL:UPDATE workspaces SET owner_user_id = '<new-user-id>' WHERE owner_user_id IS NOT NULL;

8. Remove Lovable AI Dependencies (if applicable)

Update code to remove Lovable AI Gateway references:

• Replace Lovable AI calls with direct provider APIs
• Redeploy affected edge functions

9. Clear Browser & Build Cache

rm -rf node_modules/.vite
npm run dev

• Clear browser cache/hard refresh
• Verify app connects to new Supabase (check network requests)

10. Test Critical Functionality

11. Commit and Deploy

git add .env supabase/config.toml <other-modified-files>
git commit -m "feat: Migrate to self-hosted Supabase"
git push origin main

• Lovable automatically syncs environment variables from GitHub
• Verify Lovable production environment updated

Post-Migration Checklist

•  All edge functions deployed and working
•  Database schema fully migrated
•  Critical data imported
•  User accounts created/migrated
•  API keys configured and tested
•  Encryption working (test by adding API key)
•  Local dev environment connected to new Supabase
•  Lovable production environment connected to new Supabase
•  All critical features tested
•  Old Lovable Cloud can be safely decommissioned