WordPress to Webflow migration: how to move posts, custom fields and URLs, and when not to

The short answer

A WordPress to Webflow migration is a rebuild plus a content import. Webflow has no official WordPress importer: its help center says "there's no automated way to convert a site from another platform into Webflow" (Webflow Help), and its WordPress guide tells you to export WordPress's XML, convert it to CSV and import that into a CMS Collection (Webflow Help). You rebuild the theme as Webflow pages and templates, and plugins don't come with you.

Rankings carry over when each WordPress URL either stays the same or gets a 301 in Webflow. The catch is structural: Webflow always puts CMS items under a Collection folder, such as /blog/my-post, so a WordPress blog whose posts sit at the root (/my-post/) needs one redirect per post, and Webflow recommends staying under 1,000 redirects.

Most blogs fit on Webflow Premium: USD 25 a month billed yearly for 20,000 CMS items and 40 Collections. Don't move a blog bigger than that, a WooCommerce store with thousands of products, or a site whose workflow depends on plugins Webflow can't replace.

Prices are in US dollars, before tax, read on webflow.com and the other vendors' pages on 17 October 2026.

What Webflow costs after the 2026 plan change

Webflow merged its CMS and Business plans into Premium on 13 May 2026. Existing sites switched at their first renewal on or after 29 June 2026; sites in Freelancer and Agency Workspaces switch on or after 16 November 2026 (Webflow Help). What a migrated WordPress site would buy today:

Source: Webflow pricing. Bandwidth beyond 50 GB is an add-on, from USD 20 a month for 100 GB. Our Webflow pricing 2026 guide works through renewals and add-ons, and the Webflow pricing calculator prices your own site with seats and locales.

Seats change the comparison with WordPress more than plans do. A blog edited by three people costs USD 25 + 15 + 15 = USD 55 a month on Webflow, USD 660 a year. Self-hosted WordPress doesn't charge per user, and hosting starts low: WordPress.com Personal costs USD 4 a month billed yearly and allows plugins on every paid plan (WordPress.com pricing). Our Webflow vs WordPress comparison covers editing, SEO and speed side by side.

On speed, the field data leans Webflow's way. In September 2026, 80.2% of Webflow sites in the United States passed all three Core Web Vitals on mobile, against 62.0% of WordPress sites (HTTP Archive technology report). That describes the sites on each platform, not yours: a lean WordPress theme can pass, and our website platform speed report shows the numbers by country.

Getting content out of WordPress

For most sites the cleanest path is a CSV per Webflow Collection, built from WP All Export or a script, because you control the columns: title, slug, body HTML, excerpt, featured image URL, category slugs, author slug, publish date, SEO title and meta description. Your SEO plugin stores each post's custom title and description as custom fields, so export those columns too; otherwise Webflow will fall back to the template's pattern.

Importing into the Webflow CMS

The rules from Webflow's CSV import guide:

• 4 MB per file. Split a large blog into several CSVs; how many items you can import depends on the plan.
• Rich text goes in as HTML, and Webflow "may clean up embeds to remove elements, classes, and attributes it doesn't support".
• Image fields take a URL and Webflow fetches the file, but imported images "don't get responsive image variants (srcset and sizes)". Resize them first.
• Files can't be imported: "No data maps to the file field".
• References match by name or custom slug, so import Categories and Authors before Posts.
• Locales: you can import to all locales or only the current one.
• 60 fields per Collection in the API schema (Webflow Developers); the Data API creates up to 100 items per request if you script the import instead (Webflow Developers).

Mapping custom fields (ACF) to Webflow fields

Source: the field table in Webflow's CSV import guide. Repeaters and flexible-content fields are where most of the modelling time goes: decide early whether each becomes its own Collection.

What doesn't carry over

• Plugins. Each one is replaced by a Webflow feature, a Webflow Marketplace app, custom code or nothing. List them all, with what each actually does on the site.
• Shortcodes and page-builder layouts. Shortcodes import as literal text such as [gallery ids="12,15"]. Page-builder pages keep their layout in the builder's own data, so those pages are rebuilt in the Designer. Search the export for [ before importing.
• Forms. Rebuild them in Webflow. Submissions are unlimited on paid site plans, and file uploads need Premium or Ecommerce Plus and above, at up to 10 MB per file (Webflow Help). Export past entries from your form plugin first.
• Memberships. Webflow sunset its User Accounts feature on 29 January 2026 and points customers to Outseta and Memberstack (Webflow Help). A members-only WordPress site needs one of those, or should stay.
• WooCommerce. Webflow Ecommerce tops out at 15,000 items, products, variants and categories combined, on its most expensive plan. Its product import takes a 4 MB CSV (Webflow Help). Subscriptions, complex shipping rules and large catalogs are better served by staying or by Shopify.
• Comments. They're in the XML, but Webflow's plans don't list visitor comments; its "comment" features are for reviewers of the design. Keep comments through a third-party embed, or retire them.
• Multilingual plugins. WPML or Polylang content maps to Webflow Localize, at USD 9 to 29 per locale a month. Localized URLs need Localize Advanced, and Webflow redirects "won't apply to localized slugs or subdirectories", so each language needs its own rules.

Keeping your rankings: URLs, redirects and SEO settings

Map WordPress URLs to Webflow URLs

Five Webflow rules decide whether those redirects fire (Webflow Help):

1. Redirects need a paid site plan and live in Site settings, Publishing, 301 redirects.
2. Old paths must escape % - & * ( ) = _ + ? with a %. That's why /my-post is written /my%-post.
3. "Older redirects are tried first", so add specific rules before broad patterns.
4. A path that still has a published page or CMS item can't be redirected until that page is drafted, deleted or renamed.
5. A CSV import, up to 16 MB, replaces every existing redirect (Webflow Help), and Webflow recommends 1,000 rules at most.

Trailing slashes are the quiet difference. WordPress URLs end in /, Webflow's don't: on the Webflow-hosted sites we tested on 17 October 2026, a URL with a trailing slash answered with a 301 to the version without it. Webflow doesn't document this, so test it on your staging domain. It's also why we generate one rule per old URL instead of clever patterns for WordPress sites: a capture group like (.*) can swallow the final slash, or match nothing after it, and send a post to the wrong page. If you do use a pattern, test it against real old URLs with their trailing slash.

Our redirect map generator matches the WordPress sitemap against the Webflow staging sitemap and exports the CSV for Webflow's importer.

Carry over the SEO settings

• Titles and descriptions: set them per page, and for each Collection template as a pattern built from fields (Webflow Help). Map your SEO plugin's custom title and description to plain-text fields and use those fields in the pattern, so each post keeps its own.
• Canonical: set the global canonical URL in Site settings, SEO, without the trailing slash (Webflow Help).
• Sitemap: Webflow generates /sitemap.xml automatically, or you can paste a custom one (Webflow Help). Exclude thin pages with the per-page and per-item indexing toggles.
• Structured data: each page and Collection template has a schema markup field, but reference, multi-reference and multi-image fields can't be used in it (Webflow Help).
• Search Console: on the same domain there's no Change of Address; Google says that tool is only for moves "from one domain or subdomain to another". Submit the new sitemap, watch the Pages report, and keep redirects "generally at least 1 year" (Google Search Central).

Our website migration SEO checklist covers launch day and the 90 days after it.

When not to move to Webflow

If WordPress's problem is speed or maintenance and you'd rather keep its editor, WordPress to Astro explains how to keep WordPress as a headless CMS behind a fast front end.

Cost and effort by site size

Running costs come from Webflow pricing billed yearly, before bandwidth add-ons and localization. The move prices are what each provider publishes as a starting point, not quotes. Our website migration cost guide has more providers and what pushes a quote up.

Step by step

1. Inventory: crawl the site, download every WordPress sitemap and export 12 months of landing pages and linked pages from Search Console.
2. Decide the content model: one Collection per post type, plus Categories, Tags and Authors; map every custom field using the table above.
3. Export: WP All Export or a script to CSV, one file per Collection, under 4 MB each; download the media library.
4. Build in Webflow: global styles, components, static pages and Collection templates, on the webflow.io staging domain.
5. Import: Categories and Authors first, then Posts; check item counts, images and a sample of bodies for leftover shortcodes.
6. Redirects: build the map, import it as one CSV, then test every old URL on staging.
7. SEO and tracking: title and description patterns, canonical, sitemap, schema, analytics and consent.
8. Launch: lower the DNS TTL in advance, point the domain, submit the sitemap, and watch 404s and clicks by page for 90 days. Keep the WordPress install offline but intact until then.

What to do next

Export your WordPress sitemap and run it through the redirect map generator: the number of URLs that change tells you whether Webflow is a good fit before you spend anything. If you'd like Dardo to plan or run the move, see our Webflow development service.