How to move a Lovable site to WordPress, step by step

Before you start: is it an app or a site?

For scenarios where your Lovable project saves or loads data via Lovable Cloud or Supabase, or has logic that is executed on Lovable Cloud, then it is an application and can’t be deployed to WordPress. In such cases, keep your application on Lovable and move only the public site (if any) to WordPress. This guide is for the other case: pages, a blog, a contact or quote form, a design you like. That moves well.

Step 1: get the code and the content out

You can integrate GitHub from Project settings (all plans). Alternatively, paid plan users can make use of Download codebase under Project settings > Git. You can’t run this code on WordPress, but it is useful to have: the exact colors, fonts, spacing and components are in it, and a developer rebuilding the design works from it. You can find a detailed description of the process in our guide on exporting a Lovable project.

Separately, save everything. This includes the text on each web page, the web page images at their original sizes, and any file or image downloads. If the web application uses a database to store information (i.e. a list of users, blog posts, etc.), ensure that information is also exported from Lovable/Supabase. The code exports will not include that information.

What usually goes wrong: people export the code and forget the images, which are often served from the backend’s storage rather than the repository. Save them from the live site while it is still up.

Step 2: set up WordPress and hosting

Choose a managed WordPress host and install WordPress. It’s important that your host provides features to boost performance (e.g. HTTPS, server-side caching, PHP 8.2+), and that you have access to SSH and/or SFTP so that you can upload your theme files. Your test site can be on a temporary domain or a subdomain so that you don’t have to take the Lovable site down in the process.

What often happens: the use of a heavy all-purpose theme and a page builder. It takes time to edit a universal theme. However, a block theme dedicated to your site will require less time to edit compared to a heavy theme. Also, a block theme is leaner and faster.

Step 3: rebuild the design as a block theme

Here’s the heavy lifting. A WordPress block theme is made up of templates, template parts and patterns. WordPress provides various templates (archives, search, singular, and others). You can use these templates to structure your theme. Template parts are sections of a template (header, footer, sidebar, content, etc.). Patterns are reusable sections of a template. All of these are in HTML, along with styles (colors, fonts, etc.) in theme.json. The Lovable export is a React app, where each component is styled using TailwindCSS.

• Tailwind’s config (or the CSS variables it created) encompasses the base styling for colors, type and space for your application and it goes into theme.json.
• Header and footer components → template parts.
• Each repeated element (hero unit, feature unit, testimonial, CTA) is a block pattern created from core blocks (group, column, paragraph, image, button, etc.)
• Interactive blocks (tabs, accordions, carousels, etc.) should be added as a core block or a small custom block.

These conversion tools typically involve uploading a ZIP file to get a theme. The HTML is wrapped instead of rebuilt. Because of this, sections cannot be edited as blocks and forms are markup that posts nowhere, and the page weight is whatever the app was. Budget the same again to make it a theme someone can edit.

What usually goes wrong: fonts. Lovable projects often load Google Fonts by URL. A site rebuild should include efforts to self host Google Fonts and preload the fonts to improve page speed.

Step 4: move the content into pages

Create one page for each route, drop in the patterns from step three, and paste the text. Upload images to the media library to add them to the page. Add alt text for each image. If Lovable had posts, they become posts or a custom post type, which is the first time they will have had a Publish button.

URLs are notoriously finicky. Note all the routes that the Lovable site has (e.g. /about-us, /pricing, etc.) and set the permalinks for the corresponding WordPress pages to those routes. You’ll need to set up redirects for all of these pages in step 6 of this tutorial.

Step 5: forms, analytics, consent

Replace each Lovable form with a form plugin (Gravity Forms, WPForms or Fluent Forms) that emails you. The plugins should also be able to store the entries, and integrate with Slack and your CRM. Install your tag manager once, with consent defaults that match your region, and add the privacy and terms pages. Then submit every form and check the email arrives.

What usually goes wrong: Because the host uses a generic address to send the form emails, they end up in the recipient’s spam folder. All email sent from your site should be routed through your transactional email service or email server.

See what the rebuild would cost for your site

Scan my Lovable site

Free. Under a minute. Fixed price at the end.

Step 6: redirects, if the Lovable site had your domain

If the site only ever lived at “something.lovable.app” there’s nothing to preserve, so skip this. If the site is on your own domain, and Google has previously crawled the site, you need to perform a permanent (301) redirect from the previous locations of the pages to their new locations, or the pages will lose any rankings they previously had. To do this, you can create a list of the previous page locations from your sitemap, or use the Pages report in Google Search Console. From there, you can create a new location for each of those pages on your site, and use a WordPress plugin, or contact your web host to add the redirects.

Step 7: switch the domain

With the new site live on its temporary URL, update your DNS records to point to the new host and update your WordPress site URL to match. For now, keep the project published. If you find something missing you can still look. Only unpublish it (or let the plan lapse) once the redirects and Search Console show the new site being crawled.

Usually, what goes wrong: Make sure the new host has issued the HTTPS certificate before DNS moves, or visitors see warning messages for the hour it takes.

Step 8: check it the way Google will

• Google PageSpeed Insights on the homepage, mobile and desktop. A lean block theme on decent hosting should score in the 90s on desktop; if it does not, images or fonts are usually the reason.
• Search Console: add property, submit sitemap, view page.
• Every form, on a phone, once more.
• Every old URL, if there were redirects.

Step 9: hand it to the team

Create an editor account and show each one how to use the block editor. This section is probably the most important. Once you’ve done this, editing the site becomes a lot easier, because from now on changing the site is a person and a Publish button, not a prompt and a credit.

Questions people ask

Can I convert a Lovable project directly into a WordPress theme?

Tools exist that treat exported HTML as a theme. Those tools, however, do not improve the performance of a site. Copying exported HTML this way still leaves forms and other site functionality disabled. Those tools do provide a way to quickly create an approximation of a site; however, there is still work to be done to improve the site.

Will I lose my search rankings?

Not if the URLs stay the same or redirect, the titles and descriptions come across, and the new site is at least as fast. Sites usually gain after a move like this, because a server-rendered page with proper metadata is easier for Google than an app.

How long does it take?

Building yourself using a developer: about 1 or 2 weeks for a basic site, spending most of the time in step 3. MightyMigrate: 2 days for a staging link for a simple site with 15 or less pages.

Can I keep the Lovable project after moving?

Yes. Exporting does not remove anything, and nothing on the WordPress side depends on it. Many people keep it as a design reference or let the plan lapse once the new site has been live for a month.

Lovable facts checked on 28 September 2026 against its Git sync, Publish and SEO documentation. The WordPress steps are how MightyMigrate does its own rebuilds.