# How to Move From WordPress to Webflow

Canonical: https://figment.so/blog/move-from-wordpress-to-webflow

No native importer exists. A free marketplace app moves blog posts, featured images, tags and categories, and everything else (theme, plugins, forms, comments, WooCommerce) is rebuilt by hand. Set 301 redirects before moving DNS.

**Webflow has no one-click WordPress importer, but there are two documented paths: a free marketplace app that reads your live WordPress blog directly, or a manual export-to-CSV route.** Either way only your CMS content comes across. Your theme, plugins, custom PHP, comments and working forms stay behind and need their own plan.

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

Not a native one. Webflow's integration page for WordPress says: "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](https://webflow.com/integrations/webflow-pages-wordpress-plugin)). The manual route it describes is "export XML, convert to CSV, map fields, and create collection structures by hand". Webflow's own copy warns "that workflow breaks down quickly for sites with hundreds or thousands of posts" (same source).

For blog content, 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](https://webflow.com/apps/detail/wp-to-webflow)). It reads a live, publicly accessible WordPress URL directly, with no plugin install, API key or XML/CSV conversion, and generates the matching CMS Collection structure in Webflow ([Webflow](https://webflow.com/integrations/webflow-pages-wordpress-plugin)).

Webflow also publishes a [WordPress migration checklist](https://webflow.com/migrate/wordpress-migration-checklist) that treats planning, content export, design setup, import, redirects and testing as separate phases. It is a useful project outline, not a tool.

## What does the WP to Webflow app bring over?

Its documented scope is four content types: "Posts (including post body content), Images (featured images associated with posts), Tags, Categories" ([Webflow](https://webflow.com/integrations/webflow-pages-wordpress-plugin)). The app is free, with "no initial costs or recurring subscriptions" ([Webflow](https://webflow.com/apps/detail/wp-to-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 plan's CMS item allowance, which differs by plan ([Webflow pricing](https://webflow.com/pricing)), so count your posts before you pick a plan.

| Content | Comes across via WP to Webflow app | Notes |
| --- | --- | --- |
| Blog posts (body content) | Yes | Becomes a CMS Collection item |
| Featured images | Yes | Only the featured image per post, not every image inside the post body |
| Tags and categories | Yes | Collection structure auto-generated |
| Static pages | No | Rebuild manually in the Designer |
| Custom fields (ACF, Pods, Meta Box) | No | Explicitly out of scope; add matching CMS fields by hand |
| Custom post types | No | Explicitly out of scope |
| Site design / theme | No | Listed explicitly as "site design" in the app's exclusion list |
| Plugin functionality (forms, SEO plugins, etc.) | No | Each plugin's job needs a Webflow-native or third-party replacement |
| WooCommerce products | No | Webflow's own Ecommerce is a separate setup |
| Comments | No | Not among the app's four listed content types |

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

Start with 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](https://wordpress.org/documentation/article/tools-export-screen/)). WordPress.com's export says what is left out: "Your export file will include your posts, pages, and comments but will not include your theme design, customizations, or plugins," and images are references, not files: "it contains instructions that tell your new site where to find and copy these files" ([WordPress.com](https://wordpress.com/support/export/)).

Webflow has no built-in reader for that WXR file, so in practice:

- **Theme and design.** Nothing carries over. "Site design" is listed as out of scope for the app, and the manual CSV route moves only Collection content, never a layout. Screenshot every page you rely on and plan real design time.
- **Plugins and custom PHP.** Webflow's migration page lists "plugin functionality" as outside the app's scope, with no separate import path documented. 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), so they fall under "plugin functionality." Rebuild each one with Webflow's Form element, a Designer feature that generates the input fields, a submit button and success/error messaging ([Webflow Developer Documentation](https://developers.webflow.com/designer/reference/forms)). Our [forms, bookings and checkout guide](/blog/keep-forms-bookings-and-checkout-working-after-migration) covers testing a rebuilt form before you retire the old one.
- **Comments.** WordPress's export includes comments, but they are not one of the app's four content types, and Webflow has no documented native comment feature to receive them. If a comment thread matters, export it separately from WordPress and choose a third-party embed before you drop the old page.
- **Custom post types and WooCommerce data.** The app reads neither. A custom post type (a portfolio item, a staff profile) needs its own CMS Collection built by hand and filled from a manual CSV export. A WooCommerce store needs its own commerce platform decision, separate from the blog move.

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

Build a full inventory of your current URLs, decide the new address for each, and set a 301 redirect for anything that changes. WordPress permalinks and Webflow's CMS Collection URLs are built differently, so almost no WordPress site moves to Webflow with every URL unchanged. Our [redirects guide](/blog/redirects-when-changing-website-builders) covers building the map and the Webflow-side steps 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 the moment your domain resolves elsewhere, however carefully they were set up.

If your domain also carries email, read [will switching builders break my email](/blog/change-website-builder-without-losing-email) before you touch DNS. A website move and an email move use separate records, and it is easy to break one while fixing the other.

## When does this move not make sense?

Skip it, or 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 by hand is a real project, not an afternoon's import.
- **You run WooCommerce with a real product catalog.** The app does not touch it, and Webflow's Ecommerce is a different system with its own setup, not a 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](https://webflow.com/pricing) 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 it is.** Migrating content is not migrating a layout. If the WordPress theme itself is what you like, this move costs a full redesign in the Designer on either import path.

## What if the import goes wrong?

Running the app or a manual CSV import does not change your live WordPress site, because it only reads from it. If an import has wrong fields, duplicate items or missing images, delete the affected Collection items in Webflow and re-run the import instead of patching entries one by one.

Keep WordPress live and your original XML/CSV exports saved until you have 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.
