Wix to Webflow migration that keeps your search traffic

Wix can't export a working site, so we move Wix sites to Webflow by rebuilding the pages and carrying the data across. Every Wix URL that earns visits or links keeps its path or answers with a 301 to the closest Webflow page, and metadata, canonical tags and every redirect get verified on staging before Wix lets go of the domain.

Get a proposalMessage us on WhatsApp
Dardo / Editorial illustration
On this page

Why teams move from Wix to Webflow

Teams leave Wix for ownership and limits, more than for price or speed. Wix's help center says a site has to be hosted and operated on Wix's servers, because its architecture doesn't support external hosting, so nothing built there can run anywhere else. Webflow is hosted too, but paid Workspace plans add code export, and the Premium site plan holds 20,000 CMS items across 40 Collections under Webflow's 2026 lineup, checked in October 2026.

  • CMS ceilings: once a Wix collection reaches its plan's item limit, nothing more can be added; Light stops at 1,500 items and Core at 4,000
  • A blog post prefix that can be renamed but never removed, and dynamic page URLs assembled from collection fields
  • Structured data that Wix accepts only on static pages, under 7,000 characters per markup
  • A ceiling of 5,000 redirects per site, none of which can start from the home page
  • A designer who wants Webflow's Designer and Collections with reference fields instead of Wix's editor

Wix and Webflow compared for this move

Both platforms host the site for you, so the useful questions are what can leave later, how far the CMS and URLs stretch, and who pays for editors. Prices are US figures before tax on yearly billing, read in October 2026; Wix shows US dollar prices for reference and charges by location.

Wix and Webflow compared for this move
TopicWixWebflow
Hosting and exportRuns only on Wix's servers; no site exportHosted by Webflow; code export on paid Workspace plans
Editors2 collaborators on Light, 5 on Core, 10 on BusinessOne full seat included; each Limited seat USD 15 a month
CMS capacity1,500 items on Light, 4,000 on Core, 20,000 on BusinessPremium: 20,000 items in up to 40 Collections
URL structureFixed blog post prefix; dynamic item URLs built from one or more fieldsFree slugs on static pages; each Collection item at the Collection's path plus its slug
RedirectsUp to 5,000, working only with a custom domain on WixNo hard cap, about 1,000 recommended; capture groups for patterns
Sites passing Core Web Vitals, US mobile, September 202688.7%80.2%
Entry plan with a CMS blogCore at USD 29 a monthPremium at USD 25 a month, seats extra

What you can take out of Wix, and what stays

Wix lets data out, not the site. Pages, layouts and Wix's own apps, such as Wix Bookings, Wix Events, Wix Stores and the members area, stay on Wix's servers, so each page is rebuilt and each feature is replaced in Webflow or by a separate service. Webflow's own Wix migration guide adds that fonts licensed through Wix don't come with you.

Blog posts are the hard part. Wix says it isn't possible to export blog posts to other platforms. Its Blog API is the complete route: the List Posts endpoint returns up to 100 published posts per request with the full rich content, SEO fields and URL, and we convert that structured JSON into HTML for Webflow's rich-text fields.

  • CMS collections, the data behind dynamic pages: CSV export, including hidden and system fields
  • Store products: CSV files of at most 5,000 rows each, with digital products left out by Wix
  • Site members: Wix won't export them as members for privacy reasons, so they leave as contacts and register again
  • Contacts, orders, form submissions and bookings: CSV from each dashboard, exported again on launch day because they change daily
  • Images and files: downloaded from the Media Manager and uploaded to Webflow, including every image inside a post

How Wix content maps to Webflow

Wix keeps structured content in CMS collections that feed dynamic pages, and those map well to Webflow Collections with template pages. The addresses need more care. Wix builds a dynamic item URL from the collection name and one or more fields, as in its own example /felines/large/bengal, while a Webflow Collection item sits at one path plus its slug. Collection design and template builds are handled by our Webflow development team.

How Wix content maps to Webflow
WixWebflowHow it moves
Static pagesPages laid out again in Webflow's DesignerRebuilt; auto-named slugs such as /general-1 renamed and redirected
Blog posts at /post/{slug}A Posts Collection whose URL is postBlog API, rich content converted to HTML, CSV import with the same slugs
Blog categories and tagsA Categories Collection referenced from postsImported before posts; category URLs redirected 1:1, thin tags left to 404
CMS collection and its dynamic pagesA Collection with a template pageCSV mapped field by field; multi-level URLs redirected to the new item slug
Products at /product-page/{slug}Webflow Ecommerce productsProduct CSV mapped to Webflow's product import; each old URL redirected
Booking services and eventsStatic or Collection pages with a booking or ticketing tool embeddedData kept from CSV; /service-page/ and /event-details/ URLs redirected
Wix FormsWebflow formsRebuilt with their destinations; past submissions kept as CSV
Members areaNo built-in equivalent since Webflow retired User Accounts in January 2026Members kept as contacts; Wix profile pages are noindex, so no redirect
Redirects already set on WixWebflow 301 rulesEach old source re-pointed at its final URL so nothing chains

How we move a Wix site to Webflow

This is our website migration process fitted to Wix: inventory, map, rehearse, switch, watch. The inventory starts from Wix's sitemap index, which splits into sub-sitemaps for pages, posts, categories, products, bookings, events and dynamic pages. We add twelve months of Search Console data on landing pages and links, plus the rules in Wix's redirect manager, and read the real prefixes from those files, because owners can rename the post and product prefixes. Our guide to migrating from Wix walks through the manual version.

The data comes out while the Wix plan is still active, then we design the Webflow Collections around it. The site is built on a staging address hidden from search engines, with /post/ slugs kept as they were and auto-named pages given real slugs. Fonts are licensed for use outside Wix before launch.

Redirects have to live in Webflow, because Wix's 301s only work while a custom domain is connected to Wix. Our redirect map generator matches the Wix sitemap against the staging sitemap for a first pass; the final map is reviewed row by row, with one row per old URL, one hop to its final page, never a mass redirect to the home page. The rules go into Webflow with special characters escaped, and every row is requested on staging.

Webflow's Wix guide recommends dropping the DNS TTL to the lowest value the host allows, often 30 seconds, at least one full TTL period before the switch, so we do that first. In the launch window the root A record and the www CNAME point at Webflow, MX records stay untouched, the sitemap goes to Search Console and real form entries are sent. A transfer away from Wix, if wanted, comes later. At day 30 and day 60 we review indexed pages and clicks per page against the numbers recorded before launch, then hand over the site, its DNS settings and the redirect list.

Checks before and after the domain moves

Wix sites carry URL quirks that a generic checklist misses. Each item is tested on staging, then again once the domain points at Webflow; the general list lives in our website migration SEO checklist.

  • Every URL from the sitemap index, Search Console and the old Wix rules returns one 301 to a 200 page, or a planned 404 or 410
  • Auto-named pages such as /copy-of-home and /about-4 answer at their new slugs, with the old addresses redirected
  • Query-string pages, such as restaurant menus at /menu?menu=lunch-menu, have their own rows in the map
  • Posts under /post/ resolve unchanged, and /blog/categories/ pages reach their replacements in one hop
  • Titles, meta descriptions and social images match what a crawl of the live Wix site recorded
  • Canonicals use the new URLs, and hreflang covers every locale if the site runs in more than one language
  • Structured data added to the former dynamic pages, where Wix allowed none, and checked with the Rich Results Test
  • No post image still loading from Wix's media hosting, and every form delivering to a real inbox
  • Analytics and the consent banner tested, and 404s checked daily for the first two weeks
  • Clicks per page tracked against pre-launch figures through day 60, with the Wix plan cancelled only after that review

When staying on Wix is the better call

On fees alone the move doesn't pay: Wix Core is USD 29 a month in the US and Webflow Premium with one editor seat is USD 40, on yearly billing in October 2026. Our advice is to stay when the site does its job and none of the limits above affects it.

  • Speed alone: HTTP Archive's report for September 2026 puts Wix ahead, with 88.7% of US Wix sites passing Core Web Vitals on mobile to Webflow's 80.2%, as our website platform speed report shows
  • Bookings, events, a store and a members area all run inside Wix today, and each would need a replacement on Webflow
  • The team wants a stronger visual editor but no new host: Wix Studio, compared in Wix Studio vs Webflow, keeps the site where it is
  • The aim is to own the code or cut running costs: WordPress or a coded site fits better, as Wix vs WordPress explains

If your site runs on Squarespace rather than Wix, the matching plan is our Squarespace to Webflow migration.

What Webflow costs after Wix, and what drives the quote

Webflow charges per site and per editor, while Wix bundles collaborators into each plan. The example below is a 20-page site with a 60-post blog, edited by the owner and one colleague, in US dollars billed yearly as of October 2026. To run your own numbers, use our Webflow pricing calculator, and Webflow pricing in 2026 covers the new plans.

What Webflow costs after Wix, and what drives the quote
Line itemOn Wix todayOn Webflow after the move
Site planCore, USD 29 a monthPremium, USD 25 a month
Second editorIncluded: Core allows 5 collaboratorsLimited seat, USD 15 a month
Online storeA basic store is part of CoreEcommerce Standard, USD 29 a month, 500 items, 2% transaction fee
Three years for the example siteUSD 1,044USD 1,440

Dardo doesn't publish a migration price; we quote from the URL inventory. On a Wix move the drivers are the URL and template count, the size of the blog that has to come out through the API, the collections behind dynamic pages, the store, booking and member features to replace, integrations and languages. Published prices from other providers, by platform pair and site size, are in what a website migration costs.

Questions before you choose

Can we export our Wix site to Webflow?

Not as a site. Wix says its sites have to run on Wix's servers, and there is no code export, so every page is rebuilt in Webflow. The data travels separately: collections, products, contacts and form entries as CSV files, media from the Media Manager and blog posts through Wix's Blog API.

Will we lose rankings when we leave Wix?

Expect some movement for a few weeks while Google recrawls the site, which Google's site-move guidance describes as normal. Avoidable losses come from Wix URLs that stop answering, and Wix's own redirects stop applying once the domain points away, so each address that earns visits or backlinks is given its own Webflow 301. We compare clicks by page with the baseline at 30 and 60 days.

Can we keep our Wix blog URLs in Webflow?

For posts, yes. Wix keeps posts under a /post/ prefix, and a Webflow Collection whose URL is post, with the same slugs, gives each post the address it has today. Category, tag and archive pages under /blog/ change shape, so they get 1:1 redirects, a redirect to the blog index, or a 404 for thin tags.

What happens to Wix dynamic pages?

The collection behind them exports as CSV and becomes a Webflow Collection with a template page. Wix can build a dynamic URL from several fields, while a Webflow item lives at its Collection's path plus one slug, so multi-level URLs each get a redirect. Wix allows no structured data on dynamic pages, so the new templates can add it.

What about bookings, the store and the members area?

The data can leave; the features can't. Products and bookings come out as CSV, and members leave as contacts, since Wix doesn't export members for privacy reasons. Webflow sells no booking feature, and its User Accounts ended in January 2026, which leaves bookings and member logins to a separate service. A store fits Webflow Ecommerce Standard up to 500 items.

How long does a Wix to Webflow move take?

Scope sets the build time: URLs, blog size, collections, the Wix features that need replacing and how fast decisions come back. Google then needs its own time: its guidance allows a few weeks before most of a small or medium site's pages have moved in search, and we schedule reviews at day 30 and day 60.

What happens to our Wix domain and email?

A domain bought from Wix can stay registered there and point to Webflow through its A and CNAME records, and leaving the MX records alone keeps email working. If you want to transfer it to another registrar, that can happen after launch, outside the switch window. Domains bought elsewhere and only connected to Wix just get new records at the registrar.

Is Webflow cheaper than Wix?

Usually not. For a site with a blog and two editors, Wix Core is USD 29 a month billed yearly in the US and Webflow Premium with one Limited seat is USD 40, as of October 2026. Teams move for CMS limits, URL control and design freedom, and we quote the migration itself from the URL inventory.

From the blog

Sources & further reading

Sources behind this page, with further detail from the original publishers.

Start with the Wix sitemap

Send the Wix address and the features it runs, such as a blog, store, bookings or members. We reply with the questions that set the scope: how many URLs answer, how the posts come out and what needs a replacement.