A practitioner's walkthrough of the full move: the step-by-step process, exactly what data transfers and what gets rebuilt, DTC and B2B feature parity, and the redirect playbook that preserves SEO. Written for mid-market and Shopify Plus teams weighing the switch.
A replatform doesn't lose your SEO, your orders, or your uptime. A bad replatform does. The platform isn't the risk: the execution is.
Your data moves cleanly. What gets rebuilt, and where the real value sits, is the storefront, your product configurator, and your B2B pricing logic, re-engineered to be more maintainable on Shopify. A typical move runs 4 to 8 weeks, with effectively zero storefront downtime, and a 1:1 301 redirect map is the single most important deliverable for protecting search rankings.
Most migrations are triggered by one of three pressures, and 2026 added a new one to the top of the list.
On June 1, 2026 BigCommerce re-architected its plans, renaming them (Standard becomes Core, Plus becomes Growth, Pro becomes Scale, Enterprise becomes Performance) and introducing an Open Payment Provider Fee on self-serve plans: 2.0% on Core, 1.0% on Growth, 0.6% on Scale for merchants using a non-embedded (third-party) payment gateway. Shopify Payments, by contrast, waives transaction fees, and Shopify's third-party-gateway surcharge is just 0.2% on Plus. The historic "BigCommerce has no transaction fees" pitch reverses in 2026 for most merchants on a third-party gateway.
Source: BigCommerce 2026 plan documentation; Shopify pricing.
Beyond fees, teams cite the app ecosystem (Shopify's marketplace is materially larger), admin and theme maintainability, and total cost of ownership drift as the build and integrations stack grows. None of these is a single number, which is why the decision is usually about where you want to spend the next three years of engineering effort, not the platform line item alone.
Honest note: on a contracted high-GMV BigCommerce Performance plan, the platform-fee line can still favor BigCommerce. TCO is dominated by build, processing, apps, and integration, not the platform fee, so calibrate on the whole picture, not the headline.
Teams considering the move fear the same four things: lose my data, lose my rankings, go dark during the switch, and lose a feature (usually B2B pricing). Every one of those is an execution line item, not a property of Shopify. The rest of this guide walks each one.
The fast comparison. Each row is rated against Shopify: where Shopify is better, at parity, structurally different, or has a real gap.
| Capability | BigCommerce | Shopify | Verdict |
|---|---|---|---|
| Variants per product | Up to 600 SKUs | Up to 2,048 (raised Oct 15, 2025) | Better |
| Options per product | Flexible, plus unlimited modifiers | Still 3 options per product | Gap |
| No-SKU buyer inputs | Native modifiers (text, file upload, date) | No native file-upload modifier; rebuilt via line-item properties / apps | Gap |
| Transaction fees (2026) | Open Payment Provider Fee 2.0/1.0/0.6% on non-embedded gateways | Shopify Payments waives fees; 0.2% surcharge on Plus for 3rd-party gateways | Better |
| B2B model | B2B Edition: quote-and-rep led | Native B2B on Plus: self-serve, contracted-catalog led | Different |
| Multi-storefront | One store, many storefronts, shared catalog | Markets (per country) or Plus expansion stores (per brand) | Different |
| Headless / checkout extensibility | Supported | Checkout extensibility, metaobjects, Functions | Better |
| App ecosystem | Smaller marketplace | Larger marketplace | Better |
A de-risked migration runs as six gates. Each is a checkpoint with a deliverable, and nothing advances until the evidence passes. The whole method is built to be observable, reversible, and staged.
Choosing your method first. Under ~500 products with no B2B, a manual CSV export and import can work. Above that, or with any catalog complexity, B2B price lists, or custom features, you need a migration app plus an agency build: Shopify itself ranks "hire a Shopify Partner" and "custom API solution" as its top two migration tiers, above CSV and apps.
Crawl the live BigCommerce store and take a baseline: product, variant, customer, order, category, and URL counts. Never assume the URL structure, because BigCommerce lets merchants pick from Short, Long, or Category presets plus custom paths. This baseline is what every later reconciliation is checked against.
Map every BigCommerce field to its Shopify destination, and flag the records that won't field-map automatically: products with 4+ options, modifier-driven items, the nested category tree, and B2B price lists. These exceptions become hand-shaping decisions, not silent drops.
Build and QA the new store on a Shopify staging environment while BigCommerce keeps selling. This includes the full Liquid theme rebuild (Stencil has no Shopify equivalent and does not transpile), the catalog import, and any rebuilt B2B logic.
Run the import in order (products, then customers, then orders) so records connect, and compare the imported counts against the audit baseline. Mute order-notification staff before the order run, because every imported order can email a "new order" alert. The output is a reconciliation report and a passed test matrix.
A week ahead, drop the domain's DNS TTL to 300 seconds. Load the 1:1 301 redirect map before the switch, plan the final delta sync / freeze, then flip the domain. A well-orchestrated cutover is a DNS change plus a short freeze, not an outage: the DNS step itself takes roughly 15 to 30 minutes, scheduled in a low-traffic window.
Keep the BigCommerce store exported and on a paid plan so a rollback is a simple DNS revert. After cutover, verify zero 404s, submit the new sitemap to Google Search Console, and hold the redirect map for at least a year while search re-crawls.
The differentiator isn't the tooling. It's that the method is observable (you can see every count reconcile), reversible (rollback is a DNS revert), and staged (redirects go live before the switch).
Shopify imports products, customers, historical orders, gift cards, blogs, and pages. CSV handles products and customers; orders and gift cards need a migration app or the Admin API. Here is what actually moves, and the four gotchas that catch teams.
BigCommerce splits Variants (which generate SKUs) from Modifiers (no-SKU buyer inputs like text, file upload, or date), allowing up to 600 SKUs plus unlimited modifiers per product. Shopify now allows up to 2,048 variants per product (raised from 100 on October 15, 2025), so the old 100-variant blocker is gone. The live risks are the 3-option cap and complex modifiers, which become a per-product rebuild decision (line-item properties, metaobjects, Shopify Functions, or an app), not an automated field map.
BigCommerce's nested category tree flattens. Shopify collections are flat, so hierarchy moves into navigation menus and automated-collection rules. Migration tools that map subcategories to product tags are a tell that the tree isn't preserved by default.
Customers migrate, including store credit, but passwords are never migrated: they're hashed irreversibly on the source platform. Every customer needs a Shopify account-activation invite at launch. Plan the comms for it.
Imported orders are historical records, not live transactions: nothing is re-charged. The original processed date is preserved through tooling (Shopify's createdAt is export-only via the native admin). Note that the native admin CSV importer cannot import orders at all: that requires a migration app or the Admin API.
Source: Shopify import documentation; Matrixify / LitExtension tooling docs.
The most common "Shopify can't do what BigCommerce does" objection is about B2B. The honest answer: Shopify Plus has a deep native B2B layer, but the workflow model differs and a few specific things get rebuilt. Here's the split.
BigCommerce B2B Edition is quote-and-rep led. Shopify B2B is self-serve, contracted-catalog led: companies, locations, contracted catalogs, customer-specific price lists, volume and quantity-break pricing, net terms, and purchasing controls are all native. The catch is that B2B is effectively a Plus feature: Basic, Grow, and Advanced cap at 3 active catalogs, while Plus is unlimited.
The headline: your customer list and your orders move; your B2B pricing engine and quote workflows get rebuilt on Shopify's native primitives. BigCommerce Customer Groups and Price Lists map conceptually to Shopify catalogs, price lists, and companies, but no migration tool imports catalogs or price lists: they're built via the Admin API (priceListCreate, priceListFixedPricesAdd). Done deliberately, that rebuild is an upgrade, not a loss.
To stay honest: Shopify still has a 3-options-per-product cap, and there is no native DTC member-pricing catalog the way some BigCommerce setups do member tiers. Both are workable (the cap with a rebuild, member pricing with metafields or apps), but neither is a flip-a-switch field map.
This is the number-one fear, and it's the cleanest to neutralize. The risk is real but specific: it lives in the URL change, and the fix is a deliverable, not luck.
Why every URL changes. Shopify forces fixed URL prefixes (/products/, /collections/, /pages/, /blogs/{blog}/{article}) that can't be edited. BigCommerce's structure is configurable. For most stores that means every product and category URL changes, which is why a complete 1:1 301 redirect map is mandatory, not optional.
301s don't lose PageRank. Per Google, a 301 redirect passes ranking signals to the new URL. A mishandled migration can drop organic traffic, but the loss comes from missing or broken redirects, not from the act of moving. Expect a temporary dip of a few weeks while Google re-crawls, then recovery.
Source: Shopify Help (URL structure, redirect limits); Google (301 ranking signals).
Beyond features, three commercial questions decide most moves: the pricing model, the gateway-fee logic, and the Shopify Plus vs BigCommerce Enterprise (Performance) decision at the top end.
BigCommerce's 2026 plans run Core, Growth, Scale, and Performance; Shopify runs Basic, Grow, Advanced, and Plus. The headline difference is the embedded-vs-open gateway fee: BigCommerce's Open Payment Provider Fee charges self-serve plans for using a third-party gateway, while Shopify Payments waives transaction fees outright. But the platform fee is only roughly 20 to 40% of year-one spend: implementation, processing, apps, and integration dominate total cost of ownership, and both platforms include B2B at the enterprise tier with no license-cost delta.
At the mid-market and enterprise tier, Shopify Plus includes native B2B with no separate license, supports expansion stores for multi-brand, and ships checkout extensibility. BigCommerce Performance is custom-priced (historically from around $1,499/mo) and bundles B2B Edition. Both are credible; the decision usually turns on the B2B workflow model and where your team wants to invest engineering effort.
Multi-storefront is an architecture decision, not a data copy. BigCommerce Multi-Storefront (one store, many storefronts, shared catalog) splits on Shopify into Markets (per-country, one store) or Plus expansion stores (per-brand, independent: primary plus up to 9).
Real numbers, framed as market context so you can calibrate. These are bands seen across the industry, not a quote: a scoped figure for your store comes from a crawl and a conversation.
Typical. Simple catalog moves complete in 2 to 6 weeks; enterprise B2B or multi-store projects can run several months.
Storefront rebuild, catalog migration, redirects, QA, and cutover for a typical mid-market store.
When the move includes B2B pricing logic, ERP integration, and custom features. Data migration alone can be ~30% of a legacy project.
How to read these. Platform fee is only 20 to 40% of year-one spend, so the build, processing, apps, and integration line items are what actually move the total. Use these bands to sanity-check a proposal, then get a scoped number against your real catalog, B2B complexity, and integration surface. Tooling note: apps like Matrixify, Cart2Cart, and LitExtension move records, not architecture: Cart2Cart's own docs cap at 3 options per product and turn subcategories and customer groups into tags. They're components, not the plan.
Every "Shopify can't" or "migration will" objection is execution-handled, not a platform property, with two real gaps conceded. Here's each claim against what's actually documented.
SEO preservation and data integrity are claims everyone makes. What backs them is a track record of structured, reconciled, large-catalog migrations.
A Shopify Plus B2B build and migration over a 60,000+ SKU industrial catalog: 100% of SKUs structured, attributed, and imported into Shopify. The platform was architected from the ground up: data model, product discovery, pricing logic, quoting workflows, and freight rules. The closest analogue to a BigCommerce DTC-plus-B2B move.
Support tickets down 82% after a full Magento to Shopify Plus wholesale replatform; "data migration issues" listed among the solved challenges.
Mobile order completion up 44% on the same replatform: hundreds of SKUs moved, the buyer experience rebuilt.
Cases shown are real Makro replatform work. No BigCommerce-source case is claimed; the proof is the migration-integrity and B2B-rebuild pattern, which is the exact center of gravity of a BigCommerce move.
The questions teams ask most, answered specifically.
Bring your store URL and your renewal quote. We'll crawl your BigCommerce store, map the real scope, and walk you through what migrates cleanly and what we'd rebuild on Shopify.