---
title: "Wix to Webflow Migration: A Complete Technical Guide"
slug: wix-to-webflow-migration-a-complete-technical-guide
date: 2026-08-28
author: Nachi Raman
categories: [Webflow, Migration Guide]
excerpt: "A complete technical guide to migrating from Wix to Webflow. Covers content extraction, CMS setup, image URL sanitization, 301 redirects, and DNS cutover."
tldr: "Wix to Webflow is a full rebuild: extract content via CSV or API, sanitize image URLs, rebuild the frontend, map every 301 redirect, and manage a controlled DNS cutover."
canonical: https://clonepartner.com/blog/wix-to-webflow-migration-a-complete-technical-guide
---
# Wix to Webflow Migration: A Complete Technical Guide
# Wix to Webflow Migration: A Complete Technical Guide
Migrating from Wix to Webflow is a **full rebuild**, not a transfer. Wix is a closed SaaS platform — there is no automated way to convert a Wix site into Webflow. ([help.webflow.com](https://help.webflow.com/hc/en-us/articles/51622726458899-Migrate-your-site-from-Wix-to-Webflow)) Designs, layouts, and interactions cannot be imported. What moves cleanly is structured data: CMS collections, product catalogs, and contacts export to CSV. The hard parts are blog content, image assets, business logic, structured data markup, and launch-day SEO preservation.
This guide covers every technical step — from content extraction through DNS cutover — along with the real constraints you will hit and the decisions that separate a clean migration from a months-long SEO recovery.
## Why Teams Move from Wix to Webflow
The trigger is usually a ceiling, not a feature comparison chart. Wix sites hit performance and customization limits as businesses scale:
- **DOM bloat and performance:** Wix generates heavy, absolute-positioned inline styles with deeply nested `div` structures. This hurts Core Web Vitals and complicates accessibility.
- **CMS rigidity:** Wix's Content Manager is user-friendly for simple use cases, but querying it externally or building complex relational data structures hits hard limits.
- **Limited development workflow:** Staging environments, version control, and concurrent team development are constrained compared to what engineering teams expect.
- **Restricted URL structures:** Wix forces specific URL patterns (like `/post/` for blogs) that cannot be changed.
Webflow provides clean semantic HTML/CSS output, a relational CMS with an API, native 301 redirect management, and full control over layout and responsive behavior. The trade-off: Webflow has a steeper learning curve, its own platform limits, and a more complex editing experience for non-technical content managers.
## What You Can and Can't Export from Wix
This is the part most guides gloss over. Wix's export capabilities are limited by design.
**What you can export:**
- **CMS collections** → CSV, via Wix Dashboard > CMS > Collection > More Actions > Export to CSV. Non-Latin exports use UTF-8 encoding; time fields export as UTC+0. ([support.wix.com](https://support.wix.com/en/article/cms-formerly-content-manager-exporting-content-from-your-collection))
- **Store products** → CSV, but digital products are excluded and each file is capped at 5,000 rows. ([support.wix.com](https://support.wix.com/en/article/wix-stores-exporting-your-product-list))
- **Contacts** → CSV, up to 50,000 records at once. ([support.wix.com](https://support.wix.com/en/article/wix-contacts-exporting-your-contacts))
- **Blog posts** → RSS feed at `/blog-feed.xml`, capped at the 20 most recent posts. For larger archives, use the Wix Blog API or scrape rendered pages.
- **Media files** → Manual download from the Media Manager. There is no bulk export. ([support.wix.com](https://support.wix.com/en/article/wix-media-downloading-files-from-the-media-manager))
**What you cannot export:**
- Site structure, layouts, or design
- Page-level HTML/CSS
- Forms, apps, or third-party integrations
- Blog categories/tags as structured data
- JSON-LD structured data (auto-generated by Wix; must be manually recreated)
> [!WARNING]
> **The RSS feed only returns 20 posts.** If you have more than 20 blog posts, RSS alone won't get all your content out. Supplement with the Wix Blog API, Wix Velo scripts, or a programmatic scrape of rendered pages.
This mix of exportable and non-exportable data is why a Wix-to-Webflow project with 25 pages can be harder than one with 200. A marketing site with a few static pages is mostly rebuild labor. A small site with blog history, bookings, members, or store data is a migration project. That distinction drives cost, timeline, and risk.
## Wix vs. Webflow CMS: Platform Limits Compared
Understanding what you're migrating into prevents surprises mid-project. The table below covers current limits as of 2024–2025:
| Capability | Wix | Webflow |
|---|---|---|
| CMS collections | Unlimited (practical limit ~30) | 40 collections |
| Items per collection | ~3,000 (UI degrades above this) | 20,000 (CMS plan) |
| Fields per collection | ~50 | 60 |
| CSV import row limit | Not applicable | 10,000 rows per upload |
| CSV import file size | Not applicable | 4 MB |
| Option field values | No documented limit | 100 unique values |
| Slug/name field length | Not documented | 256 characters |
| CMS API rate limit | Varies by endpoint | 60–120 req/min by plan |
| Multi-level references | Not supported | Not supported (single-level only) |
| Multilingual CMS | Via Wix Multilingual app | Via Webflow Localization (paid add-on) |
| JSON-LD structured data | Auto-generated by platform | Manual via Embed elements |
**Webflow plan naming clarification:** Webflow's CMS plan tiers are currently named **Basic**, **CMS**, **Business**, and **Enterprise** for hosted sites. The 20,000-item limit applies to the CMS plan and above. Basic is limited to 50 CMS items. Always verify current limits at [webflow.com/pricing](https://webflow.com/pricing) before scoping a project, as these change.
## Step 1: Audit Your Wix Site
Before touching Webflow, document everything on the Wix side:
- **Full URL list** — Crawl your sitemap (`/sitemap.xml`) and cross-reference with Google Search Console. Every indexed URL needs a destination.
- **Content inventory** — Pages, blog posts, products, media assets. Note content types and volume.
- **SEO metadata** — Title tags, meta descriptions, heading structure, alt text, canonical tags, Open Graph settings. Wix has no bulk metadata export, so scrape these or record them manually.
- **Structured data (JSON-LD)** — Wix auto-generates schema markup for articles, products, and breadcrumbs. This does not transfer. Document which schema types are active on which page types; you will need to recreate them manually in Webflow using Embed elements or a third-party script.
- **Third-party integrations** — Forms, chat widgets, CRM connections, analytics tags, embedded apps, and any Wix Velo backend code. Document what each integration does, what triggers it, and what data it reads or writes.
- **Performance baseline** — Record Core Web Vitals (LCP, CLS, INP), organic traffic levels, and indexed page count. You need this to measure post-migration health.
If the site uses Wix Velo, write down what the code actually does. Webflow does not have an equivalent server-side runtime — any Velo logic will need to be replaced with external services or custom middleware.
## Step 2: Plan Your Webflow CMS Structure
Webflow's CMS is collection-based. Each content type (blog posts, team members, case studies) gets its own **collection**, and each entry is a **collection item** with typed fields.
Key limits to plan around (verify current values at [webflow.com/pricing](https://webflow.com/pricing)):
- **CMS items:** 50 on Basic; 20,000 on CMS plan; higher on Business and Enterprise.
- **Collections:** Up to 40 CMS collections per site.
- **Fields per collection:** Up to 60 fields.
- **CSV importer:** 4 MB file size cap and 10,000 rows per upload. ([help.webflow.com](https://help.webflow.com/hc/en-us/articles/33961290794771-How-do-I-import-content-into-the-Webflow-CMS))
- **Name and slug fields:** Must be fewer than 256 characters.
- **Option fields:** Capped at 100 unique values.
- **File fields:** Cannot be populated from CSV — upload those manually after import.
- **API rate limit:** 60 requests/minute on CMS plan; 120 requests/minute on Business and above.
Key decisions at this stage:
- **Collection architecture** — Map every Wix content type to a Webflow collection. Don't replicate Wix's structure blindly; this is your chance to flatten unnecessary taxonomies.
- **Reference relationships** — Webflow supports single-level references between collections (e.g., blog post → author). It does not support nested or multi-level queries. If your Wix site has deep relational data, you may need to simplify or offload to an external database like Xano or Supabase.
- **Slug strategy** — Decide your URL structure now. Webflow lets you set collection slugs (e.g., `/blog/post-title`), and this directly affects your redirect map.
- **Multilingual content** — If your Wix site uses Wix Multilingual, plan for Webflow Localization as the equivalent. Webflow Localization is a paid add-on that supports alternate-language collection pages and `hreflang` tags. Each language variant requires separate redirect rules — `/old-url` and `/es/old-url` are treated as distinct paths.
> [!TIP]
> **Import reference collections first.** Webflow resolves references by slug during import. If authors, categories, or locations don't exist yet, the main import will silently miss those relationships. ([help.webflow.com](https://help.webflow.com/hc/en-us/articles/33961290794771-How-do-I-import-content-into-the-Webflow-CMS))
## Step 3: Extract and Prepare Content
### CMS Collections
For simple CMS structures, export directly from the Wix Content Manager:
1. Navigate to the **Content Manager** in your Wix dashboard.
2. Select the collection you want to export.
3. Click **Export** and choose CSV.
For complex relational data, or if you need to programmatically clean data before export, write backend functions using **Wix Velo**:
```javascript
import wixData from 'wix-data';
export async function exportCollection(collectionName) {
let results = await wixData.query(collectionName).limit(1000).find();
let allItems = results.items;
while (results.hasNext()) {
results = await results.next();
allItems = allItems.concat(results.items);
}
return allItems;
}
```
### Blog Posts
Wix's UI does not export blog posts to other platforms. ([support.wix.com](https://support.wix.com/en/article/wix-blog-request-exporting-blog-posts-to-other-platforms)) You have three extraction options:
1. **RSS feed** — Parse `/blog-feed.xml` for blogs with 20 or fewer posts.
2. **Wix Blog API** — The Posts and Stats API can query posts programmatically in batches of up to 100, with filter, sort, and paging support. The Post object exposes `title`, `excerpt`, `slug`, `seoData`, `contentText`, and `richContent`. ([dev.wix.com](https://dev.wix.com/docs/api-reference/business-solutions/blog/posts-stats/query-posts))
3. **Scraping** — Tools like Screaming Frog or a custom script can pull titles, body text, meta descriptions, and image URLs from the rendered HTML.
For API extraction, a typical query looks like:
```json
{
"query": {
"sort": [{ "fieldName": "firstPublishedDate", "order": "ASC" }],
"paging": { "limit": 100, "offset": 0 }
}
}
```
API calls require a Bearer token passed in the `Authorization` header. The token is your Wix API key, generated from Wix Dashboard > Settings > API Keys. Store it in a backend environment variable — never in browser-visible or client-side code:
```javascript
const response = await fetch(
'https://www.wixapis.com/blog/v3/posts/query',
{
method: 'POST',
headers: {
'Authorization': `Bearer ${process.env.WIX_API_KEY}`,
'Content-Type': 'application/json',
'wix-site-id': process.env.WIX_SITE_ID
},
body: JSON.stringify({ query: { paging: { limit: 100, offset: 0 } } })
}
);
```
Format your extracted blog content into a CSV matching your Webflow collection fields. The columns below map to a standard Webflow Blog collection:
```csv
Name,Slug,Post Body,Thumbnail,Meta Title,Meta Description,Published Date,Author
"My Article","my-article","
Article HTML here...
","https://static.wixstatic.com/media/abc123.jpg","My Article | Site","Description here","2024-06-15","jane-smith"
```
### The Wix Image URL Problem
One of the most common failure modes in a Wix-to-Webflow migration is broken images. Wix CMS exports often populate image fields with a proprietary protocol:
`wix:image://v1/68d3a9_1234567890abcdef.jpg/file.jpg#originWidth=1000&originHeight=1000`
Webflow's CSV importer cannot read `wix:image://` URLs. If you upload this CSV directly, every image will silently fail. You must parse and convert these strings into standard HTTPS URLs before importing.
The conversion follows a consistent pattern: extract the media identifier between `/v1/` and the next `/`, then prefix it with Wix's static CDN hostname:
```javascript
function sanitizeWixImageUrl(wixUrl) {
if (!wixUrl || !wixUrl.startsWith('wix:image://v1/')) {
return wixUrl;
}
// Extract the media identifier: everything between /v1/ and the next /
// Example input: wix:image://v1/68d3a9_abc123.jpg/file.jpg#originWidth=1000&originHeight=1000
// Example output: https://static.wixstatic.com/media/68d3a9_abc123.jpg
const parts = wixUrl.replace('wix:image://v1/', '').split('/');
const imageUri = parts[0];
return `https://static.wixstatic.com/media/${imageUri}`;
}
```
Run this transformation across your entire dataset before import. Here is an end-to-end example of how a raw Wix CSV row becomes a valid Webflow import row after sanitization:
**Raw Wix export (not importable into Webflow):**
```csv
Name,Slug,Body,Thumbnail
"Product Launch","product-launch","
","https://static.wixstatic.com/media/68d3a9_abc123ef.jpg","Product Launch | Site","Description"
```
For long-term reliability, download and re-upload images to Webflow's asset manager rather than relying on Wix's CDN. Wix could change CDN URLs or access terms at any time after you've left their platform.
### Structured Data (JSON-LD)
Wix automatically injects JSON-LD schema markup for certain page types — Article schema on blog posts, Product schema on store pages, BreadcrumbList on interior pages. This markup does not transfer to Webflow in any form.
In Webflow, you recreate JSON-LD by embedding a `
```
Document which schema types are present on your Wix site during the audit phase and recreate each one before launch. Use Google's Rich Results Test to validate after the site goes live.
### Rich Text Cleanup
Wix's Rich Text format often includes proprietary markup, custom `` elements, and inline styles. Webflow's Rich Text element will strip unrecognized HTML during import. ([help.webflow.com](https://help.webflow.com/hc/en-us/articles/33961290794771-How-do-I-import-content-into-the-Webflow-CMS)) Pass your content through an HTML sanitizer beforehand and keep only semantic tags: `
`, `
`, `
`, `
`, `
`, ``, ``.
### Static Pages
Static pages (About, Services, Contact) must be rebuilt manually in Webflow's Designer. There is no layout import path. Copy the text content, download images, and recreate the design.
## Step 4: Build in Webflow
This is the most time-consuming step, and there is no shortcut. You are building a new site.
- **Start with global styles** — Typography, colors, spacing. Webflow's class-based styling system is fundamentally different from Wix's widget-based approach.
- **Build components** — Navigation, footer, CTA blocks. Use Webflow's **component** system (formerly symbols) so changes propagate globally.
- **Create CMS collection templates** — Design the template page for each collection (blog post layout, product page layout, etc.).
- **Build responsive from the start** — Webflow gives you breakpoints for desktop, tablet, mobile landscape, and mobile portrait. Test at each breakpoint as you build, not at the end. In Wix, mobile responsiveness is partly automatic. In Webflow, you own every responsive detail — and every responsive bug.
- **Adopt a naming convention** — A standardized methodology like **Client-First** by Finsweet enforces global utility classes, REM units, and semantic HTML tags (``, `