WordPress to Webflow Migration: A Step-by-Step Guide

The short answer

A WordPress to Webflow migration has seven steps: audit your URLs and plugins, map your content to Webflow CMS collections, export and clean your WordPress content, import it as CSV, rebuild the design in Webflow, set up 301 redirects, and launch with SEO checks. The design is rebuilt, not copied across. Content volume and how many URLs change decide most of the effort, and a typical startup marketing site with a blog can move in a few weeks.

Before you start

Make sure Webflow is the right move. It suits marketing sites where you want hosting, security and updates handled for you and a team that edits visually. If you rely on complex membership, learning or e-commerce plugins, check Webflow can replace them first. Our Webflow vs WordPress comparison covers the trade-offs.

The WordPress to Webflow migration, step by step

1. Audit what you have

• Crawl the site and export every URL, title, meta description and H1.
• Export top pages by clicks from Search Console for the last 12 months.
• List pages with backlinks. These need redirects most of all.
• List every active plugin and what it does: forms, SEO, search, popups, analytics, schema. Webflow has no WordPress plugins, so each job needs a native feature, an app or custom code.
• Decide what stays, what merges and what goes.

2. Map your content to the Webflow CMS

Plan collections before you export anything. A typical mapping looks like this:

• Posts become a Blog Posts collection, with fields for title, slug, excerpt, featured image, body (rich text), publish date and SEO fields.
• Categories and authors become their own collections, linked to posts with reference fields.
• Custom post types (case studies, careers, integrations) become their own collections.
• Pages are rebuilt as static pages in the Designer.

Check URL structure early. Webflow CMS pages sit under their collection's slug, such as /blog/post-name, and since 2023 Webflow lets you nest collection pages inside folders. If your WordPress posts live at the root (example.com/post-name) or use dated permalinks, their URLs will change and every one needs a redirect. Also check your site plan's CMS item limits on Webflow's pricing page.

3. Export and clean your WordPress content

WordPress's Tools > Export creates a WXR file, an XML format containing posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies and users. Webflow's own migration guide says to convert this XML to CSV, then import the CSV into a collection.

Clean the data before importing:

• Strip shortcodes and page-builder markup from post bodies.
• Keep rich text as HTML. Webflow requires rich text fields to be imported as HTML.
• Use direct URLs for images. Image fields take a direct image URL; multi-image fields take URLs separated by semicolons.
• Re-host images if the old site is being shut down, because imported URLs that point at it will break.
• Remove letters and commas from number fields.
• Decide what to do with comments, which are not part of a typical CMS import.

4. Import into Webflow

Import the CSV into each collection and map columns to fields. Webflow's limits are worth knowing: the maximum CSV size is 4MB, file fields can't be filled from a CSV, and images imported by CSV don't get responsive variants, so upload pre-sized, compressed images. Import a small batch first, check the template, then import the rest. For very large blogs, the Webflow API is an alternative to CSV.

5. Rebuild the design

Pages and templates are rebuilt from scratch in Webflow. Treat it as a chance to fix structure: build reusable components, use a consistent class system and design CMS templates that hold up with short and long posts. This is usually the largest part of the work.

6. Set up 301 redirects

Webflow manages redirects under Site settings > Publishing > 301 redirects. You can add them one by one or import a CSV with two columns: old path and new path. Note that a new import overwrites all existing redirects, so export first and add to that file.

• Use wildcard patterns for groups of URLs. Webflow supports capture groups, so /blogs/(.*) can redirect to /articles/%1.
• Webflow recommends 1,000 redirects at most as a best practice, which is another reason to use patterns.
• Redirect each old URL to its closest new page. Google warns that sending many URLs to the homepage can be treated as a soft 404.
• Let pages you're removing on purpose return a 404 or 410.
• Keep redirects for as long as possible. Google suggests at least a year.

7. Run SEO checks and launch

• Carry over titles and meta descriptions for every page and CMS item.
• Check canonical tags, the auto-generated sitemap and robots settings.
• Update internal links to new URLs instead of relying on redirects.
• Add schema through custom code where you used a plugin before.
• Install the same GA4 property and recreate key events.
• After switching DNS, test your top 50 old URLs, submit the sitemap in Search Console and watch for errors.

Google notes that search visibility can fluctuate during a move and that a small to medium-sized site can take a few weeks for most pages to move. Our redesign checklist has a full launch-day list.

A realistic migration timeline

Most of our website projects take 2 to 6 weeks. For a startup marketing site with a blog, a migration usually breaks down like this:

• Week 1: audit, URL inventory, plugin replacement plan, CMS structure.
• Weeks 2 to 3: design of key pages and CMS templates.
• Weeks 3 to 5: Webflow build, content clean-up and import, redirect map.
• Final week: QA, SEO checks, launch and monitoring.

Thousands of posts, several languages or many custom post types add time. So does content that has to be rewritten rather than moved. We redesigned Itilite's website and rebuilt it on Webflow, and organic deals now land about 2.5x better.

Common mistakes

• Forgetting old blog category, tag and author archive URLs in the redirect map.
• Importing images that still point at the old WordPress server.
• Losing meta descriptions because they lived in an SEO plugin's fields.
• Overwriting existing redirects with a new CSV import.
• Launching on the same day as a big campaign.

FAQ

Can Webflow import WordPress content automatically?

Not directly from XML. Convert the WordPress export to CSV and import it into a collection, or use the Webflow API for larger sites.

Will migrating to Webflow hurt our SEO?

Not if you keep content, map redirects and carry over metadata. Expect some movement for a few weeks.

Can we keep the same URLs?

Often, for pages. Blog posts at the root or under dated permalinks will usually change, so redirect them.

How long does a WordPress to Webflow migration take?

A few weeks for most startup sites. Large blogs and multilingual sites take longer.

Moving off WordPress? Talk to us about a redesign and migration through our Webflow & Framer Development service.