Migrate Webflow to WordPress: Complete CMS and Design Handoff

Webflow is genuinely excellent at what it does. The Designer canvas gives you visual control that traditional themes can't match, the CMS is polished, and the exported code is clean. What Webflow struggles with — and what pushes most teams toward migrating — is total cost of ownership at scale, editorial workflow for non-designer teammates, and the plugin gap. On cost: Webflow's Site plans start at $18/month per site for basic hosting, and the paid CMS plans and Ecommerce plans compound quickly. A mid-sized business site with a CMS and light commerce runs $50-$70/month. The same site on WordPress with quality managed hosting (Kinsta, WP Engine) runs $30-$50/month, and on unmanaged hosting (Hostinger, DigitalOcean) runs $5-$15/month. Over three years, the delta is real money. On workflow: editors who aren't designers find the Webflow Editor limiting. Adding a new section requires the Designer, which requires a designer seat. Adding a plugin-style feature (advanced newsletter signup, membership gating, WooCommerce-style products) requires custom code inside Webflow that always feels like a workaround. WordPress collapses both problems: editors get the block editor, features get plugins.

Everything visual carries over: layouts, typography, colors, spacing, breakpoints, animations, interactions, hover states, form styling, and image lazy-loading. The WordPress theme enqueues Webflow's `webflow.js` runtime and its compiled stylesheet, which is what makes all of the above work. CMS collections carry over as WordPress custom post types. Each collection you had in Webflow becomes a CPT registered in the theme's `functions.php`; each item becomes a real WordPress post; each collection field (plain text, rich text, image, reference, option, date, number) maps to a WordPress custom field. Collection Pages become `single-<cpt>.php` templates, and Collection List pages become `archive-<cpt>.php` templates. What needs rewiring is anything that talked to Webflow's servers rather than living purely in the compiled output: forms (rewired to WPForms or Contact Form 7), members-only content (rewired to a WordPress membership plugin), and Ecommerce checkout (rewired to WooCommerce). These are all straightforward substitutions but they are not automatic.

Do these four things in Webflow before exporting. First, audit your interactions and delete anything that's set up but not used — the exported JavaScript will be lighter if the interaction library is minimal. Second, verify that every CMS collection has all its fields filled in for the items you want to migrate; missing fields become empty custom fields in WordPress, which is uglier than not having the field at all. Third, publish the site to your Webflow subdomain and use the browser to verify every page works — if it's broken in Webflow, it will be broken after migration too. Fourth, decide whether you want the migration to include your entire CMS or just the design shell; both are supported, but the second is faster. Export code from Project Settings → Export Code. The export is a ZIP containing HTML files, CSS, JavaScript, and images. Upload this ZIP to AI to Wordpress.

The pipeline identifies Webflow from characteristic markers in the exported code (the `.w-` class prefixes, `webflow.js`, and Webflow's data attributes on interactive elements) and applies Webflow-specific patches. A headless Chromium walks the exported HTML, extracts the shared header and footer into `header.php` and `footer.php`, maps each page to a WordPress template, and generates a `functions.php` that registers navigation menus, image sizes, and — critically — the custom post types corresponding to your Webflow collections. Collections need special handling: the pipeline reads Webflow's Collection Pages, extracts the template layout, and generates a `single-<cpt>.php` template that renders the same layout using WordPress's `get_field()` (or ACF-compatible) API. Individual items from the collection are seeded as WordPress posts during the migration; new items added later through wp-admin render through the same template automatically. Before you pay, the theme boots inside a WordPress Playground instance in your browser. Click through every page, every collection item, every form, every interaction. If anything looks wrong, fix it in the Webflow source and rerun. If everything looks right, pay €17 and download the theme ZIP.

Provision WordPress on any host. Upload the theme via Appearance → Themes → Add New → Upload, activate it, and set the home page under Settings → Reading. Recreate the navigation in Appearance → Menus using the labels from your Webflow design and assign to the primary menu location. If your Webflow project had CMS collections, populate the corresponding CPT with an initial batch of items (the pipeline seeds real posts from your Webflow exports). Editors then update items from wp-admin the same way they update any other post. If you used Advanced Custom Fields (ACF) in the theme, install the ACF plugin; the theme's field groups will be registered automatically. For forms, install WPForms, drop the shortcode onto the migrated page, and route submissions to the same email or CRM as before. For analytics, install MonsterInsights or Fathom. For SEO, install Rank Math and enable XML sitemaps — the theme already emits sensible meta tags per template, so the plugin is doing post-level editing rather than baseline SEO.

This is the part that tends to worry Webflow customers the most, and it's the part that works best in practice. Each Webflow collection becomes a WordPress custom post type. Each collection item becomes a WordPress post inside that CPT. Each field on the collection becomes a custom field on the post. Editors interact with these posts through wp-admin like any other WordPress content — same list view, same edit screen, same permissions model. If you previously used Webflow's Editor for content updates, you're now using the WordPress editor, which is more powerful and doesn't require a paid Webflow seat per editor. Collection Pages (the templates that render a single item) become `single-<cpt>.php` files in the theme. The template layout is preserved verbatim from Webflow, and field values are pulled through WordPress's `get_post_meta()` (or ACF's `get_field()`) API. Adding a new field later means adding a meta box or ACF field and updating the template — the same workflow any WordPress developer would use.

The URL structure of the WordPress build matches your Webflow routes one-for-one. Collection item URLs (`/blog/{slug}`, `/case-studies/{slug}`) match Webflow's slug structure exactly. That means, in the common case, every inbound link continues to resolve without a redirect. When you're also moving from a `webflow.io` subdomain to a custom domain, install Redirection, generate a CSV of `old_url,new_url` pairs, and import in a single shot. Submit the new sitemap in Search Console within 24 hours and request indexing for the ten highest-traffic pages. In our data, small sites re-index inside a week and larger sites inside two to three weeks. One Webflow-specific detail: Webflow's built-in SEO panel populates `<title>` and `<meta name="description">` at build time, and those tags are read out of the exported HTML and re-emitted in the WordPress theme. Install Rank Math after activation and you'll be able to edit them per-post from wp-admin.

Every Webflow-to-WordPress migration we've watched play out has the same second-order effect: the marketing team stops asking the designer for help. Copy edits happen in wp-admin. New landing pages get spun up from block templates. New product features get added via plugins in minutes rather than custom code in days. The designer, freed from being a copy-edit bottleneck, goes back to doing design work. That single change compounds. Publishing frequency roughly doubles inside a quarter. Landing page tests happen weekly instead of monthly. Case studies get added the week the customer sends them. And because the design itself survives the migration untouched, none of this comes at a visual cost — your Webflow site continues to look like your Webflow site, it just gets published from wp-admin now.