Migrations
Moving a website to a new platform.
Each guide takes one move part by part: what the old platform lets out, what the new one takes in, the order of work and the redirects. They’re written for teams doing the move themselves too.
Trusted by teams from pre-seed to the S&P 100
Every move
Pick the platform you’re on and the one you’re moving to.
- WordPress to WebflowPosts come across as CSV, pages and the design are rebuilt, and posts move under a folder. A 301 for each changed address protects the search traffic.
- WordPress to custom codeContent stays in WordPress behind the new site or leaves as XML or JSON. Design and plugins are rebuilt in code, and a redirect map protects search.
- Webflow to custom codePages are written again as components, CMS content leaves as CSV or through Webflow’s API, and a permanent redirect for each changed URL protects search.
- Framer to custom codeFramer exports no code, so pages and components are rebuilt. CMS content leaves through a plugin as CSV or JSON, and permanent redirects protect the traffic.
- Webflow to FramerCMS Collections come across as CSV and the design is redrawn in Framer. Matching CMS paths and a permanent redirect for each changed URL protect the traffic.
- Framer to WebflowCMS collections leave Framer as CSV through a plugin, every page and animation is rebuilt, and a 301 for each changed CMS path protects the traffic.
- Squarespace to WebflowOne blog and the layout pages leave as XML, converted to CSV for Webflow; the store, events and design are rebuilt. Blog posts can often keep their addresses.
Before any move
Answers that hold whichever platforms you’re moving between.
It can, and nobody can promise that every position holds. What protects them is the work around the move. We inventory valuable URLs, plan redirects and check canonicals, indexability, content and internal links. We also monitor after launch. These steps manage migration risk; they cannot guarantee that rankings will stay unchanged. Some movement in the first weeks is normal while search engines recrawl the new addresses.
Most of our website builds take four to eight weeks, and we scope and price a migration as a website project. Websites start from $15,000. The time depends on how many different page layouts have to be built again, how much content needs cleaning up or restructuring, the forms and integrations, and how many addresses change and need a redirect.
Partly. Content kept as structured records, such as blog posts, can often be exported in bulk, converted to a format the new platform accepts and imported. Pages, layouts and forms are built again on the new platform, because each platform stores design in its own way. Plan for some cleanup after any import. Each guide says what its two platforms let out and take in.
Often it makes sense, because the pages are built again on the new platform either way, and copying the old design is still a full build. The cost is that more changes at once, so a drop in traffic is harder to trace. Keep the pages that earn search traffic at their addresses or redirect each one, and change what they say with care.
Is your move not listed?
Tell us the platform you’re on and the one you’re looking at. We reply within 12 hours.
Most teams start with a call, then a sprint or an audit.
The people you’d work with, from the first call to launch