Skip to main content
NinjaNext
AI and automation

Lovable to Next.js: Read This Before You Convert

Most people want this conversion for SEO reasons that stopped applying in May 2026. What Lovable builds now, when converting is still right, and the cheaper option.

By NinjaNext TechnologiesPublished 5 min read

Key takeaways

  • Lovable does not offer a framework choice, so leaving it is the only way to get Next.js.
  • Apps created since May 2026 already render on the server, which removes the usual reason for converting.
  • Older browser-rendered apps are pre-rendered for crawlers, so the SEO case is weaker than most advice assumes.
  • Changing framework and moving the backend are two separate projects. Doing both at once is how these go wrong.

This question almost always arrives with a reason attached, and the reason is almost always search. Someone has read that an app which renders in the browser cannot rank, their Lovable project renders in the browser, and the conclusion follows. Convert it to Next.js and the problem goes away.

The reasoning was sound and is now mostly out of date. Lovable changed what it generates in May 2026, and it pre-renders the older output for crawlers. Most of the advice you will find on this was written before either of those things were true, which is why so much of it reads as more urgent than the situation warrants.

What Lovable actually builds, and when that changed

Lovable's own documentation is direct about the constraint: it does not offer a choice of framework or database. There is no setting to switch on. Getting Next.js means taking the code out and continuing the work elsewhere, which is a decision about who maintains the project rather than a configuration change.

What you have depends on when the project was created. Apps started from 13 May 2026, or 22 June 2026 on Enterprise workspaces, are built on TanStack Start, which renders pages on the server. Apps older than that are React and Vite, and render in the browser. Those are materially different starting points, so the first thing worth establishing is which one you are holding.

Why the search argument is weaker than it looks

For the older browser-rendered apps, the argument is not what it was either. Lovable serves pre-rendered copies of published pages to search engines, social preview bots and AI crawlers. So the crawler is not being handed an empty page and left to execute your JavaScript, which is the failure mode the advice was written about.

That is not the same as saying search is handled. Pre-rendering fixes whether a crawler can read the page, not whether the page deserves to rank, and the things that actually decide that are unglamorous: one page per thing a person might search for, titles and descriptions written for a result rather than a tab, headings that match the question, and other pages linking in. We have written about why an AI-built app does not show up on Google, and in practice those are the findings, not the rendering mode.

This matters commercially, because a framework migration is a project and a page of titles is an afternoon. Doing the migration first is a way of spending the budget on the part that was already working.

When converting is genuinely the right call

There are real reasons, and they are about where the product is going rather than where it is.

  • You need rendering behaviour the generated stack does not give you, and you can name the pages and the behaviour rather than describing it in general terms.
  • The app is becoming the smaller half of something larger that already runs on your own framework, and maintaining two is the actual cost.
  • You have a team who will own this code for years, and their fluency matters more than the starting point.
  • You have hit a ceiling you can demonstrate, with a page and a measurement, rather than one you have been warned about.

What these share is that someone can state the reason in a sentence without using the word future. A conversion justified by a general sense that a different framework is more professional is the expensive kind, because nothing afterwards tells you whether it worked.

What the work actually is

Your components mostly survive. React is React, and the pieces that render your screens move with little change. What does not move is everything around them: routing moves to the framework's own conventions, data fetching has to be decided per page rather than happening wherever it happens now, environment variables change shape, and anything that assumed it was running in a browser has to be told otherwise.

The trap is bundling this with the backend. If you are also leaving the managed backend, that is a second project with its own list, and Lovable's documentation is explicit that moving the database alone does not move authentication, storage, realtime or server functions. We have written up what moving off Lovable Cloud involves separately, and separately is how they should be done. Two migrations at once means that when something breaks you cannot tell which change broke it, and that is the state these projects stall in.

Either way, the step before both is owning the repository and reading what you have. That is the same first move as any inherited codebase, and it is worth doing before committing to a direction.

The option most people never consider

Lovable says eligible older projects can be upgraded to TanStack Start, which means server rendering without leaving the tool, without a migration, and without taking on a codebase you now maintain. If server rendering was the whole reason, that is the answer, and it is dramatically cheaper than the thing you came here to ask about.

So the order is: find out when your project was created, check whether an in-place upgrade is available, fix the ordinary on-page work, and only then ask whether the framework is the constraint. Most of the time the question dissolves somewhere in the first three steps. When it does not, you will be able to say exactly why, which is also what makes the work quotable rather than open-ended.

These facts changed once in 2026 and may change again, so check Lovable's own FAQ rather than an article, including this one. If you would rather have someone establish what you are holding first, our Lovable work starts by reading the project before changing anything.

Let's build it

Want help putting this into practice?

Tell us what you are building and where you are stuck. We will reply with questions, a suggested approach and next steps.