How do I export my Webflow website?

Webflow offers three export mechanisms. HTML/CSS export downloads the static assets of your marketing pages as a ZIP, works for published pages on Site plans (Basic and above). CMS content exports via CSV per collection (Designer → CMS → Collection → three-dot menu → Export). Forms and form submissions don't export. Ecommerce data exports to CSV. Member data can be exported but doesn't transfer functionally to other platforms. The combination gives you ~70% of the content; the remaining 30% (forms, interactions, backend) requires rebuilding on the new stack.

Can I use Webflow's HTML/CSS export as my new site?

As a starting reference, yes. As a long-term codebase, not really. The exported HTML is usable but verbose, the CSS is auto-generated and often larger than necessary, and there's no component structure, every page is standalone HTML. For a small brochure site, you could deploy the export as-is on a static host and save money immediately. For any site you'll continue to update, rebuilding the export into a proper static site generator (Astro, Eleventy) gives you a better long-term foundation.

How long does a Webflow to coded site migration take?

DIY, expect 20–50 hours for a typical marketing site with a CMS-driven blog, spread over 2–4 weeks. Faster than Squarespace migrations (Webflow's export is better) and much faster than Wix migrations (which have no content export). With a specialist, elapsed time is 2–4 weeks with minimal work from you. SiteShiftCo handles Webflow migrations as Core projects (from $1,900) or Custom depending on CMS complexity and interaction rebuilding scope.

What happens to my Webflow CMS content when I migrate?

Webflow CMS content is exportable via CSV per collection or via the Webflow API for more structured access. The content (titles, body, fields) transfers cleanly; CSV → Markdown conversion with frontmatter is straightforward. References between collections (e.g., a blog post referencing an author) need to be reconstructed in the new stack. Reference fields and multi-reference fields require careful mapping. For typical blog structures (post + optional categories), conversion is routine; for complex content models, budget more time.

What about Webflow interactions and animations?

These don't export. Webflow's Interactions panel lets you build animations visually, but the underlying implementation is Webflow-specific JavaScript, it doesn't run outside Webflow. Your options on the new stack: (1) rebuild the animations using CSS (for simple transitions); (2) use a library like GSAP or Framer Motion (React); (3) simplify, many Webflow interactions are decorative and the site works fine without them. For most small business sites, option 3 is often the right call.

Will my Webflow forms keep working after migration?

No. Webflow forms are processed by Webflow's backend. After export, the form HTML stays but submissions go nowhere. Replace with: Cloudflare Pages Functions (free, serverless), Formspree (easy drop-in), Web3Forms, or a direct integration to your CRM. Test form submission end-to-end on the new site before cutting over DNS.

What happens to Webflow Ecommerce when I migrate?

Webflow Ecommerce is significantly more involved to migrate than the CMS. Product data exports to CSV. Customer accounts, order history, saved payment methods, and active subscriptions don't migrate cleanly. If ecommerce is more than a marginal part of your site, consider whether Shopify is a better destination than a coded site, Shopify is built for ecommerce and has mature migration tools. A coded site makes sense for content-led Webflow sites with light ecommerce (a few products). For serious commerce, it usually doesn't.

Will I lose SEO if I migrate from Webflow?

Only if execution is poor. Webflow URL structures can typically be preserved exactly on the new site; 301 redirects should map any URLs that change. Webflow's Core Web Vitals are often mediocre, the new coded site usually performs better, which tends to improve rankings over 4–8 weeks post-migration. The risk is in missed redirects, lost metadata, or removed schema markup, all preventable.

What's the easiest way to move from Webflow to a static site?

Three-step: (1) export your Webflow pages as HTML/CSS and CMS collections as CSV; (2) set up Astro or Eleventy with a matching component structure; (3) rebuild pages as components and convert CSV to Markdown files. The exported HTML serves as a design reference during the rebuild. For Webflow users familiar with component-based design (Symbols, nested components), the Astro mental model is similar.

Is it worth hiring someone to migrate my Webflow site?

Depends on the site's complexity and your comfort with code. For marketing sites with straightforward CMS structures and few interactions, DIY is tractable for technically-comfortable Webflow users in 20–30 hours. For sites with complex CMS models, many custom interactions, or membership/ecommerce components, hiring saves significant time and reduces the risk of SEO issues. SiteShiftCo handles Webflow migrations as Core projects from $1,900, larger or more complex sites are quoted as Custom.

Why would I leave Webflow if the site is working?

Common reasons: (1) Webflow's stacked pricing (Workspace + Site plans + Ecommerce if applicable) can reach $100+/month for small sites, disproportionate to value; (2) Webflow performance is variable and often below static-site potential; (3) Ownership concerns, even with HTML/CSS export, the CMS and forms are platform-locked; (4) Complexity, Webflow's flexibility comes with learning curve and ongoing decision overhead. If the site is working well and the fees feel reasonable, staying is legitimate. If the cost or lock-in is starting to pinch, a coded site is the cleanest exit.

How to migrate from Webflow to a coded site

Webflow is the friendliest major CMS to migrate away from. Its HTML/CSS export is genuinely usable as a starting point, its CMS content exports cleanly via CSV or API, and its users are typically more technically comfortable than Squarespace or Wix users, all of which make the migration faster and less error-prone.

That said, three things don’t transfer from Webflow and need explicit attention: forms, interactions, and any memberships/ecommerce functionality. This guide walks through the full sequence with particular attention to those.

Who this is for

Good fit:

Webflow marketing sites with typical CMS-driven content (blog, case studies, team pages)
Users comfortable with component-based design and some code
Sites where the Webflow recurring cost (often $50–$200/month across Site plans and Workspace fees) feels disproportionate
Owners who want to own their code and remove recurring platform fees

Not a good fit:

Sites with significant Webflow Ecommerce (consider Shopify instead)
Sites relying heavily on Memberstack or native Webflow memberships
Agencies running many client sites on Webflow (Webflow is still a reasonable stack at that scale)
Sites where the editor’s visual workflow is load-bearing for daily use by non-technical editors

What Webflow lets you export

HTML/CSS export

On Site plans (Basic and above), Webflow’s HTML/CSS export downloads a ZIP containing:

Rendered HTML for every published static page
A compiled CSS file
JavaScript for interactions (baseline, more on this below)
Asset files (images, fonts referenced in the site)

What’s included:

Every static page as standalone HTML
CSS (auto-generated, sometimes larger than necessary)
Referenced assets

What’s NOT included:

CMS content (pages that use collections don’t export fully, only the template HTML, not populated pages)
Form submissions or form backend
Ecommerce pages (need separate handling)
Member areas

CMS export

For each CMS collection, Webflow provides a CSV export:

Designer → CMS panel → Collection → three-dot menu → Export collection items as CSV

This captures every field as a column. Reference fields export as the referenced item’s slug or ID. Multi-reference fields are semicolon-separated.

For more structured access, the Webflow API (v2) lets you pull collections programmatically, useful for larger sites where scripted conversion is faster than per-collection CSV work.

Ecommerce export

Products export to CSV. Orders, customers, and inventory history are more limited. For serious ecommerce migrations, the destination is almost always Shopify rather than a coded site.

What doesn’t export

Forms, the HTML stays, the backend doesn’t
Interactions and animations, Webflow-specific JavaScript, doesn’t run outside Webflow
Custom code embeds, exports as-is but references Webflow-specific environment
Member data, limited export, doesn’t functionally transfer
Site search, Webflow’s built-in search doesn’t transfer

Realistic time estimates

For a typical Webflow marketing site (20–40 pages, CMS-driven blog with 30–100 posts, contact form, moderate interactions):

Task	DIY time
Learning the stack (first-time)	5–15 hours (less if you’ve used component-based tools)
Content audit and page inventory	2–4 hours
HTML/CSS export and asset download	1–2 hours
CMS CSV exports	1–3 hours
Setting up Astro/Eleventy with components	3–8 hours
Rebuilding pages as components	8–15 hours
Converting CMS CSV to Markdown	2–6 hours
Rebuilding forms on new stack	2–4 hours
Handling interactions (CSS/JS or simplification)	3–10 hours
Setting up SEO preservation	2–4 hours
Testing on staging	2–4 hours
DNS cutover and verification	1–3 hours
Total	32–78 hours

Spread over 2–4 weeks. Webflow users typically complete these faster than Squarespace or Wix migrants because the skills translate well.

Step-by-step migration

Step 1: Audit the site

Full page inventory, CMS collections list, forms inventory, interactions list (each one, what it does, decision: rebuild in CSS, rebuild in JS, or drop), tracking scripts, integrations, DNS records.

Step 2: Choose your stack

For small business Webflow migrations, the most common destination:

Static site generator: Astro is a natural fit, component-based, which matches Webflow’s mental model
Hosting: Cloudflare Pages (free tier), Netlify, or Vercel
Content: Markdown for blog posts, component props for structured pages
Forms: Cloudflare Pages Functions or Formspree
Animations (if keeping): CSS for simple transitions; GSAP or Motion for complex

Component-based static generators (Astro, Next.js, SvelteKit) match Webflow’s component/Symbol mental model better than template-based generators (Hugo, Eleventy). For Webflow users, component-based is usually the natural choice.

Step 3: Export everything from Webflow

HTML/CSS export (Site settings → Hosting → Export code)
CMS CSV per collection
Ecommerce CSV if applicable
Asset library (images, videos, export via the Assets panel or via the Webflow API)
Screenshot every interactive element so you know what to rebuild

Step 4: Set up the new project

Create a new Astro (or Eleventy, etc.) project. Configure Tailwind CSS if matching Webflow’s utility-class aesthetic. Set up the component structure to mirror your Webflow symbols.

Step 5: Rebuild pages as components

The exported HTML serves as a design reference. For each page:

Open the exported HTML
Identify repeating sections that should be components (hero, feature grid, testimonials, CTA)
Build those as Astro components
Assemble page files that compose components

This is where Webflow users move fast, the component thinking already applies.

Step 6: Convert CMS content

For each collection’s CSV:

Map columns to Markdown frontmatter fields
Convert each row to a Markdown file
Use the collection’s template HTML (from Webflow export) as a reference for the layout
Handle reference fields by mapping slugs to the right Markdown files

Tools to help: custom scripts (Node.js or Python), AI-assisted conversion (paste CSV into Claude, ask for Markdown files with frontmatter).

Step 7: Handle interactions

For each interaction on your Webflow site, decide:

Keep as CSS. Simple transitions (fade in, slide, scale on hover) can be recreated with Tailwind or vanilla CSS. Usually the right call.
Keep as JS. Complex scroll-triggered animations, orchestrated sequences, use GSAP or Motion (framework-appropriate).
Drop. Many interactions are decorative. If dropping them doesn’t degrade the site’s effectiveness, skip the rebuild.

Be honest about which interactions actually contribute to the business. Many Webflow sites accumulate interactions over time that add weight without value.

Step 8: Replace forms

Webflow forms don’t work after export. Replace with:

Cloudflare Pages Functions if hosting on Cloudflare Pages (free, no vendor dependency)
Formspree, simplest drop-in replacement
Custom serverless function, if you have specific requirements (CRM integration, conditional routing)

Test every form submission end-to-end on the staging site before launch.

Step 9: Preserve SEO

Preserve meta titles and descriptions from Webflow’s SEO settings
Re-implement schema markup as JSON-LD
Generate sitemap with @astrojs/sitemap or equivalent
Configure robots.txt
Preserve URL structures exactly where possible

Step 10: Build redirect map

Webflow URL patterns are usually clean, so most URLs can be preserved. Implement 301 redirects for:

Any URL structure changes (/blog/post-slug → /articles/post-slug, etc.)
www to apex or vice versa (whichever you’re consolidating to)
Old Webflow staging URLs or preview URLs
Any removed pages (redirect to relevant alternatives)

Implement as _redirects file in Cloudflare Pages or equivalent.

Step 11: Test on staging

Before DNS changes:

Every page loads correctly
Forms submit and emails arrive
Analytics events fire
Structured data validates
Core Web Vitals scores are acceptable (should be significantly better than Webflow baseline)
Mobile experience
404 page
Redirects work

Step 12: DNS cutover

Lower TTL 48 hours beforehand
Document existing DNS (especially MX for email)
Change A/CNAME to point at the new host
Keep MX unchanged (unless also migrating email)
Verify SSL provisions
Test in incognito
Keep Webflow site active for 48 hours as rollback

Step 13: Post-launch

Submit new sitemap to Google Search Console
Verify tracking scripts fire correctly
Check redirect map via bulk tester
Monitor Search Console for 4 weeks
Cancel Webflow plan after 30 days of clean analytics

Cost of DIY vs hiring

DIY:

Learning curve: 5–15 hours (Webflow users tend to pick up Astro/Eleventy fast)
Migration work: 25–65 hours
Out-of-pocket: $10–$20
Risk: moderate, forms and interactions are the main places things go wrong

Hiring a specialist:

SiteShiftCo: Core ($1,900+) for typical Webflow marketing sites, Custom for complex CMS models or many interactions
Webflow-specialist agencies: $4,000–$15,000
Full-service agency: $12,000–$30,000

Webflow migrations are in the middle tier of difficulty, more than Squarespace (which has weaker export but simpler sites), less than Wix (which has no real export). Hiring makes sense when interactions are complex or time is the scarce resource.

What you gain, what you lose

Gains

Lower ongoing cost, $0/month vs $50–$200/month typical Webflow cost
Ownership, full code, no platform dependency
Better performance, coded sites typically beat Webflow on Core Web Vitals
Portability, change hosts anytime without rebuilding
AI-native editing, content in Markdown is natively editable by AI assistants (see Can I update my website using AI?)

Losses

Visual editor, no more Designer. Edits happen in code, Markdown, or a Git-based CMS layer
Interaction panel, custom interactions require CSS/JS skills or being willing to simplify
Some lock-in convenience, Webflow handled hosting, SSL, CDN automatically; you configure these on the new stack
Webflow Hosting speed optimizations, if you were on a high-tier Site plan, Webflow does some optimizations automatically; you’ll replicate these manually

For most small business Webflow sites, the tradeoffs favor migration. For agencies or design teams running many sites on Webflow, the Designer workflow is often worth the ongoing cost.

After migration: editing workflow

Common concerns for Webflow users leaving the Designer:

“How do I make visual layout changes?”

Options ranked by the amount of change:

Small content tweaks, edit Markdown directly or via AI assistant
New blog posts, create new Markdown file, commit
Structural layout changes, edit Astro components (requires some HTML/CSS comfort)
Major redesign, requires code changes, same as any coded site

“Can I still have a visual editor?”

Yes, with a layered Git-based CMS (TinaCMS, Decap, Keystatic). Content editing happens in a familiar visual interface; the underlying files remain Markdown.

“What about for clients who need to edit their own sites?”

If you’re an agency migrating client sites, consider keeping Webflow for clients who need the visual editor and only migrating sites where you’d prefer the lower-cost, code-based model. It’s not all-or-nothing.

Webflow alternatives, if you haven’t decided where to go yet
Will I lose SEO if I rebuild my site?, SEO preservation details
What breaks when you move a website?, the full audit checklist
How to choose a website migration service, buyer guide if hiring
Can I update my website using AI?, how editing works after migration
Glossary: Site migration, Site export, 301 redirect, Static site, Static site generator (SSG)