How to Migrate From WordPress to Webflow: A Step-by-Step Guide (2024)

Moving a live website from WordPress to Webflow isn’t a plugin-and-click job — it’s closer to rebuilding your site on new foundations while keeping the furniture. WordPress and Webflow store content differently, handle templates differently, and think about hosting differently. If you rush it, you’ll lose SEO rankings, break media links, and confuse the search engines that indexed your old URLs.

This guide walks through the actual migration process: auditing what you have, exporting it, rebuilding it in Webflow, and relaunching without tanking your traffic.

This post contains affiliate links. If you sign up for a tool through one of these links, we may earn a commission at no extra cost to you. We only recommend tools we’ve researched and believe are genuinely useful.

WordPress vs. Webflow: Quick Comparison

If your site leans heavily on WooCommerce with dozens of plugins, or you need very specific PHP-level customization, Webflow may feel restrictive. If you’re running a marketing site, agency portfolio, or blog where design control and low maintenance matter more than deep plugin ecosystems, Webflow is a legitimate upgrade.

Before You Start: Audit Your Current Site

Don’t skip this. Open a spreadsheet and log:

• Every published page and post URL
• Meta titles and descriptions for each
• Any custom post types (products, portfolio items, testimonials)
• Forms currently on the site and where submissions go
• Plugins doing something functional (not just cosmetic) — booking systems, membership gates, custom search
• Current traffic sources per page (pull this from Google Analytics/Search Console so you know what you can’t afford to break)

This audit becomes your migration checklist later — you’ll check items off as you rebuild them in Webflow.

Step 1: Export Your WordPress Content

In your WordPress dashboard, go to Tools > Export and choose “All content.” This generates an XML file with your posts, pages, comments, and custom fields. It won’t carry over design/theme data — Webflow doesn’t use WordPress themes, so that’s expected and fine.

For media, you have two options:
– Manually download your /wp-content/uploads/ folder via FTP or your host’s file manager
– Use a plugin like WP All Export if you need a structured CSV of image URLs and alt text to reference during rebuild

Separately, export your SEO data. If you use Yoast or Rank Math, export the meta titles/descriptions (most SEO plugins have their own export tool) so you’re not rewriting 200 meta descriptions from memory.

Step 2: Map Your Content Structure to Webflow’s CMS

Webflow organizes dynamic content into Collections (think: a structured database of blog posts, team members, products, etc.), rather than WordPress’s more freeform post types and taxonomies.

Before building anything, decide:
– Which WordPress post types become Webflow Collections (usually: Blog, Team, Case Studies, Products)
– What fields each Collection needs (Title, Slug, Body, Featured Image, Author, Category, Date)
– How your WordPress categories/tags map to Webflow’s reference and multi-reference fields

This mapping exercise is the single most important planning step. Rushing straight into rebuilding pages without deciding your CMS structure first is the most common reason Webflow migrations get messy.

Step 3: Set Up Your Webflow Site

Create your Webflow project and pick a plan based on what you need:

Webflow is a visual, no-code website builder with a built-in CMS, hosting, and design tools. It’s best suited for marketing teams, designers, agencies, and small businesses who want pixel-level design control without hand-coding, and who don’t need the sprawling plugin ecosystem WordPress offers.

• Best for: Design-focused marketing sites, blogs, portfolios, and small-to-mid CMS-driven sites
• Pricing: Webflow offers a free starter tier for building and staging; paid Site plans are required to connect a custom domain and unlock more CMS items, form submissions, and bandwidth. CMS and Business tier pricing scales with traffic and content volume — [VERIFY: pricing]
• Genuine limitation: Webflow’s CMS has item limits per plan and isn’t as extensible as WordPress + a plugin for niche functionality (e.g., complex membership logic, highly custom WooCommerce workflows). If your WordPress site relies on a specific plugin doing something very particular, check whether Webflow can replicate it before you commit — sometimes it can’t, and you’ll need a third-party integration or custom code embed to bridge the gap.

You can start building in Webflow’s free plan to test your Collection structure before paying for anything.

Step 4: Rebuild Your Design

Webflow doesn’t import WordPress themes — you’re designing from scratch (or from a Webflow template as a starting point). This is the most time-consuming part of the migration, so budget for it honestly:

• Start with a Webflow template close to your existing layout if you want to move faster
• Rebuild your header, footer, and core components as Webflow Symbols so they update sitewide
• Recreate your Collection page templates (e.g., one dynamic template for all blog posts) rather than designing each page manually

Step 5: Import Your Content Into Collections

Webflow supports CSV import for CMS Collections on paid CMS plans. Take your exported WordPress XML, convert the relevant fields into a CSV matching your Collection’s field structure, and import.

For sites with more than a couple hundred items, or complex relational data (categories linking to multiple posts, authors linking to bios), manual CSV mapping gets tedious. Some teams use a migration service or a developer script to automate the WordPress XML to Webflow CSV conversion — worth considering if you have 500+ posts.

Double-check after import:
– Rich text formatting (bold, links, embedded images) carried over correctly
– Featured images are actually attached, not just linked as broken URLs
– Slugs match your original WordPress URLs exactly (critical for the next step)

Step 6: Preserve Your URL Structure and Set Up Redirects

This is where most WordPress-to-Webflow migrations lose SEO ground, so slow down here.

1. In Webflow, set each page/Collection item’s slug to match your old WordPress URL exactly where possible.
2. Where you can’t match exactly (e.g., WordPress’s /category/post-name/ structure vs. Webflow’s flatter routing), set up 301 redirects. Webflow’s paid Site plans include a redirect manager under Project Settings.
3. Cross-reference your pre-migration URL list against your new Webflow URLs. Every old URL that isn’t a 1:1 match needs a redirect entry — no exceptions if you care about retaining rankings.
4. Submit your new sitemap in Google Search Console and monitor the Coverage report for 404s in the weeks after launch.

Step 7: Rebuild Forms and Functional Plugins

Go back to your audit list. For each functional plugin:
– Contact forms: Rebuild using Webflow’s native form element, connect to your email or a tool like Zapier for CRM handoff
– Booking/scheduling plugins: Usually replaced with an embedded third-party widget (Calendly, etc.) via Webflow’s embed block
– Membership/gated content: Webflow has native Memberships on certain plans, but complex gating logic may need a third-party integration
– Search: Webflow’s native search is basic; sites with heavy search needs sometimes add a third-party search widget

Step 8: Handle SEO Details

• Re-enter meta titles and descriptions from your export into Webflow’s page/Collection SEO settings
• Set canonical tags for any pages that might otherwise duplicate
• Regenerate and submit your XML sitemap (Webflow auto-generates one at /sitemap.xml)
• Reinstall your analytics and Search Console verification tags in Webflow’s site settings
• Check structured data (schema markup) — WordPress SEO plugins often auto-generate this, and you may need to add it manually via Webflow’s custom code embed

Step 9: Test on Webflow’s Staging Domain

Before pointing your domain at Webflow, test everything on the free .webflow.io staging URL:

• Click through every navigation link
• Submit every form
• Check mobile responsiveness on actual devices, not just the designer’s preview
• Run a broken-link checker across the full site
• Load key pages in an incognito window to catch anything cached or hidden behind your logged-in session

Step 10: Go Live

1. Update your domain’s DNS records to point to Webflow (Webflow gives you the exact records to add with your registrar)
2. Publish your Webflow site to the custom domain
3. Once DNS propagates (can take a few hours), do a final URL-by-url check against your redirect list
4. Keep your old WordPress site’s redirect rules or export active for a few weeks in case DNS caching causes intermittent old-site visits

Step 11: Post-Migration Monitoring

For the first 30 days:

• Watch Google Search Console daily for crawl errors or spikes in 404s
• Compare organic traffic week-over-week against your pre-migration baseline
• Check that redirects are actually firing (spot-check with a browser redirect checker tool)
• Keep your WordPress export files backed up somewhere safe for at least 90 days — don’t delete your old host immediately

Is the Migration Worth It?

Webflow makes sense if your priority is design control, reduced plugin maintenance, and a cleaner editing experience for non-technical teammates. It’s a worse fit if your site depends on deep WordPress plugin functionality — a highly customized WooCommerce store, complex membership logic, or a plugin ecosystem you’d have to rebuild from scratch with custom code.

Run the audit in Step 1 before you commit. If your functional plugin list is short, the migration is straightforward. If it’s long, budget significant time for rebuilding that functionality — or reconsider whether WordPress with a better theme and fewer plugins solves your actual problem instead.