MigrationsWixWebflowRoute 02 of 4

Wix to Webflow, with every app-shaped URL pointed somewhere before your domain moves

Wix did not only host the site. It chose the addresses, ran the bookings, stored the products and drew a second layout for phones. Moving means taking each of those decisions back, and it means the biggest redirect map of the four routes, because more of your URLs change shape here than anywhere else.

The URLs Wix chose for you

  • /post/…Wix Blog
  • /product-page/…Wix Stores
  • /service-page/…Wix Bookings
  • /event-details/…Wix Events
  • /blog/categories/…Blog taxonomy
  • /forum/…Wix Forum
  • /profile/…Members Area
  • /#!page/c1ktjThe pre-2016 editor

You did not pick these prefixes and you cannot flatten them while you are on Wix. On Webflow they become whatever you decide, which is the point of moving, and also the reason this route’s map is the largest job in the family.

There is no export button, so the live site is the inventory

Wix has no full-site export. What a particular site will hand over depends on which apps are installed and which plan it is on, so the first job on this route is finding that out in writing rather than assuming it, and everything the platform will not give up is recovered from the site while it is still serving traffic.

Usually comes out

  • Wix Stores products, as a CSV
  • Contacts and CRM records
  • Invoices and billing history
  • Media library files, downloaded one by one
  • Form submissions, exported from the inbox

Each of these is its own export, in its own place, on its own day. None of them is a backup of the site.

Stays behind

  • Pages, sections and every layout
  • Blog posts as structured content
  • Bookings services, staff and availability
  • Events, tickets and attendee lists
  • Forum threads and member accounts
  • Velo code and Wix Data collections
  • Member passwords, which never transfer
  • Fonts, colours, spacing and interactions

So where the rest comes from

A full crawl of the live site, the sitemap Wix generates, the indexed pages in Search Console and the landing pages in analytics. Four lists, reconciled into one, and the places where they disagree are exactly where the pages nobody remembers are hiding.

Images sit on the Wix CDN behind sizing parameters. They come down at full size and go up to Webflow as real assets, because a hotlinked image dies the day the subscription does.

Classic Editor or Wix Studio? The classic editor positions elements absolutely and keeps a second, hand-adjusted mobile layout. Wix Studio is genuinely responsive. Neither converts to Webflow, everything is redrawn either way, but a Studio site usually has a cleaner content model to read from, and the answer changes which parts of the estimate are large.

Every Wix app is a dependency, and half of them are running the business

A Wix site is rarely just a site. It is a stack of apps that quietly took over bookings, payments, memberships and the inbox. Each one gets an answer here (a replacement, an embed, or an honest “this does not exist on Webflow”) before a single screen is designed.

  1. Wix Bookings

    The calendar your revenue actually runs through

    Webflow does not do bookings. It stays embedded exactly as it is, moves to a scheduling product, or the migration waits until you have decided which.

  2. Wix Stores

    Products, variants, orders and payments

    Webflow Ecommerce for a genuinely small catalogue. Anything larger keeps a real commerce platform behind a Webflow front end.

  3. Wix Restaurants

    Menus, online orders and table reservations

    No Webflow equivalent. Re-plumbed onto a third party, or you stay, and re-plumbing how a kitchen takes orders is not a website project.

  4. Wix Events

    Ticketing, RSVPs and attendee lists

    The pages become a CMS collection. The money stays with a ticketing product, and the historic attendee data does not follow.

  5. Wix Blog

    Posts, categories, authors and archives

    A CMS collection with named fields. This is the one that maps cleanly, and it is usually the one carrying the rankings.

  6. Wix Forms and Inbox

    Submissions, notifications and the enquiry archive

    Webflow forms with an automation behind them. Export the existing submissions before anything is switched off. That archive is often the only copy of a year of enquiries.

  7. Members Area and Pricing Plans

    Accounts, gated content and recurring billing

    Memberstack or an equivalent. Passwords never transfer from any platform, so every member re-registers, plan the email that tells them so.

  8. Velo and Wix Data

    Custom code and database collections

    This is an application, not a website. It needs its own host and its own plan, see the custom-code route, because that is the project you actually have.

  9. Wix Chat and Automations

    Live chat and the follow-ups nobody remembers configuring

    Third-party equivalents, wired again by hand. Cheap to replace, easy to forget, and noticed immediately when a lead goes unanswered.

  10. The Wix redirect manager

    The 301s already protecting URLs you changed years ago

    Exported and carried across. Losing these is how a site loses rankings it had already recovered once, and it is the single most-forgotten artefact on this route.

Selling through Wix Stores? Every commerce warning on the Shopify route applies to you word for word. Running Velo? The project you have is the custom-code route, not this one.

The redirect map, in Wix’s own URL shapes

The good news is that the prefixes are consistent, so most of the map is wildcards rather than one row per page. The bad news is that nearly every address changes, which is why this map is written first and tested against the real URL list before DNS is touched.

Example redirect rules for a Wix site moving to Webflow
Wix URLWebflow URLRuleWhy
/post/how-we-work/blog/how-we-work301 · wildcardEvery Wix Blog post carries the same prefix. One rule covers all of them.
/blog/categories/pricing/blog/category/pricing301 · wildcardOnly if the archive is rebuilt as a collection page. If it is not, it points at /blog.
/product-page/leather-tote/shop/leather-tote301 · wildcardWix Stores puts every product behind one prefix, whatever collection it appears in.
/service-page/60-minute-facial/services/60-minute-facial301 · wildcardBookings services are pages too, and they are usually the best-ranking ones on the site.
/event-details/spring-open-day/events/spring-open-day301 · wildcardSame shape again. Past events get a destination rather than a dead end.
/copy-of-about410 GoneRetiredDuplicated pages get indexed. Retire them deliberately instead of leaving soft 404s.
/#!about/c1ktj/aboutClient-sideA pre-2016 Wix address. Nothing after the # reaches the server, so no 301 can see it.
/about/aboutUnchangedThe cheapest ranking protection there is: do not move the URL.

Scroll the table sideways to read every column.

The fragment nothing can redirect

Sites built on the pre-2016 Wix editor were addressed as/#!page-name/c1ktj. Everything after the #is never sent to a server, so no 301 rule on any platform can see it. Those URLs are caught in the browser instead: the landing page reads the fragment and forwards to the right destination. It is a small piece of script and it is the only thing that works.

Renaming a page renamed its URL

On Wix a page slug tends to follow the page name, so teams have been quietly changing addresses for years by tidying up the menu. That is why the inventory is built from indexed history and analytics rather than from today’s navigation, the URLs that still earn traffic are frequently not the ones the site currently links to.

The domain may be held at Wix

If the domain was bought through Wix, then Wix is the registrar or at least holds the DNS. Cutover means changing records inside that account, or moving the registrar first. Either way it is planned days ahead, with the TTL dropped in advance. It is also the one part of launch day that cannot be done in five minutes if nobody can find the login.

Six phases, and the second one can still stop the project

Most projects run four to eight weeks end to end, across discovery, design, build, QA and launch. Timelines hold because the sequence is the same every time. This route puts the app audit in phase two, before any design exists to defend, so that “do not move” is still an available answer when it is the right one.

  1. Rebuild the inventory from outside

    There is no export to start from, so the list is assembled from a full crawl of the live site, the Wix sitemap, the indexed pages in Search Console, the landing pages in analytics, and the rules already sitting in the Wix redirect manager.

    YoursOwner access to Wix, Search Console, analytics, and whoever holds the domain.

  2. Audit the apps before anything is designed

    Which apps are load-bearing, what replaces each one, what that costs, and what simply stops existing. It is written down and agreed here, because this is the last phase where the honest answer can still be "do not move".

    YoursAn hour with the people who actually run the bookings, the shop and the inbox.

  3. Model the content the apps were holding

    Everything Wix kept inside an app becomes a CMS collection with named fields, posts, services, events, listings. This is where a blog with four kinds of post stops pretending to be one kind of post.

    YoursHalf an hour to tell us which fields your team genuinely fills in.

  4. Design once, for every width

    The classic Wix editor draws a desktop layout and a second mobile layout that agree by hand. The rebuild is one responsive design, so a change made once is a change made everywhere.

    YoursBrand assets, and copy for anything being rewritten rather than moved.

  5. Content, assets, and the largest map of the four

    Media pulled down from the Wix CDN at full size rather than hotlinked, content into the CMS, and every redirect rule written against the real URL list and fired on the staging domain before DNS moves.

    YoursExport your form submissions, and sign off that nothing important is missing.

  6. Cutover, then cancel, in that order

    TTL dropped ahead of the switch, DNS changed, sitemap submitted, Search Console and the 404 log watched for weeks. Both hosts answer during the window, so there is no moment when nothing is live.

    YoursNothing on the day. Do not close the Wix plan because the invoice arrived.

What a URL structure looks like when somebody chose it

Victory Real Estate Group was a build rather than a Wix migration, and we are not going to claim otherwise. What it shows is the thing this route is buying you: an address for every listing that was decided rather than inherited, which is the same decision a redirect map forces on every page of a Wix site.

Victory Real Estate Group homepage built by Devdwell, a night satellite map behind the company name with a single Search now action
Listing architecture designed for search: one address per listing, chosen deliberately.
Victory Real Estate Group on a phone. The search action sits directly under the headline with the map hero behind it
One layout, every width: not a desktop design and a second mobile one.

Victory Real Estate Group

Commercial real estate 2024

Listing architecture rebuilt for search, with inquiry forms placed where intent actually peaks.

+60%
inquiries
0.00
layout shift
victoryrealestategroup.com

When you should not move off Wix

Wix is a capable product and a great many businesses on it are correctly served by it. These are the six cases where we say so on the first call, and there is no proposal afterwards.

  1. Wix Bookings is the business

    If the calendar is where the money is, moving the pages around it is cosmetic. The embed behaves identically on either platform, and you will have spent a budget to change the frame around it.

  2. Wix Restaurants is taking your orders

    Ordering, menus and reservations have no Webflow equivalent. Migrating means re-plumbing how a kitchen works to gain a faster homepage, and that trade is almost never worth making.

  3. You are on Wix Studio and nothing has refused you

    The newer editor is genuinely responsive and considerably more capable than the classic one. Platform lock-in is only a cost when it bites, if nobody has been told no, you are paying to solve a problem you do not have.

  4. Velo is holding an application together

    Custom code plus Wix Data collections is software. Webflow will not host it, and rebuilding the front end alone leaves you with the same application and a new hosting bill.

  5. The site earns nothing to protect

    The ranking argument only pays if there are rankings. On a site with no organic traffic, a migration protects nothing, put the money into content and see whether anything moves first.

  6. Nobody will own the content afterwards

    A CMS your team never opens is the trap you are already in with a new login. If there is no named owner for content after launch, the move buys a year at most.

The case for moving is a specific one: your addresses are shaped by apps you no longer use, your layouts are drawn twice and only agree by hand, or search is worth more to you than the convenience you are paying for. If none of those is true, stay where you are.

Not sure Webflow is the destination yet?

The comparison argues both sides of the platform question with no migration attached to it. The other three routes are written the same way as this one, with their own platform’s hazards rather than Wix’s.