Free migration planner
Plan your migration without losing rankings
Enter your site and where it’s moving. We list every URL, show which keep their path and build the redirect map your new platform imports.
This is an example plan for a made-up site.
The live planner isn’t switched on here yet. Book a call and we’ll run it on your site with you.
URL inventory
Every URL we found, grouped by type and path pattern.
| Type | Pattern | URLs | Keep | 301 | Check |
|---|
| Current path | On the new site | Status |
|---|
Redirect map
One 301 per URL that changes, straight to its new path. No chains.
| Old path | New path | Why |
|---|
Nothing to redirect: every URL keeps its path.
Unlocked. The plan is on its way to .
Download the redirect map in any format, or browse every URL below.
Effort
Medium
A rough band from what we could see. We fix the scope and price on a 30-minute call. Plan your migration
CMS export checklist
Do these before the old platform is switched off.
- From your current platform
Export posts and pages
Tools › Export writes one XML file with posts, pages, custom post types, categories and tags. Source: WordPress.org: Tools > Export screen (opens in a new tab)
Copy the media library
The export only links to images. Copy wp-content/uploads from your host before it goes. Source: WordPress.com: Export your content (opens in a new tab)
Save SEO titles and descriptions
Yoast or Rank Math fields aren’t always in the export. Crawl the live pages to keep them.
Export existing redirects
From your redirect plugin or server config, merged into the new map so nothing chains.
Export every collection
CMS › Collection › Export writes a CSV, archived items included, one locale at a time. Source: Webflow: Import content into the CMS (opens in a new tab)
Download images and files
The CSV links to Webflow-hosted files, which break once the site is deleted. Source: Webflow: Import content into the CMS (opens in a new tab)
Export your 301 redirects
Site settings › Publishing › 301 redirects › Export, then merge them into the new map. Source: Webflow: Import and export 301 redirects (opens in a new tab)
List interactions and forms
They are rebuilt on the new platform. Code export leaves the CMS behind. Source: Webflow: Export your site code (opens in a new tab)
Export each CMS collection
Framer’s own CMS Export plugin writes any collection to a CSV file. Source: Framer Marketplace: CMS Export plugin (opens in a new tab)
Export your redirects
The Redirect Sync plugin writes every redirect on the site to one CSV. Source: Framer Marketplace: Redirect Sync plugin (opens in a new tab)
Save pages and assets
There’s no one-click HTML export, so save every page, image and file before the plan ends. Source: Framer: Can I export my website to HTML and self-host it? (opens in a new tab)
List code components
Effects and code components are rebuilt, not exported. Agree which ones matter first.
Export CMS collections
CMS › collection › More actions › Export to CSV, for each collection. Source: Wix: Exporting content from a CMS collection (opens in a new tab)
Plan to copy blog posts
Wix can’t export blog posts to other platforms, so they are copied over. Source: Wix: Exporting blog posts to other platforms (opens in a new tab)
Download media by folder
There’s no bulk download, and free Wix media can’t be downloaded at all. Source: Wix: Downloading files from the Media Manager (opens in a new tab)
Export your redirects
The URL Redirect Manager exports its rules as a CSV to merge into the map. Source: Wix: Importing or exporting URL redirects with a CSV (opens in a new tab)
Export to WordPress XML
Settings › Export covers layout pages and one blog only. Other pages are rebuilt. Source: Squarespace: Exporting your site (opens in a new tab)
Download images one by one
Images and videos can’t be exported in bulk, so plan time for it. Source: Squarespace: Import to and export from your site (opens in a new tab)
Export products to CSV
Up to 10,000 products, without extra info, reviews or variant images. Source: Squarespace: Export products to a CSV (opens in a new tab)
Copy your URL mappings
Developer tools › URL mappings, merged into the new redirect map. Source: Squarespace: URL mappings (opens in a new tab)
Export your content
Posts, pages and collections from your CMS as CSV, JSON or XML.
Copy every image and file
From the old host or CDN, before the old site is switched off.
Save SEO fields
Titles, descriptions and social images for every page you keep.
Export existing redirects
Merge them into the new map, so old links don’t chain.
- On the new platform
Build collections, then import
CSV files up to 4 MB. Import referenced collections first so references match. Source: Webflow: Import content into the CMS (opens in a new tab)
Import the redirect CSV last
An import replaces existing redirects, and one bad row fails the whole file. Source: Webflow: Import and export 301 redirects (opens in a new tab)
Create fields, then import
Framer matches CSV columns to fields by name and uses Slug to update items. Source: Framer Academy: CSV import (opens in a new tab)
Add redirects on Pro
Site settings › Redirects, with wildcards, or import the CSV with Redirect Sync. Source: Framer: Set up redirects (opens in a new tab)
Turn content into collections
Markdown or data files with a schema, so a missing field stops the build. Source: Astro docs: Content collections (opens in a new tab)
Ship real 301s from the host
Use _redirects on Netlify or Cloudflare. A static build only writes meta refresh pages. Source: Astro docs: Routing and redirects (opens in a new tab)
Pick where content lives
A headless CMS for editors, or MDX files in the repo for a small team.
Add redirects to the config
next.config.js or vercel.json, up to 2,048 on Vercel, then bulk redirects. Source: Vercel: Configuration redirects (opens in a new tab)
- After launch
Keep redirects for a year
Google asks for permanent redirects, kept for at least a year. Source: Google Search Central: Site moves with URL changes (opens in a new tab)
Submit the new sitemap
Then watch 404s and indexing in Search Console for the first weeks. Source: Google Search Central: Site moves with URL changes (opens in a new tab)
Step-by-step guide
WordPress to Webflow migration
Plugins out, structured CMS collections in, every ranking URL kept.
Step-by-step guide
WordPress to Framer migration
For marketing sites that need to look sharp and change every week.
Step-by-step guide
WordPress to Astro migration
Code you own, content in files or a headless CMS, very light pages.
Step-by-step guide
Webflow to Framer migration
For small teams that redesign often and want motion without the setup.
Step-by-step guide
Framer to Webflow migration
When the content library, the team or SEO outgrows Framer’s CMS.
Step-by-step guide
Framer to Astro migration
Leave the hosted builder for code you own. The move we made with our own site.
Step-by-step guide
Webflow to Astro migration
Out of the hosted builder and into a codebase you own.
Step-by-step guide
Wix to Webflow migration
Wix won’t let the site leave. We rebuild it and recover the content.
Step-by-step guide
Squarespace to Framer migration
When the brand outgrows the template. Blog moved, design rebuilt.
Step-by-step guide
All migration guides
How each move works, what comes across and what gets rebuilt.
Platform URL rules
Where each platform lets your URLs stay the same
The rules the planner applies, from each platform’s own docs. Astro and Next.js can keep any path.
Webflow
Pages can sit in folders. CMS items live at /collection/slug, with a to z, 0 to 9 and hyphens only.
Framer
Pages can sit in folders. CMS pages have one slug, such as /blog/:slug, and dots in slugs work.
Astro
File-based routing, so any path can stay. Files keep their path in public/.
Next.js
Any path can be a route. Redirects live in next.config.js or vercel.json.
Official sources
- Webflow: Page URLs (opens in a new tab)help.webflow.com
- Webflow: Manage CMS Collections (opens in a new tab)help.webflow.com
- Webflow: Structure and style Collection pages (opens in a new tab)help.webflow.com
- Webflow: Import and export 301 redirects (opens in a new tab)help.webflow.com
- Webflow: Set up 301 redirects (opens in a new tab)help.webflow.com
- Framer: Duplicate a CMS page (opens in a new tab)framer.com
- Framer: Set up redirects (opens in a new tab)framer.com
- Framer plugins: Redirect Sync CSV format (opens in a new tab)github.com
- Astro docs: Routing and redirects (opens in a new tab)docs.astro.build
- Cloudflare Pages: Redirects (opens in a new tab)developers.cloudflare.com
- Netlify: Redirects and rewrites (opens in a new tab)docs.netlify.com
- Next.js: redirects (opens in a new tab)nextjs.org
- Vercel: Configuration redirects (opens in a new tab)vercel.com
- Google Search Central: Site moves with URL changes (opens in a new tab)developers.google.com
Press Escape to close.
14 official docs, read 10 October 2026.
FAQ
Migration planning questions, answered
What does the planner read?
Your public robots.txt, your homepage and the sitemaps they point to, up to 5,000 URLs. If there’s no sitemap, it follows links from the homepage to about 25 pages. It never logs in, submits forms or reads anything private.
Will my URLs change when I migrate?
Only where the new platform can’t serve the same path. Astro and Next.js can keep any path. Webflow and Framer keep most, but CMS items need a folder and a single slug (/blog/my-post), and Webflow slugs can only use a to z, 0 to 9 and hyphens. Every URL that changes gets one 301 to its new home.
Why a 301 and not a 302?
A 301 (or 308) tells search engines the move is permanent, so the old URL’s rankings and links pass to the new one. Google recommends permanent server-side redirects and keeping them for at least a year.
How many redirects can each platform take?
Webflow has no hard cap but recommends up to 1,000. Cloudflare Pages takes 2,000 static rules plus 100 dynamic ones, and Vercel 2,048 in config. When a whole group moves the same way, the planner suggests one wildcard rule instead of hundreds of lines.
Is this a full SEO audit?
No. It plans the URLs and redirects, which is where most migrations lose traffic. It doesn’t check rankings, backlinks, titles or page content. We do that part on a real project, before anything is designed.
What about images and PDFs?
On Astro and Next.js, files can keep their path in the public folder. Webflow and Framer serve files from their own CDN, so each one is marked to check by hand: link it to its new address, or redirect the old path to it.
Do you store my site or my email?
We read the public pages once to build the plan and don’t keep them. If you unlock the full plan, we email it to the address you give us and only send anything else if you tick the box for it.
Done for you
Want it moved for you? We migrate sites without losing rankings.
Same URLs where the platform allows, one 301 where it doesn’t, and SEO checked page by page before launch.
Every URL inventoried
Listed by template before anything is designed.
URLs kept or redirected
Same paths where we can, one 301 where we can’t.
SEO parity at launch
Titles, canonicals and structured data checked.