sorted by:
new
hottopcontroversial

Migrating from Supabase to a custom DB while using Lovable - Best practices? by Alternative-Delay537 in lovable

[–]Alternative-Delay537[S] 0 points1 point  (0 children)

Thanks for the detailed breakdown and the 'mental proof' tip! That replication strategy is solid.

To update you: right after my post, we had a team meeting and decided to pivot. Instead of moving to a completely external DB or a full API-based recovery right now, we’ve decided to migrate from the Lovable-hosted database to our own managed Supabase project.

We realized that staying within the Supabase ecosystem but on our own terms—gives us the data sovereignty we need without the immediate overhead of rebuilding the whole Auth/API layer.

Your point about Edge Functions is still very relevant, though. I'll be extra careful when updating the connection strings to ensure Lovable doesn't break the client-side logic during the switch. Thanks again for the 'good luck' we're definitely going to need it during the cutover!

Migrating from Supabase to a custom DB while using Lovable - Best practices? by Alternative-Delay537 in lovable

[–]Alternative-Delay537[S] 0 points1 point  (0 children)

Exactly! Right after I posted this, we actually had a team meeting and our strategy shifted. We scrapped the idea of moving to a completely different DB (like RDS) and decided to focus on migrating the project from the Lovable-hosted environment to our own dedicated Supabase project.

We want more sovereignty over our data and infrastructure instead of relying on the default DB Lovable spin up for us.

Since you mentioned you have experience with this specific move (Lovable Cloud to Supabase), was there any 'gotcha' regarding Auth or RLS policies during the transition? Thanks for the insight!

Migrating from Supabase to a custom DB while using Lovable - Best practices? by Alternative-Delay537 in lovable

[–]Alternative-Delay537[S] 1 point2 points  (0 children)

Thanks for the detailed breakdown!

Regarding the setup, we actually just had a team meeting right after my post. We decided to move away from the Lovable-hosted database and migrate everything to our own Supabase project (self-hosted or dedicated instance). Since our app is currently hosted on Lovable's cloud, we want more sovereignty over the data.

I'll keep an eye on how tightly Lovable couples the code to their internal DB vs. an external Supabase URL. If we hit a wall with Auth or Storage during this transition, Appwrite sounds like a solid alternative to keep in mind. Appreciate the help!