BigCommerce exports core records well. The work sits in modifiers, customer pricing and native features that Shopify handles differently.
Options that create SKUs, modifiers that change price and text inputs collected at purchase have different destinations in Shopify. We map each behaviour and test products that use the most demanding combinations.
Trade pricing, groups and quantity rules may need Shopify B2B, an app or custom logic. We test sample customers and prices in the chosen setup rather than assuming a direct conversion.
Reviews often support import. Loyalty balances, subscription payment methods and some app histories may not. We confirm export and import paths with each vendor and plan customer communication where continuity is not possible.
Product, category, blog and landing-page routes are crawled and mapped. Faceted URLs are handled as families. Redirects are checked after launch as single hops.
We agree the full data run and the later delta, including how new orders and catalogue changes are identified before cutover.
Source and destination counts are compared, then representative products, customers, orders, prices, images and app data are checked in detail. We place a real test order before cutover and repeat agreed live checks after the switch.
From-price or scoped after source review
Data only
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.
Starting price · scoped after discovery
Migration and build
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.
Starting price
Plus, B2B, multi-market
From £8,000From $10,500
Shopify Plus, B2B, multi-market, multi-language, custom integrations or headless work. These configurations are sized after discovery, not instant-priced.
Starting price · scoped after discovery
Application subscriptions on the destination store are yours and are listed in the scope rather than absorbed. Estimator output is indicative and non-contractual.
Each one is classified before the import. Some become variants, some become line-item properties, some need an application, and occasionally the honest answer is a separate product. It is the decision that most affects both the price and the storefront afterwards.
Not in the same way as BigCommerce on a standard plan. Where the requirement is a genuine trade catalogue, the destination is a B2B configuration. Where it is a discount tier, there are simpler answers. Which one it is gets established in discovery.
The list can be exported and it is worth having, but it is rebuilt rather than copied. Migrating an old redirect list unchanged and adding a new layer on top produces multi-hop chains that lose value at every step.
Usually not. Most review applications support an import, so historical reviews can be preserved. Loyalty balances and subscription payment methods are a different matter and generally cannot transfer, which needs a customer communication plan.
A real example tells us more about the mapping than the catalogue size.
