WordPress
Wix
Squarespace
HubSpot
Custom
WordPress
Wix
Squarespace
HubSpot
Custom
Migrate to Webflow
The mapcomes first
Migrations do not fail on design. They fail on URLs. Whatever you are moving from, the first deliverable is a redirect map built from what Google actually has indexed — and it exists before a single page is designed.
Where you are now
Six platforms, one method
Two have a page of their own. The rest are jobs we do regularly and have not written up yet — send the URL and you get the same answer you would get from a page.
Page live
WordPress
The most common move we do. Posts, pages, media and every indexed URL, rebuilt in Webflow with a tested redirect map. Fixed scope.
Page live
Wix
Wix has no export button. Every page, post and image is rebuilt by hand, which is slower than anyone would like and the only way it actually works.
Ask us
Squarespace
Close to Wix in shape — limited export, and a design that has to be rebuilt rather than ported. The blog exports cleanly; almost nothing else does.
Read this first
Shopify
Usually the wrong move. Webflow Ecommerce caps products at 50 variants and cannot be combined with localization at all. If your shop is real, keep it on Shopify and move only the marketing site.
Ask us
HubSpot CMS
Almost always driven by the licence cost. The pages are the easy part; the integrations are the scope, so those get mapped before anything is quoted.
Ask us
Custom or hand-built
Bespoke PHP, an ageing framework, something a developer built in 2016 and then left. These are the ones where the URL list matters most, because nobody still has a map of it.
The number you will be shown
The scary data is not yours
Every migration agency quotes research like this at you, and the research is real. One study of 1,052 migrations found a median recovery time of 304 days.
22.8%
Of domain migrations recovered their traffic within 90 days, across 1,052 studied
304
Days — the median time to get back to the pre-migration baseline
13.9%
Had still not fully recovered after three years
Read the method, though: those are domain migrations. Moving to a new domain throws away every signal attached to the old one. A platform move on the same domain, with the same URLs, is a far smaller change — the risk that remains is URL changes and content restructuring, which is exactly what a redirect map controls. If you are keeping your domain, most of that chart is not about you.
Which is also why we will ask you not to rebrand at the same time. Do both at once and if traffic drops you will never know which one caused it.
How every one of them runs
The five steps
The order is the whole thing. Every migration that goes wrong went wrong because one of these happened after the one below it instead of before.
01
Crawl what you have, before anything else is discussed
Every indexed URL, taken from a crawl and from Search Console — not from your sitemap. The sitemap is what somebody intended; the other two are what Google actually has. Those lists are never the same, and the gap is exactly where traffic goes missing.
02
Write the redirect map before the design
Every old URL gets a destination or a decision. Pages that are being merged, dropped or renamed get decided now, in a spreadsheet, rather than discovered later in Search Console. Nothing becomes a 404 by accident.
03
Build on a staging URL you can open any time
Not a weekly reveal. There is a link, it is current, and you are welcome to look at it at two in the morning and send notes.
04
Test the map against the live URL list
Every redirect fired and checked before anything switches, not after. This is the step that gets skipped when a launch date slips, and it is the step that decides whether the launch date mattered.
05
Switch, then watch it daily for a fortnight
Search Console coverage and crawl errors, every day for the first two weeks. Problems found in week one are cheap. The same problems found in month three have already cost you the traffic.
Whatever you are moving from
What comes with you, and what does not
This is the same on every platform, and the right-hand column is the one worth reading twice. We list it before quoting rather than discovering it in week three.
Comes with you
On every platform
✓Pages, posts and their URLs
✓ Images and files, re-uploaded and re-linked
✓Titles, meta descriptions and canonicals
✓Categories, tags and authors, as CMS structure
✓ Forms, rebuilt as native Webflow forms
✓Your domain and your rankings, if the map is right
Does not
Plan for these, or decide to drop them
XComments — Webflow has no native comment system
XAnything a plugin did server-side: gated content, conditional logic, file-upload workflows
XCustom post types with no Webflow equivalent, without restructuring first
XYour current theme’s design, unless rebuilding it is in the scope
Scope
Four variables
No number on this page, because a migration quote that ignores these four is a number somebody made up. Send the URL and you get a real one the Within 1 business day.
01
How many indexed URLs
Forty pages and four thousand pages are different jobs. The number that matters comes from Search Console, not from the page count somebody remembers.
02
How much of it is CMS
A blog with authors, categories and tags is collection architecture, and that is most of the work. A brochure site is not, and it is quick.
03
Whether the design is being rebuilt
A like-for-like rebuild and a redesign are two different projects, and people describe both with the same sentence. We ask which one you mean before quoting, every time.
04
What it connects to
A form that emails you costs nothing. A form that writes to a CRM, gates a download and triggers a sequence is the actual scope of the project.
Questions
Fair questions
01
Will we lose traffic?
02
Can we rebrand at the same time?
03
How long?
04
Can we publish?
05
Our platform is not on the list
06
Can you just do the redirect map?
READY TO SWITCH PLATFORMS?
Send the URL
We will crawl it, tell you how many indexed pages you actually have, and quote from that rather than from a guess. Including when the answer is that you should stay put.