Comes across
- Products and variants, through the catalogue export
- The category tree and its nesting
- Customer accounts and addresses
- Order history, and any blog posts
The catalogue, the customers and the order history all export. The pricing logic does not: modifiers, price lists and customer groups are BigCommerce concepts that WooCommerce has no core equivalent for.
Most migration disputes come from this list being assumed rather than agreed. So we agree it first.
BigCommerce splits product options in two: variants, which carry their own SKU, and modifiers, which change the price without creating one. WooCommerce only has the first. Every modifier becomes either a variation or an add-on field, and that choice changes how the catalogue is managed for years afterwards.
Customer-group pricing is built into BigCommerce and is a plugin decision in WooCommerce. On a B2B catalogue it is a functional requirement rather than a nicety, so the plugin gets chosen and tested against your real price bands before the import, not after.
Most stores of any age carry years of 301s in the built-in redirect manager. Those get exported alongside the crawl, or you inherit a fresh URL map and quietly drop every redirect that was already holding old links together.
Every URL currently indexed, exported to a sheet. This becomes the redirect map and the definition of done.
What the platform gives us, compared against what the crawl found. The difference is the rebuild, and it gets priced before we start.
The new site goes up somewhere private, with real content imported, so you review the actual thing rather than a mockup.
Old URL to new URL, one row at a time, tested as 301s on staging before anything points at production.
DNS moves, then we monitor crawl errors and traffic for the fortnight that follows, because that is when problems surface.
Something not covered here? Ask us directly and an engineer will answer.
Ask a questionFrom BigCommerce we can bring over: products and variants, through the catalogue export; the category tree and its nesting; customer accounts and addresses; order history, and any blog posts. Everything else on the site has to be rebuilt, and we agree which is which before quoting.
The parts with no equivalent on the other side: the Stencil theme, which is Handlebars and does not convert; checkout, shipping zones and tax rules; anything installed from the BigCommerce app marketplace; price lists, customer groups and B2B pricing. This is where the cost sits, so it is priced up front rather than discovered halfway through.
Not if the redirects are done properly. We crawl every URL that is currently indexed, map each one to its new address, and test those as 301s on staging before anything points at production. Then we watch crawl errors and traffic for the fortnight after cutover.
BigCommerce splits product options in two: variants, which carry their own SKU, and modifiers, which change the price without creating one. WooCommerce only has the first. Every modifier becomes either a variation or an add-on field, and that choice changes how the catalogue is managed for years afterwards.
Customer-group pricing is built into BigCommerce and is a plugin decision in WooCommerce. On a B2B catalogue it is a functional requirement rather than a nicety, so the plugin gets chosen and tested against your real price bands before the import, not after.
We will crawl it, work out what the export actually gives us, and come back with a fixed price and the redirect map included.
A free audit first
We'll look at your site and tell you straight what needs doing.
Fixed scope, fixed price
Agreed in writing before any work starts. No hidden fees.
A real engineer on the call
You talk to the people who do the work, not a sales script.
Ask anything you’d like cleared up: how we work, what we build, or the projects we have delivered.
Popular questions