NEWAI-native design subscriptions are back
Book a call

WordPress to Webflow migration

WordPress to Webflow, with your rankings intact

Leave plugin updates and developer tickets behind. We rebuild your site in Webflow, move the content into structured collections and protect every URL that ranks.

Plan your migrationWhat moves, what doesn’t
Typical timeline
6 to 8 weeks for a typical SaaS marketing site
Cost
Quoted after the URL inventory
SEO risk
Medium: WordPress and Webflow structure URLs differently
Moves cleanly
Posts, pages, categories, tags and custom fields
Must be rebuilt
Theme and layouts, plugin features, forms

In short

Checked against WordPress and Webflow docs

A WordPress to Webflow migration is a rebuild plus a content move. WordPress exports posts, pages and custom fields as an XML file, which we clean and turn into CSV for Webflow’s CMS import or push through the Webflow API. Themes and plugins don’t carry over, so the design is rebuilt in Webflow and plugin features are replaced. Every old URL gets kept or a one-to-one 301 before launch.

Why teams move

Why teams leave WordPress for Webflow

  1. Marketing can’t ship without engineering

    On most WordPress setups anything beyond body copy needs a developer. With a Webflow design system and CMS, marketers publish landing pages and edit layouts themselves.

  2. Plugin debt

    A few years in, most WordPress sites run a dozen plugins that each need updating, and some conflict. Every one is a security surface and a speed cost. Webflow folds most of that into the platform.

  3. Speed and Core Web Vitals

    Heavy themes and stacked plugins make WordPress slow unless someone manages it. Webflow’s hosting and cleaner output start from a better place.

  4. The design ceiling

    Page builders impose their own design language. For a SaaS company whose site is a big part of the brand, Webflow lets you build exactly what was designed.

Old vs new

WordPress vs Webflow, for this move

WordPressWebflow
UpkeepWordPressCore, theme and plugin updates are yoursWebflowHosting, security and updates handled by Webflow
EditingWordPressBlock editor or a page builder, layout changes often need a developerWebflowVisual editor; marketers change layouts within the design system
Content modelWordPressPosts, pages, custom post types and fieldsWebflowCMS collections with reference fields
RedirectsWordPressUsually a plugin or server configWebflowBuilt in, with wildcard capture groups
Extending itWordPressA huge plugin ecosystemWebflowNative features, apps and custom code

Last updated

Webflow vs WordPress: the full comparison

What moves, what doesn’t

What comes across from WordPress

WordPress exports content, not design. Plan for a rebuild of everything you can see and a careful move of everything you’ve written.

  • Content

    Tools > Export gives an XML file with posts, pages, custom post types, comments, custom fields, categories and tags. We clean it, map it to collections and import it as CSV or through the API.

  • CMS

    Post types become Webflow collections; categories and tags become reference fields. Shortcodes, page-builder markup and fields Webflow can’t hold (like file fields) are cleaned up or rebuilt by hand.

  • SEO

    Titles and descriptions from Yoast or Rank Math are exported and set per page and per collection item. Redirects go into Webflow’s 301 settings, imported from a CSV map.

  • Forms

    Contact Form 7, Gravity Forms and the like are rebuilt as Webflow forms, connected to your CRM or a form tool, and tested end to end.

  • Integrations

    Each plugin is matched to a Webflow feature, an app or a few lines of custom code. Plugins with no equivalent (memberships, complex calculators) are flagged at the audit, not at launch.

  • Animations

    Theme and page-builder effects don’t move. Interactions are rebuilt in Webflow, usually better than before, since they’re designed rather than inherited.

  • Media

    The XML file links to media rather than including it. Images referenced in CMS items import by URL; everything else is pulled from the media library or wp-content and re-uploaded.

Moves over
Exported, imported, then checked by hand
Partly
Some of it imports, the rest is redone
Rebuilt
Nothing to import, we rebuild it
Replaced
Swapped for the new platform’s equivalent

Content model

How WordPress content maps to Webflow

  1. Posts

    Blog posts kept in the WordPress database, written in the block editor and exported as one XML file.

    On WordPress

    Blog posts collection

    A Webflow collection filled from the cleaned export, imported as CSV or through the Webflow API.

    On Webflow

    What you get CMS › Blog Posts

    Author, date, featured image, SEO title and description as fields.

  2. Custom post types

    Extra content types such as case studies and resources, registered by the theme or a plugin.

    On WordPress

    One collection each

    Each type becomes its own Webflow collection, with its fields set up before anything is imported.

    On Webflow

    What you get CMS › Case Studies

  3. Categories and tags

    Taxonomies that group posts, each with an archive page that WordPress generates by itself.

    On WordPress

    Linked collections

    Collections of their own, linked to posts with reference and multi-reference fields.

    On Webflow

    What you get Blog Post › Tags (multi-reference)

  4. ACF and custom fields

    Extra fields on posts and pages, added by Advanced Custom Fields or by the theme’s own code.

    On WordPress

    Typed collection fields

    Collection fields with one type each, such as text, number, date, image or option.

    On Webflow

    What you get Case Study › Industry (option)

  5. Pages

    Pages built in the block editor or a page builder, often carrying shortcodes and inline styles.

    On WordPress

    Static Webflow pages

    Static pages built in the Designer from the design system’s shared components and variables.

    On Webflow

    What you get Pages › Pricing

Process and timeline

How we move a WordPress site to Webflow

Our usual order for a SaaS marketing site with a blog. Bigger libraries and gated content take longer.

  1. Audit and URL inventory

    Week 1

    Crawl every URL, export top pages, rankings and backlinks, and record titles, descriptions and headings for each page. This list decides what must not move.

  2. Redirect map and content model

    Week 1

    Decide every URL’s fate (keep, 301 or retire to its closest page) and map each post type and field to a Webflow collection before anything is designed.

  3. Design system and rebuild

    Weeks 2 to 4

    Build type, colour and spacing variables and reusable components in Webflow, then the page templates and collection pages.

  4. Content migration

    Weeks 4 to 5

    Clean the WordPress export (shortcodes, inline styles, dead embeds), import it as CSV or through the API, then check items and images by hand.

  5. SEO parity and QA

    Weeks 5 to 6

    Set titles, descriptions, alt text and schema, import the 301 map, and test every form, link and redirect on staging.

  6. Launch and watch

    Launch and 4 weeks after

    Launch early in the week, submit the sitemap, then watch 404s, indexing and rankings daily against the baseline.

Full step-by-step guideWordPress to Webflow Migration: How to Rebuild Your Site Without Losing Traffic

SEO safety

The pre-launch checklist for WordPress to Webflow

Rankings are lost in three ways: broken URLs, missing on-page signals and crawl problems. 4 stages, from the first crawl to the weeks after launch, close all three. Tick the checks as you go; your progress stays in this browser.

Stage 1 of 4

Before the build

Know every URL and where it goes before anything is designed.

Stage 2 of 4

During the build

Carry every on-page signal across, page by page.

Stage 3 of 4

Before launch

Real redirects and a clean path for crawlers, ready for the switch.

Stage 4 of 4

After launch

Watch what Google sees in the first weeks and fix it fast.

Free migration planner

Plan your WordPress to Webflow redirects

Enter your site to list every URL, see which keep their path on Webflow and get the 301 redirect map.

What people worry about

What WordPress teams worry about

  1. Will we lose our Google rankings?

    Not if the redirect map and on-page SEO are done before launch. A small dip in week one while Google re-crawls is normal; a dip that keeps going means a redirect gap, which we look for daily.

  2. Will our whole blog history come over?

    Yes. Posts, categories, tags and custom fields come out of the WordPress export and go into collections. Webflow’s Premium plan holds 20,000 CMS items; we check your count at the audit.

  3. What happens to our plugins?

    We list every active plugin at the audit and decide for each: native Webflow feature, an app, custom code or drop it. Anything without a good replacement is raised before you commit.

  4. Does the design have to change?

    WordPress themes don’t convert, so the site is rebuilt either way. You choose: a faithful rebuild of today’s design, or a redesign during the move.

When not to migrate

When to stay on WordPress

  • WooCommerce or a membership plugin is the core of the business. Rebuilding that elsewhere is a bigger project than a website migration.

  • You have tens of thousands of posts and a large editorial team in wp-admin every day.

  • The site is fine and fast, and the real problem is the design. A redesign on WordPress may be enough.

  • You depend on a plugin with no equivalent anywhere else.

Not sure which side you’re on?

If one of these is you, staying on WordPress is probably the better call. We’ll say so on the first call.

Book a call

Cost and time

What to budget for

  • Typical timeline
    6 to 8 weeks
    A typical SaaS marketing site: homepage, product pages, pricing, a few solution pages and a blog. Large libraries or gated content take longer.
    From our WordPress to Webflow guide
  • Typical cost
    Custom
    Price depends on page count, content volume, how much is redesigned and the integrations. We quote after the URL inventory.
    What drives the cost of a migration

FAQ

WordPress to Webflow questions

Adrian

Moving from WordPress to Webflow?

Every URL mapped, the CMS rebuilt, SEO kept. We scope it on a 30-minute call.

Plan your migration
Can Webflow import a WordPress site automatically?

Not the whole site. Webflow’s own guide is export XML, convert it to CSV, import into collections, then rebuild the design and set up redirects. A third-party app can pull posts, featured images, tags and categories, but not pages or custom fields, so most real sites still need a mapped import.

How many CMS items can Webflow hold?

Since Webflow’s May 2026 plan change, the Premium site plan includes 20,000 CMS items and 40 collections. Bigger sites need one of Webflow’s higher plans; we check the fit at the audit.

How do redirects work in Webflow?

In Site settings > Publishing you add 301 redirects one by one or import them as a CSV. Capture groups handle patterns like /blog/(.*). Webflow has no hard limit but recommends staying under about 1,000 rules, so we use patterns where we can.

How long does a WordPress to Webflow migration take?

Six to eight weeks for a typical SaaS marketing site with a blog, including design system, rebuild, content, redirects and QA. Hundreds of posts, complex functionality or gated content add time.

Can we keep WordPress running during the move?

Yes, and you should. The WordPress site stays live until launch day; we build and test Webflow on staging, then switch the domain.

Keep exploring

All migrations

Platform facts checked on . Platforms change their exports and limits; we recheck at the start of every project.

You've reached the end, so now…

Tell us what you’re building.

We’ll help you map the right scope, team, timeline, and next steps.

Book a call