The short answer
Move the marketing pages of a Lovable project into the client's WordPress and leave the app itself, with its logins and database, running on Lovable. Split the routes first, quote the page list, convert with UiChemy, review on staging, set client roles, add redirects for changed URLs, and agree in writing who maintains each half.
What you need
- Edit access to the client's Lovable project. Download codebase is a paid Lovable feature; Git sync to GitHub, GitLab or Bitbucket is on every Lovable plan.
- A route list from the client's app, so you can mark each page as marketing or app before you quote.
- A WordPress install on the client's hosting, plus a staging copy for review, with Elementor or Gutenberg active.
- The UiChemy plugin on that site and Claude with the UiChemy MCP, or a WordPress MCP you already run.
- Access to the client's DNS, because the marketing site and the app will usually end up on different hostnames.
- A paid UiChemy plan if the client will edit pages themselves. Role Manager isn't on the Free plans.
Step by step
Split the project: what moves, what stays
Go through every route in the Lovable project. Public pages that only show content (home, features, pricing, about, contact) are candidates for WordPress. Anything that needs a signed-in user, reads or writes the database, runs an edge function or takes a payment stays in Lovable. Lovable's built-in backend (Cloud) holds the database, authentication, storage and functions, and UiChemy doesn't document converting any of them. Ask Lovable to do the inventory for you in Chat mode, which discusses the app without changing code.
List every route in this project. For each one, tell me whether it reads from or writes to the database, requires a signed-in user, calls an edge function, or takes a payment. Return a table with columns: route, purpose, uses backend (yes/no), notes.Scope and quote from that list
Quote the marketing pages as a fixed list, with a set number of review rounds. Put app changes on a separate line, because they happen in Lovable, not in WordPress. Name what's out of scope in writing: user accounts, the dashboard, payments, and any data migration. A client who thinks the whole product is moving will read a page migration as a broken promise.
Plan the domains before you build
The usual split is WordPress on the root domain and the app on a subdomain. Lovable supports custom domains and subdomains on paid plans, for example app.clientdomain.com. Decide this now so every Sign in and Get started button on the new pages can point at the right address from the first draft.
Convert the marketing pages
Download the Lovable ZIP and convert only the routes you scoped. The full walkthrough is in the Lovable to Elementor steps, so it isn't repeated here.
Convert only these routes from the attached Lovable ZIP to WordPress with the UiChemy MCP, using Elementor: /, /features, /pricing, /about, /contact. Skip every route that needs a login. Point every Sign in and Get started button to https://app.clientdomain.com. List anything you could not convert.Review on staging, side by side
Put the converted pages on a staging copy of the client's WordPress. Staging sites don't count against Composer site limits. For comparison, send the client a Lovable shared preview link next to the staging URL. Lovable's preview links are view-only, can carry a password, and don't need a Lovable account, so the client sees both versions without joining the project.
Hand over with roles on both sides
In WordPress, use the UiChemy Composer role manager to give the client's marketing person front-end Design Mode for copy, images and links, and keep structure and code for your team. In Lovable, check who owns the project. Lovable's Transfer ownership setting moves the one existing project to a new owner. Remixing makes a copy instead, and a remix never carries database records, secrets, custom domains or collaborators.
Redirects and SEO before the DNS switch
Map every old public URL to its new WordPress address and add 301 redirects for any path that changed. Set titles and meta descriptions in Rank Math or Yoast, then submit the new sitemap in Google Search Console after launch. Test the Sign in links from the live marketing pages into the app subdomain once DNS has moved.
Write down who maintains what
After launch there are two systems. WordPress pages are edited by the client inside their role, with plugin and core updates on your retainer or theirs. The app keeps being built in Lovable, on whichever Lovable workspace pays for it. Put both in the handover document, with names, so the next change request reaches the right person.
What carries over and what does not
What you get
- The client's public pages run on WordPress they own, editable without a prompt and with a normal SEO plugin.
- The app keeps working in Lovable on its own subdomain, with its users, data and payments untouched.
- A quote the client can read: a fixed page list, a named out-of-scope list and a maintenance owner for each half.
- Old URLs redirect to their new addresses, so links and search rankings that point at the previous pages still land somewhere.
What does not carry over
- This doesn't move the app. Logins, databases, payments and server functions are not documented as converted by UiChemy.
- Two systems mean two bills and two places to make changes. Some clients will prefer to keep everything in Lovable, and that's a fair choice for a small product.
- Download codebase needs a paid Lovable plan. On Free, use Git sync to get the code out.
- Lovable projects created from May 13, 2026 use TanStack Start with server code. Pages that render their content on the server need checking after conversion, since only what's on the page converts.
- UiChemy outputs to Elementor and Gutenberg today. Bricks is listed as coming soon.
Troubleshooting
A marketing page shows data from the app
That section depends on the backend. Rebuild it with static content in WordPress, or leave that page in Lovable and link to it.
Sign in buttons still point at the old domain
Search the converted pages for the old address and update the links, or redo the conversion with the app URL in the prompt.
The client can't see the Lovable preview link
Check the link wasn't deleted and send the password separately. Preview links are view-only and don't need a Lovable account.
Search traffic dropped after launch
Check the redirect map for missing paths, confirm the new pages have titles and meta descriptions, and resubmit the sitemap.
The remixed project is missing its data
Remixing never copies database records or secrets. Use Transfer ownership when you mean to hand over the original project.
The client wants to edit a page and breaks the layout
Restrict their role to front-end Design Mode in the role manager.
Frequently asked questions
Should every Lovable project move to WordPress?
No. If the product is mostly app with a thin landing page, moving one page adds a second system for little gain. The split pays off when the client needs a content site they can edit, rank and grow.
Can the app and the WordPress site share a domain?
Yes, by splitting hostnames. WordPress takes the root domain and the Lovable app runs on a subdomain such as app.clientdomain.com, which Lovable supports on paid plans.
How do I price this migration?
Price the marketing pages as a fixed list with set review rounds, and quote app work separately. Redirect mapping and the handover document are real work, so put them on the quote too.
Does the client need a Lovable account to review?
No. A Lovable shared preview link opens without an account and can be password-protected.
Who owns the code after the move?
Lovable says users own the apps, code and content they create, subject to third-party rights such as open-source licenses. The WordPress pages are standard content on the client's install.
Can I do this on a Free Lovable plan?
Partly. Download codebase is on paid plans, while Git sync is on every plan, so you can still get the code out through a repository.
What does UiChemy cost for this job?
A single client site fits the Designer plan at $8 a month billed yearly, or Composer Solo at a one-time $89. Agencies running several of these should read AI to WordPress for agencies; solo designers should see the freelance designer workflow.
The client hasn't picked a builder yet. Where do I start?
If they're still choosing, our Figma Make vs Lovable comparison and the Bolt alternatives list cover the trade-offs.