How to Migrate from Webflow to UnfoldCMS

Webflow's visual designer is the best in the business — designers love it, and rightly so. The bills are another conversation. Site plans climb from $14 to $49/month per site, Workspace plans add per-seat fees, and the Business plan is $39/site/month for traffic any real marketing site exceeds. For agencies running ten client sites, the math hits $5,000–$15,000/year before custom-code add-ons. This page is for teams who've decided the design freedom isn't worth the recurring tax.

TL;DR: Migrating from Webflow to UnfoldCMS takes 1–2 days for typical content sites. Export Webflow CMS Collections as CSV, transform, import via UnfoldCMS REST API, rebuild the frontend in Aurora (or your own theme), set up redirects, point your domain. One-time UnfoldCMS license at $39–$799 replaces Webflow's $168–$5,000+/year per site. We offer a Migration Concierge service at $499 that handles it for you in 7 days.

Why Teams Migrate Off Webflow

Three reasons account for ~90% of Webflow migrations. None are speculative — they show up in every "we left Webflow" thread on r/webflow and the IndieHackers forum.

1. Per-site pricing for agencies. Webflow charges per project, not per organization. Ten client sites means ten Site plans at $14–$49/month each — $1,680–$5,880/year just for hosting. Add the Workspace plan for collaboration and you're at $11,000+/year for a small agency. UnfoldCMS Agency tier is $799 once for unlimited domains.

2. CMS limits at the wrong scale. The Basic plan caps at 2,000 CMS items, the CMS plan at 10,000, the Business plan at 10,000 with higher form submission limits. Real content sites hit these ceilings within 12–24 months and face a forced upgrade — or worse, a forced migration off Webflow when the next tier is also too small.

3. You don't own the platform. Webflow's designer is proprietary. The site code can be exported as static HTML/CSS, but the CMS, hosting, forms, and ecommerce features only run on Webflow's infrastructure. If they raise prices, deprecate features, or change terms, you're along for the ride. Self-hosted UnfoldCMS runs on any PHP host you control.

We covered the cost reality in detail in UnfoldCMS vs Webflow — including the agency math.

What "Migrate from Webflow" Actually Involves

Six concrete steps. Plan for 1–2 days for a typical site, more if your design is complex.

1. Export Webflow CMS Collections via the Designer's CSV export
2. Transform the CSV to UnfoldCMS post format — different field names, different categorization model
3. Import to UnfoldCMS via the REST API (single endpoint, accepts the transformed JSON)
4. Migrate assets — download images from Webflow's CDN, upload to your media store
5. Rebuild the frontend — pick an UnfoldCMS theme (Aurora ships free) or fork one. This is the bulk of the work for design-heavy sites
6. Set up redirects — Webflow's URL structure differs from UnfoldCMS, so 301 redirects preserve your SEO

For a site with 200 CMS items and 500 assets, plan ~12 hours of focused work. For a complex design, double it.

Step-by-Step: Webflow to UnfoldCMS Migration

Step 1: Export your Webflow CMS Collections

Webflow exports CMS data as CSV, one Collection at a time. From the Webflow Designer:

1. Open the Designer for your site
2. Click CMS in the left panel
3. Open each Collection (Blog Posts, Authors, Categories, etc.)
4. Click the Export button (top right) → Export CSV
5. Save each CSV with a clear name: posts.csv, authors.csv, categories.csv

What you get:

• One CSV per Collection
• Reference fields exported as the referenced item's slug (not its ID)
• Image fields exported as Webflow CDN URLs
• Rich Text fields exported as HTML

Note: Webflow does NOT export draft items by default. Go to the Collection → filter by "Draft" status to export those separately if needed.

Step 2: Export site assets

Webflow doesn't have a bulk asset export. Two options:

Option A — Site code export (Workspace plan or above): Settings → General → Export Code. Downloads a zip with all images, CSS, JS, and HTML. Use this for design reference and to grab assets in bulk.

Option B — Manual CDN scrape: Walk your CSV, extract each image URL (typically uploads-ssl.webflow.com/...), download them with a script. The script in Step 5 handles this.

If you're on the Starter plan, Option A isn't available — you'll need to scrape from the CDN URLs in your CSV exports.

Step 3: Transform the CSV to UnfoldCMS format

Webflow CSVs look like this (simplified):

Name,Slug,Post Body,Author,Category,Featured Image,Published On,Draft
"My Post","my-post","<p>Hello</p>","john-doe","tutorials","https://uploads-ssl.webflow.com/abc/img.jpg","2025-04-01",false

UnfoldCMS expects flat post data. A 50-line Node script handles the transform:

// transform.js
import fs from 'fs';
import { parse } from 'csv-parse/sync';

const csv = fs.readFileSync('posts.csv', 'utf8');
const rows = parse(csv, { columns: true, skip_empty_lines: true });

const posts = rows
  .filter(r => r['Draft'] !== 'true')
  .map(r => ({
    title: r['Name'] ?? 'Untitled',
    slug: r['Slug'] ?? r['Name']?.toLowerCase().replace(/\s+/g, '-'),
    body: r['Post Body'] ?? '',
    seo_title: r['SEO Title'] ?? null,
    meta_desc: r['SEO Description'] ?? null,
    posted_at: r['Published On'] ?? r['Created On'],
    content_type: 'post',
    is_published: r['Draft'] !== 'true' && r['Archived'] !== 'true',
    extra_attributes: {
      webflow_slug: r['Slug'],
      webflow_author_ref: r['Author'] ?? null,
      webflow_category_ref: r['Category'] ?? null,
      webflow_image_url: r['Featured Image'] ?? null,
    },
  }));

fs.writeFileSync('unfold-import.json', JSON.stringify(posts, null, 2));
console.log(`Transformed ${posts.length} posts`);

The body field is already HTML in Webflow's CSV export, so no conversion needed. Author and Category references stay as slugs in extra_attributes for a second-pass resolve in Step 6.

Step 4: Import to UnfoldCMS

UnfoldCMS exposes a bulk import endpoint:

curl -X POST https://your-unfoldcms.com/api/posts/bulk-import \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d @unfold-import.json

The endpoint accepts an array of post objects and returns a result summary:

{
  "imported": 187,
  "skipped": 13,
  "errors": [
    { "index": 42, "reason": "duplicate slug" }
  ]
}

For 200 posts, the import takes 30–60 seconds.

Step 5: Migrate assets

Two paths depending on volume:

Under 1,000 assets — script the upload from Webflow's CDN to your UnfoldCMS media store:

// upload-assets.js
import fs from 'fs';
import fetch from 'node-fetch';
import FormData from 'form-data';

const posts = JSON.parse(fs.readFileSync('unfold-import.json', 'utf8'));

for (const post of posts) {
  const url = post.extra_attributes?.webflow_image_url;
  if (!url) continue;

  const filename = url.split('/').pop().split('?')[0];
  const imageRes = await fetch(url);
  const buffer = Buffer.from(await imageRes.arrayBuffer());

  const form = new FormData();
  form.append('file', buffer, filename);

  await fetch('https://your-unfoldcms.com/api/media', {
    method: 'POST',
    headers: { Authorization: `Bearer ${process.env.UNFOLD_TOKEN}` },
    body: form,
  });

  console.log(`Uploaded ${filename}`);
}

Over 1,000 assets — keep them on Webflow's CDN and rewrite URLs in your post bodies. Webflow's CDN keeps serving images even after you cancel hosting (for 30 days), giving you time to migrate at your own pace.

Step 6: Rebuild the frontend

This is the painful part — Webflow's design lives in their proprietary Designer, not in code you can copy-paste.

Three options:

Option A — Use Aurora (free, ships with UnfoldCMS): The fastest path. Aurora is a polished marketing-site theme with hero, features, blog, and pricing sections built in. Configure via the admin UI. Your content goes live in 2–4 hours.

Option B — Export Webflow code as design reference: Use Webflow's "Export Code" feature (Workspace plan) to download HTML/CSS. Reference the design when building a custom Blade template. Plan 2–5 days of frontend work.

Option C — Hire a designer: For a critical site where the Webflow design is a competitive advantage, get a custom theme built. Typical cost: $2,000–$10,000 for a full custom theme. Still cheaper than 3 years of Webflow Site plans.

Most agencies pick Option A and customize colors/fonts via the theme editor. The marketing-site polish is "good enough" without weeks of design work.

Step 7: Set up redirects

Webflow's URL structure typically uses /blog/{slug} for posts and /{collection-slug}/{item-slug} for other Collections. UnfoldCMS uses /blog/{slug} for posts and /{slug} for pages. Plan for redirects.

UnfoldCMS has a built-in redirects table. Bulk-import a CSV via the admin or API:

from,to,status
/blog/old-slug-1,/blog/new-slug-1,301
/our-team/jane-doe,/about/team,301

Or via API:

curl -X POST https://your-unfoldcms.com/api/redirects/bulk \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: text/csv" \
  --data-binary @redirects.csv

Step 8: Update your DNS and forms

Webflow handles DNS, hosting, and forms in one bundle. UnfoldCMS gives you each piece separately:

• DNS: Point your domain at your new UnfoldCMS host (Cloudflare, Vercel, or any PHP host)
• Forms: UnfoldCMS includes a built-in forms feature. Re-create your Webflow forms in the admin UI. Submissions land in the database; integrations (email, Slack, webhooks) wire up via the admin
• Ecommerce: If you used Webflow Ecommerce, that's a deeper migration. UnfoldCMS isn't an ecommerce platform — pair it with Stripe Payment Links for simple cases or pick a dedicated commerce platform (Shopify, Medusa.js)

What Breaks (and How to Handle It)

Real Webflow migrations always hit edge cases. Here are the common ones.

Custom Webflow interactions. Webflow's Interactions panel (animations, scroll triggers, hover states) doesn't transfer. If your site relies heavily on these, plan to rebuild them in CSS/JS. For most marketing sites, simple Tailwind utilities and CSS transitions cover 90% of what Webflow Interactions did.

CMS Reference fields. Webflow's references between Collections (Post → Author, Post → Category) export as slug strings, not IDs. After import, you need a second-pass script to resolve these — match the slug stored in extra_attributes.webflow_author_ref to the new UnfoldCMS author/category records.

Rich Text embeds. Webflow's Rich Text supports embedded videos, code blocks, and custom HTML. Most of these export as HTML in the CSV and render fine in UnfoldCMS. Edge cases: Webflow's "Lottie" animations and custom embedded code blocks may need manual handling.

Webflow Forms. Form schemas don't transfer. UnfoldCMS has a forms module with similar fields (text, email, select, file upload). Re-create each form via the admin UI. Submissions go to the database with the same field structure.

Webflow Ecommerce. Product Collections, variants, and order data don't transfer to UnfoldCMS (it's a content CMS, not an ecommerce platform). For ecommerce sites, use UnfoldCMS for the marketing site + blog, then pair with Shopify Hydrogen, Medusa, or Snipcart for the storefront.

Site search. Webflow's site search is built-in. UnfoldCMS includes basic search but for advanced needs (typo tolerance, faceted search) drop in Algolia (free tier handles most projects) or Meilisearch (self-hosted).

Timeline: How Long Does Webflow Migration Take?

For typical content sites, the breakdown:

DIY time assumes a developer comfortable with Node, CSV, and a little Blade templating.

Concierge time is the Migration Concierge service — $499 for sites up to 500 CMS items, custom quote above that. We handle the export, transform, import, asset migration, redirects, and Aurora theme setup. We don't replicate complex Webflow interactions — those are out of scope or quoted separately.

When NOT to Migrate Off Webflow

Be honest about it. Webflow is genuinely strong for some teams.

Stay on Webflow if:

• Your design is the product — you're a design agency where Webflow's visual flexibility is a core competitive advantage
• Your team is designer-led and nobody on staff can edit Blade templates or CSS
• You depend on Webflow Ecommerce and the migration cost (rebuilding the storefront elsewhere) exceeds 5 years of Webflow fees
• Your traffic is low enough that the Site plan covers you and you don't expect to outgrow it
• You use Webflow Interactions extensively and rebuilding them in CSS/JS is more expensive than the recurring fee
• You're satisfied with the per-site pricing and don't have ten client sites bleeding $500/month each

If two or more of these apply, migration probably isn't the win you're hoping for. Read the honest comparison and decide accordingly.

What You Get After Migrating

Direct comparison for a typical agency running 10 client sites:

Trade-offs are real — Webflow's visual designer is genuinely better than any code-based theme system. But for the 80% of teams who don't need pixel-perfect custom design, UnfoldCMS replaces Webflow for ~95% less over 5 years.

FAQ

How much does it cost to migrate from Webflow? Free if you DIY (just developer time). The Migration Concierge service is $149 for a 30-min consultation + written plan, or $499 for done-for-you migration of one site up to 500 CMS items + media. Complex Webflow Interactions or Ecommerce are quoted separately.

Will my SEO survive a Webflow to UnfoldCMS migration? Yes if you set up 301 redirects from old URLs to new ones, preserve content per URL, regenerate your sitemap, and resubmit to Google Search Console. The most common SEO mistake is shipping the migration without redirects — that drops you from page 1 to page 5 for weeks.

Can I keep my Webflow design after migrating? Partially. You can export Webflow's HTML/CSS as static reference (Workspace plan or above), then rebuild the design in an UnfoldCMS theme. Most teams discover that Aurora (the free default theme) covers 70–80% of typical Webflow designs without rebuilding. For pixel-perfect replication, plan 2–5 days of frontend work or hire a designer.

What about Webflow Interactions and animations? Webflow's Interactions panel doesn't transfer. Simple animations (fade-in, slide, hover) rebuild in 1–2 hours of CSS. Complex scroll-triggered animations or Lottie integrations need a JS library (GSAP, Framer Motion). For most marketing sites, the recurring cost of Webflow exceeds the one-time cost of rebuilding interactions.

Can I run Webflow and UnfoldCMS in parallel during migration? Yes. Common pattern: import to UnfoldCMS, run both side-by-side for 2 weeks at a staging subdomain, run a sitemap diff to catch missing pages, then cut DNS to UnfoldCMS. Webflow stays as your safety net for 30 days.

What about Webflow Ecommerce? Ecommerce migrations are deeper than content migrations. UnfoldCMS isn't an ecommerce platform — content lives in UnfoldCMS, products and orders go to a dedicated commerce platform (Shopify, Medusa.js, Snipcart). Plan to rebuild your storefront in whichever commerce platform fits.

How do I migrate Webflow Forms? Re-create each form in UnfoldCMS's admin Forms module — same field types (text, email, select, file). Submissions go to the UnfoldCMS database. Email notifications, Slack webhooks, and Zapier integrations wire up via the admin UI.

Will Webflow charge me during the migration? Yes — Webflow bills monthly until you cancel the Site plan. After cutover, run UnfoldCMS for 30 days, verify nothing depends on Webflow's CDN or forms, then cancel Webflow plans. CDN images keep serving for ~30 days after cancellation, giving you a buffer.

Can I migrate Webflow CMS Collections with custom fields? Yes. UnfoldCMS supports arbitrary fields via the extra_attributes JSON column. Custom Webflow fields (rating, color picker, multi-reference) map to JSON values that your frontend can read directly. The fields don't render in the admin UI by default, but can be exposed via the post editor's custom-fields panel.

Is the Webflow API available for the migration? Yes for the Workspace plan or above. The Webflow Data API lets you read CMS items programmatically — useful if CSV export is missing fields. For Starter plans, CSV export is the only option.

Methodology

Pricing data is from webflow.com/pricing as of May 2026. Migration time estimates are based on production migrations our team has executed for content sites of varying sizes. Step-by-step instructions reference Webflow's official Designer documentation and UnfoldCMS API docs. Edge cases (Interactions, Forms, Ecommerce) are sourced from real migration tickets in our support queue.

Migrate from Webflow to UnfoldCMS

Three paths depending on how hands-on you want to be:

• DIY — follow this guide, write the transform script yourself, ship it in 1–2 days. Free.
• Migration Starter ($149) — 30-min call where we audit your Webflow site, identify migration risks (Interactions, custom embeds, ecommerce), and write you a tailored migration plan. You execute it.
• Migration Concierge ($499) — done for you. We export, transform, import, migrate assets, set up redirects, and configure Aurora. 7 days, up to 500 CMS items. Custom quote above. Complex Interactions quoted separately.

Get started with UnfoldCMS — one-time license, full source, no per-site fees. The Agency tier at $799 covers unlimited domains and is the obvious pick for any agency running 5+ Webflow client sites.

For more context, see UnfoldCMS vs Webflow, CMS for agency client sites, or browse all migration guides.

If after reading this you decide Webflow is still the right call, that's a fine answer too. The point of this page is to give you the information to choose, not to push every team toward migration.

Related: CMS for agency client sites, migrate from WordPress, or browse all CMS comparison guides.