What actually changes when you move a BigCommerce store to Shopify

How close the two platforms actually are

Most replatforming guides open with a warning about everything you are about to lose. A BigCommerce to Shopify migration does not deserve that opening. Both are hosted SaaS with a themed storefront, a REST and a GraphQL admin API, webhooks, a hosted checkout and an app marketplace doing the same jobs. Products, customers and orders move across without much drama.

The awkwardness sits in a short list of things BigCommerce ships in the box that Shopify either models differently or hands to a paid app. Get that list into the estimate and the project is dull in the good way. Miss it and you find out in week six, with the catalogue half loaded.

One practical note first. Shopify's own Store Migration app does not support BigCommerce. Checked on 12 August 2026, the platforms it supports are Amazon, Clover, eBay, Etsy, Lightspeed, Square, Wix and WooCommerce. So a BigCommerce migration is a CSV job, an API job, or a job for a tool like Matrixify. Budget for that instead of assuming there is a button.

The no-transaction-fee argument is over

For a decade the loudest line in any BigCommerce pitch was that it charges no transaction fees while Shopify taxes you for not using Shopify Payments. That line retired on 1 June 2026, when BigCommerce renamed its plans and introduced an Open Payment Provider fee on order volume settled through any gateway that is not on its embedded provider list. The rates landed almost exactly where Shopify's already were.

Both waive the fee on their own rails. Shopify Payments carries no platform fee on any plan, and BigCommerce charges nothing on orders settled by an Embedded Payment Provider, a list that includes Stripe, PayPal and Adyen. Land on Shopify Payments after the move and the comparison collapses back to card rates and your acquirer.

BigCommerce still wins at the top tier, where the fee goes to zero under contract while Shopify Plus keeps 0.2% on volume outside Shopify Payments. If you process serious money through a negotiated acquirer that Shopify will not replace, run that arithmetic before anything else here. Below that, it is noise.

The revenue ceilings matter more. BigCommerce Core auto-upgrades above 30,000 USD of trailing twelve month GMV, Growth above 100,000 USD, and Scale charges a 0.9% overage on monthly GMV above 33,333 USD. Shopify has no equivalent cap. Anyone who priced BigCommerce in 2023 should re-price it before defending the status quo.

Options and modifiers do not map onto Shopify variants

This is the part that makes BigCommerce migrations expensive, and it is the part most quotes ignore because it does not show up until someone opens a real product.

BigCommerce splits product choices in two. Variant options generate variants, the sellable things with SKUs and stock. Modifier options are choices that do not change which item comes off the shelf: engraving text, a gift box, a cut-to-length measurement, shipping insurance. Modifiers carry price adjusters, they can be free text or a file upload or a date picker, and you can hang as many on a product as you want. What they cannot do is hold a SKU or track inventory. The split is deliberate and well designed.

Shopify has no modifier concept. It has options, capped at three per product by a shop resource limit, and variants generated from every combination of them, up to 2,048 since October 2025. Anything outside those three options becomes a line item property: a string on the cart line that does not adjust price, does not appear in inventory and does not create a variant.

So a BigCommerce product with size and colour variants plus five modifiers arrives on Shopify as a two-option product with theme-level fields, and the price adjusters have to be rebuilt elsewhere. In practice that means an options app pricing the add-on through a hidden line item, a draft order or a Shopify Function. Each of those has a failure mode, usually around discounts, taxes, or a headless storefront that never learned about the hidden line.

Audit the catalogue before you price the project

1. Export the product list and count how many products carry any modifier at all. That count, not the size of the catalogue, is what sets the cost of this part of the project, so get it before anyone quotes a number.
2. Split those into modifiers that only adjust price and modifiers that change how the order gets fulfilled. The second group needs its data to reach the warehouse, not just the order screen.
3. Find every modifier being used to fake inventory, where someone tracks stock in a spreadsheet because the modifier cannot hold it. Those products break, and they are also the ones Shopify models better once you convert them to real variants.
4. Only then choose between three Shopify options, an options app, and splitting one BigCommerce product into several. Splitting is unfashionable and often correct, because it gives every sellable thing a SKU.

URLs and redirects: you lose control of the path

BigCommerce lets you set the full path of a product, category, brand, page or post to almost anything. Products default to the root, so /blue-widget/ is an ordinary BigCommerce product URL, categories nest, and you can restructure the whole site by editing a field. It also writes a 301 automatically when you change a product, category or page URL, unless you untick the box.

Shopify does not work that way, and no plan changes it. Products live under /products/, collections under /collections/, static pages under /pages/, articles under /blogs/blog-handle/article-handle. You control the handle. You do not control the prefix. Plus does not buy an exception.

So you need a mapped redirect file rather than a pattern rule, because the old and new paths do not share a shape. Shopify's redirect tool accepts a CSV. Build the map from a full crawl plus a Search Console export and redirect every URL with impressions in the last twelve months, because the long tail is where the traffic loss hides.

The flatter structure itself is not the ranking disaster people fear. Google does not need a category path to understand a product. The real nuisance is the duplicate product path Shopify still generates, where the same product answers at /products/handle and at /collections/name/products/handle. Canonicals resolve it and serious themes get it right, but verify on the theme you actually ship.

Faceted search changes hands

BigCommerce ships faceted search, its own filtered product search, on the Scale and Performance plans only. If someone has spent months tuning those facets, that work goes to a different system with different rules.

Shopify's equivalent is Search & Discovery, published by Shopify, free, on every plan. It handles filters, synonym groups, typo tolerance, product boosts and recommendations. Filters come from availability, category, price, product type, tags and vendor, and from product options, metafields and metaobjects. The ceiling is 25 filters per store, which is comfortable for apparel and tight for an industrial catalogue where every category has its own spec sheet.

Even-handed version: Search & Discovery beats BigCommerce standard search, sits roughly level with BigCommerce faceted search for most catalogues, and arrives free two plan tiers lower. If 25 filters is genuinely not enough you are looking at Algolia or a comparable app, which is a monthly line item that belongs in the migration budget rather than in a post-launch surprise.

Multi-storefront and B2B, where BigCommerce still has arguments

BigCommerce multi-storefront and Shopify expansion stores answer the same question in incompatible ways, and the difference matters more than the counts. BigCommerce gives Core up to three storefronts, Growth five and Scale eight, at 30, 50 and 100 USD per month for each one past the first. They share one control panel and one catalogue, with per-storefront overrides on pricing, content and channel assignment. The shared catalogue is the whole point.

Shopify Plus includes a main store plus nine expansion stores on the contract at no extra licence cost, and they share nothing. Each is a separate myshopify.com domain with its own admin, products and inventory. Shopify's position is that most reasons to run a second storefront (another currency, another language, market pricing, a country domain) belong to Markets inside one store, and that is right often enough that plenty of BigCommerce multi-storefront setups collapse into a single Shopify store. Test it first. If your storefronts really do share a catalogue, expansion stores hand you a sync problem someone has to own forever.

B2B has moved in Shopify's favour. Companies, company locations with location-level permissions, quantity rules and price breaks, net payment terms, ACH, vaulted cards, PO numbers on draft orders and quick order lists now run on Basic, Grow and Advanced as well as Plus. Below Plus you get three active B2B catalogues and cannot assign one directly to a company. Plus removes the cap, adds direct assignment, deposits, partial payments and payment requests per fulfilment.

BigCommerce answers with customer groups from Growth up and B2B Edition as a paid add-on quoted by sales rather than a line on the pricing page. For a mid-sized wholesaler whose pricing fits in three catalogues, Shopify is now the cheaper answer, which was not true two years ago. For a distributor running a real quoting workflow across hundreds of contract price lists, BigCommerce holds up better and I will not pretend otherwise. That merchant should stay put, not migrate sideways.

Checkout: you trade code access for Shop Pay

BigCommerce publishes its checkout as open source. checkout-js is a React application on GitHub, and you can fork it, add steps, add fields and change the flow on any plan, including the 29 USD one. Nothing on Shopify gives you that at any price.

Shopify customisation runs through checkout extensibility: apps and extensions in defined slots. On Basic and above you can customise the thank you and order status pages and set branding in the checkout editor. Extensions on the information, shipping and payment steps, plus the Checkout Branding API, require Shopify Plus. That is a real loss of control and worth saying plainly.

What comes back is Shop Pay and a checkout Shopify tests and updates without asking you. That trade favours most merchants, because most forked checkouts get worse as the fork drifts from the platform. It does not favour all of them. If your checkout carries something that earns its complexity, a configurator, a quote step, a regulated disclosure field, price a Plus extension build into the migration instead of assuming it ports.

The order to run it in

A BigCommerce to Shopify migration has a natural sequence, and most of the pain in one comes from doing step five before step two.

1. Crawl the live BigCommerce site and export Search Console data. This is the redirect map and the page inventory, and it is worthless if you gather it after launch.
2. Audit modifiers and decide the Shopify product model per product family. Nothing else can be estimated until this is settled.
3. List every BigCommerce built-in you rely on and find its Shopify equivalent with a price against it: reviews, faceted search, customer groups, storefronts, checkout logic.
4. Move the catalogue into a development store and load real data early. Sample data hides exactly the products that break.
5. Rebuild the theme against the real catalogue. Do not port BigCommerce Stencil templates; the object models differ enough that a rewrite is faster than a translation.
6. Load the redirect CSV, verify a sample by hand, then cut over DNS. Watch Search Console coverage daily for the first fortnight and fix 404s the same week they appear.

Two things worth setting expectations on. Rankings usually wobble for a few weeks after a replatform even when the redirects are perfect, because Google re-crawls and re-evaluates the whole path structure. And the store you launch on Shopify should not be a copy of the store you left, because copying a BigCommerce theme into Liquid carries over every conversion problem it already had.

Common questions

Can Shopify import my BigCommerce store automatically?

No. As of 12 August 2026, Shopify's Store Migration app lists Amazon, Clover, Etsy, eBay, GoDaddy, Lightspeed, Square, Squarespace, Wix and WooCommerce as supported sources. BigCommerce is not among them. You move products, customers and orders using CSV exports, the Admin API, or a third-party tool such as Matrixify, and you map product options manually because the two platforms model them differently.

What happens to BigCommerce product modifiers on Shopify?

They do not transfer, because Shopify has no modifier concept. Shopify allows three options per product and generates variants from them, up to 2,048. Anything beyond that becomes a line item property, which is text on the cart line that does not adjust price or track inventory. Priced or stocked modifiers need either a product options app or the product split into several Shopify products.

Will my rankings drop when I migrate from BigCommerce to Shopify?

Expect a few weeks of movement even with a clean migration, because Shopify forces every URL into fixed prefixes such as /products/ and /collections/ and Google has to re-crawl the new structure. The controllable part is the redirect map. Build it from a full crawl plus Search Console data, redirect every URL with impressions in the last twelve months, and load it before DNS cutover rather than after.

Is Shopify cheaper than BigCommerce in 2026?

They are much closer than they were. Since 1 June 2026 BigCommerce charges an Open Payment Provider fee of 2.0%, 1.0% and 0.6% on its Core, Growth and Scale plans, effectively matching Shopify's 2%, 1% and 0.6% third-party gateway fees. Both waive it on their own payment rails. BigCommerce now also enforces GMV thresholds on lower plans, which Shopify does not.

Do I need Shopify Plus to migrate from BigCommerce?

Usually not. Plus is required for checkout extensions on the information, shipping and payment steps, the Checkout Branding API, unlimited B2B catalogues, and expansion stores. If you are leaving a mid-tier BigCommerce plan without a forked checkout, Advanced covers it. Merchants who fork BigCommerce checkout or run several storefronts off a shared catalogue should price Plus into the decision from the start.