The hardest part of a Wix to Webflow migration is the blog, because Wix's own help centre says it is currently not possible to export blog posts to other platforms. Your CMS collections export to CSV. Your design, your blog and your media library do not export in any form Webflow can read, and Webflow's help centre says plainly that the move "is a rebuild, not a transfer".
This guide covers what you can get out of Wix, three ways to move the blog, the redirect map for each Wix URL pattern, and the domain question: transfer it, point it, or leave it where it is. Every limit comes from Wix's or Webflow's own documentation, read on 4 November 2026.
Wix to Webflow migration: what moves and what does not
Webflow's Wix migration article starts with an audit: every static, dynamic and member page, every content type, font, form, app, custom code snippet and redirect. That audit matters more on Wix than on most platforms, because so little of the site leaves Wix in a usable format.
| Wix component | Export from Wix | Into Webflow |
|---|---|---|
| Page design, layouts, animations | None | Rebuilt by hand; some animations need Webflow Interactions with GSAP or custom code |
| CMS collections you created | CSV, one collection at a time; time fields in UTC+0 | CSV import per Collection, up to 4 MB per file |
| Blog posts | Not exportable to other platforms | Copied by hand or pulled by script, see below |
| Store products | Exportable; digital products are not | Webflow Ecommerce, products live under /product/ |
| Media library | No bulk export of all media at once | Upload to the Assets panel, or import by URL |
| Fonts supplied by Wix | Licensed for use on Wix only | Source and license separately |
| Velo code and Wix apps | None | Rebuild with Webflow features, apps or custom code |
| Existing 301 redirects | CSV export from the URL Redirect Manager | Rewrite and merge into the Webflow redirect list |
Source: Webflow Help Center, Migrate your site from Wix to Webflow; Wix Help Center, CMS export and URL redirect articles; read 2026-11-04
Fonts are the surprise line. Webflow's article warns that fonts available through Wix are licensed for digital use only within your Wix site. If the brand typeface came from Wix's font menu, check whether a web licence is needed before the designer starts.
Dates shift on CMS exports. Wix exports time fields as UTC+0. A post published at 9:00 in New York arrives four or five hours later in the CSV, depending on the season. Convert before you import if the time is shown on the page.
Images imported by URL lose responsive variants. Webflow's import article says images mapped from a URL get no srcset, so upload important images directly. An image field also needs a direct URL that ends in a supported file extension, so check that the Wix media URLs in your export qualify before relying on them.
Getting the blog out of Wix
The blog is usually where the organic traffic sits, and it is the one part of a Wix site with no export button. Wix lists blog export as a feature request it is collecting votes for. That leaves three routes.
| Route | What you get | Where it stops |
|---|---|---|
| Copy by hand (Webflow's suggestion) | Full control of formatting, a chance to edit as you go | Time: every post, image and link is touched once |
| Blog RSS feed | Title, link and summary in a feed you can parse | Wix shows at most the 20 most recent posts |
| Script against Wix's Blog/Posts collection | Title, slug, published date, excerpt, plain and rich content, cover image, categories, tags, author | Rich content must be converted to HTML; developer time |
Source: Webflow Help Center; Wix Help Center, Wix Blog feature request articles; Wix Developers, Wix Blog Collections; read 2026-11-04
Under about 30 posts, copy by hand. It is slower per post but needs no tooling, and most small blogs need an editorial pass anyway.
Over that, script it. Wix's developer documentation describes Blog/Posts, Blog/Categories and Blog/Tags as system collections with read permission set to anyone and every field read-only. The Posts collection includes the slug, the original published date and the post page URL, which are the three fields the redirect map depends on. We would export them to one CSV per Collection, convert rich content to HTML, and keep each file under Webflow's 4 MB limit.
Import in order. Webflow matches reference fields by converting plain text into a slug and looking for an item with that slug. Import Categories and Authors first, then Posts. If a category has a custom slug on Wix, put that slug in the CSV rather than the display name, or the reference imports blank.
Keep the original dates. Map Wix's published date to its own date field and sort by it. Otherwise every post looks as if it was written on import day.
Our WordPress to Webflow migration checklist covers the CSV and reference-field mechanics in more depth; they apply unchanged to a Wix source.
The SEO redirect map for Wix URLs
Rankings are lost on URLs that 404 after launch. Wix uses a small number of fixed URL patterns, which makes the redirect map shorter than on most platforms, as long as you know which ones you have.
| Wix pattern | Example | Webflow URL | Rule |
|---|---|---|---|
| Static page | /about | /about | None if the slug is kept |
| Blog post (default prefix) | /post/my-post | /post/my-post | None: name the Collection URL "post" |
| Blog post, moved to /blog | /post/my-post | /blog/my-post | One wildcard: /post/(.*) to /blog/%1 |
| Blog category | /blog/categories/news | /category/news | One wildcard: /blog/categories/(.*) to /category/%1 |
| Store product | /product-page/red-sweater | /product/red-sweater | One wildcard: /product%-page/(.*) to /product/%1 |
| Language folder | /es/about | /es/about via Webflow Localize | Separate rules for each locale |
| Dynamic pages | Prefix set by the site owner | Collection URL of your choice | One wildcard per prefix, or single rules |
Sources: Wix Help Center, URL structure and blog category articles; Webflow Help Center, redirects and page URLs; read 2026-11-04
Check your prefixes first. Wix lets owners rename the "post" and "product-page" prefixes in SEO Settings, and sets up automatic redirects when they do. A crawl of the live site, or the Post Page URL field from the Blog/Posts collection, tells you what the prefix really is.
Collection pages cannot sit in folders. Webflow's page URLs article says only static pages can be organised in folders, so /blog/categories/news cannot be reproduced exactly. That is why the category row needs a wildcard. On a site with Webflow Ecommerce turned on, /product and /category are reserved for the store, so pick another Collection URL for blog categories.
Escape the old path. Webflow requires a % before special characters in the old path, including the hyphen, underscore, question mark and equals sign. That is why the product rule reads /product%-page/. The new path is written normally.
Order is age. Webflow runs redirects in the order they were added. Add single-page rules before the wildcards that would otherwise catch them.
Stay under 1,000 rules. Webflow sets no hard limit but recommends 1,000 at most, because every rule is added to a file that browsers download. Wix's fixed patterns mean most sites need a handful of wildcards plus single rules for retired pages.
Rewrite old Wix redirects. Export them from Wix's URL Redirect Manager (More Actions, Export redirects). Point each one at the final Webflow URL rather than at another redirect, so nothing chains. Once the domain points at Webflow, Wix's redirects stop running.
Our website migration SEO checklist covers the crawl, the rehearsal on staging and the 30-day watch after launch.
Transfer the domain from Wix to Webflow, or point it
Most people searching how to transfer a domain from Wix to Webflow are trying to do something Webflow does not offer. Webflow is not a domain registrar, so a domain cannot be transferred to Webflow. It is connected by DNS records wherever it is registered.
| Option | What you do | Watch for |
|---|---|---|
| Keep it at Wix, point it | In Wix Domains, Manage DNS Records: add the Webflow A and CNAME records, delete the old ones | Wix says changes can take up to 48 hours to spread |
| Keep it at Wix, move the DNS | Set custom nameservers for a DNS host you choose | Registration stays at Wix; Wix no longer manages the DNS |
| Transfer it to another registrar | Request the EPP code from Wix, start the transfer at the new registrar, then point it | 60-day lock, up to 7 days, business email stops until MX records are re-added |
Source: Wix Help Center, connecting a Wix domain to an external site and transferring a domain away from Wix; Webflow Help Center; read 2026-11-04
Pointing is the shortest route. Webflow's DNS article lists three records: an A record for @ with the value 198.202.211.1, a CNAME for www with the value cdn.webflow.com, and a TXT record for _webflow with the one-time verification value shown in Site settings. Wix's article warns to delete old A records after adding new ones, to avoid a conflict. SSL is issued once the records point at Webflow, which Webflow says typically takes a few minutes.
Transferring needs planning. Wix sends the transfer code to the registrant contact email, and recommends turning off private registration first so the email is not missed. The domain must be unlocked. ICANN rules block a transfer within 60 days of purchase, of a registrant contact change or of a previous transfer. Wix itself recommends keeping the domain with Wix if you can.
Protect email. If the company's mailboxes run on the domain, list the MX records before you touch anything. When pointing, change only the A and CNAME records. When transferring, re-add the MX records at the new host straight away.
Lower the TTL in advance. Webflow recommends dropping the TTL to the lowest value your DNS host allows, typically 30 seconds, at least one full TTL period before the switch. Change the records only when the Webflow site is finished, redirects are added and QA has passed.
The cutover, in order
- Crawl the Wix site, export Search Console's top pages and list every URL with traffic or backlinks.
- Export CMS collections, store products and existing redirects from Wix; pull the blog by script or copy it.
- Download images from the Media Manager, folder by folder, and confirm font licences.
- Model Collections in Webflow and set the blog Collection URL to match the Wix prefix.
- Import Categories and Authors, then Posts, keeping slugs and original dates.
- Rebuild pages, forms and integrations, then add tracking in Site settings.
- Write the redirect CSV with escaped old paths, specific rules before wildcards and separate rules per locale.
- Publish to the webflow.io staging domain and test every row of the redirect map.
- Lower the TTL, then add the Webflow A, CNAME and TXT records and remove the Wix ones.
- Publish to the custom domain, rerun the redirect map against it, submit the sitemap and watch Search Console.
Keep the Wix site and its plan until the redirect report is clean. Google advises keeping redirects for at least a year and expecting rankings to fluctuate while it recrawls; it says permanent redirects do not cause a loss in PageRank.
What this means for your Wix to Webflow migration
We build marketing sites in Webflow and applications in Next.js, so we are not neutral about the destination. Wix is a capable platform, and for a site that sells, books or takes payments its built-in apps may be reason to stay; our Webflow vs Wix Studio comparison covers that decision. This guide assumes it is made.
On most Wix moves, the redirect map is short and the blog is the work. If the blog runs to hundreds of posts, we would script the Blog/Posts export rather than copy by hand, and we would put the URL map in week one of our four-week marketing-site process, before design starts. Our Webflow builds take two to three weeks per site, and our largest Webflow CMS holds over 1,200 items; our Webflow CMS limits guide shows how much room a plan leaves. Our marketing website service page explains how we scope a Wix to Webflow migration.
