Moving from Wix to Webflow without rebuilding twice

The reason people put off moving from Wix to Webflow is that it looks like an all-or-nothing weekend: take the old site down, rebuild everything, hope the new one is ready before anyone notices the gap. That fear rests on a false premise. Nothing about this move requires downtime. Webflow gives every project a free staging address the moment you create it, so the entire rebuild happens there while the Wix site keeps earning exactly as it was, until the moment you point the domain somewhere new. The work is not smaller than people think — it is ordered differently: inventory first, staging build second, apps third, cutover last, not scrambled together the way a rushed weekend forces it to be.

That ordering matters because the two platforms do not talk to each other. There is no import button, no plugin, no shared format. Wix does not offer a code export in the first place, so whatever exists on the current site has to be re-entered by hand regardless of how similar the finished pages end up looking — a rebuild from a checklist, not a transfer that keeps failing.

Before Webflow, an inventory of what Wix is currently serving

Open a crawler — for a Wix site under a few hundred pages this takes minutes, not a specialist tool — and produce a flat list of every URL currently live. Against each one, note whether it carries search traffic, whether other sites link to it, and roughly what it's about. This is the step people skip as busywork ahead of the "real" job of building in Webflow, and it's the step that decides whether the move costs you anything. A URL with real traffic needs a one-to-one redirect to wherever the same content lives on the new site; a URL nothing points at is available to drop, a legitimate outcome rather than a gap, since carrying every old page forward for completeness adds maintenance weight for pages that were never doing anything. The fuller method for turning this inventory into a redirect map, including which duplicate-URL traps inflate it for no reason, is in keeping your URLs when you move.

While you are in the Wix dashboard, pull the content too: page copy, images at full resolution, form field configurations, and a note of which pages use which apps. None of it transfers automatically, so collecting it before you open Webflow saves the re-entry from becoming a scavenger hunt across two open tabs.

Where reach fits before you open either dashboard

If what is actually moving is a single person's page — a portfolio, a consultant's one-pager, a CV that behaves like a website — the honest first question is whether "migrate to Webflow" is even the right project, because reach builds that page faster than either platform lets you configure a redirect. Upload the CV you already have, answer a short form, and a complete page is generated in about twenty seconds; you can be live on a free yourname.joinreach.app subdomain in under two minutes — often faster than inventorying a Wix site and relearning Webflow's box model to reproduce three sections and a contact link.

The limit is real: reach makes exactly one page, with no sub-pages, no CMS, and no contact form beyond a mail link. If the Wix site being replaced has a services page, a blog with its own ranking history, or more than one URL that matters, reach is the wrong tool for it — Webflow's collections and multi-page structure are built for that job instead.

Build on staging while the old site keeps earning

Webflow assigns every new project a .webflow.io address automatically, live from the moment you start. Build the entire site there — every page, every collection, every form — as the real site under construction, not a preview. Do not touch the Wix domain or account until staging has been checked page by page, form by form, with nothing left as a placeholder. This removes the downtime fear entirely: the Wix site is still what visitors and search engines see for the whole rebuild, which can run days or weeks without anyone who currently uses it noticing a thing. One cost lands earlier than people expect, though: Webflow's free Starter plan caps a project at two published pages, staging included, so anything beyond a two-page site needs the Basic or Premium site plan selected before the staging build can go further — that subscription starts running during the rebuild, not at cutover. Test staging on an actual phone rather than the browser's device emulator, which won't catch a validation rule that only breaks with a real keyboard.

The Wix trap that costs the most rebuild time: absolute positioning

Wix's classic editor lets you drop any element at any pixel position on the canvas, with nothing snapping it onto a grid unless you ask. That freedom is the entire personality of Wix, and it is also the single biggest reason a Wix-to-Webflow rebuild takes longer than people budget for. A page built with elements pinned to arbitrary coordinates has no underlying structure to read off and re-enter — no column count, no consistent gutter, no relationship between elements a new tool can infer. You are not porting a layout; you are rebuilding, from scratch, the structure that would have produced the picture in front of you, in a system where every position is an expression of padding, margin and alignment rather than a coordinate.

The mobile layout compounds this. Wix's classic editor generates a separate mobile version from the desktop one, adjustable independently, so a Wix site edited for a while often has desktop and mobile layouts that have quietly drifted apart — a button moved on one, a headline shortened only on the other, invisible until you check. Rebuilding in Webflow is the moment to stop carrying that drift forward: decide the mobile layout on its own terms rather than matching whatever the old version ended up as.

Budget for this specifically. A five-page site with careful absolute positioning on every page takes noticeably longer to rebuild than one that stuck close to Wix's own grid-assisted tools, because the second already has something close to a structure to translate. The first does not, and pretending otherwise is where rebuild estimates go wrong.

Apps with no Webflow equivalent, and what actually replaces them

Wix's App Market covers ground Webflow's own feature set does not: bookings, email marketing, review widgets, membership areas, live chat, each built by a vendor that only builds that one thing. None of it transfers, and unlike the layout work above, this is a research problem, not a rebuild problem — you are choosing a new vendor for each function, not reconstructing what the old one did.

Some of it has a direct swap: a booking app maps onto a Webflow-compatible booking tool, usually a third-party embed since Webflow's own toolset has no scheduling; a membership area maps onto Webflow's native Memberships feature, closer to a real replacement since it's Webflow's own product; basic email capture maps onto a form plus whatever email tool you already use. Some has no clean equivalent — a loyalty program or a niche app like a restaurant menu builder often has nothing to embed, and the honest options are a lesser general embed or dropping the feature. Make this list before staging is finished: discovering a missing booking flow the week the domain moves is a worse week than discovering it while Wix still takes bookings.

The cutover hour

Once staging is fully tested and the redirect map is written, the domain move is short and goes in a fixed order. First, lower the TTL (time to live) on the domain's DNS records a day or two before cutover, if your registrar allows it — a shorter TTL narrows the window where some visitors reach the old site and some reach the new one, though it doesn't remove that window, since propagation still takes minutes to hours. Second, point the domain's DNS at Webflow rather than Wix, following Webflow's own instructions for the record types it asks for — the step people call "the migration," though by now it's close to the smallest piece of work left. Third, verify the domain inside Webflow and wait for the SSL certificate to issue, out of your control once DNS has propagated. Fourth, once the new domain is live, work down the redirect map, checking that the highest-traffic old URLs land on their actual replacement rather than a generic homepage redirect — a redirect to the wrong destination reads to a search engine much like a dead page, and the ranking signal does not follow it anywhere.

Keep the Wix account active for a few days after cutover rather than canceling it immediately. That overlap is cheap insurance against a redirect gap or a DNS record that turns out to matter, like an MX record if email runs through the same domain. None of this has to happen at 2 a.m. or on a weekend — the old site keeps serving visitors through the propagation window regardless of when you start, the payoff of building on staging first: cutover is a sequence to follow, not a deadline to survive.

What each platform costs, for the same decision

Tool	Price	Billing	What it's for here
reach	$0 subdomain, or $4.99 Premium	per month, or $49/year	The single-page replacement, if that's actually all the Wix site is
Wix Light (what you're likely already paying)	$17	annual, paid in full	Where the content currently lives
Webflow Basic	$15/mo annual, $25/mo monthly	custom domain, no CMS	Multi-page site with no structured content
Webflow Premium	$25/mo annual, $39/mo monthly	CMS collections	Multi-page site with a blog, a project list, or any repeating content type

Prices checked August 2026. Webflow's workspace plan and any seats run alongside the site plan above, a separate line item if more than one person needs editor access — the Webflow review goes through all four billing axes. If the Wix site you're leaving is genuinely one page, the reach row above is worth taking seriously before either Webflow tier, since it skips both the box-model relearning and the redirect-map work above. The Wix review covers the template lock-in that often triggers a move like this, and the switching website builders pillar covers the parts of a migration that apply regardless of which two platforms are involved.

Who this move actually suits

Webflow is the right destination for a Wix site that has outgrown Wix's feature set in a specific, nameable way — a content type that needs to repeat with structured fields, a design requirement Wix's editor cannot produce, or CSS-level control over every breakpoint instead of the mobile-sync workarounds above. It is wrong for a site that just feels dated; a current price, a recent example and design attention on the platform you're already on is cheaper and carries none of the redirect risk here. And if the site never was more than one page, the honest comparison isn't Wix against Webflow at all — it's whether either is worth the rebuild when the job was always a single page that a CV-driven generator produces in under two minutes.