WordPress to Webflow Migration: The Complete Checklist (50+ Projects)

You've spent years building content and SEO authority on WordPress. Moving to Webflow shouldn't mean starting over. We've completed 14+ WordPress-to-Webflow migrations and 30+ total migrations across platforms since 2019, and this is the checklist we actually use — the items that prevent broken redirects, lost rankings, and the kind of post-launch fires that ruin the first month on a new platform.

This isn't a tutorial on how to use Webflow's designer. It's the operational checklist for planning, executing, and verifying a migration without losing what you've built.

Migration Trust Bar:

• 14+ WordPress-to-Webflow migrations completed
• 30+ total platform migrations (Joomla, Squarespace, HubSpot, custom)
• 100% SEO preserved on Wellness Everyday migration (70+ pages, Joomla to Webflow)
• 6-10 weeks typical migration timeline

What a WordPress-to-Webflow Migration Actually Involves

A migration moves your website from one platform to another. In practical terms, this means:

• What gets transferred: Content (pages, blog posts, media files), SEO metadata (titles, descriptions, URLs), CMS structure, and analytics configuration.
• What gets rebuilt: Visual design, page layouts, custom functionality (anything PHP-based), forms, and third-party integrations. Webflow's visual editor replaces your WordPress theme and most plugins.
• What improves: Page load speed (no plugin overhead), CMS editing experience (visual editor vs. block/classic editor), security posture (no plugins to patch), and marketing team independence (content changes without developer involvement).
• What to expect: 6-10 weeks for a typical B2B marketing site (20-50 pages). Larger sites or full redesigns can take 10-16 weeks. Your team will be involved in content review, redirect approval, and UAT testing.

The site isn't just moved — it's rebuilt in a new system. That's why the checklist matters. Skip steps and things break silently.

What Goes Wrong When Migration Isn't Done Right

Broken 301 Redirects (SEO Killer #1)

Every URL that changes between WordPress and Webflow needs a 301 redirect pointing old to new. Miss a redirect on a high-traffic page and Google sends visitors to a 404 error. Do that across 50 URLs and your organic traffic drops off a cliff within days.

How we prevent it: We build a complete redirect map spreadsheet — every old URL mapped to its new Webflow URL — and test each redirect individually before launch. On the Wellness Everyday migration (70+ pages, Joomla to Webflow), the redirect map had 200+ entries. We tested every single one.

Lost Meta Titles and Descriptions

WordPress SEO plugins (Yoast, Rank Math) store custom meta titles and descriptions. If these don't transfer to Webflow, Google re-indexes your pages with auto-generated metadata — and your click-through rates can drop 20-40%.

How we prevent it: We export all metadata before migration and verify every page's meta title and description in Webflow before launch.

Broken Integrations

WordPress plugins connect to CRMs, email tools, analytics, payment systems, and more. Each connection needs a Webflow equivalent. Miss one and lead data stops flowing, forms break, or tracking goes dark.

How we prevent it: A complete integration inventory in Phase 1. Every plugin gets mapped to its Webflow replacement before we write a line of code.

Extended Downtime During Cutover

DNS propagation can take 15 minutes to 48 hours. If something goes wrong during that window, your site could show errors to real visitors.

How we prevent it: We build and test everything on a webflow.io staging domain first. The DNS switch is the last step, and we monitor continuously during propagation.

Post-Launch Bugs

Formatting issues, broken links, missing images, forms that submit to nowhere — these surface when real traffic hits a site that was only tested internally.

How we prevent it: A full QA phase with cross-browser testing, mobile testing, form testing, and link auditing before launch, followed by 30 days of daily monitoring after.

WordPress vs Webflow: What Changes

DimensionWordPressWebflowPage speedVaries (plugin-dependent, often 3-5s)Fast by default (sub-3s, CDN-backed)CMS editingBlock/classic editor, plugin-dependentVisual editor, inline editingDesign controlTheme-dependent or custom codedFull visual design control, no theme neededSecurityManual (plugin updates, patches, backups)Managed (automatic SSL, DDoS protection)SEO toolsYoast/Rank Math pluginsBuilt-in (meta, OG, sitemaps, redirects)HostingSelf-managed or managed WP hostingBuilt-in (AWS + Fastly CDN)Plugin library60,000+ pluginsNo plugins; integrations via native, Zapier, or custom codeDeveloper dependencyHigh for anything beyond contentLow for content; medium for structural changesE-commerceWooCommerce (very capable)Native e-commerce (limited to 15K products)

WordPress wins on plugin variety, e-commerce depth, and entry-level cost. Webflow wins on design control, speed, security overhead, and marketing team independence. For B2B marketing sites with 10-200 pages, the total cost of ownership over 3 years typically favors Webflow once you factor in plugin licenses, security monitoring, developer maintenance, and hosting upgrades.

The Migration Checklist

Phase 1: Pre-Migration Audit (Week 1-2)

Content Inventory

• Export your full sitemap using Screaming Frog, Sitebulb, or a similar crawler — every URL including custom post types, taxonomy pages, and archives
• Count exact numbers: static pages, blog posts, landing pages, category/tag archives, custom post types
• Document your WordPress CMS structure — every custom post type, custom field (ACF, etc.), and taxonomy
• Flag dynamic content (filtered archives, search results, related posts) that needs a Webflow solution
• Screenshot every unique page template (most WordPress sites use 5-15 distinct templates)
• Catalog all media files — total count and size, since large libraries (1,000+ images) need a transfer plan

SEO Baseline

• Export Google Search Console data: top 50 pages by traffic, all indexed URLs, any manual actions
• Document all meta titles and descriptions from Yoast, Rank Math, or your SEO plugin
• Map your current URL structure (WordPress often uses /category/, /blog/, date-based paths, or custom slugs)
• Export existing 301 redirects from Yoast, Redirection plugin, or .htaccess
• Run PageSpeed Insights on your top 10 pages — this becomes your performance benchmark
• Note all structured data/schema markup (FAQ, HowTo, Article, etc.) — you'll recreate these in Webflow
• Document canonical tags and hreflang tags if applicable

Technical Inventory

• List every active WordPress plugin and what it does — each one needs a Webflow equivalent or a conscious decision to drop it
• Document all third-party integrations: CRM, email marketing, analytics, chat, payments, scheduling
• Check for custom PHP in functions.php or custom plugins — this logic needs a Webflow equivalent
• Test every form and document where submissions go (CRM, email, Google Sheet, etc.)

Phase 2: Planning and Architecture (Week 2-3)

Information Architecture

• Design your Webflow CMS collections — translate WordPress post types into Webflow collections
• Map WordPress custom fields to Webflow CMS fields (text, rich text, image, video, link, reference, multi-reference, date, switch, color, number, option)
• Define your new URL structure — keep URLs as close to WordPress structure as possible to minimize redirects
• Build your redirect map spreadsheet: Column A = old WordPress URL, Column B = new Webflow URL. Every changed URL needs a row. This is the single most important document in the migration.
• Choose your Webflow Site Plan based on content inventory: Basic (no CMS), CMS (under 2,000 items), Business (under 10,000 items)
• Set up your staging environment on a webflow.io subdomain

Content Strategy

• Decide: full redesign or visual replica? This affects timeline and budget by 2-4 weeks.
• Audit content quality — migration is the best time to cut dead weight (low-traffic pages, outdated posts, duplicate content)
• Set a content freeze date: after this date, no new WordPress content is published. Anything created after the freeze gets added to Webflow manually.

Phase 3: Build and Content Transfer (Week 3-7)

Development

• Build global styles first: typography, colors, spacing, button styles. Establish your design system before building pages.
• Build CMS collection templates (blog, case study, team member) — these drive the most pages
• Build static pages: homepage, about, contact, service/product pages
• Implement responsive design across all four Webflow breakpoints (1920px, 991px, 767px, 478px)
• Add interactions and animations — Webflow's interaction system replaces most JavaScript plugins from WordPress

Content Migration

• Import structured CMS content via CSV — clean data first (remove WordPress shortcodes, fix formatting, verify image references)
• Upload and compress media files to Webflow's asset manager
• Transfer rich text content carefully — WordPress block/classic editor content doesn't paste cleanly into Webflow
• Rebuild manual pages that don't map from WordPress templates

SEO Transfer

• Add all meta titles and descriptions to every Webflow page and CMS item
• Set up all 301 redirects in Webflow (supports bulk import)
• Configure Open Graph titles, descriptions, and images per page
• Review auto-generated sitemap.xml — verify all important pages are included
• Re-implement structured data (FAQ, Article, Organization, BreadcrumbList schema) via custom code embeds
• Set up canonical URLs where needed

Phase 4: Testing and QA (Week 7-8)

Functional Testing

• Submit test data through every form — verify data arrives at the correct destination
• Check at least 5 CMS items per collection to verify template rendering with different content
• Test all integrations: CRM sync, analytics tracking, chat widgets, email marketing
• Cross-browser testing: Chrome, Safari, Firefox, Edge on actual devices
• Mobile testing on real iOS and Android devices — scroll, tap, fill forms, test different page types
• Run a full link check across the staging site — every internal link should point to a valid Webflow page
• Run PageSpeed Insights and compare against your WordPress baseline from Phase 1

SEO Validation

• Crawl the staging site with Screaming Frog — verify page count, no orphan pages, no broken links, all meta tags present
• Manually test at least 20 redirects (prioritize highest-traffic pages)
• Verify robots.txt blocks staging from search engines and sitemap will be correct once live

Phase 5: Launch (Week 8-9)

• Enforce content freeze if not already active
• Final content sync — transfer anything published between freeze date and now
• Point your domain to Webflow — update DNS records per Webflow's registrar-specific documentation
• Monitor DNS propagation (15 minutes to 48 hours depending on registrar and TTL settings)
• Verify SSL is active on all pages once DNS propagates
• Submit new sitemap.xml to Google Search Console
• Request re-indexing for your top 10-20 pages via Search Console's URL inspection tool
• Keep old WordPress site accessible (not public) for 30 days for reference

Phase 6: Post-Launch Monitoring (30 Days)

• Monitor Google Search Console daily for the first two weeks — watch for indexing errors, crawl issues, traffic changes
• Re-test your full redirect map on the live domain — some redirects fail silently during DNS propagation
• Track 404 errors via Webflow analytics and Search Console — add new redirects as they appear
• Compare Core Web Vitals against Phase 1 baseline — you should see improvement
• Watch organic traffic in Google Analytics — a small dip in the first 1-2 weeks is normal as Google re-crawls. If traffic drops more than 15% without recovering within 3 weeks, investigate redirect issues
• Test forms again with real-world scenarios
• Decommission WordPress hosting after 30 days — save a full backup first

Migration Case Study: Wellness Everyday

Client: Wellness Everyday (healthcare/government)

Migration: Joomla to Webflow

Scope: 70+ pages, full content restructure, complete redesign

Redirect map: 200+ entries, each tested individually

Result: 100% SEO preserved, zero downtime during cutover

The Joomla CMS was outdated and difficult for their team to update. After migration, their marketing team could publish content changes in hours instead of filing tickets. The redirect map was the difference between preserving 3+ years of search authority and starting from scratch.

TenOneTen Ventures migrated from WordPress to Webflow in a 6-week build. Their site now supports 200+ podcast episodes, a portfolio of 100+ investments (including 4 unicorns), and the team has managed it independently for 3+ years post-launch.

WordPress Plugin to Webflow Equivalents

WordPress PluginFunctionWebflow EquivalentYoast / Rank MathSEO managementBuilt-in (meta, OG, sitemaps, redirects)Gravity Forms / WPFormsForm builderWebflow native forms or Typeform/Jotform embedWP Super Cache / W3 Total CachePerformanceNot needed (Webflow CDN handles caching)Wordfence / SucuriSecurityNot needed (managed hosting, auto SSL, DDoS protection)Elementor / DiviPage builderWebflow visual editor (replaces both the builder and theme)WooCommerceE-commerceWebflow E-commerce (up to 15K products) or ShopifyACF (Advanced Custom Fields)Custom CMS fieldsWebflow CMS fields (native, no plugin needed)WPML / PolylangMulti-languageWebflow Localization (add-on)MemberPressMembershipsMemberstack or Webflow MembershipsZapier / WP WebhooksAutomationZapier / Make (works with Webflow natively)Google Analytics pluginTrackingGoogle Tag Manager embed (custom code)Redirection plugin301 redirectsWebflow native redirects (bulk import)

The biggest shift: WordPress relies on plugins for functionality. Webflow handles most of it natively (SEO, hosting, security, caching, forms, CMS). The remaining gaps get filled by 2-3 integrations instead of 15-30 plugins.

Frequently Asked Questions

Will I lose my Google rankings if I migrate from WordPress to Webflow?

Not if done correctly. The key is a complete 301 redirect map (every old URL redirecting to its new location), transferring all meta titles and descriptions exactly, and submitting a new sitemap to Search Console. Across our 14+ WordPress-to-Webflow migrations and 30+ total migrations, we've maintained SEO authority by following a structured redirect and monitoring process.

How long does a WordPress to Webflow migration take?

6-10 weeks for a typical B2B marketing site (20-50 pages with blog and basic CMS). Larger sites (100+ pages) or migrations that include a full redesign can take 10-16 weeks. Content transfer and redirect mapping typically take longer than people expect.

How much does a WordPress to Webflow migration cost?

Migration-only (content transfer, redirects, minimal design changes): $5,000–$15,000 depending on site size. Migration with redesign: $15,000–$50,000+. Platform costs shift from WordPress hosting ($30–$100/month + plugin licenses) to Webflow ($23–$60/month, no plugin costs). Most companies see lower total cost within 12-18 months.

What happens to my WordPress plugins?

Each plugin's function needs a Webflow equivalent. SEO (Yoast replaced by Webflow native), security and caching (handled by Webflow hosting), forms (Webflow native or Typeform/Jotform), analytics (Google Tag Manager). See the plugin equivalents table above. Most WordPress sites with 20+ plugins end up needing only 2-3 third-party integrations on Webflow.

Do I have to recreate all my blog posts manually?

Structured content (blog posts, team members, case studies) imports via CSV into Webflow's CMS. Rich text formatting, embedded images, and WordPress shortcodes don't transfer cleanly — you'll need to review and clean up each piece. Static pages are usually rebuilt from scratch in the new design.

Will my site go down during migration?

We build and test everything on a staging domain before touching your live site. The only downtime risk is during DNS propagation (15 minutes to 48 hours after pointing your domain). We monitor continuously during this window and keep your WordPress site accessible as a fallback for 30 days.

What about WooCommerce? Can Webflow replace it?

Webflow's native e-commerce handles up to 15,000 products (Advanced plan). For focused product lines under 500 SKUs, it works well. If you're running a large WooCommerce store with complex inventory, multi-warehouse fulfillment, or advanced product variants, Shopify is typically a better migration target than Webflow E-commerce.

How do I keep my SEO rankings during migration?

Three non-negotiable steps: (1) Build a complete 301 redirect map — every URL that changes gets a redirect. (2) Transfer all meta titles and descriptions exactly as they were. (3) Submit your new sitemap to Search Console immediately after launch and request re-indexing for your top pages. Then monitor daily for 2 weeks.

Can I migrate only part of my WordPress site to Webflow?

Yes. Some companies migrate their marketing site to Webflow while keeping their blog on WordPress (or vice versa). This works via subdomain setup (e.g., blog.yoursite.com stays on WordPress, yoursite.com moves to Webflow). It adds complexity but is sometimes the right approach for very large content libraries.

What if something breaks after launch?

We monitor every migration for 30 days post-launch — tracking Search Console errors, 404s, form submissions, and Core Web Vitals. Most issues surface in the first 1-2 weeks and are redirect-related. Having the WordPress site accessible (not public) as a reference makes debugging faster.

Should I redesign during migration or just move the content?

Most of our clients (about 80%) use migration as an opportunity to redesign. The content transfer work happens regardless, and rebuilding in Webflow means you're already investing in development time. A 1:1 replica saves on design but still requires full development effort. If budget is tight, migrate first and redesign in phases after.

Does Webflow handle sites with hundreds of blog posts?

The CMS plan supports 2,000 total CMS items and Business supports 10,000. "CMS items" includes everything — blog posts, team members, case studies, and any other collections. A site with 500 blog posts plus other content fits comfortably on the Business plan ($39/month annual). Sites with 10,000+ items need Enterprise or a headless CMS integration.