Move Your Lovable App to Next.js and Keep the URLs
We do not start new sites in Lovable. This is for an app that's already a Lovable or Vite project and should become a Next.js codebase we maintain in Cursor. The point of the move is to keep the URLs. We have not measured whether traffic holds, so we will not promise that.
Why leave the Vite app
A Lovable app is a Vite and React bundle. A marketing site that depends on Google, AI Overviews, and shared links wants each URL to return a complete document, with its own title, description, canonical, and JSON-LD. New Dashworth work starts in that document model, in Cursor. This page is only for something that is already on the other stack.
Next.js App Router is the stack used for that document model. St. Johns County Living and Itinerant Man run on it. This page does not claim a measured cutover for either one.
URLs are the asset
The migration inventory is a list of current URLs, the title and H1 on each, and the URL they must keep or redirect to. New vanity paths are a last resort. If a path has to change, it gets a permanent redirect from the old one. Query parameters that never should have been indexed get dropped on purpose.
The essay Move a Lovable site to Next.js is the field notes version of this process, including what we refuse to claim about traffic.
How the work proceeds
- 01
Export the URL list
Pull every URL from the live sitemap and the routes in the app. Note which ones are indexable.
- 02
Map each URL
Keep the path, or write a 301 from the old path to the new one. Do this before design changes.
- 03
Rebuild the document head
Title, description, canonical, Open Graph, and JSON-LD move with the page, matching the visible content.
- 04
Restore the crawler files
sitemap.xml, robots.txt, and llms.txt are republished. Search Console is checked for coverage after launch. Traffic change is recorded only once data exists.
Proof in the portfolio
Questions
Why migrate a Lovable site to Next.js?
To get server-rendered pages, stable metadata, and a URL model search and answer engines can rely on, in a repository Dashworth maintains in Cursor. New work does not stay on Lovable. An existing Lovable app is moved when those URLs matter.
Will the URLs stay?
Not if the migration is done as a map instead of a redesign of the paths. Every old indexable URL is kept or permanently redirected. That is the requirement. It still does not prove that rankings will be unchanged. That has to be measured afterward.
How long does a migration take?
It follows the number of templates and URLs, not a slogan. A small marketing site is a short project. A site with a large city silo or a content archive takes longer because every URL has to be accounted for. You get a range after the sitemap is counted.
The work stays with Dashworth.
Call or text 650-393-3378. We meet in Northeast Florida and San Mateo, and we take contract roles inside larger companies. No account managers, no handoffs.