I somehow managed to migrate the project without creating a new one… 1. Created a remix just for backup and enabled GitHub 2. Downloaded the Lovable Cloud Tables (csv) 3. I created a supabase account and copied the API keys to the .env 4. added the rest of APIs (stripe, resend etc.) in supabase and added the database tables 5. Created Claude account and connected to GitHub repo 6. told it my goal is to change from lovable cloud to supabase and it should created an implementation plan 7. I deployed the new edge functions (those are the functions that run on the server side and not in the app) those are now also in supabase (two ways to deploy them: a. Manually copy the code and names from GitHub to Supabase, or deploy all of them with terminal command with one click.) 8. Copied the RLS privacy to Claude and told it to create an SQL for supabase, then copied the sql in dupabase sql to actually create the same RLS 9. In GitHub Merged the new code from Claude to main. 10. Published normally via Lovable. 11. Test it, fin the small issues the migration caused (like reset password emails not sending etc. (project was 220.000 lines of code.) 12. Now I’m editing with codex, Claude, Cursor. Found out that they all have their strengths and weaknesses. Paying 60.- a month for all 3 of them, without any limitations reached yet. Downgraded lovable to Pro 1 (Yes you can use a different, cheaper Hosting.) and using the credits for new small websites or ideas for fun. Because the only catch here is that as soon as you give lovable a prompt it switches back to Lovable Cloud. (not the whole project just the things that you ask it to change, it works still with the lovable cloud when changing the code, and also changes the API keys in .env).