---
title: "Migration guide — how a Sitejump website migration works"
description: "The full Sitejump migration walkthrough: free audit, migration plan, one-time payment, MCP rebuild in Lovable, 301 redirects and launch verification."
canonical: https://sitejump.dev/migration-guide
lang: en
lastmod: 2026-08-14
---
# How a Sitejump migration works

## 1. Run the free audit

Paste your live website address. Sitejump crawls a sample the way a search engine does, detects the CMS, counts pages and languages, and extracts your colours, fonts and metadata into a preview report.

## 2. Review the migration plan

The audit returns a page inventory, an SEO report, the design tokens found on your site, and the size tier your migration falls into — so you know exactly what will be moved before paying anything.

## 3. Pay once for the migration

One-time payment tiered by page count: Starter €49 up to 25 pages, Business €99 up to 100 pages, Pro €199 up to 500 pages. No subscription. The full crawl then runs and packages the site.

## 4. Connect the MCP connector and rebuild

Paste your Sitejump MCP URL into Lovable (or Claude, ChatGPT, Cursor, Gemini). The assistant reads the migration package and rebuilds the site page by page as React + Tailwind, following the captured layout, content and design tokens.

## 5. Apply the 301 redirect map

Every old URL is mapped to its new Lovable route. Apply the generated redirect map so links from Google, other sites and campaigns keep resolving, and titles, descriptions and canonicals carry across unchanged.

## 6. Launch and verify

Publish in Lovable, point your domain at the new site, then run the launch verifier to confirm redirects resolve, metadata matches, and the sitemap, llms.txt and Markdown mirrors are being served.

## Supported platforms

WordPress, Drupal, HubSpot CMS, Sitecore, Webflow, Squarespace, Wix, Shopify, Ghost, Contentful, Sanity, Strapi, Adobe Experience Manager, Optimizely (Episerver), Kentico, Umbraco, Joomla, Craft CMS, Magento (Adobe Commerce), BigCommerce, Weebly, Framer, Duda, Bubble, Notion Sites, Carrd, Jimdo, Blogger, Medium, TYPO3, Contao, Concrete CMS, Payload CMS, DatoCMS, Storyblok, plus custom and bespoke stacks — the crawler reads the rendered site, so the source platform never has to cooperate.