Migration guide

Can you migrate WordPress to Webflow?

Last updated: July 2026 · By the Replatform Radar team — specialists in pre-migration CMS content audits

Yes — WordPress to Webflow is a popular move for marketing and brochure sites that want visual, no-code design control and managed hosting. Webflow combines a visual designer with CMS Collections, so you rebuild the site's design in the canvas and re-model content as Collections rather than migrating a database wholesale. It suits small-to-mid content sites well, but Webflow enforces CMS item and plan limits and is less suited to very large or deeply relational content models. Expect to redesign, not just import, and to re-create anything that relied on WordPress plugins.

WordPress is a coupled PHP CMS: content lives in MySQL, layout comes from a theme, and functionality is added through plugins for SEO, forms, and commerce. Content is stored as HTML with Gutenberg blocks and shortcodes, and custom fields commonly come from ACF. It is flexible and self-hosted, but it also carries plugin maintenance, security patching, and hosting overhead.

Webflow is a visual website builder with a built-in CMS. Designers build layouts directly on the canvas with production-grade HTML/CSS output, and structured content is stored in CMS Collections rendered through Collection templates. Migrating from WordPress means recreating the design in Webflow, defining Collections that mirror your post types, and importing content — typically via CSV or the Webflow API — while working within Webflow's per-site CMS item and plan limits.

In your report — not a generic checklist

The WordPress → Webflow detail, catered to your site

A pre-migration scan produces a report tailored to this exact transfer, covering the parts that decide whether the project goes smoothly:

How WordPress and Webflow compare across the dimensions that matter for a migration
The field-mapping table — what each WordPress construct becomes in Webflow
The WordPress to Webflow-specific gotchas that silently cause data loss, broken links, and ranking drops
Realistic timeline and cost drivers for this migration
Your own site’s findings scored against all of it

Scan my site for this migration →

In depth

What a WordPress to Webflow project actually looks like

A realistic shape for this specific transfer. Phases, the work inside each, and the failures that recur on this exact platform pair. Spans assume a mid-size estate; large or multi-site estates run longer.

Fit check and content auditWeeks 1-2
- Count posts, pages and custom-post-type items against Webflow's CMS item limits before anything else - this number decides whether the project is viable as scoped.
- Inventory plugin-driven functionality (forms, membership, commerce, SEO, custom fields) and mark each native, third-party, or dropped.
- Identify thin, stale and duplicate content to retire rather than rebuild; Webflow's limits make pruning a design constraint rather than a nicety.
- Export ACF and custom-field structures and check how well they flatten - deeply relational models are where this migration gets expensive.
Design rebuildWeeks 2-6
- Rebuild the theme visually in the Webflow Designer; there is no import path for a WordPress theme, so budget this as a design project.
- Model Collections against the pruned content structure, keeping reference and multi-reference fields inside Webflow's per-collection limits.
- Build the components and interactions that plugins previously supplied, or choose third-party embeds where no native equivalent exists.
Content migrationWeeks 5-8
- Export WordPress content to CSV per Collection; rich text and image fields need careful formatting to survive import cleanly.
- Re-upload media and re-link assets - WordPress upload paths are not preserved, so embedded image references must be rewritten.
- Re-create reference relationships by matching slugs, and verify multi-reference fields imported completely rather than partially.
Launch and redirectsWeeks 8-10
- Map every WordPress permalink to its new Webflow path; permalink structures almost always change, and this is the main SEO risk.
- Configure Webflow's 301 redirects and verify them against the URLs that actually receive traffic and inbound links.
- Re-submit sitemaps and watch coverage errors closely through the first month.

Pre-launch verification checklist

The checks worth running before DNS moves. Each one maps to a failure we see repeatedly on WordPress to Webflow projects.

Total CMS items sit comfortably under the plan ceiling, with headroom for a year of publishing.
Every WordPress permalink with traffic or inbound links has a verified 301 to a live Webflow URL.
Rich text imported without broken markup, and embedded images point at Webflow assets rather than surviving /wp-content/ paths.
Forms submit end to end, including notifications and any CRM or email-tool handoff a plugin used to perform.
Per-page SEO fields - title, description, Open Graph, canonical - are populated; these moved from an SEO plugin into page settings and are easy to leave blank.
Structured data the SEO plugin emitted automatically is re-created deliberately, because Webflow does not add it for you.
The RSS feed and any subscriber integrations still function, if the blog had an audience.

Risk register

Risk	Likelihood	Mitigation
Content volume exceeds Webflow CMS limits after work has started	High	Count items and check plan ceilings in week one; prune or reconsider the platform before design work begins.
Structured data and SEO metadata lost along with the SEO plugin	High	Treat schema and meta fields as explicit build items per template rather than post-launch cleanup.
Relational content models flattened badly	Medium	Prototype the two most complex Collections with real data before committing to the full model.
Permalink changes costing organic traffic	High	Build the redirect map from analytics and inbound-link exports, and verify with a status-code sweep after launch.

FAQ

WordPress to Webflow: frequently asked questions

Can I move my WordPress blog to Webflow without losing SEO?

Yes, if you map every old URL to its new Webflow path with 301 redirects, re-enter title tags and meta descriptions per item, and rebuild your sitemap. WordPress permalinks rarely match Webflow's structure, so a redirect plan is the single most important step for preserving rankings.

Is there a WordPress to Webflow importer?

Partly. Webflow imports CMS content via CSV, and its API supports scripted imports, but there is no one-click migrator that moves themes, plugins, and content together. In practice you export WordPress content, reshape it to match your Collections, and rebuild the design manually in the Designer.

Does Webflow have a limit on how much content I can migrate?

Yes. Webflow caps CMS items per site based on your plan — 2,000 on the CMS plan and up to 10,000 on Business — so very large WordPress sites may not fit without upgrading, splitting content, or choosing another platform. Check your post/page count against the target plan's limit before committing.

What happens to my WordPress plugins in Webflow?

They do not transfer. Webflow has no plugin system, so plugin functionality must be replaced: native Webflow forms for Contact Form 7, per-item SEO settings for Yoast, Webflow Ecommerce or an external service for WooCommerce, and embeds or Webflow Apps for the rest.