Plan your move from WordPress to Webflow

Move a WordPress marketing site to Webflow without losing pages, posts or search traffic: what moves, what gets rebuilt and the steps in order.

Content export
Posts, categories, tags and images come across with an import app or a CSV. Pages are rebuilt.
Rebuilt in Webflow
The theme, page-builder layouts and anything a plugin adds to the page.
Biggest search risk
WordPress URL patterns, such as dates in post URLs, that Webflow can’t reproduce exactly.
Can stay where it is
A store, membership area or booking tool that works well can stay connected.

Is the move worth it?

Why teams move from WordPress to Webflow

  • Fewer moving parts

    No plugin, theme or core updates to schedule. Webflow hosts the site and maintains the platform.

  • Editors can’t break the layout

    Editors change text, images and CMS items inside a design that stays fixed.

  • Design control without a page builder

    Layouts are built visually with real classes and components, not nested page-builder blocks.

  • Less to patch

    There is no plugin stack to keep secure. Third-party scripts and connected tools still need review.

When staying on WordPress is the better call

If the site depends on WooCommerce, a membership plugin, a learning platform or custom PHP, moving those functions is a project of its own. A WordPress site that is fast, secure and easy for the team to edit is rarely worth moving just to change platforms.

What moves

Where each part of the WordPress site goes

Everything is listed before anything moves. This is how each kind of content usually maps; your inventory decides the final plan.

On WordPressIn WebflowHow it gets there
PostsA Blog posts CMS collectionThe WP to Webflow app from the Webflow Marketplace, or a CSV built from the WordPress export. The body arrives as HTML in a rich text field.
Categories and tagsTheir own collections, linked to posts with reference fieldsImported with the posts, then checked on a sample.
PagesStatic pages built from Webflow componentsRebuilt. Import tools skip pages, because Webflow’s API can’t create static pages.
Featured and inline imagesImage fields and rich text images on Webflow’s hostingImage fields upload on import. Check that images inside the body text no longer load from the old site.
AuthorsAn Authors collection referenced from each postA short CSV, then linked to the posts.
Custom post types and ACF fieldsA collection per type, with matching fieldsMapped field by field and imported by CSV or the Webflow API.
Yoast or Rank Math titles and descriptionsSEO title and description fields on each collectionExported as columns and bound to the collection template’s page settings.
Contact Form 7, Gravity Forms or WPFormsWebflow forms, or an embed from your form toolRebuilt, then tested end to end into email or the CRM.

Rebuilt rather than moved

  • Shortcodes and page-builder blocksElementor, Divi or Gutenberg layouts don’t survive an export. Post bodies are cleaned to plain HTML.
  • Plugin features on the pageSliders, tabs, popups, galleries and search are rebuilt with Webflow elements or replaced with a tool.
  • Theme templatesHeaders, footers and the post template become Webflow components and a CMS template page.

Step by step

How to move a WordPress site to Webflow

Before the move

  1. Crawl and list every URL

    Pages, posts, category and tag archives, author pages and media, each with its traffic and links from Search Console.

  2. List every plugin and what it does

    For each one, decide: a Webflow feature, a connected tool, or retired.

  3. Design the CMS structure

    Collections and fields for posts, categories, authors and any custom post types.

  4. Write the redirect map

    Every old URL against its new one, agreed before the build starts.

The move

  1. Build the templates

    Components, static pages and a template page for each collection.

  2. Import a sample, then everything

    Ten varied posts first, including the longest and one with embeds. Fix the mapping, then import the rest.

  3. Rebuild forms and integrations

    Analytics, consent, forms and any CRM connection, each tested on staging.

  4. Review on staging

    Your team checks content, links and forms on the staging site.

After the move

  1. Launch with redirects

    Import the redirect CSV, publish, switch the domain and test a sample of old URLs.

  2. Submit the new sitemap

    In Search Console, then watch the indexing and 404 reports.

  3. Monitor against the baseline

    Compare traffic and rankings page by page for several weeks and fix gaps quickly.

  4. Hand over

    A recorded walkthrough of the CMS, so the team can publish from day one.

Search traffic

Keeping your rankings through the move

Google treats a migration as a site move. These are its rules, then the risks that are specific to WordPress.

What Google asks for

  • A permanent (301) redirect from every changed URL straight to its closest replacement, with no chains.
  • No redirecting old pages to the home page in bulk. Pages with no replacement return a 404 or 410.
  • Redirects kept for at least a year, and a new sitemap submitted in Search Console.
  • Some ranking movement is normal while Google recrawls. On a medium-sized site it can take a few weeks or more to settle.

The migration SEO checklist lists every check before, during and after the move.

If traffic drops anyway, these are the checks to run.

  • Date and category permalinks

    URLs like /2024/05/post-name/ can’t be reproduced in Webflow, where CMS items sit at /collection/item/. One wildcard redirect rule can map the whole pattern to the new path.

  • Archives, tags and attachment pages

    WordPress creates tag, author, date and attachment pages automatically. Redirect the ones with traffic or links to a relevant page, and let thin ones return a 404.

  • Titles and descriptions

    Yoast and Rank Math store these outside the post body. Export them on purpose, or every post launches with a default title.

  • Links inside posts

    Old links in article bodies still point at old URLs. Redirects catch them, but updating them during the import sends readers straight to the new page.

Your part

What your team does during the move

  • A short content freeze

    Publishing pauses on the old site between the final content import and launch, usually a few days. Anything urgent in that window is added to Webflow by hand.

  • One person who decides

    Someone who can approve the content structure, what gets retired and the final sign-off.

  • A staging review

    Your team clicks through the staging site, checks the content and submits every form before the domain switches.

What you provide

  • Admin access to WordPress, or a full export (Tools, then Export)
  • A list of active plugins and what each one does for you
  • Access to the domain and DNS
  • Search Console and analytics access, for the baseline

Questions about the move

How do I migrate from WordPress to Webflow?

List every URL and plugin, design the CMS collections, import the posts with an app or a CSV, rebuild the pages and forms in Webflow, then launch with 301 redirects and a new sitemap. The steps above go through it in order.

Can I migrate WordPress to Webflow without losing SEO?

You can avoid the avoidable losses: keep the content and titles, redirect every changed URL to its closest replacement and submit the new sitemap. Some movement while Google recrawls is normal, and no migration can guarantee identical rankings.

Can we keep the same URLs?

Often. Pages and posts can keep their paths when the Webflow folder and collection structure allows it. Date-based post URLs and deep category paths have to change, and each one gets a permanent redirect.

Is there a tool that imports WordPress into Webflow?

Yes. The WP to Webflow app on the Webflow Marketplace imports posts, categories, tags and images into CMS collections. It doesn’t build pages or the design, and every imported post still needs a check.

What happens to our plugins?

Each one is reviewed for what it does. Some have a native Webflow equivalent, some become an integration, and some functions stay on another service. Those decisions are agreed before the build.

Can marketing keep publishing during the move?

Yes, until the final import. After that, a short freeze keeps both sites in step, and anything urgent is added to Webflow by hand.

What about WooCommerce?

Webflow has its own ecommerce, but a large or complex store is often better on a dedicated platform such as Shopify, or kept running while the marketing site moves. That decision comes first.

How long does a migration take?

It depends on the number of pages and posts, how many features need replacing and how much content needs cleaning. The first step is an inventory of pages, posts, forms and integrations, and the estimate follows from it. Nothing is estimated before that list exists.