Webflow to Wix Studio: the complete migration guide

No, and it's worth understanding why so you don't lose time trying. Webflow's code export produces HTML, CSS, JavaScript and your Assets panel images. Wix states that importing a site created outside of Wix isn't supported, so there's nothing to import that file into. Your content is a different story: CMS collections, products, orders, form submissions and your full 301 redirect list all export to CSV and all import into Wix. The design gets rebuilt, the content gets moved.

Webflow removed the legacy Editor on 4 August 2026. Content editing now happens inside the Designer under roles assigned to seats, with existing Editor users migrated to a free client seat or limited seat and given the Content editor role. If your team published through the old Editor and the workflow changed under them this month, that's why. It affects every Webflow site with a non-designer publishing content, and for a lot of teams it's the reason they started looking.

It depends which plan you were on, and Webflow's own announcement is worth reading before you decide. From 13 May 2026 it merged the CMS and Business Site plans into a single Premium plan and, in its words, “the yearly plan is increasing to $15/month, the monthly plan increases to $25/month” for Basic, with the static page limit doubling to 300. Former CMS customers pay slightly more. Former Business customers pay less at the base price but get half the bandwidth, 50GB instead of 100GB, so restoring it costs an add-on. Existing sites moved at their first renewal on or after 29 June 2026, or 16 November 2026 on Freelancer and Agency Workspaces. The bigger number is usually not the Site plan at all: it's the editor seats, since Webflow bills additional editors and content editors separately. Compare total cost of ownership rather than the headline plan price.

This is the migration where you're best placed to avoid it, because Webflow hands you your own redirect map on the way out. Every 301 you've built exports to CSV, so the URL history you'd normally have to reconstruct arrives as a file. Wix Studio imposes no path structure on standard pages, so most addresses can stay identical, and CMS page paths can be preserved because Wix's dynamic page prefix is editable. The real risk is metadata: titles, descriptions and Open Graph live in Webflow's page settings and appear in no export, so they're pulled from a crawl and diffed against the new site before the domain moves.

Mostly not. Standard pages keep their paths, because neither platform forces a structure on them. Collection pages come down to how the Wix CMS is set up: the dynamic page prefix is a default you can edit, so an existing /blog/post-name or /projects/project-name structure can be carried across rather than redirected. Where something does change, it gets a mapped redirect merged into the file Webflow exported, never a blanket rule pointing an old section at a new index page.

They become Wix CMS collections, and the concepts line up closely enough that this is translation rather than redesign. Each Webflow collection exports as its own CSV; Wix imports up to 50,000 items per file, so volume is rarely the issue. Two things need handling rather than pasting. Rich text exports as HTML, and multi-reference fields export as comma-separated text, which has to be rebuilt into real reference fields in Wix or the relationships you designed quietly disappear.

This is the single most expensive mistake available on this move. Webflow states that image and file URLs in a CMS export point back to the site you exported the collection from, and that if you delete that site those assets and links break, including images inside rich text. Webflow documents no bulk asset download, so the files come down by hand before anything is cancelled. Practical rule: keep the Webflow site paid and live until the Wix site is serving your domain and the 30-day monitoring window has opened clean.

They get rebuilt, not ported, and in the case of forms that's an improvement on what Webflow itself offers off-platform. Webflow doesn't process form submissions on exported sites and points you at a third-party form service. On Wix, forms, submissions, notifications and follow-up automations are native. Interactions depend on Webflow's own JavaScript bundle, so the motion is rebuilt with Studio's animation tools, matched to intent rather than copied frame for frame. Your existing submissions export separately and come with you.

You can usually drop it. Webflow sunset User Accounts on 29 January 2026 and stated the data wouldn't be migrated to the CMS, which pushed a lot of sites onto Memberstack or Outseta. Wix has native members, gated content and access groups, so the gating gets rebuilt inside the platform and the extra subscription stops being necessary. Your member list is the part to plan for: it comes from your current provider's export, not from Webflow, so pull it before you cancel anything.

From €1,750, quoted as a fixed price before anything starts, and two to five weeks from kickoff to launch plus a 30-day monitoring window that runs while you're already live. The number moves on how many CMS collections need modelling, how much interaction work has to be rebuilt rather than simplified, and whether there's a store. A brochure site with one collection sits at the bottom of that range. Worth putting against it: what you currently pay for Webflow plans and seats, plus anything you added after the User Accounts sunset.

The exports are genuinely easy, and for a small site this is doable. Webflow gives you clean CSVs for collections, products, orders, submissions and redirects, and Wix imports all of it. Where it turns is specific. Pulling every CMS image down by hand before the URLs die is tedious and unforgiving. Rebuilding multi-reference fields from comma-separated text is fiddly and silent when it goes wrong. Re-entering metadata across a large site from a crawl is where organic traffic actually gets lost. And the design rebuild is the real work, because a Webflow site is usually well built and matching it takes more than approximating it. The reliable signal is your CMS: one collection and a handful of pages is a weekend. Four collections, a store, and a redirect file with hundreds of rows is not.