// Insights / Migration

BigCommerce to Shopify Plus Migration: The 2026 Playbook

Tim Sullivan · Sonder, Melbourne · Published 2 August 2026

BigCommerce lost 551 merchants to competitors and gained only 312 in the 90 days ending July 2025. That is a 1.8-to-1 loss ratio. Active stores fell from 48,231 at peak to 37,140 by May 2026, an 8% year-over-year decline and the steepest annual drop the platform has recorded. Meanwhile, BigCommerce posted its first GAAP-profitable quarter by shedding lower-tier merchants and concentrating on enterprise accounts that now represent 75% of annual recurring revenue.

If you are a mid-market brand on BigCommerce doing $10M to $50M in revenue, this creates a specific kind of uncertainty. The platform is not dying. It is pivoting. And that pivot might or might not include you. BigCommerce's enterprise bet means more resources flowing toward large accounts, more features built for complex B2B use cases, and less investment in the mid-market capabilities that might be exactly what you need.

This is not a hit piece on BigCommerce. It is a practical playbook for brands evaluating whether to stay or go, and if you go, how to migrate to Shopify Plus without breaking your business in the process.

The Honest Comparison: BigCommerce vs Shopify Plus in 2026

Before talking about migration mechanics, you need to understand what you are actually gaining (and what you are giving up) by moving to Shopify Plus. Most comparison articles gloss over the tradeoffs. We will not.

Capability BigCommerce Enterprise Shopify Plus
Platform licensing Custom pricing, typically $1,000-$15,000/mo based on GMV $2,300/mo (3-year term) + 0.25% of GMV above ~$800K/mo
B2B capabilities Strong native B2B with customer groups, price lists, quote management, purchase orders Native B2B with company accounts, buyer portal, unlimited price catalogues, payment terms, EDI integration (Winter 2026)
Checkout customisation Full control via Stencil framework and Checkout SDK Checkout UI Extensions + Shopify Functions (checkout.liquid fully deprecated)
Headless commerce Strong headless story via GraphQL Storefront API. BigCommerce was headless-first before Shopify. Hydrogen framework (React-based) + Storefront API. Newer but maturing rapidly.
Multi-storefront Native multi-storefront from a single dashboard. Each store can have its own domain, theme, and product catalogue. Expansion stores at $250/mo each, or Shopify Markets for international storefronts from one store.
App ecosystem ~1,300 apps. Functional but significantly smaller. ~13,000+ apps. The largest commerce app ecosystem by an order of magnitude.
Developer talent Smaller pool. BigCommerce developer rates tend to be $150-$250/hr due to scarcity. Massive pool. Competitive rates from $100-$250/hr with far more options.
AI and agentic commerce Limited AI features. No equivalent to UCP or native AI agent integrations. Universal Commerce Protocol (UCP) enabled by default. Products auto-syndicated to ChatGPT, Copilot, Google AI Mode. Campaign Autopilot for ad management.
International Multi-currency and multi-language supported but requires more manual configuration. Shopify Markets with up to 50 markets from one store. Managed Markets (merchant of record) for hands-off international compliance.

Where BigCommerce Is Genuinely Better

We are going to be honest here because the "Shopify is better at everything" narrative is not accurate:

  • Native multi-storefront: BigCommerce's multi-storefront is more mature and more flexible than Shopify's expansion store model. If you run five distinct brands from one back office, BigCommerce handles this more elegantly today.
  • Headless maturity: BigCommerce was headless-first. Their GraphQL Storefront API is mature, well-documented, and battle-tested. Shopify's Hydrogen is catching up fast but is still newer.
  • Checkout flexibility: BigCommerce's Checkout SDK gives you more raw control over the checkout flow than Shopify's extension model. Shopify deliberately constrains checkout to maintain security and performance guarantees. If you need deeply custom checkout flows, BigCommerce offers more latitude.
  • No transaction fees on third-party gateways: BigCommerce does not charge additional transaction fees for using non-native payment gateways. Shopify charges 0.15-0.2% on Plus for third-party gateways (waived if you use Shopify Payments).

Where Shopify Plus Wins

  • Ecosystem scale: 13,000+ apps versus 1,300. This is not just a vanity metric. It means for any operational need, there are likely multiple mature, well-supported apps on Shopify. On BigCommerce, you may be limited to one option or building custom.
  • Developer availability: Finding a strong BigCommerce developer is significantly harder and more expensive than finding a Shopify developer. This affects your ongoing development velocity and cost.
  • AI and agentic commerce: Shopify's Summer '26 Edition made UCP the default. Your products are discoverable by AI shopping agents across ChatGPT, Copilot, Google AI Mode, and Gemini without any custom build. BigCommerce has no equivalent.
  • Platform momentum: Shopify ships 150+ features per edition, twice a year. The velocity of platform improvement is measurably higher. Features that require custom development on BigCommerce are often available natively on Shopify within 6-12 months.
  • International selling: Shopify Markets and Managed Markets are a generation ahead of BigCommerce's international capabilities. If international expansion is on your roadmap, this matters. Read our international expansion playbook for the full picture.

What Migrates and What Does Not

This is where migration planning gets real. Understanding exactly what transfers cleanly and what requires rebuilding determines the true cost and timeline of your migration.

Clean Transfers

  • Products: Product data (titles, descriptions, images, variants, SKUs, prices, weights) migrates cleanly via CSV export/import or migration tools like LitExtension, Cart2Cart, or custom scripts.
  • Customers: Customer profiles (names, emails, addresses, order history) transfer. Note: customer passwords do not transfer. Every customer will need to reset their password on first login to the new store. Plan your communication around this.
  • Orders: Historical order data migrates for reference, but it becomes read-only in Shopify. You cannot modify or refund migrated orders through the Shopify admin.
  • Blog posts: Content transfers, though formatting may need cleanup.

Requires Rebuilding

  • Theme/storefront: BigCommerce Stencil themes do not convert to Shopify Liquid themes. Your storefront is rebuilt from scratch. This is usually the largest line item in a migration budget.
  • Custom code and scripts: Any custom JavaScript, webhooks, or server-side scripts built for BigCommerce need to be rebuilt for Shopify's architecture.
  • Integrations: Every third-party integration (ERP, CRM, email marketing, shipping, accounting) needs to be reconnected. Many of these integrations have Shopify-native equivalents or apps, but they still require configuration and testing.
  • Gift cards: Active gift card balances do not transfer. You need a plan: honour them manually, issue Shopify gift cards to match, or communicate a redemption deadline before migration.
  • Discount and promotion rules: BigCommerce promotions and price rules do not map 1:1 to Shopify's discount system or Shopify Functions. Each needs to be rebuilt.
  • Customer groups and price lists: BigCommerce's customer group structure differs from Shopify's B2B company model. If you use customer groups for wholesale pricing, plan the B2B architecture migration carefully.

SEO: The Migration Risk Nobody Budgets Enough For

This is where BigCommerce-to-Shopify migrations go wrong more often than anywhere else. BigCommerce and Shopify use different URL structures by default:

  • BigCommerce: /product-name/ or /category/product-name/
  • Shopify: /products/product-name and /collections/collection-name

Every product, collection, and page URL changes. Without a comprehensive 301 redirect map, every inbound link, every Google ranking, and every bookmarked URL breaks. For a brand with 2,000+ products and years of SEO equity, this is not a minor concern. It is a potential revenue cliff.

The SEO Migration Checklist

  1. Crawl the existing site before migration. Export every URL that receives organic traffic (not just products: categories, blog posts, custom pages, and even pagination URLs).
  2. Build a redirect map covering every URL. Automate where possible, but manually verify high-traffic pages. A single missed redirect on your top product category page can cost thousands in lost organic traffic per week.
  3. Preserve meta data: Titles, descriptions, and structured data should transfer exactly. Do not let the migration tool generate new meta descriptions from product content.
  4. Submit updated sitemaps to Google Search Console immediately post-launch.
  5. Monitor organic traffic weekly for 90 days post-migration. Some ranking fluctuation is normal. A sustained drop indicates missed redirects or canonicalisation issues.

In a living ecosystem, SEO monitoring is continuous, not a 90-day post-migration afterthought. Our monitoring surfaces ranking drops per market and per keyword cluster within days, not months.

The Migration Timeline

Realistic timelines based on complexity:

Scenario Description Timeline
Straightforward migration Under 500 products, standard theme, 2-3 integrations, no B2B 6-8 weeks
Mid-complexity migration 500-5,000 products, custom design, 5-8 integrations, basic B2B or wholesale 10-16 weeks
Enterprise migration 5,000+ products, ERP integration, B2B with customer groups, multi-currency, complex promotions 16-24 weeks

These timelines assume a single cutover rather than a phased migration. For brands with complex B2B operations, we sometimes recommend a phased approach: migrate DTC first, then layer in B2B 4-6 weeks later once the core platform is stable.

Investment Ranges

Realistic investment ranges for BigCommerce to Shopify Plus migration:

Scenario Description Investment
Straightforward DTC migration Theme rebuild, data migration, core integrations, SEO redirect map, QA and launch $50,000-$90,000
Mid-complexity with B2B Custom design, B2B architecture migration, ERP reconnection, advanced discount logic, comprehensive SEO preservation $120,000-$220,000
Enterprise with multi-market Full DTC + B2B migration, multi-market international setup, ERP and EDI integration, headless or hybrid storefront, complex fulfilment routing $250,000-$420,000

These numbers include project management, design, development, data migration, QA, SEO preservation, and launch support. They do not include ongoing platform management, which is a separate conversation, and the most important one.

The Post-Migration Problem

Here is what most migration articles do not tell you: the migration itself is not the hard part. The hard part is what happens after.

A typical agency migration engagement looks like this: 12-16 weeks of build, a launch day, 2-4 weeks of "hypercare" (fixing bugs), and then the engagement ends. The agency moves on. Your team inherits a platform they did not build, with integrations they do not fully understand, running on a codebase documented in Jira tickets that nobody will ever read.

Within six months, the site starts drifting. Shopify ships new features that nobody adopts because nobody is watching the changelog. A plugin update breaks a checkout flow and it takes two weeks to notice because the monitoring was in the agency's infrastructure, not yours. Performance gradually degrades as new apps are installed without load testing. The B2B buyer portal that was carefully architected during migration gets one customisation request after another from sales, each one adding complexity that was not in the original design.

This is not specific to BigCommerce-to-Shopify migrations. It is the structural failure of the project-based agency model applied to something that is not a project. Your commerce platform is not a building that gets constructed and handed over. It is a living system that needs continuous attention.

Dimension Project-based migration Living ecosystem migration
Launch day Project delivered. Clock starts on hypercare. Launch is the beginning of the relationship, not the end.
Integration monitoring Your team's responsibility after handover. AI monitoring surfaces integration failures (ERP sync errors, webhook timeouts, payment gateway issues) automatically. Human experts act on alerts.
Platform updates You find out about Shopify updates when something breaks or a competitor mentions them. New Shopify features evaluated within days of release. Relevant features implemented proactively.
Performance Fast at launch. Gradually degrades as apps accumulate and nobody profiles the impact. Performance monitored continuously. Degradation caught and resolved before it affects conversion.
SEO post-migration Monitored for 90 days, then responsibility transfers to your marketing team. Rankings monitored per market and per keyword cluster indefinitely. Drops surfaced and diagnosed within days.
Six months later You are searching for a new agency because the original team has no context. Same team, full context, continuous improvement. The site is measurably better than launch day.

When Not to Migrate

Migrating platforms is expensive, disruptive, and carries real risk. Here are situations where staying on BigCommerce is the right call:

  • Your BigCommerce store is working well and growing: If your conversion rates are strong, your integrations are stable, and your team is productive on the platform, there is no compelling reason to migrate. Platform switching has a real cost in disruption and institutional knowledge loss.
  • You rely heavily on multi-storefront: If you run multiple distinct brands from one BigCommerce instance and that architecture is working, Shopify's expansion store model may be a step backward for your specific use case.
  • Your B2B is deeply integrated on BigCommerce: If you have spent years building custom B2B workflows, customer group logic, and pricing rules on BigCommerce, migrating that complexity to Shopify's newer B2B model is expensive and risky. Make sure the delta justifies the cost.
  • You are under $5M in revenue: The economics of a Shopify Plus migration do not make sense below a certain revenue threshold. If your annual revenue does not justify a $50K+ migration investment, consider whether BigCommerce on a lower tier, or even Shopify (non-Plus), is a better fit.

Next Steps

If you are on BigCommerce and evaluating a move to Shopify Plus, the first step is not choosing an agency. It is getting an honest assessment of whether migration makes sense for your specific business.

We will audit your current BigCommerce setup, map your integrations and customisations, identify the migration complexity, and give you a realistic scope, timeline, and investment range. If staying on BigCommerce is the right call for your business, we will tell you that. We would rather lose a project than gain a client who should not have migrated.

About the author

Tim Sullivan

Lead Solutions Architect at Sonder. Has led platform migrations from BigCommerce, Magento, SFCC, and custom platforms to Shopify Plus for brands doing $10M-$100M in annual revenue. Based in Melbourne.

// Platform migration

Stay or migrate. Get honest numbers.

We will audit your BigCommerce setup, map the migration complexity, and give you a realistic scope and investment range. Brands doing $10M+ in annual revenue evaluating a move to Shopify Plus.

Replies within one business day. From the person who architects the migration.