Migration guide

Migrate any legacy CMS into Lovable

A complete walkthrough of how Sitejump turns a WordPress, Drupal, HubSpot, or Sitecore site into a Lovable-ready React + Tailwind project — with every URL, redirect, image, metadata tag, and language version preserved.

What Sitejump is

Sitejump is an AI migration engine that clones the structure, content, assets, and SEO metadata of an existing website and hands the result to Lovable so an AI assistant can rebuild it as a modern React + Tailwind project. It exposes its work as a Model Context Protocol (MCP) server, which means Lovable, Claude, ChatGPT, Cursor, Gemini, and any other MCP-capable assistant can drive the rebuild directly from your chat.

Why teams choose Lovable

The migration is only worth the effort if the destination is materially better than staying put. Here's what changes about running your website the day you land in Lovable:

• Edit by prompt, not by ticket. Marketing describes the change in plain English and the built-in AI applies it — no dev queue, no plugin update window, no staging deploy.
• AI-native, MCP-ready. Built-in AI assistant, agents, image generation, and MCP connectors mean the site keeps getting smarter as models improve. A legacy CMS gets older; a Lovable site gets better.
• Portable React + Tailwind you actually own. No HubL, no Liquid, no Twig, no Handlebars, no Sitecore renderings, no OSGi. Any developer — or any AI assistant — can extend the code, and no vendor can hold it hostage.
• One product instead of a stack of subscriptions. Hosting, CDN, SSL, custom domains, forms, basic analytics, and security scanning are included, replacing the CMS licence + host + form plugin + CDN + monitoring line items.
• Built-in SEO and AEO. Per-route meta, canonicals, JSON-LD, sitemaps, and answer-engine-friendly content structure ship out of the box — not a paid SEO plugin bolted on.
• Grows from marketing site into real product. Built-in payments, auth, and database mean the site can grow into gated content, checkout, or dashboards without another re-platform.
• One-time migration, no retainer. Pay once and keep editing the site yourself — every change is a prompt to the AI agents, in this chat or through the MCP connector in Lovable, Claude, ChatGPT or Cursor. No tickets, no lock-in.

For platform-specific versions of this argument — including honest comparisons against Webflow, Framer, and rebuilding in Next.js on Vercel — see the WordPress → Lovable, HubSpot CMS → Lovable, and Sitecore → Lovable guides.

The three-step flow

Every migration follows the same three steps:

1. Free audit. Paste your legacy site URL. Sitejump fetches your sitemap, samples pages, detects your CMS, extracts colours, fonts, and language versions, and estimates your total page count so it can recommend the right tier.
2. One-time payment. Confirm the tier and check out via Stripe. There is no subscription and no per-page metered pricing after that.
3. Rebuild inside Lovable. Paste the MCP URL into Lovable (or Claude / ChatGPT / Cursor / Gemini) once. The assistant then pulls each page, image, and redirect through the connector and reconstructs the site inside a Lovable project.

Supported legacy CMSes

Sitejump works on any site that serves HTML over a public URL. It has been tuned for the CMSes enterprise teams get stuck on:

• WordPress
• Drupal
• HubSpot CMS
• Sitecore
• Adobe Experience Manager (AEM)
• Contentful
• Webflow
• Squarespace
• Wix
• Joomla
• Magento (content pages)
• Shopify (marketing pages)
• Custom PHP / Rails / .NET stacks

If your stack is not listed but the pages are publicly reachable, the audit still works — the CMS fingerprint step simply falls back to a generic classifier.

Product names above are trademarks of their respective owners. Sitejump is an independent migration service and is not affiliated with or endorsed by any of them.

What the free audit returns

• Detected CMS and fingerprint signals.
• Estimated total page count and the recommended pricing tier.
• Sitemap availability and a sample of discovered page paths.
• Extracted brand palette and font pairing.
• Detected language versions.
• High-level improvement signals for SEO, accessibility, and structure.

Nothing is charged for the audit. It runs in seconds and returns the same summary whether you started it from the landing page or from an AI assistant that has the MCP connector attached.

What the paid migration returns

• Full crawl of every page in your tier, respecting robots.txt and rate limits.
• Rehosted assets — images and downloadable files copied into Sitejump storage so your new project never breaks when the old site goes away.
• Design tokens — palette, font pair, type scale, spacing scale, border-radius scale, CTA button style, logo, and favicon.
• 301 redirect matrix from every legacy path to a proposed clean path, as JSON, CSV, Netlify _redirects, or a Vercel vercel.json block.
• Per-page SEO report — title/description lengths, canonical and og:image presence, structured-data flag, h1 count, images missing alt, internal link count.
• Structured data — every JSON-LD block (Organization, Article, Product, BreadcrumbList, FAQPage, etc.) captured verbatim so Lovable can re-emit it.
• Per-locale page lists for multilingual rebuilds.

How the MCP connector works

The Model Context Protocol lets an AI assistant call remote tools during a conversation. Sitejump exposes one MCP server per account at https://sitejump.dev/mcp. It is protected by OAuth 2.1 against your Sitejump identity, so only migrations you have paid for on your account are reachable through it.

You add the URL once. From that moment on, every migration you buy on the same account is reachable through the same connector — there is nothing to reconfigure per site. Inside the assistant, you talk to the migration in natural language: “rebuild the /about page”, “list every French page”, “give me the redirect CSV”. The assistant calls the matching tool and does the work.

A per-site direct-access token URL of the form /api/mcp/<token> is also available under the Advanced section of your account for scripting and CI use where OAuth is inconvenient.

Setup in Lovable, Claude, ChatGPT, Cursor, Gemini

Lovable

Open a Lovable project → + → Project connectors → All connectors → Custom MCP (bottom of the list). Paste https://sitejump.dev/mcp. If Lovable asks for a name, enter Sitejump exactly. A browser tab opens once for Google sign-in — that is the OAuth handshake and cannot happen inside the chat. Approve, close the tab, and the connector is live.

Claude Desktop

In Settings → Connectors → Add custom connector, paste the same URL. Claude walks you through the same OAuth popup.

ChatGPT (custom GPT Actions)

ChatGPT’s custom GPTs use OpenAPI Actions rather than MCP. Import the OpenAPI schema at https://sitejump.dev/api/public/openapi.json as an Action, choose OAuth as the auth type, and the same Sitejump identity works. The Action exposes the highest-value tools: start_free_audit, get_audit_summary, list_pricing_tiers, create_checkout, and get_migration_status.

Cursor

Add the URL as a remote MCP server in Cursor’s MCP settings. Same OAuth popup, same tool list.

Gemini

On any Gemini surface that supports remote MCP servers (Gemini in Google AI Studio, or a Gemini-powered client with MCP support), add https://sitejump.dev/mcp as a custom MCP server. Sign-in is usually one click — Gemini and Sitejump both use Google.

SEO preservation

SEO risk is the reason most enterprise teams put off legacy CMS migrations. Sitejump treats it as a first-class output, not a follow-up task:

• Every title, meta description, canonical, and og:* tag is captured on the way in.
• Every legacy path becomes a row in the 301 redirect matrix so no ranking URL is orphaned.
• Structured data blocks are captured verbatim and re-emittable in the new project.
• Sitemap and robots.txt are regenerated for the new structure.
• AEO signals (FAQ blocks, HowTo blocks, breadcrumbs) are surfaced so the Lovable AI can reproduce them cleanly.

Pricing

One-time payment per migration. EUR is the base currency; Stripe Adaptive Pricing converts to your local currency at checkout.

• Starter — EUR 49. Up to 25 pages, up to 3 languages.
• Business — EUR 99. Up to 100 pages, up to 10 languages.
• Pro — EUR 199. Up to 500 pages, unlimited languages.

The tier is recommended automatically from the audit’s page count so you never pay for a bigger tier than your site needs.

FAQ

Full FAQ lives on the landing page.

Moving the site yourself? Work through the SEO migration checklist — the inventory, redirect mapping and launch-day checks that keep rankings intact.

← Back to home