Webflow Migration Guide: How to Move Your Site Off Webflow

Your Webflow migration has one job: move the site without creating a bigger workload for your marketing team. Exporting the code won’t get you there. You keep the HTML, CSS, and JavaScript, while CMS content, forms, ecommerce, and other dynamic features need to be rebuilt or replaced. That’s where a migration that looks simple on paper turns into weeks of tickets and implementation. An AI growth platform gives you a different path by carrying over your existing structure and brand, then continuing to improve the site after it goes live.

Key takeaways

• Webflow exports static code only. CMS content, forms, ecommerce, user accounts, and site search require complete rebuilds on the destination platform.
• Migration time depends on scope. CMS relationships, ecommerce, accounts, localization, forms, and interactions add work beyond moving static pages.
• Code export requires a paid Workspace plan. Site plans alone do not include export functionality.
• CMS image fields may export as hosted URLs. Download or remap important assets before decommissioning the source site.
• 301 redirects protect existing URLs and search signals. Missing redirects create 404s and unnecessary indexing risk.
• Ploy’s website slurp creates an editable first pass from the rendered site. CMS records, app data, and dynamic functionality still need separate migration and review.

Understanding why teams leave Webflow

Most teams don’t leave Webflow because the platform is bad. They leave because their growth outpaced what Webflow was designed to handle.

CMS limitations hit first

Webflow’s May 2026 plan update raised the Premium Site plan to 20,000 CMS items. Teams planning larger programs should still compare collection, relationship, localization, and app requirements rather than evaluating capacity by item count alone. See Webflow’s May 2026 plan update.

Feature gaps create workarounds

Multi-language support, subscription billing, complex shipping rules, and user dashboards all require external tools stitched onto Webflow. Each integration adds another dashboard and another potential point of failure.

Designer dependency slows your team down

Webflow’s Designer requires trained users. Editor mode restricts non-designers to copy changes only. Marketing teams wait for design tickets instead of shipping campaigns.

Costs compound at scale

Add-ons like Localization, Analyze, and Optimize increase your monthly bill. Agencies managing multiple client sites feel this across their portfolio.

Long-term growth strategy considerations

You should consider where your site needs to be in 12-24 months, not just what’s painful today.

• Do you need app functionality? User dashboards, gated content, and API integrations require capabilities Webflow wasn’t built for.
• Is site ownership non-negotiable? Some organizations require full code ownership for compliance, security, or vendor risk reasons.
• Does your team have the technical capacity to rebuild? Honest assessment of available hours and expertise prevents mid-migration stalls.
• Will the new platform also stop working after launch? Migrating from one static platform to another trades one set of problems for a similar set.

Ploy addresses the underlying pattern: websites that require constant manual intervention to stay optimized. Instead of rebuilding once and starting the decay cycle over, Ploy Web continuously monitors technical SEO, Core Web Vitals, Answer Engine Optimization, and content freshness, drafting improvements automatically while your team reviews and approves.

Your essential website migration checklist

Pre-migration planning and preparation

Week 1-2: Audit and document

A complete inventory prevents surprises during the rebuild phase. Most migration delays stem from undocumented integrations or forgotten functionality.

• Content audit: Document every page, CMS collection, blog post, and asset. Screaming Frog crawls your live site and exports a complete URL list.
• Integration inventory: List every connected tool including analytics, forms, CRM, marketing automation, chat widgets, and payment processors.
• Feature documentation: Note custom interactions, animations, conditional visibility, and any logic built into the site.
• SEO baseline: Export current rankings, organic traffic, and backlink profile. This becomes the benchmark for post-migration monitoring.

Redirect mapping starts here, not at launch. Create a spreadsheet mapping every current URL to its destination URL on the new platform. This task alone takes 4-12 hours depending on site size.

Choose your destination platform before starting exports. The platform dictates how you’ll handle CMS migration, form replacement, and functionality rebuilds.

During migration: Export and rebuild

Export process (Week 2-3)

Webflow’s export provides static code only. Understanding what transfers and what doesn’t prevents wasted effort.

Export steps:

1. Log into Webflow Designer with a Workspace plan
2. Press Shift + E or click the Webflow logo and select Export Code
3. Click Prepare ZIP and download when ready
4. Export each CMS collection separately as CSV
5. Download all images from the Assets panel before deleting the source site

Asset warning: CMS image fields may export as hosted URLs rather than bundled files. Download or remap important assets and verify the destination before decommissioning the source site.

Rebuild phase (Week 3-6)

Rebuilding takes the bulk of migration time. Budget 40-100 hours for implementation depending on site complexity and destination platform.

You’ll need to find replacement tools for:

• Form handling: Formspree, Basin, Netlify Forms
• Site search: Algolia, Google Programmable Search
• User authentication: Memberstack, Auth0
• Ecommerce: Shopify, WooCommerce, Snipcart

Post-migration validation

Launch week (Week 6-8)

• Implement 301 redirects using your pre-built mapping. Methods vary by hosting: .htaccess files for Apache, Cloudflare redirect rules, or platform-native redirect managers.
• Test every redirect with HTTPStatus.io or similar tools. Verify each old URL returns a 301 status pointing to the correct destination.
• Submit updated sitemap to Google Search Console immediately after launch.
• Reconnect analytics and verify tracking fires correctly on all pages.
• Cross-browser testing across Chrome, Firefox, Safari, and Edge plus mobile devices.
• Form submission testing to confirm replacements work and notifications route correctly.

First month monitoring

• Check Google Search Console daily for the first two weeks, then weekly for two months.
• Monitor traffic patterns against your pre-migration baseline.
• Run weekly broken link audits with Screaming Frog.
• Track Core Web Vitals to catch performance regressions early.

For teams using Ploy, the migration process starts with a fast, editable first pass of the rendered site, preserving the visible structure and brand foundation for review. CMS records, integrations, and dynamic functionality are scoped separately before cutover.

Website migration services and tools

DIY vs. professional migration services

DIY makes sense when:

• Your site has 5-15 pages without complex CMS structures
• No ecommerce functionality to rebuild
• Destination platform is template-based (Wix, Squarespace)
• Your team has bandwidth for a multi-week project

Professional help makes sense when:

• Your site exceeds 50 pages
• Complex CMS structures with references between collections
• Ecommerce migration required with product catalog and order history
• Custom Webflow interactions need preservation
• Strict SEO requirements with no tolerance for traffic loss

Ploy’s agency partner network includes studios like Tonik (the team behind Ploy’s own site) and TNT Growth (an Inc. 5000 agency managing ad spend). These partners help customers launch, migrate, and scale websites using Ploy as the underlying platform.

Tools to streamline your migration process

Site crawling and audit:

• Screaming Frog: Comprehensive URL export and broken link detection
• Google Search Console: Current ranking and indexing baseline

Redirect testing:

• HTTPStatus.io: Bulk redirect verification
• Redirect Path (Chrome extension): Real-time redirect chain inspection

Content transfer:

• HTTrack/wget: Download rendered pages including dynamic content that export misses
• CSV tools: OpenRefine for bulk content cleanup and transformation

WordPress-specific:

• Udesly Converter: Transform Webflow exports into WordPress themes
• WP All Import: CSV content import with field mapping

Performance validation:

• Google Lighthouse: Core Web Vitals and performance scoring
• WebPageTest: Detailed load waterfall analysis

For teams moving to Ploy, these tools become less necessary. Website slurp handles the import. Built-in analytics combine server-side and client-side tracking. Continuous optimization eliminates the post-launch audit cycle.

How Ploy streamlines migration and drives continuous growth

From Webflow to Ploy: A rapid transition

A Webflow migration can range from a straightforward page move to a multi-phase rebuild. The largest variables are CMS structure, forms, ecommerce, accounts, localization, integrations, and custom interactions.

Ploy approaches the first pass differently.

• Website slurp recreates the rendered site for review. It captures visible structure, components, design patterns, and brand voice so the team is not starting from a blank canvas.
• Dynamic systems are scoped separately. CMS records, forms, ecommerce, accounts, and integrations still need explicit migration or replacement plans.
• The imported design foundation guides future pages. New work can reuse the established patterns after the team reviews and confirms them.

Beyond migration: Sustained performance with AI

Migration is a one-time event. What happens after determines whether your new site creates value or starts the same decay cycle.

Most websites stop working the day they launch. Search algorithms change. Competitors update positioning. Buying intent shifts. The site sits frozen while the market moves around it.

Ploy keeps working after launch.

• Technical SEO monitoring catches issues before they affect rankings
• Core Web Vitals optimization maintains fast load times as content grows
• Answer Engine Optimization structures pages for AI citation across ChatGPT, Perplexity, Gemini, and Google AI Overviews
• Internal linking improvements strengthen site architecture automatically
• Content freshness recommendations identify pages that need updates

Ploy drafts the changes. Your team reviews and publishes. The work that usually requires dedicated resources happens in the background.

Ploy Grow extends the value beyond your website. Instead of treating visitors as anonymous traffic, visitor de-anonymization identifies companies researching your business, enriches them with firmographic data, scores buying intent, and syncs qualified accounts to your CRM. Integrations with Attio and HubSpot connect website activity directly to sales workflows.

Ploy Ads closes the loop. Ad creative generation, competitor campaign monitoring, and full-funnel attribution connect every impression back to pipeline. The three engines share context, so insights in one part of the platform create opportunities in the others.

Handling CMS content and complex data transfers

Challenges with complex content structures

CMS migration is where most Webflow exports fall apart. The platform stores content in collections with references, multi-image fields, rich text, and relationships that don’t map cleanly to other systems.

What breaks during export:

• Multi-references between collections lose their connections in CSV format
• Rich text fields export as HTML with embedded image URLs pointing to Webflow’s CDN
• Image fields export as URLs only, not the actual files
• Color, video, and file fields lose formatting and require manual recreation
• Collection item limits on the destination platform may not match Webflow’s 20,000 cap

Common failures:

• Images display as broken links after source site deletion
• Blog posts reference authors that exist in a separate collection, breaking the relationship
• Category structures flatten into text instead of maintaining hierarchy
• Custom field types require manual recreation on the new platform

Ensuring data integrity across platforms

Before export:

1. Download all images from the Assets panel
2. Document collection relationships with a visual diagram
3. Export each collection to CSV and verify all fields populated
4. Screenshot any conditional visibility or collection sorting logic

During transfer:

1. Find-replace image URLs in CSV files to point to new hosting locations
2. Recreate collection structures on the destination before importing content
3. Import parent collections (authors, categories) before child collections (posts, products)
4. Validate reference fields reconnected properly after import

Webflow-specific gotcha: Images in rich text fields remain as Webflow CDN URLs even after you’ve downloaded assets separately. These break when the source site goes offline. Use find-replace across all CSV files to update image paths before importing.

Ploy’s website slurp can recreate the rendered pages and visible design foundation without relying on Webflow’s code export. CMS records, collection relationships, app logic, accounts, and other dynamic data still require a separate migration plan and validation.

Post-migration optimization

Monitoring key performance indicators

The first 90 days after migration determine whether the project succeeded. Establish clear metrics and monitor them actively.

SEO health indicators:

• Organic traffic compared to pre-migration baseline
• Indexed page count in Google Search Console
• Crawl errors and 404 rates
• Ranking positions for top 20 keywords
• Backlink profile stability (check for lost links)

Performance metrics:

• Core Web Vitals: LCP, FID/INP, CLS across mobile and desktop
• Page load times by template type
• Server response times

Tracking form submissions:

• Form submission rates
• Goal completions compared to baseline
• Bounce rate changes by landing page

Set alerts for significant deviations. A 20% traffic drop within two weeks signals redirect issues or indexing problems that need immediate attention.

Implementing continuous improvement cycles

Most migration guides stop at “monitor for 30 days.” That misses the larger pattern: websites require ongoing work to maintain and improve performance.

Traditional approach:

• Quarterly SEO audits with consultant or agency
• Monthly content reviews
• Periodic Core Web Vitals checks
• Annual or bi-annual site refreshes

Each cycle requires scheduling and budget. The work piles up between audits. Small issues compound into larger problems.

Ploy’s continuous approach:

Ploy Web monitors automatically and drafts improvements without waiting for scheduled audits:

• Technical SEO issues surface as they occur, not during quarterly reviews
• Content optimization recommendations appear based on actual search demand and competitor changes
• Core Web Vitals stay optimized as new pages publish
• Answer Engine Optimization adapts as AI answer engines evolve

Ploy Grow adds optimization beyond the website itself. Visitor identification turns traffic into actionable accounts. Intent scoring prioritizes outreach. CRM synchronization keeps sales informed without manual data entry.

The result is a site that improves between major initiatives instead of degrading. Your team focuses on strategy and campaigns while Ploy handles the execution.

Frequently asked questions

What happens to my Webflow site during migration? Do I need to keep it live?

Keep your source site available until the destination has passed content, asset, redirect, form, and analytics checks. CMS image fields may reference hosted URLs, so copy or remap important assets before decommissioning the source. The rollback window should reflect the site’s complexity and business risk rather than a fixed number of days.

How do I handle custom fonts that were uploaded to Webflow?

Custom fonts uploaded to Webflow don’t export with the site code. You need the original font files to install them on your new platform. If you licensed fonts specifically through Adobe Fonts or another service connected to Webflow, verify those licenses transfer to self-hosted usage. Google Fonts transfer without issues. For custom or licensed fonts, check your original purchase agreement for hosting rights on the new platform.

What’s the SEO impact if I don’t set up 301 redirects correctly?

Missing or incorrect redirects turn old URLs into 404s, interrupt internal paths, and prevent external links from reaching the intended content. Preserve important URLs where possible, map changed URLs with permanent redirects, and monitor crawl errors and search performance after launch.

Can I migrate my Webflow ecommerce store with order history and customer accounts?

Order history exports as CSV and can import into most ecommerce platforms like Shopify or WooCommerce. Customer accounts are more complex. Webflow stores authentication data that doesn’t export in a format other platforms accept. Most teams notify customers to create new accounts on the migrated store. For subscriptions, you’ll need to work with your payment processor (Stripe, etc.) to migrate recurring billing relationships to the new platform’s integration.

How do I handle Webflow interactions and animations after export?

Webflow interactions export as JavaScript, but they reference Webflow’s runtime library. Simple CSS animations may work. Complex multi-step interactions typically need rebuilding with GSAP, CSS animations, or the destination platform’s animation tools. Document each interaction before migration with screen recordings. Budget 2-4 hours per complex interaction for recreation on the new platform.

What if my team lacks technical skills for the migration?

Options exist across the complexity spectrum. Template-based platforms like Wix and Squarespace require less technical skill but involve manual page recreation. Ploy’s website slurp reduces blank-canvas work by creating an editable first pass. Sites with custom functionality, complex ecommerce, or strict SEO requirements still benefit from technical support and a reviewed migration plan.

How long should I wait before deleting my old Webflow account?

Keep the source available until the destination has passed redirect, asset, form, analytics, search, and rollback checks. The appropriate retention period depends on site complexity, traffic, publishing cadence, and operational risk; cancel only after the team confirms the old environment is no longer needed.