Migrate WordPress to Webflow: Steps, Costs, SEO, and Common Pitfalls

There's no migrate button. According to Webflow's migration overview, switching is a rebuild, not a transfer. Its guide to switching from WordPress doesn't name an import tool. Instead, it lays out this path: export your WordPress content as XML, convert it to CSV with a converter, import it into CMS Collections, then handle design, redirects, and SEO, and publish at the end. So your text and images move over semi-automatically, while layout and functionality get rebuilt. Our take: For your rankings, the list of your old URLs matters more than any design detail.

How do you migrate WordPress to Webflow step by step?

In six steps, and the order matters: the URL plan comes before the first import, and the launch comes last.

1. Inventory: Record every public URL, for example from your XML sitemap, the list of addresses your site provides to search engines. In Google Search Console, Google's reporting tool for site owners, flag the pages that bring in clicks. Add a list of all your plugins, each with the function you actually use it for.
2. Content model: Decide what becomes a CMS Collection in Webflow, meaning a set of similar items such as blog posts, categories, or authors, and what stays a static page. Your home page, services, or contact page get rebuilt in the Webflow Designer, because the CSV import only fills Collections.
3. Export: Under Tools > Export, WordPress generates an XML file in WXR format, a WordPress flavor of XML. According to the WordPress documentation, it contains posts, pages, custom post types, comments, custom fields, categories, tags, and users. An XML to CSV converter turns it into spreadsheets that you then clean up: one file per Collection. For blog posts, there's a shortcut: the free WP to Webflow app from third-party developer Eclipse SRL in the Webflow Marketplace connects to your live WordPress site and, according to its description, transfers posts, images, categories, and tags into Webflow Collections. It requires a CMS plan, and its description says nothing about SEO fields or redirects. Spot-check the result, especially the slugs, because your redirect list is built on them.
4. Import: According to Webflow's help article on CSV import, each file can be up to 4 MB, and how many items fit in total depends on your Site plan, the Webflow plan for an individual website. Import categories and authors before the posts: Webflow matches reference fields, meaning fields that point to an item in another Collection, by the name or slug of the target item. The slug is the last part of the URL. Separate multiple references with semicolons.
5. Build and redirects: You design the templates for Collection pages and the static pages, and set up a permanent 301 redirect for every changed URL.
6. Launch: Switch the domain, publish, test the old URLs, and submit the new sitemap in Search Console. Don't shut down the old WordPress site until every import is done and every redirect has been checked. Keep a full backup.

How do you avoid losing rankings during the move?

With a complete redirect list: every old URL points directly to its matching new page via a 301. In its guide to site moves with URL changes (updated August 20, 2026), Google recommends permanent, server-side redirects with status code 301 or 308. You should keep them in place for as long as possible, generally at least one year. The key rules from that guide:

• Straight to the destination: no redirect chains, meaning no redirect to an address that itself redirects again.
• Not wholesale to the home page: Google explicitly advises against redirecting many old URLs to a single irrelevant page such as the home page.
• Update internal links: Menus, buttons, and in-text links point to the new URLs, not to old ones that have to redirect first.
• Set canonicals: Every page points to itself with a canonical tag. This tag tells search engines which address is the authoritative one.
• Swap the sitemap: Submit the new sitemap in Search Console and remove the old one.

Some fluctuation happens anyway: Google itself says to expect it while it recrawls and reindexes your site. In Search Console, the reports on sitemaps, indexing, and search queries show you whether traffic is shifting from the old URLs to the new ones.

In Webflow, redirects live under Site settings > Publishing > 301 redirects. According to Webflow's help article on redirects, you need a paid Site plan or a paid Workspace plan (the plan for your team's workspace), and the rules only take effect once you publish. You can redirect entire folders with wildcards: the rule /blog/(.*) with the target /articles/%1 sends every old blog URL to the new address with the same slug. Webflow recommends no more than 1,000 redirects, though there's currently no hard limit.

Which URLs carry over to Webflow, and where do you need redirects?

Static pages can usually keep the same address in Webflow; blog posts can't always. Every Collection item sits inside a folder: the Collection URL forms the folder, and the item's slug follows it, as in /post/my-post (Webflow help on Collections). You choose the folder name yourself. How much work you're facing depends on your permalink structure, the URL scheme set in WordPress under Settings > Permalinks:

Then there are slugs Webflow can't keep as they are. According to Webflow's help on page URLs, Webflow only supports lowercase Latin letters from a to z and numbers in page URLs, and it converts uppercase letters automatically. Old addresses with umlauts like ä or ü, or other special characters, therefore change, and each one needs its own redirect. During acceptance testing, also try old addresses with a trailing slash.

Which pitfalls cost the most in a migration?

These five, because they're easy to miss before launch, and afterwards visitors and Google end up on error pages or half-finished content.

1. A redirect import wipes out all previous ones. Webflow also accepts redirects as a CSV with two columns, old path and new path, up to 16 MB per file. But according to Webflow's help on importing redirects, every new import overwrites all existing redirects. If you upload a second list, the rules from the first one are gone, and every old URL it covered ends up on an error page. So before each import: export, merge, then upload. A single invalid row makes the whole import fail.
2. A page blocks the redirect. If a page still exists at the old path, Webflow says you have to delete it, save it as a draft, or change its slug before you can set up the redirect.
3. Images without responsive variants. With a CSV, you import images by their direct URL. According to the CSV import help linked above, Webflow doesn't create responsive variants for images imported this way, so there are no smaller versions for smartphones. Resize large files to a sensible size before importing, or phones will load the full original. And don't take the old site offline while the import is running: the image URLs have to be reachable.
4. Shortcodes and page builders. According to the WordPress documentation, shortcodes are WordPress-specific codes written in square brackets. Nothing outside WordPress executes them, so in a rich text field (a Collection's body text field) they show up as plain text. Webflow does accept embedded HTML, but according to the import help it may clean it up, removing unsupported elements, classes, and attributes along the way. Search for square brackets before importing and replace galleries, forms, or buttons. Plan pages made with page builders, meaning layout plugins, as a rebuild from the start: the import moves content into fields, not design.
5. Plugins with no equivalent. Forms, comments, shop, member area, multiple languages: the CSV import brings content into Collections, not functionality. Every line on your plugin list needs a replacement in Webflow, an external service, or a conscious decision to drop it. If the contact form is missing on launch day, you lose inquiries. Meta titles and descriptions from your SEO plugin don't move over on their own either. Webflow's guide explicitly lists them as part of the SEO stage, so check whether they show up among the custom fields in your export, and create dedicated fields for them in the Collection.

What does it cost to move from WordPress to Webflow?

Two items: the one-time project and the ongoing Webflow plan. The project gets more expensive the more page types, content, plugin features, and changed URLs you bring along. For context: at blocks&colors, Webflow websites start at around €3,000, and our projects typically take 2 to 8 weeks.

On top of that comes the ongoing Webflow plan. Without a paid plan there are no redirects, and the number of CMS items you can import also depends on the plan. So add up your posts, categories, and authors before you pick a plan on Webflow's pricing page, and compare that with what WordPress costs you today in hosting, maintenance, and plugin licenses.

Our take: Usually, it's not the design that blows the budget but the cleanup: shortcodes, orphaned categories, full-size images, and plugins nobody remembers the purpose of. Each of these questions needs a decision that no converter makes for you. If you do the inventory up front, you get a reliable quote and fewer change orders. You'll find how we approach Webflow projects in our services, and our project for SSI Group is one example of a relaunch.

What does this mean for you?

Before you request quotes or start on your own, clarify five points. With them, the effort can be estimated realistically:

• URL list: all public addresses, their clicks, and their new destination. It drives the redirect effort more than any other number.
• Permalink structure: If your posts sit directly after the domain and there are more than 1,000 of them, you'll exceed Webflow's recommended maximum for redirects. Then it's worth asking which old posts need to move at all, decided by clicks and inbound links.
• Plugin list: one decision per plugin: replace it, solve it externally, or drop it.
• Launch date: not right before a trade show, your peak season, or a campaign, because Google warns of ranking fluctuations while it recrawls the site.
• Ownership: One person owns the redirect list for at least a year and never uploads a new CSV without exporting first.

If you'd rather not tackle the inventory alone, get in touch.