BigCommerce to Shopify migration Move your store without losing your rankings or your variants.
We pull products, variants, customers and orders through BigCommerce's REST and GraphQL APIs, rebuild the apps handling special features, and redirect every old URL to its new address. Your BigCommerce store stays live until launch day.
What does a BigCommerce to Shopify migration involve?
It means pulling data through BigCommerce's mature REST (Catalog) and GraphQL (Storefront) APIs and writing it into Shopify, with automated verification at the end. BigCommerce lets merchants choose from several URL structures — short, long, category-based or custom — so we check your store's actual setting before mapping redirects, rather than assuming a default. Variants are capped at 600 per product (250 on Multi-Storefront), both comfortably under Shopify's current 2,048 limit; the real mapping work is around "modifiers", which don't generate SKUs on BigCommerce and need a different Shopify equivalent. It's quoted after a store review, usually takes 2–6 weeks, and your BigCommerce store stays live until cutover.
What we move from BigCommerce, and how
BigCommerce is a mature SaaS platform, architecturally close to Shopify — both REST and GraphQL APIs are well documented.
| What we move | How, technically |
|---|---|
| Products | Via the Catalog REST API or the GraphQL Storefront API (bearer token auth), with price, stock and description. |
| Variants | Up to 600 per product (250 on Multi-Storefront) — under Shopify's 2,048 cap; "modifiers" (which don't create SKUs) get mapped to line item properties or a customisation app, not to variants. |
| Images | Pulled via the API and re-uploaded to Shopify, which re-hosts them on its own CDN. |
| Specs | Custom fields and options become Shopify metafields or options, depending on how the old store used them. |
| Categories | Become Shopify collections; BigCommerce only uses a product's first assigned category in its own URL, which we account for in the mapping. |
| Customers | Native export (Customers > Export) or API, requiring "Manage Customers" and "Export Customers" permissions. Passwords can't be moved — see below. |
| Order history | Native export (CSV/XML) or API, recreated as history on Shopify, without touching current stock. |
| Pages | Pulled via export or API, with images re-hosted and links updated to the new addresses. |
| Reviews | BigCommerce's native reviews have no built-in export — pulled via a third-party review import/export app. |
| Coupons | Recreated as Shopify discounts, based on the rules visible in the BigCommerce store. |
| Redirects | BigCommerce offers several URL structure options (short, long, category, custom) — we confirm which one your store uses before mapping every old URL. |
| Google/Meta feeds | Reconnected with a Shopify feed app, with a custom identifier if you want to keep ad history. |
What can't move anywhere, and how we work around it
Three things have no direct technical path.
Customer passwords
BigCommerce confirms directly that passwords are never available for export — not via CSV, not via API — because they're hashed beyond recovery. On new Shopify stores, customers sign in password-free, with a one-time code emailed at first login.
Old order dates
Shopify's API doesn't allow backdating an imported order's date. Old orders show up chronologically as "new" in the customer's account. We tag them invisibly so your new theme can treat them separately.
Installed apps
Each BigCommerce app is built for its own architecture and doesn't "move." We identify the real function and rebuild it with an equivalent Shopify app or theme code.
The gotchas we check as standard
These are exactly where a generic migration gets it wrong.
- Modifiers aren't variants. BigCommerce "modifiers" (unlimited in number) don't generate SKUs and don't count toward the 600-variant cap — they typically map to line item properties or a customisation app on Shopify, not to the variant system.
- URL structure is a per-store setting. Short, long, category-based or custom — we confirm which one is active before generating redirect mappings, not assuming a default.
- Multi-Storefront lowers the variant cap. 250 per product instead of 600 — relevant if your store uses BigCommerce's Stencil Multi-Storefront setup.
- Reviews need a third-party export. BigCommerce's native reviews have no built-in export path, so a dedicated app handles extraction.
- Shopify's current official app doesn't list BigCommerce. An older, now-retired "Store Importer" once covered more platforms, but it's no longer available on the App Store — don't rely on that history as a current option.
What it costs, and what moves the price
The price is quoted after we see your store.
- How many products and variants you have, and whether you use modifiers heavily.
- Which URL structure setting your store uses.
- How many custom apps need replacing with Shopify equivalents.
- Whether you want reviews migrated, which needs a third-party export app.
As a reference, a new Shopify store build starts from €950 + VAT.
When migration isn't worth it
If your BigCommerce store runs well and the subscription cost is justified by your order volume, you don't have a strong technical reason to migrate — both platforms are mature, hosted SaaS with comparable reliability. Migration tends to make sense when you want Shopify's larger app ecosystem and theme market, or when consolidating multiple regional storefronts onto one platform your team already knows.
Questions about BigCommerce migration.
Can't find your answer? Message us on WhatsApp at +40 785 735 820.
How much does a BigCommerce to Shopify migration cost?
It's quoted after we review your store, because the price depends on how many products and variants you have (BigCommerce allows up to 600 per product, more than Shopify's old limit but under the current 2,048), which URL structure setting you're using, and how many apps need replacing. As a reference, a new Shopify store build starts from €950 + VAT.
Does Shopify have an official app for migrating from BigCommerce?
No. BigCommerce doesn't appear on Shopify's current official Store Migration app or in Shopify's help documentation for supported source platforms. An older, now-retired Shopify app once covered more sources, but it's no longer available — migration today depends on a dedicated tool or a third-party provider.
Will I lose my Google rankings after migration?
The risk drops a lot when it's done properly. BigCommerce lets merchants choose between several URL structures (short, long, category-based or custom), so we check your store's actual setting before mapping every old URL to its new address with a permanent redirect.
What happens to products with many variants?
BigCommerce caps standard stores at 600 variants per product (250 on Multi-Storefront), both under Shopify's current limit of 2,048. The more relevant mapping issue is BigCommerce "modifiers", which don't generate separate SKUs — they typically map to line item properties or a customisation app, not to Shopify variants.
What transfers and what doesn't?
Products with variants and images transfer, along with categories, customers and order history, pulled via BigCommerce's REST and GraphQL APIs. Passwords don't transfer — BigCommerce confirms they're never available via CSV export or API, since they're hashed beyond recovery. Installed apps get rebuilt as Shopify equivalents.
How long does a BigCommerce migration take?
Usually two to six weeks, depending on the number of products, how many custom apps need replacing, and how clean your current URL structure is. Your BigCommerce store stays live until launch day.
First step
Send us your store's address.
We look at how many products you have, which URL structure you use and which apps you rely on, then tell you what can move, what needs rebuilding and what it costs.