A WordPress to Webflow migration rebuilds your whole marketing site: the sitemap, every page and every CMS collection. It keeps your rankings when every old URL has a mapped 301 redirect, and your pipeline when the forms and tracking are tested before launch.
This checklist comes from two WordPress to Webflow migrations we ran in 2026, for a cybersecurity SaaS and an HR compliance SaaS. It covers the SEO work every guide covers, then the lead and ad tracking that decides whether the new site keeps its pipeline.
What does a WordPress to Webflow migration involve?
A WordPress to Webflow migration involves six stages: audit and plan, design, copy and content, the build, redirects and tracking, then launch. Moving the blog is one part of stage three.
Both migrations behind this checklist were whole-site rebuilds on Webflow. The cybersecurity SaaS got a new sitemap and menu, with about 30 main pages and 25 guides rebuilt to signed-off designs. The HR compliance SaaS relaunched with 41 static pages, plus 14 CMS templates for its blog, customer stories, training courses and careers. On both, the brand went into Webflow first as a style guide of colours, type and components, and every page was built from those parts.
Content moves into Webflow's CMS by CSV import or through Webflow's API, and AI now does most of the work. On the cybersecurity SaaS, AI moved all 323 blog articles through the API and checked each one twice against its WordPress original. People wrote the rules first, down to which headings stay H2, and signed off a pilot of seven articles before the rest moved.
The outliers still take people's time. The longest article, with 82 images and 17 tables, took three hours on its own. Redirects worked the same way. On the HR compliance SaaS, AI mapped the 190 old URLs it was sure of and flagged 238 for the client's team to decide.
What happens to your WordPress plugins when you move to Webflow?
Every WordPress plugin stops working at cutover, so each job it did needs a named owner on Webflow before launch. The plugins are easy to list. What they were doing is what gets missed.
| The job | Typical WordPress plugin | Who does it on Webflow |
|---|---|---|
| Page titles, meta descriptions and canonical tags | Yoast SEO or Rank Math | Webflow's page settings and CMS fields, filled from a WordPress export |
| XML sitemap | Yoast SEO or Rank Math | Webflow's auto-generated sitemap |
| llms.txt for AI assistants | Yoast SEO, which generates one automatically | An llms.txt file you upload to Webflow |
| Redirects | Redirection, or the SEO plugin | Webflow's 301 redirect settings, imported as a CSV |
| HubSpot tracking code and form capture | The HubSpot WordPress plugin | HubSpot's Webflow app, or a custom code snippet in the site head |
| Contact forms into HubSpot | Contact Form 7 or Gravity Forms | HubSpot forms placed with HubSpot's embed code |
| Cookie consent | Cookiebot or CookieYes | The consent tool's Google Tag Manager template |
| Google tag and Tag Manager | Site Kit or a Tag Manager plugin | One Google Tag Manager container in Webflow's custom code |
| Caching and image compression | WP Rocket or Smush | Webflow's hosting, plus images compressed before upload |
The HubSpot row does the most damage when it's missed, because HubSpot's form capture depends on it. HubSpot's collected-forms tool needs its tracking code on the page, or the HubSpot WordPress plugin. On Webflow, neither exists until someone adds the code, and without it HubSpot can't track visits or capture non-HubSpot forms.
We place HubSpot forms with HubSpot's embed code on every build, because HubSpot's Webflow app gave us trouble. The app averaged 2.8 out of 5 from 79 reviews on HubSpot's marketplace when we checked in September 2026.
Why do WordPress to Webflow migrations lose leads?
WordPress to Webflow migrations lose leads in four places, and none of them shows up in a rankings report. Ads keep pointing at old URLs, forms lose their hidden fields, pages go missing from the inventory, and launch day breaks what nobody tested.
Ads keep pointing at the old URLs. Paid campaigns, email templates and social profiles all link to the old site. Google's guide to auto-tagging says the GCLID has to reach the final landing page for conversions to be tracked. We point every ad's final URL at its new page before cutover, so no paid click depends on a redirect to get there.
Forms come back without their plumbing. A rebuilt form keeps its visible fields because someone can see them. The hidden ones survive only if someone listed them. After one of our launches, the post-launch tracking audit found the demo form had no hidden gclid field.
The HR compliance SaaS team turned down an embedded calendar on the demo page. A booking made there couldn't be tied back to paid activity. The form stayed as the first step, with the calendar after it.
Pages go missing from the inventory. Thank-you pages, old campaign pages and partner pages rarely show up in a sitemap export. The cybersecurity SaaS found three live thank-you pages eight days before launch, and a set of campaign pages the day after it. Those campaign pages ended up redirected to the homepage.
Launch day breaks the obvious things. At launch, one form loaded empty, three buttons had no links and /demo returned a 404. That was the cybersecurity SaaS, and all three were dealt with the same day because someone clicked through the live site straight away.
What is the three-ledger check?
The three-ledger check is a launch test for the three systems that keep a record of your site: Google, your CRM and your ad platforms. The guides we read test the first and give the other two a line or two.
| Ledger | What it records | What a migration breaks | The launch-day test |
|---|---|---|---|
| URLs, links, titles and descriptions | Unmapped URLs, lost metadata and internal links to old addresses | Crawl the old URL list and confirm every URL lands on a live page | |
| Your CRM | Form fields, lead source and routing | Missing tracking code, missing hidden fields and broken routing | Submit every form, then check the contact's source and owner in HubSpot |
| Your ad platforms | Tags, conversion actions and click IDs | Ads still pointing at old URLs, tags nobody rebuilt and consent that blocks everything | Open each ad's final URL with ?gclid=TeSter-123 and confirm the value reaches the page |
The gclid test comes from Google's own auto-tagging check. Add gclid=TeSter-123 to each ad's final URL, load it, and check the value is still there once the page loads. The CRM test is the same one that opens our LinkedIn ads conversion checklist.
What should a WordPress to Webflow migration checklist include?
A WordPress to Webflow migration checklist should cover all three ledgers, from the inventory before the build to the first 30 days after launch. We sign off a launch only when every blocker is ticked and every other item is either ticked or deferred in writing.
1. Before the build
2. Google's ledger
3. Your CRM's ledger
4. Your ad platforms' ledger
5. Launch week
6. The first 30 days
How long does a WordPress to Webflow migration take?
A WordPress to Webflow migration for a B2B SaaS marketing site takes eight to twelve weeks. Design sign-off sets the pace more than the content move does. On the cybersecurity SaaS, the whole blog moved in the second and third weeks of the build.
On the HR compliance SaaS, a crawl of 485 URLs came down to 439 unique ones, and 411 redirects went live on launch day. The build took seven and a half weeks, and a seven-day window at the end covered about 70 migration tasks.
The cybersecurity SaaS went live 70 days after kickoff, with 51 days of development and a 275-rule redirect map that included 35 wildcard rules. Launch slipped about three weeks past the first plan. Sections added after design sign-off, a font kit tied to one person's account and a Webflow plan that couldn't build components each cost days.
Google then needs a few weeks or more to show a medium-sized site's new URLs, according to its site move guidance.
How much does a WordPress to Webflow migration cost?
In the UK, published prices for a Webflow build from finished designs start at about £10,000, and design-and-build projects start between £15,000 and £25,000. We checked those prices on each agency's own site in September 2026 for our comparison of UK Webflow agencies for B2B SaaS.
Migration work moves the price more than the number of pages does. A blog of 323 posts or a map of 400 redirects adds days that a ten-page site never needs. Ask for the design, the content move, the redirect map and the tracking rebuild to appear as named lines in the quote.
Our own projects start from £15,000 at a fixed price.
Should you hire a Webflow migration agency or do it yourself?
Do it yourself if the site is small, keeps its current design, runs no paid media and sends its forms to an inbox. Hire help when the move comes with a redesign, or involves paid traffic, HubSpot routing or a blog of over a hundred posts.
Three questions separate agencies that protect pipeline from agencies that protect rankings. Ask who rebuilds the tracking and tests it on launch day. Ask to see the redirect map as a spreadsheet before cutover, and ask how they check that paid clicks still carry their gclid after launch.
Our WordPress to Webflow migration service is built around those three answers. One senior team handles strategy, copy, design, the Webflow build, the redirect map, tracking and HubSpot forms, at one fixed price. The standard plan is eight weeks for a marketing site, and larger migrations are planned week by week.
We run paid media for B2B SaaS teams, so we build every site for the traffic that will land on it. The three-ledger check runs before any launch is announced, and the same team can keep your campaigns running into the new site afterwards.
Why a WordPress to Webflow migration is a pipeline project
Rankings get the attention in a migration because they show up in a week. The tracking gaps can take a quarter to surface, as paid pipeline nobody can explain. Treat the new site as a pipeline project from the first crawl, and run the three-ledger check before anyone announces it.
