Supabase Setup
Before we begin the migration, you need a Supabase project ready to receive your data. Here’s how to set it up.Step 1: Create Your Supabase Account
Sign up at supabase.com
Go to supabase.com and create an account.Recommendation: Use the same email as your Lovable account for easier tracking.
Step 2: Create a New Project
Configure your project
Organization: Your company or personal orgProject Name: Choose something descriptive
- Good:
myapp-production - Good:
crm-migrated - Avoid:
test,new-project
- Generate a strong password
- Save it in your password manager
- You’ll need this for direct database access
- Choose closest to your users
- Consider data residency requirements
- Common choices: US East (N. Virginia), EU (Frankfurt), Asia (Singapore)
Step 3: Gather Connection Information
Once your project is created, we need these details:Project URL
Location: Project Settings → APIFormat:
https://[project-ref].supabase.coExample: https://abc123def456.supabase.coWe need this for: API calls, storage accessAnon/Public Key
Location: Project Settings → API → Project API KeysFormat:
eyJhbGciOiJIUzI1NiIs...We need this for: Client-side authenticationService Role Key
Location: Project Settings → API → Project API Keys⚠️ Keep this secret! Never expose in client code.We need this for: Admin operations during migration
Database Password
You created this during project setup.We need this for: Direct PostgreSQL access
Share securely: Send these credentials via encrypted channel (1Password, secure email, or scheduled call). Never post in public channels.
Step 4: Configure Your Project
Enable Required Extensions
Go to Database → Extensions and enable these (if your app uses them):Common Extensions
Common Extensions
uuid-ossp- UUID generation (most apps need this)pgcrypto- Cryptographic functionspg_trgm- Trigram matching for search
Advanced Extensions
Advanced Extensions
postgis- Geographic datapgvector- Vector similarity searchpg_stat_statements- Query performance
Set Up Authentication Providers
If you use social login:Configure OAuth Apps
For each provider:
- Create OAuth app in provider console
- Add callback URL:
https://[project-ref].supabase.co/auth/v1/callback - Copy Client ID and Secret to Supabase
Configure Storage (Optional)
If you want specific storage settings:Step 5: Prepare for Migration
- Supabase account created
- New project provisioned
- Region selected (close to users)
- Required extensions enabled
- Auth providers configured (if using OAuth)
- Service role key secured
- Database password saved
- Project URL documented
Security Checklist
Enable Row Level Security
We’ll set this up during migration, but verify it’s available.Go to Database → Tables and check that new tables will have RLS.
Review API Keys
- Anon key: Safe for client-side code
- Service role key: NEVER in client code, only server-side
Set up backup policy
Supabase automatically backs up Pro+ projects.Go to Database → Backups to verify schedule.
What Happens Next
Once you’ve completed setup:- Send us your credentials (securely)
- We’ll schedule the migration (usually within 48 hours)
- We’ll run a test migration on a subset of data
- You’ll review the results and approve
- We’ll execute the full migration
- You’ll update your app with new connection strings
- We’ll monitor for 48 hours to ensure stability
Post-Migration Connection Details
After migration, you’ll need to update your app with these values:Questions about setup? Contact us at support@nextlovable.com or check Supabase’s documentation.
