How to Migrate Webflow to WordPress

To migrate from Webflow to WordPress, set up WordPress on a host, rebuild your design with a WordPress theme, move your CMS content, copy your images off Webflow, keep or redirect your old URLs, then point your domain at WordPress. Webflow has no WordPress export, so the content moves either as a CSV file you import, through a migration tool, or by hand. Your pages, forms and interactions don't move at all: you rebuild them. Cancel your Webflow plan last.

We checked every Webflow, WordPress, Google and third-party detail below on 13 November 2026, on their own websites.

Which route fits you

• A few pages and posts: rebuild the pages and copy the posts by hand. It costs nothing.
• A blog with dozens or hundreds of posts: use a CSV import plugin or Blog Porter for the posts, and rebuild the rest of the site yourself.
• You want to keep designing in Webflow: a converter such as Udesly turns a Webflow design into a WordPress theme. It's a different job from moving existing content.
• A large site, a store, or no time: hire an agency or migration service, and ask exactly what they move.

The Webflow Pages plugin is not a migration

Webflow has its own WordPress plugin, Webflow Pages, and it's easy to mistake for a migration tool. It does the opposite. Webflow says it lets you build pages in Webflow, then serve them on your WordPress site. The pages still live in Webflow, so you keep paying for and publishing the Webflow site.

It's useful if you want Webflow pages inside an existing WordPress site. It's no use if you're leaving Webflow. Its WordPress.org listing also says it hasn't been tested with the latest three major releases of WordPress, and Webflow says it isn't compatible with Webflow Ecommerce.

Every way to move Webflow to WordPress, compared

Some details behind the table:

• The CSV export. Webflow exports each Collection as a CSV file. Rich text comes out as HTML, reference fields as plain text, multi-reference fields as comma-separated text, and images as links to files Webflow hosts. WordPress has no built-in CSV importer for posts, so you need a plugin. WP All Import imports CSV files into posts, but downloading images into the Media Library and importing custom fields are Pro features.
• The code export. Webflow can export your site's HTML, CSS and JavaScript, on paid Workspace plans only. CMS content isn't included, Collection lists come out empty, and forms and site search stop working.
• Udesly. Its process starts with exporting your site's code from Webflow and uploading it for conversion into a theme. You then manage the content in WordPress. The page doesn't say it imports your existing Collection items, so plan to move those separately.
• Migration services. Some cover more than a blog. LitExtension, for example, says its Webflow to WordPress service moves products, customers and orders into WooCommerce as well as CMS items. Ask any service which Collections, images, URLs and redirects are included.
• Blog Porter. A WordPress plugin that reads your public blog listing page and imports each post it finds. What Blog Porter moves from Webflow has the details. It moves blog posts only, so you still rebuild the rest of the site.

How to export your Webflow blog compares the content routes in more depth, field by field.

What moves and what you rebuild

Whatever route you choose, some things only exist in Webflow:

• Content that can move: CMS Collection items (blog posts, authors, categories, case studies), their images, and the text on your static pages.
• What you rebuild: the design, static page layouts, navigation, forms, interactions and animations, site search, components, and any Ecommerce or user account features. Webflow's code export leaves out CMS, User Accounts and Ecommerce content, and forms and site search don't work on exported sites.

Step by step: Webflow to WordPress

Each step has a short reason. Where one of our other guides goes deeper, the step links to it.

Before you start

1. List what you're moving. Go through the Pages panel and the CMS panel and write down every static page, Collection, form, interaction, integration and piece of custom code. Mark each one "move" or "rebuild". Why: you can plan the rebuild now, instead of finding the gaps after launch.
2. Save a copy of your Webflow sitemap. Open yoursite.com/sitemap.xml and save it. If it's missing, turn on Auto-generate sitemap under Site settings → SEO and publish. Why: after launch you'll test these old URLs one by one, and the file disappears when the domain moves.
3. Export your Webflow redirects. If you've set any up, export them as a CSV file from Site settings → Publishing → 301 redirects. Why: they stop working when your domain leaves Webflow, and old links that rely on them break.
4. Download your form submissions. In Site settings → Forms, open each form's submissions and click Export all. Webflow says files people uploaded come out as URLs in the CSV, so save any you need. Why: the submissions live in Webflow, not in your inbox, and you lose access when the site goes.
5. Export every Collection as a CSV backup. In the CMS panel, open each Collection and click Export. The file includes archived items, and on a site with more than one language it only includes the locale you're viewing. Why: even if a tool moves your posts, a spreadsheet of every item is a cheap backup and a checklist to compare against.

Build the WordPress site

1. Choose hosting and install WordPress. Pick a host and install WordPress, either with the host's installer or by following WordPress's installation guide. WordPress recommends PHP 8.3 or later, MySQL 8.0 or MariaDB 10.11 or later, and HTTPS. Blog Porter needs WordPress 6.4 and PHP 7.4 or later. Build on the host's temporary address, and tick Discourage search engines from indexing this site under Settings → Reading until launch. Why: your Webflow site stays live while you build, and visitors and Google don't find a half-finished copy.
2. Pick a theme and rebuild the design. Your Webflow design doesn't transfer. Choose a theme from the theme directory or elsewhere. With a block theme, the Site Editor lets you design the header, footer, templates and styles with blocks. If you'd rather keep designing in Webflow and convert the result, look at a converter such as Udesly. Why: the theme decides how every post and page looks, so settle it before you check the content.
3. Rebuild your static pages, menus and forms. Recreate your home, about and contact pages, and give each the same slug it had on Webflow. Rebuild forms with a WordPress form plugin and send a test submission. Interactions and animations need rebuilding too, with your theme, blocks or custom code. Why: none of these come across in a CSV export or a blog migration, and matching slugs means fewer redirects.

Move the blog and other CMS content

1. Choose how you'll move the posts. For a handful, copy them. For more, use a CSV import plugin or Blog Porter. How to export your Webflow blog covers each route, what it misses, and how to map the CSV columns. Why: the right method depends on how many posts you have and how much image work you'll accept.
2. If you use the CSV, map the fields. Map Name to the post title, Slug to the post slug, your rich text field to the content, your main image field to the featured image, and a date column to the publish date. Webflow keeps Created On, Updated On and Published On dates for each item, so pick one deliberately. Filter out archived items first, unless you want them back. Why: a wrong mapping is easier to fix in the spreadsheet than in hundreds of posts.
3. If you use Blog Porter, check your listing page first. Install the plugin and enter the public page that lists your posts, such as yoursite.com/blog. It reads the posts in that page's Collection list, whether they live at /blog/post-name or under their own path such as /post/post-name, and follows Webflow's Next button. A Collection list shows up to 100 items unless pagination is on, so turn it on for a bigger blog and remove any display limit or filter. A "load more" button that uses a script only shows the first batch. Why: Blog Porter only reads posts that the listing shows and anyone can open, and the free analysis lets you compare its count with your Collection before you pay.
4. Check your publish dates before importing. Blog Porter reads each post's date from article structured data (JSON-LD) or, without it, from a date shown on the post page in an element whose class name includes date. Without either, posts are dated the day you import them. On a paid plan, you can add schema markup to your Collection page and bind its date to your post's date field. Why: fixing dates before the import is quicker than fixing them post by post afterwards.
5. Import the posts. Blog Porter shows every post it found and the exact price before you pay: $0.20 per post, minimum 5 posts, paid once, so a 100-post blog costs $20. It imports the title, the main rich text field, the slug, the date, and available inline and featured images, in resumable batches. It also imports the author and tags when your structured data includes them, and copies each post's meta description into Yoast SEO, Rank Math or SEOPress. Run it again later and posts it already imported are left out by default. Why: checking the post count against your Webflow Collection before you pay tells you nothing is missing.
6. Get every image off Webflow's servers. Search your WordPress posts for website-files.com, the address Webflow's image CDN used on every blog we checked. Every result still loads at least one image from Webflow. Blog Porter downloads available images into your Media Library and lets you retry any that fail. After a CSV import, use an image import feature such as WP All Import Pro's, or a plugin like Auto Upload Images, which imports external images when you save a post. Why: Webflow says its hosted images break if you delete the site, including images in rich text.
7. Check categories, authors and other references. Webflow categories and authors are usually separate Collections linked by reference fields. In a CSV they arrive as text, which you map to WordPress categories and users. Blog Porter imports a category when the post page links to its category page, such as /blog-categories/news. Posts with several categories shown in a nested Collection list, or templates that don't link to them, need categories added in WordPress. Give each category the same slug as its Webflow item, and use bulk editing to add one to many posts. Why: category pages and archives are part of how readers and search engines find older posts.
8. Move your other Collections. Case studies, team members or job listings don't fit WordPress posts neatly. Import them as pages, or as a custom post type that a plugin or your theme provides. Why: putting them in your blog would mix them into your post archive and feed.
9. Spot-check a sample of posts. Compare a few old and new posts side by side: title, date, author, formatting, embeds and links. Webflow rich text can hold code embeds and component instances, and Blog Porter removes forms and scripts from post content, so look closely at posts that used them. Why: problems are easier to fix before visitors and Google arrive.

Keep your URLs

1. Set your permalinks to match Webflow. Every Webflow post lives under its Collection URL, such as /blog/post-name or /post/post-name. Under Settings → Permalinks, choose a custom structure with the same path, such as /blog/%postname%/. Keep your Webflow URLs in WordPress covers folders, category bases and trailing slashes. Why: if the URLs match, old links and search results keep working with no redirect map to maintain.
2. Redirect every URL that changes. Google recommends permanent server-side redirects (301 or 308) straight to the new URL, kept for at least a year, and warns against sending lots of old URLs to an unrelated page such as your home page. A plugin such as Redirection handles 301s, regular expressions and CSV imports, and logs 404 errors. Add the Webflow redirects you exported in step 3 as well. Why: without redirects, old links and search results lead to "not found" pages.

Launch

1. Lower your DNS TTL a week ahead. Google suggests lowering the TTL to a few hours at least a week before the move. Why: when you switch, visitors reach WordPress sooner instead of a cached Webflow address.
2. Point your domain at WordPress. Your domain's DNS records live with your registrar or DNS host, not in Webflow. A domain bought inside Webflow is bought from IONOS, so its records are in your IONOS account. Replace the A and CNAME records that point at Webflow with the ones your WordPress host gives you. If you change nameservers instead, copy your email (MX) and other records to the new DNS host first. Why: until the domain points at WordPress, visitors still see the Webflow site.
3. Open the site to search engines. Untick Discourage search engines from indexing this site under Settings → Reading. While it's ticked, WordPress turns off its built-in sitemap. Check that the site loads over HTTPS. Why: while it's ticked, WordPress asks search engines not to index the site.

After launch

1. Test your old URLs. Open the URLs from the sitemap you saved in step 2. Each one should load the same page or post, or redirect to it in a single step. Why: it's the quickest way to catch a missed redirect or a permalink that doesn't match.
2. Tell Google. In Search Console, submit your new sitemap. WordPress has one at /wp-sitemap.xml, unless an SEO plugin replaces it. If your URLs changed, Google's site move guide suggests submitting the old sitemap too. If your domain changed, use the Change of Address tool. Why: the sitemaps help Google find your new URLs and the redirects from your old ones.
3. Watch Search Console for a few weeks. Look for pages Google can't find or index, and fix the old URLs behind them. Why: Google says to expect temporary fluctuation in rankings during a move, so a dip isn't always a problem, but a growing list of errors is.
4. Cancel Webflow last. Wait until every page, post, image, form and redirect checks out, and a website-files.com search of your WordPress posts comes back empty. Webflow says canceling a paid Site plan removes your custom domains and unpublishes the site, including the staging address, at the end of the billing period, and that Webflow purchases are nonrefundable. Why: Webflow is your fallback copy, and some of your images may still live there.

Frequently asked questions

Does Webflow have a WordPress export?

No. Webflow exports each CMS Collection as a CSV file, and on paid Workspace plans it exports your site's code without the CMS content. WordPress can't import either one as it is. You need an import plugin, a migration tool or a developer.

Is the Webflow Pages plugin a way to migrate?

No. It shows pages you build in Webflow on a WordPress site, so the Webflow site has to stay. Without a paid Site plan, its WordPress.org listing says you're limited to 2 pages and 50 CMS items, with a "Made in Webflow" badge.

Can I turn my Webflow design into a WordPress theme?

Not directly. Webflow's code export gives you static HTML, CSS and JavaScript, not a theme. A converter such as Udesly builds a theme from that export. Otherwise you recreate the design with a WordPress theme, which is also a chance to fix anything you didn't like.

Will I lose my Google rankings?

Keeping your URLs, or redirecting each one that changes, is what protects them. If only the hosting changes, Google treats it as a move without URL changes. Where URLs do change, map each old one to its new equivalent and use permanent redirects. Even then, Google says to expect rankings to fluctuate for a while during a move.

What happens to my images on Webflow's CDN?

They keep loading from Webflow until you delete the site, then they break. That includes images inside rich text. Copy each one into your WordPress Media Library and update the posts that use it, either with an import tool or by hand.

Can I keep my Webflow URLs?

Yes, if you keep the same domain and set your WordPress permalinks to your Collection URL, such as /blog/%postname%/. The only difference is usually the final slash, and WordPress redirects the version without it. Keep your Webflow URLs in WordPress has the details.

What happens to my Webflow forms and submissions?

Forms don't move, and Webflow says forms don't work on an exported site either. Rebuild them with a WordPress form plugin, and download your old submissions as CSV files before you cancel.

Do Webflow interactions and animations transfer?

No. Webflow says interactions rely on its own JavaScript files. Rebuild the ones you need with your theme, a block or animation plugin, or custom code.

Can my site stay online during the migration?

Yes. Build WordPress on your host's temporary address while Webflow keeps serving your domain. Visitors only see WordPress once you change the DNS records.

How much does it cost?

WordPress itself is free. You pay for hosting, and for any premium theme or plugins you choose. Moving posts can be free by hand or with the free version of a CSV plugin, while image import needs a paid plugin or tool. Blog Porter costs $0.20 per post, minimum 5 posts, paid once. Agencies quote per project.

When should I cancel my Webflow plan?

After launch, once every page, post, image, form and redirect checks out on WordPress. Cancellation takes effect at the end of your billing period and Webflow purchases are nonrefundable, so time it to your renewal date.

My Webflow site has more than one language. What changes?

A CSV export only includes the locale you're viewing, so export each one. Webflow's 301 redirects don't apply to localized subdirectories such as /es/, so plan their redirects separately. In WordPress, a multilingual plugin links translations together. Blog Porter imports each language's listing page as separate posts and doesn't link them as translations.

Can I move a Webflow Ecommerce store?

Not with a CSV of blog posts or with Blog Porter, which moves posts only. You'd rebuild the store with a WordPress store plugin such as WooCommerce and move products, customers and orders with a tool or service built for stores.

Every Webflow guide, in order

1. How to migrate Webflow to WordPress: this page, every route and every step.
2. How to export your Webflow blog: the CSV export, field by field, the API and Blog Porter.
3. Keep your Webflow blog URLs in WordPress: match your Collection URL or redirect your old links.