How to move a Lovable website to WordPress

Step-by-step: export a Lovable React site, convert the pages to WordPress and keep your design, SEO and URLs intact.

Convert2WP – convert your AI website to WordPressClick here

Why people move from Lovable to WordPress

Lovable is excellent for building a website quickly with AI prompts. Many owners later want WordPress because they need a familiar editor for colleagues, thousands of plugins, cheaper hosting or full ownership of their files.

The goal of a migration is simple: keep the look and the content, but gain an editable WordPress site.

Step 1 – Export or connect your project

Connect your Lovable project to GitHub or download the code. Write down every public page URL so you can recreate the same addresses later.

Step 2 – Convert the pages

A converter such as convert2wp.net reads the rendered pages and turns them into WordPress pages and a theme. Text, images, colours and layout come along.

Backend logic (databases, logins, payment flows) is not converted. You rebuild those parts with WordPress plugins such as WooCommerce, a form plugin or a membership plugin.

Step 3 – Keep your SEO

Use the same slugs, set a permalink structure of 'Post name', install an SEO plugin and add 301 redirects for any URL that changes. Submit the new sitemap in Google Search Console.

Step 4 – Small fixes afterwards

Small visual glitches after a conversion are normal. Most are fixed in minutes in the block editor or with a plugin.

Anatomy of a Lovable export

A Lovable project is a Vite application written in React and TypeScript, styled with Tailwind CSS and built on shadcn/ui components, which in turn wrap Radix UI primitives. When you open the repository you will find a src folder with pages or routes, a components/ui directory with dozens of small primitives, and a single global stylesheet that defines design tokens as CSS custom properties. In production, Vite bundles all of this into one HTML shell, a hashed JavaScript chunk and a hashed CSS file.

For a migration this structure is good news. The design system is centralised in tokens such as --primary, --background and --radius, so colours and spacing can be mapped one-to-one onto a WordPress theme.json palette. The components themselves do not need to survive; what matters is the markup they produce once rendered.

Mapping shadcn and Radix patterns to blocks

In practice I map the recurring Lovable patterns as follows: Card becomes a Group block with a border and radius style, Accordion becomes the core Details block, Tabs become a small tabs block plugin or stacked sections on mobile, Dialog-based popups become a lightweight modal plugin, and Button variants become registered block styles on the core Button block. Carousels built with Embla are usually replaced by a simple slider block or, better for performance, a static grid.

Lucide icons are rendered as inline SVG in the DOM, so after conversion they arrive as SVG markup that weighs a few hundred bytes each. That is lighter than the original icon library and needs no further work.

Decoupling Lovable Cloud and Supabase calls

Many Lovable sites call a database for testimonials, contact submissions or logins. Those calls are not converted. I inventory every network request in the browser's developer tools before the migration, then decide per feature: static data becomes WordPress content, form submissions move to a form plugin, and authenticated areas move to WordPress users with a membership plugin. Where an external API must stay, a small custom plugin calls it server-side with the key stored in wp-config.php, never in the page.

Field notes: auditing a Lovable export before conversion

In client projects I start with a fifteen-minute audit of the published Lovable site rather than the repository. I list every public URL, note which pages are generated from data and which are static, and record the title and description each page currently serves. That inventory becomes the acceptance checklist for the WordPress version: same URLs, same headings, same intent per page.

The second part of the audit is dependency mapping. Lovable projects frequently pull images from storage buckets, call server functions for forms and load fonts from external CDNs. Each of those becomes a decision: images go into the media library, forms move to a form plugin, fonts are self-hosted. Writing these decisions down before converting prevents the classic situation where a page looks right but silently still depends on the old platform.

Convert2WP – convert your AI website to WordPressClick here