WordPress to Webflow
Content and custom fields, plugin-dependent features, new collection layouts and an editor’s review of the imported pages.
Website migration planner.
Know what needs to move, who owns it and what to check. Build a starting checklist and a redirect map your team can review.
Your checklist starts here.
Choose the platforms and what needs to move. Your plan will cover content, ownership, testing and launch checks.
No site scan or account access needed. Build a plan from the scope, or try the clearly labelled example.
Content & URLsTesting & handoverPeople & approvals
Assumes you have permission to move the site and a team to review it. Not an audit, cost estimate, automated migration or guarantee of search performance. This page does not save your work.
Old path. Right destination.
Add exact paths or import a two-column CSV. These are structural checks, not a crawl or live HTTP test.
Import or paste a CSV
Header: from,to. Import replaces the current map. Maximum 500 mappings / 200 KB. Only import non-sensitive route data.
Case and trailing slashes are preserved. No regex, wildcards, query strings or external destinations. For a domain move, select domain change and enter both origins in the scope.
Add a mapping to check it.
CSV is a handover format, not a host-specific configuration. Verify destination existence, content relevance, redirect codes and live behaviour separately. Review the map again if the scope changes.
Move the content.
Keep the context.
A new platform is only part of the move. Collections, images, forms and the pages people rely on all need somewhere to go.
Choose what is changing and the checklist adapts. A WordPress move calls out plugins and custom fields. An Astro or Sanity setup adds editing, preview and publishing checks.
Shape your plan
Every old path
needs a decision.
Match changed URLs to a relevant new page. The map flags structural problems in your entries, including duplicate sources and loops. Shared destinations and chains need a deliberate review.
Export the CSV for your developer. The actual redirect rules, content relevance and live responses still need testing on your chosen platform.
Review your mappingIllustrative redirect review
/about-us/aboutDirect destination/blog/story/insights/storyReview the content match/about/about-usLoop if combined with the first rowDifferent moves.
Different things to check.
Illustrative scopes, not completed client projects. Use the platforms and features that match your own move.
Webflow to Astro + Sanity
Keep the content model and frontend in view. Review custom code, forms, content extraction, preview and the publishing workflow.
A new domain, same platform
Coordinate domain ownership, DNS and release checks. Enter both origins so identical paths on different sites are not mistaken for self-redirects.
For the search side of a URL change, see Google’s site-move guidance and its redirect documentation. The planner organises work; it does not certify compliance or search outcomes.
Before you move.
What does the website migration planner do?
It turns your selected platforms and scope into a starting checklist. You can update task statuses, add owners and notes, check an explicit redirect map and download your work. It does not inspect, move or change your website.
Is the planner free, and do I need an account?
It is free to use without an account or email address. There is no payment step and no gate on the plan or redirect CSV downloads.
Can I plan a move from WordPress to Webflow or Webflow to Astro?
Yes. The checklist adapts to WordPress, Webflow, Framer, Sanity with a frontend, Astro with a CMS, or an undecided platform. A headless move still needs a content model, a frontend and an editing workflow. Platform-specific tasks are prompts for review, not a compatibility assessment.
Does the redirect checker visit my website?
No. It checks only the mappings you enter. It flags duplicate source paths, self-redirects, loops, chains and shared destinations within the supplied map. It cannot confirm whether a destination exists, is relevant, returns the right HTTP status or is already affected by another redirect rule.
What CSV format can I import or export?
Use two columns headed from,to, with one mapping per row. Quoted fields are supported. The limit is 500 mappings and 200 KB per import. Exact paths are supported; wildcard rules, query strings, fragments and external destinations are not. Case and trailing slashes are preserved. A cross-domain map needs both website origins and exports full URLs.
Can I upload the CSV straight to my hosting platform?
Not without checking its requirements. The CSV is a review and handover format, not a ready-to-install configuration. Your developer should translate the approved map into the destination platform’s rules and test it in the real environment. A many-to-one mapping may be valid but needs a content review.
Will a migration protect all my search rankings?
No tool or checklist can guarantee that. The planner helps organise review work, but it does not measure search performance or certify a launch. Capture a baseline, review URL changes and monitor the actual move with the people responsible for the site.
Are my plan and uploaded files saved?
The planner processes inputs and CSV files in the current browser tab. It does not upload them to a planning service or save them in local storage. Site analytics still follow the site’s normal privacy policy, but this tool sends no form values or file content to analytics. Download the Markdown plan and CSV before leaving or refreshing; there is no saved account or plan re-import.
Want a team behind the move?
We help plan the content, build the new site and work through the handover. Start with the site you have and what needs to change.
Talk through your website move.
Tell us what you use today, what is changing and where your team needs help.