A limited source export rebuilt into a complete destination store across one cutover seam.

Wix to Shopify migration as a planned rebuild

The export gives you less than you expect, the content lives inside the editor, and the URL map has to be built from a crawl of the live site.

Where the work goes

You get the products. You rebuild the rest.

Set the expectation first, because it is the whole shape of the project.

Wix is a closed system. There is no database access, the export options are narrower than most source platforms, and a great deal of what makes the site look finished exists only inside the editor.

In practice, product data can usually be extracted in a workable form. Content is a different matter: page layouts, galleries, embedded blocks and design elements do not export into anything portable, so pages are rebuilt as Shopify templates and sections rather than migrated.

Historical order and customer data is the area where expectations most often need managing. What can be retrieved varies by plan and by what the store has actually recorded, and a migration plan that assumes a complete order history is a plan that will be revised in week two.

The compensating factor is that Wix stores are usually smaller and younger than the businesses on other platforms, so a reconstruction is proportionate. The move is frequently the right moment to correct a catalogue that grew informally.

What moves

Entity by entity, from a typical Wix store

Confirmed against your actual account and plan, because the limits vary.

Wix entities, transfer position and the decision each requires
EntityNormally transfersWhere a decision is needed
ProductsYes, in a workable form, with imagesOption and variant structures that were entered inconsistently over time
CollectionsUsually, though structure is often informalWhether to reproduce the current grouping or take the chance to restructure
CustomersPartially, depending on plan and what was recordedHow to communicate reactivation to a list that may be incomplete
Order historyLimited, and confirmed before it is promisedWhether historical orders are imported, archived separately or accepted as lost
Blog postsContent usually retrievable, formatting rarely intactWhich posts justify rebuilding, and which are better retired
Site pagesNo, in any useful senseWhich pages are rebuilt as templates and which are consolidated
MediaYes, once retrieved from the live siteImage quality and sizing, which is often the weakest part of a Wix store
URLsReconstructed from a crawlEvery route family needs a rule, since there is no rewrite table to inherit

What a specific Wix account can export depends on its plan and its history. We confirm it against your account before the scope is fixed, rather than quoting from a general capability list.

Reconstruction

What has to be built rather than moved

This is most of the project, and it should be priced as build work.

The site itself

Every page is rebuilt as a Shopify template or section. That is a real cost, and it is also the opportunity: the rebuild usually replaces a set of one-off pages with a small system the team can reuse.

The catalogue model

Wix catalogues tend to grow informally, with inconsistent options, duplicated products and variants used for things that are not variants. Correcting that during the move costs less than correcting it afterwards.

Forms, bookings and applications

Wix bundles booking, forms, memberships and email into the platform. On Shopify each is a separate choice with its own cost, and the total is worth comparing honestly before the move rather than after the first invoice.

The URL map

There is no rewrite table to export, so the map is built from a crawl of the live site combined with search data where it is available. Routes that no crawl finds and no report lists cannot be redirected, and that limit is stated plainly.

Price the rebuild honestly. Calling it a migration does not make it smaller.

URLs and search

Building a map with no rewrite table

Everything comes from observation of the live site.

Because the source cannot hand over its route list, the map is assembled from evidence and then verified.

  • A full crawl of the live site, recording every reachable route and status
  • Search Console landing pages exported where access exists
  • Product routes mapped to Shopify handles, with the existing slug kept where it is sensible
  • Blog routes mapped into the Shopify blog structure
  • Standalone pages mapped, consolidated or deliberately retired
  • Parameterised and internal search routes handled with rules
  • Any external link source checked, since backlinks may point at routes no crawl reaches
  • Every rule verified as a single hop after launch

Where a route cannot be discovered, it cannot be redirected. Saying so before the project starts is better than explaining it after a traffic drop.

The rest of the project

Design, integrations, validation and cutover

On a Wix move, design and build carry most of the weight.

Swipe the parts

Design

The theme decision

Since the site is being rebuilt anyway, this is a genuine design opportunity rather than a reproduction exercise. Most Wix moves suit a well-implemented theme with the effort spent on structure and photography.

  • Rebuild as a reusable template system, not page by page
  • Address image quality, which is usually the weakest inherited asset
  • Keep the number of bespoke pages small

Systems

What Wix was bundling

Email, forms, bookings and memberships each need a replacement chosen and costed. The comparison should be made before the move, because the bundled price is easy to underestimate.

  • List every bundled feature actually in use
  • Choose and cost a replacement for each
  • Confirm data can be exported before switching

Proof

Validation

With a smaller catalogue, validation can be thorough: every product checked against the live site, and the full journey tested rather than sampled.

  • Product-by-product comparison against the source
  • Full journey tested with a real order
  • Redirect map verified against the crawl

Switch

Cutover and rollback

Wix sites usually run on a Wix-managed domain arrangement, so the domain move is planned in advance with the registrar rather than on the day.

  • Domain and DNS control confirmed before the date is set
  • Switch scheduled at a quiet trading hour
  • Source site kept published until the new one is proven
Price drivers

What actually moves the number

Mostly the rebuild, not the data.

A Wix migration is priced from how much has to be recreated.

  • The number of distinct page layouts that have to be rebuilt
  • Catalogue size and how consistently it was entered
  • Whether historical orders and customers can be retrieved at all
  • How many bundled Wix features need a replacement
  • The number of discoverable routes needing redirect rules
  • Photography quality, and whether assets need reworking
  • Whether the domain is under your direct control

The estimator handles standard Wix moves well, because the variables are fewer than on an open-source platform. Unusual cases still route to manual scoping.

Money

What this work starts at

Published starting figures in GBP and USD, excluding VAT.

Migration and rebuild

From-price or scoped after a source review

Data only

Data migration

From £1,000From $1,300

Products, customers, orders and content mapped into a Shopify store that already exists or is priced separately. Fixed once source access and a sample migration are reviewed.

  • Documented mapping of the selected entities
  • Sample migration before the full run
  • Validation against the source records
  • Redirect mapping where URLs change

Starting price · scoped after discovery

Migration and build

Shopify launch

From £5,000From $6,500

Moving to Shopify and building the store in one project, so the data and the storefront land together rather than in two disconnected pieces of work.

  • Store build, configuration and templates
  • Managed data migration within stated limits
  • Redirects, analytics and technical SEO baseline
  • Launch, training and short post-launch support

Starting price

Most Wix moves are priced closer to a new build than to a data migration, because the site is being reconstructed. That is stated up front rather than discovered in the scope.

Questions

Asked before this work is agreed

Can our Wix design be moved across?

No. Wix layouts exist inside its editor and have no portable form. Pages are rebuilt as Shopify templates and sections, which is a cost, and also the reason most stores end up with something more maintainable than they had.

Will we keep our order history?

Partly, and it depends on the account. We confirm what your specific Wix plan will release before the scope is fixed. Where history cannot be retrieved in full, the options are a partial import or an archived export held outside the store.

What about our Wix bookings or membership features?

Those are Wix products rather than storefront data. Each one needs an equivalent chosen and costed on Shopify. Doing that comparison before the move avoids the common surprise of a bundled feature turning into three subscriptions.

Will our search rankings survive?

Rankings are never guaranteed. What we can do is crawl the live site, map every discoverable route to a destination, keep metadata and content where it still applies, and verify each redirect after launch. Routes nothing can discover cannot be redirected.


Send the Wix URL and the page count.

A crawl of the live site is the fastest way to size a Wix move, because the export tells you less than the site does.

Discuss a project