Webflow to WordPress migration service

A move from Webflow to WordPress is not a copy. Webflow's help center describes two exports: each CMS Collection as a CSV file, and, on a paid Workspace plan, the site's HTML, CSS, JavaScript and images as a ZIP file. Neither is a site WordPress can import. WordPress's own Import screen lists no importer for a CSV file or for Webflow.

So this service is your content carried across and your design rebuilt. We bring each Collection into WordPress from its CSV, build the pages again, copy every image off Webflow's addresses, and redirect each old address to its new one.

Who it is for, and who it is not

It fits when all of these are true:

• you have decided to leave Webflow, and the site will be WordPress afterward
• you do not want to rebuild the pages and bring the Collections across yourself
• people reach the site from search results and from links on other sites, and you want each old address to keep leading somewhere

A move is not always needed. Some things can be changed where the site is.

• The trouble is who can edit. Webflow has a content editor role. Its help says content editors "can update site copy, media, and CMS content without changing design". If small text changes wait on one designer, that role may be the fix.
• The trouble is addresses that changed, or old links that break. Webflow has 301 redirects of its own, under Site settings, then Publishing. Its help says they need a paid Site plan, or a Workspace on a paid Workspace plan.
• The site is not found in search. That is search work, and it is done where the site is: see Webflow SEO. A move does not fix it by itself.
• You want the files on a server of your own. On a paid Workspace plan, Webflow's code export gives you the site's code to "host it anywhere you like". It leaves out CMS content, and forms and site search do not work in it, so this suits a site that has none of those.
• Nobody will look after a WordPress site. Webflow's help describes its hosting as "a completely managed solution for site hosting". On WordPress you choose the hosting, and someone has to keep the site updated and backed up: the WordPress maintenance checklist shows what that involves. If the Webflow site does what you need, staying is a reasonable choice.

And it is not this service in these cases.

• The site is small and has few Collections. You can move it yourself with how to migrate from Webflow to WordPress.
• You want a different look. This service rebuilds the design you have. A new one is design and development.
• The site is already WordPress, and only its hosting is changing. That is a copy with a fixed price: see WordPress migration.
• The site is on something other than Webflow. See the migrations page. If you do not know what a site is built with, the platform detector reads it from outside.

What you get

• A written list before you decide. What Webflow exports from your site, what has to be rebuilt, and each Collection, form and animation named.
• A fixed quote in writing. The assessment that comes before it is free, and you owe nothing after it.
• Your pages in WordPress, with your content in them. Collections are brought in from Webflow's CSV files, static pages are built again, and the design is rebuilt to match what you have.
• Images that live on your own site. Every image and file is copied into WordPress, so nothing is left loading from Webflow.
• Old addresses that still lead somewhere. A page that can keep its address keeps it. Every other old address is redirected, and the redirects are checked before the domain is changed.
• A new site you have seen before your visitors do. It is built on a staging copy while your Webflow site stays live. The domain is changed only after you have looked at it.

What moves, and what is rebuilt

What Webflow exports is stated here from its help center as of October 2026.

Code export and your plan

Webflow says code export is for paid Workspace plans, and that "Site plans do not include the ability to export your site's code". A Site plan is what lets a site be published to your own domain. A Workspace plan is a separate thing, so a site can be live on a paid Site plan and still have no code export.

You do not need to change plans for the move. With the export, the design is rebuilt from its CSS. Without it, the design is rebuilt from the live pages. The CSV export of a Collection is a different feature, in the CMS panel.

Webflow's list of what the exported code leaves out includes CMS content, Ecommerce content, form processing and past form submissions, site search, password protection, localized content and code components. So the code export is not the whole of a site that uses any of those, on any plan.

What happens to images kept on Webflow

Webflow's help says a file uploaded to the Assets panel or to a Collection field is delivered through Webflow's content delivery network. A Collection's CSV gives each image and file as a Webflow-hosted address, not as a file. In Webflow's words, those addresses "point back to the site you exported the Collection from. If you delete that site, those assets and links break, including images in rich text fields."

So a WordPress site that was filled from the CSV and left alone would still be showing images from Webflow, and would lose them when the Webflow site was deleted.

We copy every image and file into the WordPress Media Library and point each page and post at the new copy. The images folder in the code export holds the images from the Assets panel only, so the images in Collections are fetched from the addresses in the CSV. Before the domain is changed, the new site is checked for anything still loading from Webflow. Keep the Webflow site in your account until that check has passed.

What happens to your old addresses

Search engines and other sites link to your Webflow addresses. Each one has to lead somewhere on the new site.

Webflow gives a Collection URL that matches the Collection's name and lets you change it, so we work from the addresses your site answers at, not from the defaults. A page that can keep its address keeps it. Every other old address is redirected to its new page.

Webflow's help says what happens to an old address with no redirect: the visitor is "led to a 404 page".

Redirects you made in Webflow are carried over too. They are under Site settings, then Publishing, then 301 redirects, and Webflow exports them as a CSV file. Once the domain points at the new site, Webflow no longer answers for those addresses. The redirects are made on the WordPress site, and they are checked before the domain is changed.

How it works

What we need from you to start

For the assessment, the form asks for your name, an email address for the reply, where the site is now, where you want it, roughly how big it is, and its address if you can share it. In the message, say:

• how many static pages and Collections the site has, and roughly how many items are in each Collection
• whether it has a store, forms, or more than one language
• whether your Workspace is on a paid plan, if you know
• which animations the site could not do without
• when you would like to move

We use these details to reply to you about this request, and for nothing else.

For the move itself:

• A way into the Webflow site that you give and take away. We never ask for your Webflow password. We come in through the guest role Webflow has for agencies: a Workspace owner or admin goes to Team, then Users, then "Agency or Freelancer Guests", and clicks "Invite guest". Webflow says the host keeps ownership and the guest joins for free. Its help says a guest must hold a Freelancer or Agency Workspace plan, and we hold an Agency Workspace. When the move is done, you remove us with "Remove from Workspace".
• The WordPress hosting, bought by you. You add us as a user on the new site, from the "Add New User" screen in WordPress.
• Your Webflow Site plan, kept running until the new site is live on your domain.
• Someone who can sign in where the domain is registered. The DNS records are changed there.

What it does not cover

• Hosting and Webflow's fees. You buy the hosting for the WordPress site. Your Webflow plans are yours to cancel. Webflow says that canceling a Site plan removes the custom domains and unpublishes the site, and that "Webflow purchases are nonrefundable".
• Email. Mailboxes are not moved, and there is nothing of yours to move: Webflow says it does not provide email hosting.
• New design work. The service rebuilds the design you have. A new look is a separate job: see design and development.
• Looking after the site afterwards. Updates, backups and monitoring are a care plan. See WordPress maintenance, or WooCommerce maintenance for a store.

Moves from other platforms are on the migrations page, among them Framer to WordPress.

Before you ask: do it yourself, or check first

Each of these is free to use.

• How to migrate from Webflow to WordPress. The whole move by hand, step by step, and where it goes wrong.
• How to migrate a website without losing SEO. What Google and Bing document about a move.
• WordPress migration cost. What moves the price of a change of platform, and what a quote should say. Hold ours against it.
• Website migration checklist. The order of work before, during and after the switch.
• Redirect map builder and redirect checker. The first turns a list of old and new addresses into redirect rules. The second shows where an old address leads now, hop by hop.
• Moving a WordPress site or changing platform. Every page we have on the subject.