Most agencies sell you the destination. We start with where you already are.

Walk into almost any WordPress to Webflow migration pitch and you hear the same things. Webflow is easier to use. Easier to publish. Easier to design. Your team will love it. All true. And all about the platform you are moving to.

Here is what gets skipped. The website you already have. The traffic it earns. The backlinks pointing at it. The redirects quietly doing their job. The meta tags and schema someone set up years ago. That is the part that decides whether your migration is smooth or a mess, and it is the part most people ignore until it is too late.

We do it the other way around. Before we open Webflow, we take a step back and prep everything you already have. Across the roughly 12 WordPress to Webflow migrations we have run, including Transfr at 250 pages and Team Cymru at around 500 static pages plus thousands of dynamic ones, that prep is the single biggest reason they landed clean.

This is Part 1 of our complete guide to migrating from WordPress to Webflow. It covers the work nobody sells you and everybody needs: prepping your current site so the build has something solid to stand on. Skip it and you meet it again later, as Search Console errors, lost rankings, and missing content. Do it first and the build is almost boring.

A migration is a replatform, not a move

Start here, because it changes everything that follows.

When you move a WordPress site to a new host, the site comes with you. Same theme, same plugins, same database. When you move to Webflow, almost none of that travels. Webflow has no plugins, no PHP, no WordPress database. Your content has to be pulled out, reshaped, and rebuilt inside a different structure.

Webflow's own official migration checklist says it plainly. Before anything else, you "evaluate and document your website's full functionality, content, structure, and design needs" and "inventory all content types, plugins, theme customizations, and integrations." That is not busywork. That is the project taking its real shape.

So the first question is not "how do we build this." It is "what do we actually have." You cannot rebuild what you have not counted.

Step 1: Audit what your site already has, before you touch Webflow

This is where the migration is won. Not in Webflow. In your current site.

Most teams migrate straight into Webflow because they can. They are excited about the new platform, so they rush to rebuild in it and skip the prep. That is the single biggest mistake in a migration, and it is why rankings drop and content goes missing. So before we open the Designer, we take inventory of everything your current site has earned.

Start with your analytics. Which pages drive the most traffic, and why. What visitors click, and what they ignore. This tells you which pages are doing real work, so you protect them instead of treating every URL as equal.

Audit your backlinks. The pages other sites link to are the ones carrying your authority. Map every page that earns backlinks, and every page that sends them. If links were lost somewhere along the way, find them, and where it makes sense, plan to recreate the pages that earned them.

Capture every piece of SEO work already done. Redirects already in place. Meta titles and descriptions. Schema markup. Years of on-page work live on your WordPress site, and none of it travels on its own. Document all of it so it gets replicated exactly, not rebuilt from memory and quietly lost.

Lock your URL structure. Pull every current URL and plan to preserve the exact structure wherever possible. The fewer URLs change, the less can break.

As you go, make one call for every item: does it become a static page or a CMS Collection in Webflow? Webflow's own checklist tells planners to note exactly that, "whether a piece of content will be a static page or part of a CMS Collection." Your homepage, about, and service pages are static. Your blog posts, case studies, and team members are Collections. And anything that no longer earns traffic or conversions does not get rebuilt at all. You redirect it and leave it behind. A migration is the best chance you will get to ship a smaller, sharper site.

The one document the whole migration runs on

For Transfr, all of this lived in a single Google Sheet that became the source of truth for the entire move. A script inside the sheet pulled every URL on the site automatically, so nothing got missed by hand. Around it, we mapped everything else the migration needed:

  • Every current URL on the site
  • Every redirect already running
  • Every page earning backlinks, and every page sending them
  • The full CMS map: each WordPress custom post type matched to its new Webflow CMS Collection
  • Every new URL, plus a separate tab for any new redirects we need to create

By the time that sheet is finished, the migration is basically decided. The build just executes it. That is what prep actually means. Not a vague checklist, a real document that maps your whole site before anyone opens Webflow.

Step 2: Map the plugin and feature gaps

Here is the trap that sinks more migrations than any other. Teams assume their plugins have Webflow equivalents. Most do not, at least not the way they expect.

WordPress runs on plugins. Webflow does not have them. Functionality that lived in a plugin becomes a native Webflow feature, a built-in integration, or a third-party app, and sometimes it becomes a rebuild. You need to know which before you scope the work.

WordPress (plugin or feature)Webflow equivalentPlanning noteYoast / Rank Math SEONative SEO settings (meta titles, descriptions, auto sitemap, canonical)Built in. Export your current meta first so nothing is lost.Contact Form 7 / Gravity FormsNative Webflow forms, or an integration like HubSpotNative forms cover most needs. For CRM logic, plan the HubSpot forms connection up front.WooCommerceWebflow EcommerceFine for a standard catalog. Audit custom checkout, subscriptions, and plugins before you commit.Membership plugins (MemberPress, etc.)Memberstack or Outseta (third-party apps)Webflow retired native User Accounts. Plan a third-party tool, and know member data does not migrate.Media library / DAMWebflow Assets, or a DAM app like BynderInventory total media size now. Large libraries need a plan, not a drag and drop.Page builders (Elementor, Divi)The Webflow DesignerNo import. Page-builder layouts are rebuilt by hand. Budget for it.

One gap deserves its own line, because the date is fixed and the data is unforgiving. Webflow sunset its native User Accounts feature on January 29, 2026. If your WordPress site gates content behind logins, you cannot rebuild that with a native Webflow feature anymore. You plan for a third-party tool like Memberstack or Outseta, and you accept that existing member accounts do not transfer automatically. That is a migration of its own, inside the migration. Find it in planning, not at launch.

Step 3: Plan how your content actually gets across

A five-page brochure site and a thousand-post blog are not the same project. Your master sheet tells you which one you have. Now you plan how each kind of content travels, because the path is different for each. Here is how we actually do it.

Redirects and sitemaps go in as a file. The URL and redirect map you built in Step 1 imports straight into Webflow through an XML file. That is how you carry your structure across without hand-entering hundreds of redirects one at a time.

Blog posts and CMS content get exported, then cleaned. This is the tricky part. If your WordPress site was built with Elementor or another page builder, exporting your content drags along a mess of code and junk div elements. So we run it through a WordPress export tool, for example the free Exporter for Webflow plugin, to get a clean file of your posts and CMS content. Then we clean that file with AI before it goes into Webflow. Done right, you keep everything: meta titles, meta descriptions, URLs, the content itself, and the images inside it. For very large libraries, past roughly 10,000 items, that content moves through Webflow's CMS API rather than a single upload.

Static pages are often faster to rebuild by hand. Your homepage and design-led pages usually carry so much page-builder markup that exporting them causes more problems than it solves. Often the cleanest path is to bring the real content across and rebuild the page properly in the Designer, using the same Webflow development best practices we follow on any new build. There is no importer that recreates a design-led page for you, and anyone who tells you there is a one-click way to move a whole WordPress site is selling you the export step and leaving out the rebuild.

Step 4: Set timeline and budget expectations honestly

This is where you protect the relationship with your CEO. Vague numbers create broken promises. So here is how we talk about it.

Timeline and cost are driven by one thing: scope. The size of your inventory and how much you redesign along the way. As rough planning bands, drawn from the moves we and other agencies run:

  • A small marketing site with a light content set is typically a matter of a few weeks.
  • A mid-size B2B or SaaS site with a real blog and several templates usually runs closer to a couple of months.
  • A full redesign plus migration, where you are not just moving the site but rethinking it as a modern SaaS website, runs longer still.

We are deliberately not quoting a precise dollar figure or a fixed week count here, because the specific numbers floating around migration blogs do not survive scrutiny. The honest answer is a range that depends on your inventory, and the only way to tighten it is to do Steps 1 through 3 first. That is the whole reason planning comes before a quote.

The planning mistakes that blow up migrations

Almost every migration disaster traces back to the same root: prepping the platform you are moving to instead of the site you already have.

  • Migrating straight into Webflow. The big one. Teams get excited about the new platform and rush to rebuild in it, skipping the prep on the old site, its content, and its assets. Everything below flows from this.
  • No analytics or backlink audit. Treating every URL as equal, then losing the few pages that carried most of your traffic and authority.
  • Not capturing existing SEO work. Redirects, meta tags, and schema left behind on WordPress instead of replicated on Webflow.
  • Assuming plugins map one to one. They do not. The gap analysis in Step 2 is not optional.
  • Forgetting the membership cliff. Member data does not migrate, and the native feature is gone. Plan the replacement early.
  • Trying to export static pages. Wasting days fighting page-builder markup to do something a clean rebuild does faster.

Skip the prep and you do not avoid the work. You just meet it after launch, when it is far more expensive:

  • Search Console fills with errors.
  • On-page SEO breaks across the site.
  • Content, files, and images you used to have go missing.
  • Analytics craters on pages that used to perform, usually because one important URL got missed.

Not one of these is a Webflow problem. Every one is a prep problem. Which is good news, because prep is the part you fully control.

The limits, and how we plan around them

No honest guide pretends the move is frictionless. Here is what to plan around.

  • Manual rebuild is real work. Static pages and page-builder layouts get rebuilt, not imported. We scope that time openly instead of pretending a tool erases it.
  • Memberships need a third-party plan. With native User Accounts gone, gated content means Memberstack or Outseta and a separate member-data plan. We flag this in the first audit.
  • Large media and large catalogs need sizing. Big libraries and complex stores are not drag and drop. We size them against your inventory before quoting.
  • Imported content needs a cleanup pass. Rich text and shortcodes do not always survive a clean export. We budget review time per Collection.

These are not reasons to stay on WordPress. They are the reasons planning exists. Every one is manageable when you find it now instead of at launch.

Plan a WordPress to Webflow migration: FAQ

How do I start planning a WordPress to Webflow migration?

Start with your current site, not Webflow. Audit your analytics to find the pages that drive traffic, map your backlinks, and document every redirect, meta tag, and schema markup already in place. We pull all of it into one master sheet that scripts every URL and maps your CMS structure before any design work begins. Prepping what you already have is what keeps the migration clean.

Can I import my WordPress site into Webflow automatically?

Partly. Your redirects and sitemap import through an XML file, and blog posts and CMS content can be exported with a WordPress export tool, cleaned up, then imported into Webflow Collections. But static, design-led pages such as your homepage are rebuilt by hand in the Webflow Designer. There is no official one-click importer that recreates a full WordPress site, so be wary of anyone who promises one.

What happens to my WordPress plugins in Webflow?

They do not transfer. Webflow has no plugins. Each plugin's job becomes a native Webflow feature, a built-in integration, or a third-party app. SEO and forms are largely native, media can use an app like Bynder, and memberships move to Memberstack or Outseta since Webflow retired its native User Accounts on January 29, 2026.

How long does a WordPress to Webflow migration take?

It depends entirely on scope. A small marketing site can be a few weeks, while a content-heavy B2B site or a full redesign runs longer. The size of your content inventory and how much you redesign are the two biggest factors, which is why an accurate timeline only comes after the audit.

Before you migrate, talk to us

The build is the part everyone shows off. The prep is the part that decides how it goes.

If you are weighing a move off WordPress, the most useful thing you can do is start with the site you already have, not the one you are moving to. Audit what it earns. Map what it would take to carry every bit of that across. That is exactly the work we do first on every migration, and across roughly 12 of them it is what has kept rankings and content intact through the move.

Want a real read on what yours would take? Talk to us about your migration, and we will look hard at what you already have before we say a word about Webflow.

Next in this series: Part 2, rebuilding your site in Webflow. How your master sheet becomes real Collections, templates, and pages. And when you are ready to go live, our guide to protecting your search rankings during the move covers the redirect and SEO side in full.