Database & Supabase
Integrations & Backend · 11 articles
[Database] Can I connect multiple Supabase databases to one Lovable project?
Lovable supports connecting one Supabase project via the native integration. For multiple databases, you can manually add additional Supabase connections via Edge Functions and API calls in your code. This requires some manual setup beyond the one-click integration.
[Database] Help! I'm stuck in the Lovable ecosystem and can't migrate my database
Your data is stored in Supabase (PostgreSQL), which is fully portable. Export via Supabase's native tools or pg_dump, then migrate to any PostgreSQL host. Lovable generates code synced to GitHub—export and redeploy to another platform (Vercel, Netlify, custom servers). You're never truly locked in.
Advanced migration using the Supabase CLI
Use the Supabase CLI (`npm install -g supabase`) to pull schema and data from your source project (`supabase db pull`, `supabase db dump`), then push to the target project (`supabase link`, `supabase db push`). This command-line approach is faster and more reliable than manual dashboard migrations, especially for large databases. Full instructions are in Supabase CLI documentation.
Can I change my mind after adding Cloud to my project?
The reference material does not specify whether you can remove Cloud from a project or revert to Supabase. For details on switching between Cloud and Supabase after setup, contact support@lovable.dev.
Can I connect my project to a backend to store data?
Yes, Lovable has native Supabase integration. Click 'Connect' from Cloud → Supabase, select your project, and confirm. Lovable can then generate database tables, authentication, and Edge Functions. For other backends (Firebase, AWS, custom APIs), use Edge Functions and manual API calls.
Can I export my Cloud project to Supabase?
The reference material does not describe exporting a Cloud project to Supabase. Both use PostgreSQL databases under the hood, but migration would be complex. Contact support@lovable.dev about data migration options if you need to switch platforms.
Can I migrate my project from Supabase to Cloud?
The reference material does not describe a migration path from Supabase to Cloud. Since both use PostgreSQL, manual export/import of data might be possible, but Lovable doesn't provide an automated migration tool. Contact support@lovable.dev to discuss options for migrating projects, databases, and authentication.
Can I use one Supabase database for multiple Lovable projects?
Yes, you can connect multiple Lovable projects to the same Supabase instance. This is useful for monoliths or related microservices. However, each project shares the same database and authentication context. Be careful with RLS policies and data isolation—set up row-level security properly to prevent unintended data leakage between projects. Contact support@lovable.dev for architectural guidance.
How is the region selected when I enable Cloud?
When you enable Cloud for a project, Lovable likely selects a region based on your location or account settings. The reference material doesn't detail the exact selection logic. Check your Cloud settings or Project Settings to see which region was assigned. Contact support@lovable.dev if you need a different region.
I'm currently using the Supabase integration. What does this change mean for me?
Lovable Cloud is an alternative to the traditional Supabase integration, offering tighter integration and simplified setup. If you're using Supabase, you can continue using it—no changes required. Cloud is a newer option for new projects or migrations. Both support databases, authentication, file storage, and real-time features. You don't have to migrate unless you choose to.
Is there a limit to file uploads with Supabase storage?
Supabase Storage on the free tier allows up to 50MB per file. Paid tiers increase this limit. File storage is generous overall, but very large files (>50MB) may need custom handling. For apps needing massive file uploads, consider chunked uploads or alternative storage. Prompt Lovable to implement large file handling if needed.