You're seeing Seahawk's original 2015 colors and logo. Thousands of WordPress sites maintained since.

Book a call Free rebuild
Home/Development/How to Migrate From Webflow to WordPress: Step-by-Step Guide
Guide

How to Migrate From Webflow to WordPress: Step-by-Step Guide

Published November 11, 2025 9 min read

Webflow is a capable visual builder, and plenty of businesses build their first serious site on it. Some later move from Webflow to WordPress because they want to choose their own hosting, use a wider range of plugins and integrations, run a store on WooCommerce, or hand the site to a team that already works in WordPress. Whatever the reason, the move goes smoothly when you know what comes across and what you rebuild.

Webflow has no export to WordPress. You can export your CMS content as CSV files and import them, but static pages, interactions, forms, and ecommerce checkout are rebuilt. This guide covers what transfers, every step in order, how to map redirects so you keep your rankings, how to switch DNS without downtime, and when to hand the job off.

What transfers from Webflow and what you rebuild

ContentHow it moves to WordPress
CMS Collections (blog posts, case studies, team members)Exported as CSV, imported into posts or custom post types
Images and files in CollectionsExported as Webflow-hosted URLs, then imported into the media library
Static pages (home, about, services)Rebuilt in WordPress; text is copied across
Design, layout, and stylesRebuilt with a block theme or page builder
Interactions and animationsRebuilt or simplified; they do not import
FormsRebuilt with a forms plugin; past submissions exported as CSV
Ecommerce productsExported as CSV, mapped into WooCommerce
Checkout, payments, orders, and customer accountsSet up again in WooCommerce
301 redirects already set in WebflowExported as CSV and added to your WordPress redirect list
SEO titles and descriptionsCopied from a crawl of the live site, or from CSV columns, into your SEO plugin

Webflow also offers a code export on some plans. It gives you static HTML, CSS, and JavaScript, which is handy as a reference for your designer, but it is not a migration path: Webflow's code export documentation notes that CMS content, ecommerce, and form processing are not part of it.

Before you start

  • Keep your Webflow site plan active until the WordPress site is live and checked. Exported image URLs still point at Webflow's servers, and Webflow's import and export documentation warns they stop working if the site is deleted.
  • Crawl the live site with an SEO crawler and save every URL with its title, meta description, H1, and status code. This list becomes your redirect map and your checklist.
  • Inventory everything that is not content: forms and where their notifications go, custom code embeds, analytics and tag manager snippets, site search, password-protected pages, localized versions, and any third-party integrations.
  • Check where your domain is registered and who can change its DNS records. You need that access on launch day.
  • Choose WordPress hosting, a theme, and a page builder (if any) before you start, so you are not making platform decisions halfway through the build.

How to migrate from Webflow to WordPress, step by step

Step 1: Set up WordPress on staging

Install WordPress on your new host at a staging or temporary address. Your Webflow site stays live and untouched while you work. In Settings, Reading, tick "Discourage search engines from indexing this site" so the staging copy stays out of Google until launch.

Step 2: Match your URL structure

Webflow puts Collection items under the Collection's slug, so a blog post usually lives at /blog/post-name. Before importing, set Settings, Permalinks to a custom structure such as /blog/%postname%/ so your post URLs stay the same. If you have several Collections, create a custom post type for each one with the same slug. Every URL you keep is a redirect you do not need.

Step 3: Export your CMS Collections

In the Webflow Designer, open the CMS panel, choose a Collection, and use Export to download it as CSV. Repeat for each Collection. A few details matter when you import:

  • Rich text fields export as HTML, so formatting and links come across.
  • Images and files export as URLs on Webflow's servers, not as files.
  • Multi-reference fields export as comma-separated text, which you can map to categories, tags, or related posts.
  • A full Collection export includes archived items, so filter out anything you do not want published.
  • If you use Webflow Localization, the export only covers the locale you are viewing. Export each language separately.

Step 4: Import the CSV files into WordPress

Use a CSV import plugin that lets you map columns to WordPress fields. Map the name to the post title, the slug to the post slug, the rich text field to the content, the main image to the featured image, and the published date to the post date. Map any extra fields to custom fields so templates can display them. Run a small test import of five or ten items first, check the result, then import the rest.

Step 5: Bring images into the media library

Images inside imported posts still load from Webflow. Most import plugins can download featured images during import; for images inside the post content, use a plugin that pulls external images into the media library and rewrites the links. Check a sample of posts afterward and confirm every image URL now uses your own domain.

Step 6: Rebuild your static pages

Webflow pages built in the Designer do not export to WordPress, so each one is rebuilt. Start with your global styles: colors, fonts, spacing, and button styles in the theme. Build the header, footer, and repeated sections as reusable patterns, then rebuild each page and copy its text across. Rebuild the pages that bring in the most traffic and leads first, and check each one on mobile as you go.

Step 7: Rebuild interactions, forms, and integrations

Webflow interactions run on Webflow's own scripts and have no WordPress equivalent to import into. Recreate the ones that matter with CSS, block animation settings, or your page builder's motion options, and drop the purely decorative ones if they slow the page. Rebuild each form with a forms plugin, send a test entry, and confirm it reaches the right inbox. Export your past form submissions from Webflow's form settings if you need to keep them. Re-add analytics, tag manager, chat, and any custom code embeds.

Step 8: Move your store, if you have one

Webflow Ecommerce lets you export products, variants, and categories as CSV. The file is laid out for Webflow, so map its columns to WooCommerce fields with the WooCommerce product importer or a mapping plugin, then check prices, variants, stock, and images. Payment gateways, shipping, and tax rules are set up fresh in WooCommerce. Customer passwords cannot move between platforms, so plan an email inviting existing customers to set a new password.

Step 9: Restore SEO details

Install an SEO plugin and copy each page's title and meta description from your crawl. Check headings, image alt text, Open Graph images, and internal links, which should all point to the new WordPress URLs. Add structured data for your business and articles, and confirm the XML sitemap lists the pages you want indexed.

Redirects: keep your Webflow rankings

Any URL that changes needs a 301 redirect from the old address to the new one. Build the list from your crawl, then add three more sources:

  • Existing Webflow redirects. Webflow lets you export your 301 redirects as CSV. Bring them across so older links keep working, and point each one straight at its final page to avoid chains.
  • Collection URLs you renamed. If you change /blog/ to /articles/, one pattern redirect covers every post.
  • Trailing slashes. Webflow URLs usually have no trailing slash and WordPress adds one. WordPress redirects the slashless version on its own, so you only need redirects where the slug itself changes.

Add the redirects with a redirect plugin or at the server level. After launch, run your full list of old URLs against the live site and confirm each returns a single 301 to a working page. Our website migration guide covers redirect mapping and post-launch monitoring in more depth.

Switching DNS without downtime

A site hosted on Webflow uses DNS records that point your domain at Webflow, usually A records for the root domain and a CNAME for www. To launch:

  1. A day or two ahead, lower the TTL on those records so the change spreads quickly.
  2. Remove the staging noindex setting and run a final check of forms, checkout, and redirects on staging.
  3. Replace the Webflow A and CNAME records with the ones your new host gives you. Leave MX and other email records alone, or your mail stops.
  4. Issue an SSL certificate on the new host as soon as the domain resolves there, and confirm the site loads over HTTPS on both the root and www versions.
  5. Unpublish the custom domain in Webflow only after the new site is serving traffic, and keep the Webflow plan until you are sure every image and file has moved.

After the migration

  • Submit the new sitemap in Google Search Console and watch the page indexing and 404 reports for the first few weeks. Our guide on how to get your website on Google walks through those reports.
  • Run a speed test. Rebuilt pages with large images or heavy animation scripts are the usual culprits.
  • Set up updates, backups, and security monitoring. Webflow handled these as a hosted platform; on WordPress, you or your care plan do.
  • Cancel Webflow only when everything is confirmed working.

Do it yourself or get help?

A small Webflow site with a handful of pages and one blog Collection is a realistic DIY project with this guide. Several Collections with references between them, a store, multiple languages, heavy interactions, or a site that brings in most of its leads from search is where a missed redirect or a broken form starts to cost money.

Our WordPress migration services handle the whole move from Webflow: CMS export and import, images, page and design rebuild, forms and integrations, WooCommerce setup, redirects, testing, and DNS cutover, all done by Seahawk's own team. Webflow moves are quoted in Dev Hours, at $79 an hour, after we review your site, and you approve the quote before work starts. Coming from another builder? See our guides to Wix to WordPress and Squarespace to WordPress.

Frequently asked questions

Can you export a Webflow site to WordPress?

Not directly. Webflow can export your CMS Collections as CSV files, which you import into WordPress posts or custom post types, and your ecommerce products as CSV for WooCommerce. Static pages, styles, interactions, and forms do not export in a form WordPress can use, so they are rebuilt with a theme or page builder.

Will moving from Webflow to WordPress hurt my SEO?

It does not have to. Crawl the Webflow site first, keep URLs the same where you can, add a 301 redirect for every URL that changes, bring across your existing Webflow redirects, and copy titles and descriptions into your SEO plugin. Some movement in the first weeks is normal. Lasting drops almost always trace back to missing redirects or noindex left on.

Do Webflow interactions and animations carry over?

No. Interactions run on Webflow's own scripts, and WordPress has nothing to import them into. Recreate the important ones with CSS, your theme's block settings, or a page builder's motion features. It is also a good moment to drop decorative animations that add weight without helping visitors or conversions.

How long does a Webflow to WordPress migration take?

It depends on the number of pages to rebuild, how many Collections you have, and whether there is a store. A small brochure site with a blog can move in a few days of focused work. Several Collections, multiple languages, or Webflow Ecommerce take longer. Keep Webflow live until the new site is tested, so there is no gap.

What happens to my Webflow forms and past submissions?

Forms stop working once the site leaves Webflow, because Webflow processes the submissions. Rebuild each form with a WordPress forms plugin and test that notifications arrive. Before you cancel, export past submissions as CSV from Webflow's form settings, and save any uploaded files separately, since they are stored as Webflow URLs.

How much does it cost to have my Webflow site moved to WordPress?

With WP Services, a Webflow migration is quoted in Dev Hours, at $79 an hour, after we review the site. The quote depends on the number of pages, Collections, interactions, languages, and whether you run a store. You approve it before any work starts. Hosting and premium plugins are separate costs.

WP Services

WordPress services at revolutionary pricing.

Productized WordPress services, from builds to care, delivered by Seahawk and tracked in one app. For the WordPress lovers.