How to Move From WordPress to Webflow

No, Webflow doesn't have a one-click WordPress importer, but it does have a documented path: a free marketplace app that reads your live WordPress blog directly, or a manual export-to-CSV route for everything else. Either way, only your CMS content comes across. Your theme, your plugins, any custom PHP, your comments, and your working forms stay behind and need their own plan. This is what Webflow's own pages say the move includes, what's out of scope, and how to keep your URLs working once you switch.

Does Webflow have an official way to import a WordPress site?

Not a native one. Webflow's own integration page for WordPress says it plainly: "Webflow handles site design, CMS content management, and hosting. But it has no built-in way to pull existing content from a WordPress site" (Webflow). The manual route it describes is "export XML, convert to CSV, map fields, and create collection structures by hand" — workable, but Webflow's own copy warns "that workflow breaks down quickly for sites with hundreds or thousands of posts" (same source).

For blog content specifically, Webflow's Marketplace lists the WP to Webflow app, built by a third-party developer (Eclipse SRL) and reviewed for the marketplace: "Webflow has reviewed this app to ensure high quality site development. We do not endorse or certify these apps" (Webflow). It reads a live, publicly accessible WordPress URL directly — no plugin install, API key, or XML/CSV conversion needed — and generates the matching CMS Collection structure in Webflow automatically (Webflow). Webflow also publishes a general WordPress migration checklist covering planning, content export, design setup, import, redirects, and testing as separate phases — useful as a project outline even though it's not a tool itself.

What does the WP to Webflow app actually bring over?

Its documented scope is four content types: "Posts (including post body content), Images (featured images associated with posts), Tags, Categories" (Webflow). The app is free, with "no initial costs or recurring subscriptions" (Webflow), but it needs a Webflow site on a CMS plan or higher. The app sets no item limit of its own; the ceiling is your Webflow site plan's CMS item allowance, which differs by plan (Webflow pricing, checked September 2026). Count your posts before you pick a plan.

What doesn't come across at all, and what do I do about it?

Start from what WordPress itself exports. Self-hosted WordPress's Tools → Export screen exports your data ("posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies, and users") as an XML file (WordPress.org). WordPress.com's version of that export is explicit about the other half of the picture: "Your export file will include your posts, pages, and comments but will not include your theme design, customizations, or plugins," and even the images are references, not files — "it contains instructions that tell your new site where to find and copy these files" (WordPress.com).

None of that WXR file imports into Webflow directly; Webflow's own page confirms it has no built-in reader for it. In practice:

• Theme and design. Nothing carries over — "site design" is explicitly listed as out of scope for the WP to Webflow app, and the manual CSV route only ever moves Collection content, never a layout. Screenshot every page you rely on and plan real design time before you go further.
• Plugins and custom PHP. Webflow's own migration page lists "plugin functionality" as outside the WP to Webflow app's scope, with no separate import path documented elsewhere for it. Whatever a plugin did — a contact form, a membership gate, a custom checkout step, a page builder's layout logic — becomes a separate decision on the Webflow side: a Webflow-native feature, a JavaScript embed, or a third-party service.
• Forms. These are almost always plugin-driven in WordPress (Contact Form 7, WPForms, Gravity Forms), which puts them under "plugin functionality" — out of the WP to Webflow app's scope. Rebuild each one using Webflow's own Form element, a built-in Designer feature that generates the input fields, a submit button, and success/error messaging automatically (Webflow Developer Documentation). Our forms, bookings and checkout guide covers testing a rebuilt form before you retire the old one.
• Comments. WordPress's own export includes comments, but comments aren't one of the WP to Webflow app's four content types, and Webflow has no documented native comment feature to receive them. If a post's comment thread matters, export it separately from WordPress and decide on a third-party embed before you drop the old page.
• Custom post types and WooCommerce data. Neither is read by the app. A custom post type (a portfolio item, a staff profile) needs its own CMS Collection built by hand and populated from a manual CSV export; a WooCommerce store needs its own commerce platform decision entirely, separate from the blog move.

How do I keep my URLs and rankings after the move?

WordPress permalinks and Webflow's CMS Collection URLs are built differently, so almost no WordPress site moves to Webflow with every URL unchanged. Build a full inventory of your current URLs, decide the exact new address for each one, and set a 301 for anything that changes — our redirects guide covers building that map and the Webflow-side steps for setting the 301s once your Collections exist. Add the 301s in Webflow before you move DNS, so they work from the first minute. WordPress's own redirect settings (a plugin like Redirection, or .htaccess rules) stop applying to any traffic the moment your domain resolves elsewhere, no matter how carefully they were configured on the old side.

If your domain also carries email, read will switching builders break my email before you touch DNS. A website move and an email move are separate records, and it's easy to break one while fixing the other.

When does this move not make sense?

Skip this move, or at least slow down, if any of these apply:

• Your site leans on plugins for core function — membership, complex forms, a page builder, a custom checkout — rather than mostly being a blog. Rebuilding that functionality by hand is a real project, not a one-afternoon import.
• You run WooCommerce with a real product catalog. The WP to Webflow app doesn't touch it, and Webflow's own Ecommerce is a different system with its own setup, not a migration target for existing WooCommerce data.
• You have more content than your Webflow plan's CMS item limit. Compare your post, tag and category count with the CMS item allowance on Webflow's pricing page before you start. A very large archive may need a higher plan, or a decision about which old posts to leave behind.
• You want to keep your design exactly as-is. Migrating content is not migrating a layout. If the WordPress theme itself is the thing you like, this move costs you a full redesign in the Designer regardless of which import path you use.

What if the import goes wrong?

Nothing about running the WP to Webflow app or a manual CSV import changes your live WordPress site — it only reads from it. If an import comes out with the wrong fields, duplicate items, or missing images, delete the affected Collection items in Webflow and re-run the import rather than trying to patch individual entries. Keep WordPress live and your original XML/CSV exports saved until you've checked every migrated post against the original, confirmed images display, and verified your redirects resolve to the correct new page — only then cancel WordPress hosting.

Bottom line: There's no native WordPress-to-Webflow importer. The free WP to Webflow app covers blog posts, images, tags and categories automatically; everything else — plugins, custom PHP, comments, forms, WooCommerce, and the design itself — is a separate, manual rebuild. If the real complaint is WordPress's plugin and maintenance overhead rather than needing Webflow's specific CMS, our guide to moving from WordPress to Figment covers a different kind of destination: a Figma file published directly as a site, with its own tradeoffs.