Ninoo Builder
Move a whole app from Lovable
Importing brings your code. The Move from Lovable checklist brings the rest: the database and its users, uploaded files, sign-in, payments, AI and your domain. Your Lovable app keeps running the whole time, so you can test everything before anyone notices a change.
Where to find it
Import the app first (how to import). The project then shows a warning that it still uses its Lovable backend, with a Move from Lovable button. The checklist is also under More → Integrations. Only the project owner can make changes there; people you share the project with can follow along.
Each step says what it's for, where it stands, and has the button that moves it forward. You can stop at any point and come back later.
What you need
A Supabase account (larger apps may need one of Supabase's paid plans), your Lovable project, and, for the last step, access to your domain's DNS settings.The steps
- 01
Your code
Already done by the import. Until step 4 the preview still talks to your live Lovable data, so look but don't sign up or buy. - 02
Your own Supabase
Connect your Supabase account and let Ninoo create an empty project. See Supabase, Stripe and AI. - 03
Tables and functions
Ninoo creates the tables fromsupabase/migrationsand deploys every function insupabase/functions. Big apps take a few minutes. - 04
Your data
In Lovable open Cloud, then Advanced settings, and choose Export data. Upload that file (up to 5 GB) and press Load. Ninoo loads it on its own servers, so you can close the page while it runs, and in one go: if anything fails, nothing is changed. Loading again later replaces only the tables in your export (and the accounts); other tables are left alone. Accounts keep their passwords; everyone signs in once more. The file is deleted as soon as it has been loaded. - 05
Uploaded files
Lovable's export has no files. Ninoo gives you a short message to paste into Lovable's chat; Lovable adds a small read-only function that lends the files for 7 days. Paste its address back and Ninoo copies every bucket. If it stops, run it again: files already in your new project are skipped. Ask Lovable to delete the function afterwards. - 06
Live updates
Ninoo finds the tables your app watches for live changes and switches them on in the new project. - 07
Scheduled jobs
Lovable doesn't export timed jobs. Paste their list and Ninoo's agent recreates them. - 08
Secrets
Add each API key your functions read (email, payments, other services). Ninoo lists the missing ones by name. - 09
Sign-in
Lovable apps sign in with Google through Lovable's own service, which stops working once you leave. Ninoo's agent switches the code to your Supabase project's sign-in, and the checklist links to where you add your Google client. It also lists the callback addresses that change, so you can update them at Google, Stripe and other services. - 10
Payments
Connect your Stripe key; Ninoo points the webhooks at your new functions. Start with a test key. - 11
AI features
Lovable's AI service only works on Lovable. Turn on Nicrron AI and Ninoo's agent switches the calls over. - 12
Test in the preview
Sign up a test account, check your main pages, files, a test payment and AI. Tick each one off. - 13
Switch over
Pause changes in Lovable, export and load your data one last time, publish, and add your domain under Domains. Ninoo writes down your domain's old DNS first, so going back is a copy and paste.
What moves and what doesn't
| Thing | How it moves |
|---|---|
| Code, pages, styling | The import. |
| Tables and server functions | From your code, in step 3. |
| Rows in your tables | Lovable's data export, in step 4. |
| User accounts and passwords | In the same export. Sessions don't move, so everyone signs in once. |
| Uploaded files | Copied bucket by bucket in step 5. |
| Secrets (API keys) | Lovable can't export them: add each one again. |
| Scheduled jobs | Lovable can't export them: paste the list in step 7. |
| Google sign-in | Your own Google OAuth client, added in Supabase. |
| Your domain | Pointed at Ninoo in the last step. |
Going back
- Before the switch-over there is nothing to undo: Lovable is still your live app.
- After you change your domain's DNS, set it back to the old records the checklist saved. Anything people did on the new app since then stays in your new Supabase project.
- Keep your Lovable project for at least a week after switching. Download one last export before you delete it; Lovable removes its exports with the project.