BigCommerce to Shopify migration
We move BigCommerce stores onto Shopify and Shopify Plus with the catalogue, customers, order history and search rankings intact. Your BigCommerce store keeps selling right up to the day we switch.
Track record
The figures below are the practice a BigCommerce to Shopify migration is delivered from.
$100M+
Revenue our clients have taken through the Shopify stores we built and migrated. A migration is judged on what the store earns after cut over, not on whether the records landed.
500+
Builds, migrations and ongoing Shopify work across five hundred plus projects. A BigCommerce migration is not a first attempt here, it is a repeat of a process that has been run and corrected many times.
12+
BigCommerce is one of twelve platforms we move stores off. That range is why we recognise a BigCommerce specific problem, such as customer group pricing, before it reaches your new store.
10+
If your BigCommerce store sits alongside a till, the counter moves with it. We migrate ten plus POS systems onto Shopify POS so stock and customers stay in one place.
Why move
BigCommerce is a capable platform. The reasons merchants leave it are specific, and they are mostly about the checkout, the app ecosystem and how much you can change without a developer.
BigCommerce restricts what you can do to the checkout unless you are on its top tier. Shopify Checkout is the most tested checkout in ecommerce, and on Plus you can extend it with apps and your own code without rebuilding it.
The Shopify App Store is several times larger than the BigCommerce marketplace. In practice that means the integration you need usually already exists, and the developers who know it are easier to hire.
BigCommerce theme changes usually mean a developer and a Stencil build. Shopify 2.0 sections mean merchandisers change pages themselves instead of raising a ticket and waiting a sprint.
Shopify Markets handles currencies, domains, duties and local payment methods from one admin, rather than running a separate storefront for each region.
Shopify against BigCommerce
These are current figures from company filings and live storefront data, not from us, so check them before you quote them to a board. Worth knowing too: BigCommerce’s parent renamed itself Commerce.com in August 2025 and now trades as CMRC, folding BigCommerce in with Feedonomics and Makeswift. The platform is still supported. The question is not whether it works. It is whether the gap below matters at your scale.
3.1 to 1
Store Leads counted 31,946 stores moving onto Shopify against 10,271 leaving, in the year to mid 2026. That is the whole market rather than one platform pair, and it is measured from live storefronts rather than estimated. The traffic runs three to one in one direction.
41%
Shopify Plus takes about 41% of that band. BigCommerce reaches roughly 9%, which is its strongest showing anywhere and still four times behind. If that band is where you sit, it is where your peers already went.
$216B
Gross merchandise volume through Shopify in the first half of 2026, up 33% on the year before, taken from the company’s own filings. Scale of that kind is what pays for checkout, fraud and payments work you never have to do yourself.
8%
Live stores peaked at 48,231 in late 2019 and sat near 37,000 by May 2026, down about 8% in a year as the company moved upmarket. Fewer stores means a smaller pool of apps, agencies and developers who know the platform.
Scope
BigCommerce and Shopify are both hosted platforms, which makes the migration sound simpler than it is. They differ on URL structure, on how variants and custom fields are stored, on how customer pricing works and on what the checkout allows. Here is what is in scope on every project.
Data migration
Everything in your BigCommerce store that has a home on Shopify is migrated. Anything without a direct equivalent becomes a metafield rather than being quietly left behind. The last card is the honest part, the things that genuinely do not transfer.
Titles, descriptions, SKUs, prices, images, stock levels and every variant and option set you sell on.
BigCommerce categories become Shopify collections, with the nesting rebuilt as navigation and automated rules where they fit.
Accounts, billing and shipping addresses, customer groups and the history that tells you who your best buyers are.
Full order history with line items, statuses, totals, tax, shipping and refunds, attached to the right customer. Your original BigCommerce order numbers are kept on the record so support and accounting can still find an order by the number the customer has.
BigCommerce custom fields are mapped to Shopify metafields and wired into the theme, so they still show on the page.
Content, images and internal links, cleaned up on the way rather than pasted across with the old markup.
Meta titles, descriptions, canonical tags and image alt text move unchanged, so pages are not indexed from scratch.
Ratings, comments and authors move into your chosen Shopify reviews app. This one needs deciding early, because the app choice sets the format.
Passwords cannot move on any platform, because they are stored irreversibly hashed. Customers set a new one once, and we plan that email with you rather than letting them discover it. Gift certificate balances and discount codes are recreated rather than transferred, and custom Stencil code is rebuilt in Liquid because the two share nothing.
App by app
A BigCommerce app and its Shopify namesake are rarely the same product, and some of the biggest names run on both. Your own list is audited in discovery and priced before the build. These are the swaps that come up on almost every BigCommerce store.
BigCommerce filters products natively. Shopify does it through Shopify Search and Discovery, which is free, built by Shopify and enough for most catalogues. Deeper faceting on large or attribute heavy catalogues goes to Boost, Searchanise or Klevu. Searchanise runs on both platforms, so the move is a reconfiguration rather than a new tool.
Yotpo, Stamped and Okendo all have Shopify apps, so the vendor usually stays and the content is imported. Judge.me is the common choice on a tighter budget. Pick the app before the migration starts, because it sets the import format and reviews are the thing most often dropped in launch week.
ShipperHQ, the usual answer for rate rules and multi origin shipping on BigCommerce, publishes a Shopify app. Simpler rate tables fold into Shopify Shipping. Carrier calculated rates need Shopify Plus or the annual plan, which is worth knowing before you budget.
BigCommerce B2B Edition does not get replaced by an app. Shopify Plus covers company accounts, price lists, buyer portals and payment terms natively, so the work is configuration rather than a subscription. On plans below Plus this is customer tags and a wholesale app, which is a real downgrade and we will say so.
Feedonomics is the common BigCommerce feed tool and it still supports Shopify, though it is now owned by BigCommerce’s parent, which is worth a thought. Shopify’s native Google, Meta and marketplace channels cover most catalogues without a third tool.
Rebillia and PayWhirl subscribers cannot be moved as live contracts. Billing agreements are tied to the gateway and the platform, so subscribers re authorise on the new store. Recharge or Shopify Subscriptions takes over, and the customer messaging is planned with you rather than improvised.
Why Speed Plus
BigCommerce lets you publish products at flat custom URLs. Shopify puts them under a fixed structure. That means every indexed address changes, and a store with years of backlinks has the most to lose. We export the full indexed URL list in discovery, map each one to its Shopify address, and verify the set before the domain switches. See how the SEO work runs.
BigCommerce prices by customer group. Shopify uses price lists on Plus for B2B and customer tags for everything else. If that mapping is left until after import, buyers see the wrong prices on launch day. We map every group to its Shopify mechanism first.
A BigCommerce app and its Shopify namesake are rarely the same product. We list every active app in discovery and name the Shopify equivalent, the replacement or the custom build, with the cost attached, before the build starts.
Your BigCommerce store keeps selling until the moment DNS switches. We build and load the new store in parallel, so there is no maintenance window, no closed shop and no day of lost orders.
The people who scope your migration are the people who build it. No handover to a delivery team who were not in the room when the awkward parts were agreed.
We review the store, audit the integrations and put a fixed price in writing before the work starts. What moves that number.
Before you start
The checks we run before moving any BigCommerce store, from customer groups and custom fields to redirect mapping and payment gateways. Use it to brief us, or to brief anyone else.
No cost. We send it as a PDF.
Our migration process
Six steps, no downtime. Your BigCommerce store keeps taking orders until the day you choose to switch.
We read your BigCommerce store rather than guess at it. We record the plan you are on, the catalogue size, the option and variant structure, every active app, how customer group pricing is configured and the full indexed URL list. Group pricing and custom fields are the two that cause the most damage when they are found late, so they are found first.
Want to see what your own migration involves?
Get a free migration planProducts, customers, orders, categories and content are exported over the BigCommerce API into a private Shopify store. Custom fields are mapped to metafields before import, not after, because a field that was not mapped does not appear at all. Everything is reconciled against the source before the build continues.
Worried about a specific part of your catalogue?
Talk it through with usEvery app on your BigCommerce store is matched to a Shopify equivalent, replaced or rebuilt. Direct API integrations to an ERP, a PIM or a fulfilment house are rebuilt against Shopify rather than pointed at it. This is the part that moves the price, so it is priced on day one.
Running an ERP or a custom integration?
Ask about your stackYour Stencil theme is rebuilt as a Shopify 2.0 theme rather than converted, because nothing in a BigCommerce theme transfers. Brand, layout and product templates are matched, and a migration is the natural moment to fix the pages that were never converting anyway.
Migrating and redesigning at the same time?
Ask about a redesignEvery indexed BigCommerce URL is mapped to its Shopify address and the whole set is tested before go live. Metadata moves unchanged. This is the step that decides whether the migration costs you traffic, and it is entirely avoidable work that people still skip.
Worried about rankings?
See how we protect themWe run the pre launch checklist, switch DNS in a quiet window and keep the BigCommerce store available for reference. Then we watch Search Console, checkout conversion and every integration daily for thirty days, because the first month is when the things testing missed show up.
Ready to put a date on it?
Start your migrationMigration scenarios
Almost every BigCommerce store we are asked to move is one of these three, or a combination of them. The detail changes, the shape of the work does not.
BigCommerce standard plan, retail catalogue
Thousands of products carrying option sets that BigCommerce stores differently to Shopify variants. The work is in the mapping, not the volume.
Every product, variant and custom field reconciled against the BigCommerce API before launch.
BigCommerce with an ERP
The catalogue is the easy half. The integration that writes stock and pulls orders has to be rebuilt against Shopify, and it has to be priced before anyone commits to a date.
Integrations scoped and priced on day one, then built alongside the theme rather than after it.
BigCommerce B2B Edition
Group pricing and buyer accounts are where a BigCommerce migration goes wrong quietly. Mapped to Shopify Plus price lists and company accounts in discovery, then tested against live buyer logins.
Trade pricing verified against real buyer accounts before the domain switches.
SEO migration
BigCommerce lets you publish a product at almost any URL you like. Shopify puts every product and collection under a fixed structure. That means every address on your store changes, which makes redirects the single biggest risk in a BigCommerce migration and the one most often left to the last week. We map a redirect for every URL before launch and watch Search Console afterwards.
Products, categories, pages and blog posts each get a permanent 301 to their new address. Nothing is left to a catch all redirect pointing at the homepage, which passes no ranking signal and annoys the visitor.
We redirect what Google actually has indexed, pulled from Search Console and a crawl, rather than the list of pages someone remembers building.
Titles, descriptions, canonical tags and image alt text transfer unchanged, so pages are not re indexed from scratch.
We submit the new sitemap and monitor crawl errors, 404s and ranking movement after cut over, and fix what appears within hours rather than at the next sprint.
Which BigCommerce you are on
All of them migrate to Shopify. Which one you are on changes the effort and where the complexity sits, not the outcome.
The most common migration. The catalogue moves cleanly, the checkout is the reason for the move, and the work concentrates on redirects, apps and the theme rebuild.
Usually compared against Shopify Plus. Enterprise stores tend to carry API integrations and checkout customisation, so the integration audit is where the real scoping happens.
Company accounts, customer group pricing, buyer portals and payment terms map onto Shopify Plus B2B natively rather than needing an app. The mapping is done in discovery so the rebuild is explicit.
Cost and timeline
There is no useful single price for a replatform, and anyone quoting one before seeing your store is guessing. These are the five things that move the number. We review your store and put a fixed price in writing before any work starts.
Ten thousand simple products is a smaller job than five hundred carrying deep option sets and custom fields that have to be remodelled as variants and metafields.
The single biggest variable. An ERP, a PIM or a custom checkout integration costs more than anything in the catalogue.
Group pricing, company accounts and trade catalogues add a workstream of their own, and it is the one that has to be tested against real buyer logins.
Rebuilding your existing look is one price. Redesigning while you migrate is another. Nothing in a Stencil theme carries over either way.
A store with years of indexed pages and earned links needs a fuller redirect map and closer monitoring than a store launched last year.
Our Shopify expertise
A migration is usually the start. These are the other places we work.
Any platform to Shopify, from BigCommerce and WooCommerce to Magento, Salesforce and custom builds.
Square, Clover, Lightspeed and QuickBooks tills moved onto Shopify POS.
Company accounts, price lists, quotes and credit terms, native rather than bolted on.
Shopify 2.0 themes your team can edit, built to match what you already have.
ERP, PIM, email and custom checkout logic, reconnected and tested.
What we have learned moving stores and tills onto Shopify, written up.
Commerce Cloud replatforming, with the cartridge and integration audit done before the price.
Why Speed Plus
We are a Shopify Plus Partner and migrations are the work we do most. You get one team from the first store review through to the month after launch, and a price agreed in writing before anything begins.
Security
A migration means handing someone API credentials, your customer records and your admin. Here is exactly how we treat it.
No store access, no database, no screenshots until the agreement is signed.
A complete copy of your BigCommerce data and media is taken first. Nothing on your live store is changed.
Data leaves BigCommerce over an encrypted API connection and enters Shopify through the official Admin API. We ask only for the scopes the job needs, and credentials are revoked at the end.
Migration files are deleted once you confirm the new store is correct. We keep no copies.
A GDPR ready process, on Shopify, which is itself PCI DSS Level 1 certified.
FAQ
The questions we get asked on almost every migration call.
Four to ten weeks for most stores, from the first review to launch. A straightforward catalogue with a theme rebuild sits at the short end. Deep option sets, an ERP, B2B pricing or a redesign running alongside the migration push it to the long end. You get a date in the written scope, not a range.
No. Your BigCommerce store keeps taking orders until the day you choose to switch. We build and load the new store in parallel on a private Shopify URL, then change DNS in a quiet window.
Not if the redirects are done properly. BigCommerce lets you set flat custom URLs and Shopify uses a fixed structure, so every address changes. We map a permanent 301 for every indexed URL before launch, move the metadata unchanged and watch Search Console for thirty days afterwards. More on the SEO work.
Products with variants, images and stock, categories, customers with their addresses and groups, full order history, custom fields, blog posts, pages and SEO metadata. The full list is here.
Customer passwords, gift card balances, discount codes and any custom BigCommerce code. Passwords cannot cross between platforms, so customers set a new one on first login and we tell them before launch rather than letting them find out. Discount codes are recreated, gift card balances are planned for, and custom code is rebuilt or replaced.
No. Their accounts, addresses and order history move across. They set a new password the first time they sign in, which Shopify handles with an account invite. We send that as a planned email rather than a surprise.
Not natively at the same depth, and we would rather say that here than after launch. BigCommerce ships faceted search on its higher plans at no extra cost. On Shopify the free Search and Discovery app covers filtering for most catalogues, but a store that depends on deep multi attribute faceting needs a paid app such as Boost, Searchanise or Klevu, at a monthly cost BigCommerce was absorbing. In discovery we check your analytics to see how customers actually use your current filters, then recommend the cheapest option that matches real behaviour, and we price it into the plan rather than leaving you to find it.
Yes. Shopify Plus B2B covers company accounts, custom catalogues, price lists, buyer portals and payment terms natively. We map your existing B2B configuration to its Plus equivalent in discovery so the rebuild scope is explicit before development starts.
They become price lists on Shopify Plus for B2B pricing, or customer tags for segmentation on other plans. This mapping is agreed before any product is imported, because group pricing applied after the fact is the most common source of wrong prices on launch day.
They are mapped to Shopify metafields and wired into the theme so they still display. A custom field that is not mapped before import simply does not arrive, which is why the mapping is part of discovery rather than a later task.
It depends on catalogue complexity, integrations, B2B configuration and design scope. We will not quote a number before seeing the store. We review it, audit the integrations and give you a fixed price in writing before any work begins. What moves the price.
Yes, and it is usually the sensible moment. Nothing in a BigCommerce Stencil theme transfers to Shopify, so the storefront is being rebuilt either way. Redesigning while you migrate costs less than doing it twice.
No. Stencil and Liquid are different technologies and no BigCommerce theme converts to Shopify. We rebuild the storefront, matching your brand and layouts, as a Shopify 2.0 theme your team can edit afterwards.
Yes, into whichever Shopify reviews app you choose. The app has to be chosen early because it sets the import format. Left until launch week, reviews are the thing that usually gets dropped.
Yes, and you should. Changing platform and domain at the same time doubles the risk for no benefit. We keep the domain and move the platform underneath it.
Thirty days of monitoring is included on every migration, covering crawl errors, 404s, checkout conversion and integration health. Ongoing Shopify support carries on after that if you want it.
They reconnect rather than migrate. Klaviyo, for example, keeps the same account and subscriber list, but the BigCommerce integration is switched off and the Shopify one switched on, and flows triggered by BigCommerce events have to be rebuilt against Shopify events because a trigger cannot be edited once it is set. We line that up before cut over so your abandoned checkout and welcome flows keep running on launch day instead of going quiet for a week.
The store review starts within days of access being granted, and it is the real answer to scheduling, because it produces the scope, the risk list and the fixed price that let both sides commit to a date. Build slots depend on current bookings, which we will tell you plainly on the first call rather than promising a start date we cannot hold.
Thirty days of monitoring is part of every migration: Search Console, analytics, checkout and every integration queue watched daily, with fixes for whatever real traffic surfaces that testing did not. After that most clients keep us on for ongoing work, but the migration stands on its own and ends with your team trained on the Shopify editor.
Insights
Posts are on the way.
Start here
Tell us what you are running on BigCommerce and what it connects to. You get back a written scope, an integration audit and a fixed price before any work starts.
Every Magento version, including Magento 1 and Adobe Commerce
Send us your BigCommerce URL and the plan you are on. Within two working days you get a written plan, a fixed price and a list of exactly what moves. No cost and no pressure.
