May 19, 2026 by Alex Massaad · 9 min read

BigCommerce to Shopify Migration: What Actually Breaks

BigCommerce to Shopify is one of the easier migrations on paper. Both platforms are SaaS, both have similar admin paradigms, and the data shapes are closer than they look. We’ve moved a lot of stores between them, and the merchants who came from BigCommerce had a much smoother first month on Shopify than the ones who came from WooCommerce or Magento.

That said, “easier” is relative. There are still a handful of places where the migration genuinely breaks if you’re not paying attention. This guide covers those places, with focus on the things that catch people the first time, not the obvious stuff every migration guide already lists.

The Honest Reason Most Merchants Move

The two patterns we see repeatedly:

1. Cost at scale. BigCommerce’s Pro and Enterprise tiers price themselves into a difficult conversation once your annual revenue clears certain thresholds, and the upgrade path can be steep. Shopify’s pricing curve is flatter.
2. App ecosystem and developer pool. Shopify has more apps, more agencies, more developers, and more public knowledge. When something breaks at 11pm, the StackOverflow answer probably exists.

Neither platform is “better” in the abstract. We’ve taken stores both directions over the years. But if you’ve decided to move, here’s the migration guide.

What Translates Cleanly

These come over without much pain:

• Products and variants (with one important asterisk on options, see below)
• Customer records (minus passwords, same constraint as every migration)
• Order history (as reference data, not as live orders you can refund)
• Pages (about, FAQ, policies)
• Discount codes (most rule types map; some BigCommerce promotion logic does not)
• Shipping zones and rates (concept maps, configuration is manual)
• Tax setup (concept maps, tax registrations need to be re-entered)
• Storefront analytics IDs (drop them in and go)

For these, the migration is a CSV export, a transform, and a Shopify import. Tools like Matrixify or LitExtension automate most of it.

What Actually Breaks

This is where this post earns its keep.

1. Modifiers vs Variants

BigCommerce has two distinct concepts: variants (separate SKUs, different prices, different inventory) and modifiers (text fields, dropdowns, file uploads, checkboxes that change a single product without becoming a new SKU). Shopify only has variants. There is no modifier equivalent in core Shopify.

If your BigCommerce store uses modifiers heavily (think: monogramming, gift wrap, custom engraving, configurable product options), those need to go somewhere on Shopify:

• Line item properties if the modifier is text the customer types
• Apps like Infinite Options or Globo Product Options if you need dropdowns, checkboxes, or file uploads
• Convert to variants if the option meaningfully changes price or inventory and you’re under Shopify’s variant limits

Plan this before you migrate. Modifiers ported as nothing means orders come through Shopify missing customization data, and that’s a real customer service headache.

2. The Variant Limits

Shopify caps products at 3 option types (e.g., size, color, material) and 100 variants per product on most plans. Plus stores can request the expanded variant limit (up to 2,000 variants per product). BigCommerce has no equivalent hard cap.

If you have a product with size × color × material × material thickness × pattern, that’s 5 option types. BigCommerce handles it. Shopify won’t, without restructuring. The standard solutions:

• Combine two options into one (e.g., “Color/Pattern” as a single option with values like “Red - Stripes”)
• Split into multiple products linked via a metafield-based “combined listing”
• Use a variant-extending app

The variant audit is one of the first things to do. Run a query against your BigCommerce catalog: how many products have more than 3 option types, and how many have more than 100 variant rows? If those numbers are non-zero, factor restructuring time into the migration.

3. Categories Are a Tree, Collections Are Not

BigCommerce categories are hierarchical: Furniture > Living Room > Sofas > Sectional Sofas. Shopify collections are flat. There is no native category nesting.

The standard workaround is to use collection naming conventions and the navigation menu to imply hierarchy, while the URL stays flat (/collections/sectional-sofas rather than /collections/furniture/living-room/sofas/sectional-sofas). For most stores, this is fine. For large catalogs where breadcrumbs and faceted navigation matter for SEO, plan a more deliberate solution: collection metafields that store parent/child relationships, plus theme code that renders breadcrumbs from those metafields.

This one tends to surface late in a migration because everything looks fine in the admin until someone asks “where do the breadcrumbs go?”

4. URL Structure Changes

Products line up almost perfectly. Categories need a path swap. Brand pages have no native Shopify equivalent and need the most thought, since they often pull SEO traffic on long-tail “brand + product” queries. Blog URLs change shape entirely.

Every URL that changes needs a 301 redirect. Shopify’s bulk redirect import (CSV) handles this fine for most stores. For stores with thousands of redirects, an app like Easy Redirects or Bulk Redirect helps manage them at scale.

5. Themes Don’t Port

BigCommerce themes are written in Stencil (Handlebars + custom helpers). Shopify themes are written in Liquid. They are structurally similar but syntactically different, and there is no automated converter that produces production-quality output.

If you spent significant money on a custom BigCommerce theme, accept that the storefront is a rebuild. The good news is the rebuild is often a chance to upgrade to Online Store 2.0 (Shopify’s section-based architecture, much better merchandising flexibility) and to drop apps that were workarounds for Stencil limitations.

We typically recommend either:

• Pick a premium Shopify theme ($300 to $400 from the Shopify Theme Store) and customize it to match the brand. Faster, cheaper, modern architecture.
• Build custom on Online Store 2.0 if the brand or merchandising story demands it.

Trying to ask a developer to “convert” the BigCommerce theme line by line is the slowest, most expensive path, and produces the worst result.

6. Multi-Storefront vs Markets

BigCommerce’s Multi-Storefront feature lets one account run multiple distinct stores (different domains, different catalogs, different themes) under a single backend. Shopify does not have a direct equivalent on standard plans. The closest is:

• Shopify Markets for region-specific pricing, currency, and content variations on the same store
• Shopify Plus with multiple separate Shopify stores (“expansion stores”) sharing inventory through a third-party connector
• Headless with multiple frontends pulling from one Shopify backend

If you’re using BigCommerce Multi-Storefront for true distinct brands (different SKUs, different fulfillment), you’re looking at multiple Shopify stores. If you’re using it for region or language variations on the same brand, Markets is usually the right fit. This decision affects pricing tier, app stack, and architecture, so settle it early.

7. Customer Passwords

Same constraint as every migration. BigCommerce passwords use one-way hashing, Shopify uses different one-way hashing, and neither platform exposes the raw passwords. Every customer needs to reset on first login. Plan a clear comms email, and time the migration so customer support is ready for the wave of “I can’t log in” tickets in the first 48 hours.

8. B2B Setup Is Not 1:1

BigCommerce B2B Edition has price lists, customer groups, quote workflows, and shared shopping lists baked in. Shopify B2B (on Plus) has similar features, but the data model is different: companies have locations, locations have catalogs and price lists, and B2B customers are linked to locations rather than to “groups.”

If you’re a B2B merchant on BigCommerce considering Shopify, the migration is not just a data move. It’s a re-modeling of how your wholesale relationships are structured. Worth a dedicated planning conversation before you commit.

The Migration Order We Run

1. Audit the catalog. Variant counts, option types, modifier usage, brand pages, categories with depth greater than two.
2. Audit URLs. Export the full URL list with Screaming Frog. Map every URL to its Shopify destination. This is the redirect spreadsheet.
3. Audit modifiers. For every modifier in BigCommerce, decide where it goes on Shopify (line item property, app, variant, or removed).
4. Pick the theme. Premium theme or custom build. This decision drives content migration, since theme determines section types.
5. Migrate data in this order: products, then customers, then collections (categories), then pages, then redirects, then orders for reference.
6. Build the storefront. New theme on Shopify, configured to match brand and merchandising.
7. Test in a development store. Real product data, real customer accounts, real test orders.
8. Cutover. DNS swap, watch checkout for 48 hours, monitor Search Console weekly for the first month.

The work between steps 2 and 7 is where most of the time goes. The cutover itself is a couple of hours. The audits and the rebuild are weeks.

Realistic Timelines

Most of the variability comes from three things: variant restructuring if you have option-type counts above three, B2B re-modeling if you’re using BigCommerce B2B Edition, and integrations with external systems (ERP, PIM, 3PL).

Mistakes We See Most Often

1. Skipping the modifier audit. Modifiers don’t show up in the standard migration tool reports. They are easy to forget until customers start complaining that their personalization options are missing.
2. Assuming categories will translate. They don’t. Plan the collection structure before touching the importer.
3. Forgetting brand pages. If “Acme + product” queries drive meaningful traffic, brand pages need a migration plan, not “we’ll figure it out later.”
4. Letting the theme be an afterthought. The storefront rebuild is the longest part of a serious migration. Start it early, in parallel with data planning.
5. Underestimating B2B. A B2B Edition migration is a different project than a B2C migration with a few wholesale customers. Don’t combine them in the timeline.

Do You Need Help?

A small BigCommerce store with simple products, no modifiers, and no B2B can be migrated by one person with the right tooling in a couple of weeks. The Shopify Help Center docs on importing from BigCommerce will get you most of the way there.

A complex store with custom themes, B2B Edition, multi-storefront, or significant traffic you cannot afford to lose is not a DIY job. The cost of a bungled migration (lost rankings, broken checkout, missing customer data) is much higher than the cost of working with someone who has done this before.

We’ve handled migrations from BigCommerce, WooCommerce, Magento, and custom platforms. If you’re on WooCommerce, our WooCommerce to Shopify migration guide covers the gotchas specific to that path. For build cost expectations after a migration, see how much a custom Shopify store costs in 2026.

If you’d like to talk through your specific setup, reach out for a free consultation or learn more about our Shopify design and development service. We’ll tell you straight whether a migration makes sense for your store and what it would actually take.