WordPress to Webflow Migration: The 30-Step Checklist and What You Lose Along the Way

Webflow's own help centre is blunt about it: there is no automated way to convert a site from another platform into Webflow, and a migration "will be a rebuild, not a transfer". Your content can be imported. Your theme, plugins, page-builder layouts and URL structure cannot. Most of the risk in a WordPress to Webflow migration sits in that gap.

This guide is the checklist we would run, in order, with every limit taken from Webflow's or WordPress's own documentation in October 2026. If you are still deciding whether to move, our Webflow vs WordPress comparison covers that; this page assumes the decision is made.

There is no converter, only importers

Search for a "WordPress to Webflow converter" and you will find tools that move content, not sites. Webflow's own migration overview says you recreate page layouts, styles, CMS structure and interactions manually, using the old site as a reference. That leaves four ways to get content across.

For a blog of a few hundred posts, the CSV route is usually enough. A scripted import earns its cost when there are several related post types or rich text needs systematic clean-up; our Webflow CMS limits post covers the rate limits.

What you lose along the way

WordPress runs on plugins. Webflow runs on built-in features, apps and custom code. Decide, feature by feature, what replaces each plugin or whether it goes.

The URL row matters most. Webflow item pages follow one pattern, Collection URL then item slug, with at most one dynamic segment and that segment last. A WordPress site set to "Post name" serves posts at the root, so moving to Webflow changes every post URL. Static pages can keep their exact paths; CMS items cannot.

Comments and members are the quiet losses. WordPress's export includes comments and users. Webflow has nowhere native to put either. Webflow ended User Accounts on 29 January 2026 and points customers to Outseta and Memberstack instead.

Shortcodes come across as text. Post content is exported raw, so a gallery or button shortcode arrives as the bracketed code itself. Nothing on the Webflow side runs it.

The URL plan: where rankings are kept or lost

A replatform on the same domain is gentler than a domain move, but losses come from the same place: old URLs that return 404, redirect chains and internal links to retired paths. Dan Taylor's study of 892 domain migrations, published by Search Engine Journal in January 2025, found an average of 523 days for the new domain to match the old one's estimated organic traffic, and 17% had not recovered after 1,000 days. That is a proxy, not a platform-migration benchmark, and domain moves are harsher. Treat it as the downside case.

Four things about Webflow redirects catch most teams out.

Hyphens must be escaped. Webflow requires a % before special characters in the old path, including the hyphen, the underscore, the question mark and the equals sign. A WordPress slug such as /my-post becomes /my%-post in the rule. One invalid rule fails the whole CSV import.

Order is age. Webflow runs redirects oldest first, so specific rules must be added before the wildcards that would otherwise catch them.

Imports overwrite. Uploading a redirect CSV removes every existing redirect on the site. Export first, merge, then import.

The 1,000-rule guidance. Webflow sets no hard limit, but recommends 1,000 rules at most because each one adds to a file browsers download. A blog with 1,500 root-level posts needs 1,500 single rules, half as many again as the guidance, so prune or merge thin posts before the move.

The 30-step checklist

Audit, before anyone opens Webflow.

1. Crawl the live WordPress site and list every URL that returns 200, plus every URL in its sitemaps.
2. Pull landing pages from analytics and Search Console, and mark every URL with organic entrances or backlinks as must-redirect.
3. Export the content from Tools, Export, All content. WordPress produces a WXR file covering posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies and users.
4. List every plugin and what it does on the front end: forms, SEO, search, members, translation, schema, sliders.
5. List custom post types, custom fields and taxonomies. These become Collections and fields.
6. Count items per type against the plan: 20,000 CMS items and 40 Collections on Premium, 50 items on the free Starter plan.
7. Decide what not to move, such as thin tag pages, expired events and attachment pages. Each dropped URL still gets a redirect to its closest live page.

Model and map.

1. Draw the Collection model: Posts, Categories and Authors at minimum, joined by reference fields.
2. Choose Collection URLs, keeping old paths where Webflow allows it.
3. Build the URL map: old URL, new URL, rule, owner, tested yes or no.
4. Group rows into patterns. Use wildcards where a pattern holds and single rules elsewhere, and stay under 1,000.
5. Write down the replacement, or the decision to drop, for comments, members, search and translation.

Content.

1. Convert the WXR file to one CSV per Collection. Rich text makes files large, so split by year to stay under 4 MB each.
2. Import Categories and Authors first, then Posts, so reference fields match by slug.
3. Map the SEO plugin's titles and descriptions to plain text fields, then bind them in Collection page settings.
4. Clean rich text: shortcodes, page-builder markup, inline styles, empty paragraphs.
5. Re-upload important images, because images imported by URL get no responsive variants. Then search rich text for images still served from the old WordPress host.
6. Upload PDFs and other files by hand; file fields do not import from CSV.
7. Take a backup before each import. Webflow offers one at import time and restores from Site settings.

Build and redirects.

1. Rebuild templates and static pages from the old site as a reference.
2. Rebuild forms, notifications and integrations; test each one end to end.
3. Write the redirect CSV with escaped old paths, specific rules before wildcards, and separate rules for any locale folders.
4. Export existing redirects, merge, import, then publish to staging.
5. Test every row of the URL map you can on staging: one 301, landing on a page that returns 200.

Launch.

1. Lower the DNS TTL to the lowest value, typically 30 seconds, at least one full TTL period before the switch.
2. Point the domain: an A record to 198.202.211.1, a CNAME for www to cdn.webflow.com, and the _webflow TXT verification record. SSL is issued once the records point at Webflow.
3. Publish to the live domain and run the URL map against it.
4. Submit the new sitemap in Search Console, update internal links to final URLs, and check that each page's canonical points at itself.

After launch.

1. Keep redirects for at least a year, Google's guidance, and keep the WordPress install offline but intact until the redirect report is clean.
2. Watch Search Console's indexing and top-page traffic weekly, fix 404s as they surface, then restore the TTL.

Moving the blog itself

The blog is where most of the work and most of the traffic sit. Three habits keep it intact.

Import references first. Webflow matches reference fields by converting plain text into a slug, so "Jane Smith" looks for jane-smith. If an author has a custom slug, the match fails silently and the field imports blank. Use the slugs from WordPress, not display names.

Keep the dates. Map the WordPress publish date to its own date field and sort and display by it. Webflow's own created and published dates will be the import date, so every post would otherwise look new.

Keep the slugs. The item slug is the one part of a post URL you control. If the old slug was /my-post/, keep my-post, and the redirect is a one-line change of folder rather than a guess.

What this means for your WordPress to Webflow migration

We build marketing sites in Webflow and applications in Next.js, so we are not neutral about the destination. The checklist is the same whoever runs it. On a marketing site with a few hundred posts, we would expect steps 1 to 12 to decide the outcome; the import itself is the easy part. Our largest Webflow CMS holds over 1,200 items, well inside the Premium plan's 20,000.

Budget the URL map and redirect testing as real work, not a launch-day task. In our four-week marketing-site process we would put both in week one, before design starts. Our marketing website service page explains how we scope a migration build.