BigCommerce to Shopify Migration: Complete 2026 Guide

BigCommerce vs. Shopify at a glance

This is a different migration from the Magento one. Both platforms here are hosted SaaS, both have real CSV tooling, and the catalog concepts map more cleanly than most pairs. The friction is concentrated in four places: the URL structure, the variant model, modifiers, and the theme. Know those four and the rest is admin work.

One quirk worth naming because it's so often the reason people leave: BigCommerce moves you up a plan tier automatically once your trailing-twelve-month sales cross the tier's threshold. Nothing equivalent exists on Shopify - you pick the plan. If that's what brought you here, the good news is the rest of this migration is very doable in-house.

Before you start: audit your BigCommerce store

BigCommerce stores are tidier than Magento stores, but the tidiness hides the two things that don't migrate: modifiers and customer-group pricing. Spend a couple of hours on this audit before exporting anything.

1. Count what you have. Products → View for the product count, Customers for the customer count, Storefront → Product Categoriesfor the category tree. Screenshot the totals - they're your verification numbers after import.
2. Find every product that uses modifiers. Modifiers are BigCommerce's non-SKU options: engraving text boxes, gift-wrap checkboxes, file uploads, "add a second unit" pick lists. They do not come along in the product CSV, and Shopify has no native feature for them. List these products now; section 5 covers your options.
3. Check for products with more than 3 options. BigCommerce allows more option dimensions than Shopify's hard 3-option cap (Size, Color, Material is the classic trio). A product with Size + Color + Length + Style needs restructuring before it can exist on Shopify - usually by splitting into multiple products or folding two options into one.
4. List customer groups and their pricing rules. Customers → Customer Groups. If wholesale customers get 20% off via a group rule, that logic needs a Shopify equivalent (B2B catalogs on Plus, or an automatic discount / app on lower plans) before launch, or your trade customers see retail prices on day one.
5. SEO baseline. Export your top pages from Google Search Console (Performance → Pages, 16-month range, sorted by clicks). Because BigCommerce URLs live at the domain root, every one of these URLs will change - this list is your minimum redirect map.
6. Crawl the live site.Screaming Frog (free up to 500 URLs) gives you the complete URL inventory including web pages, blog posts, and category paths - the ground truth you'll diff your redirect map against.

Step 1 - Export everything from BigCommerce

BigCommerce's export tooling is genuinely good - better than most platforms you could be migrating from. Everything lives under the control panel's export screens:

The four exports you need

1. Products - Products → Export, and choose the Bulk Edit template. This matters: Bulk Edit is the template with specifically named columns (including Product Image File - 1, Product Image File - 2… for images and per-SKU rows for variants), and it's the format every migration tool expects. Export as CSV. If your control panel is on the newer import/export experience, the equivalent is the products export with all columns included.
2. Customers - Customers → Export. Name, email, addresses, phone, customer group, store credit. Passwords are not in the file and never will be - they're hashed. Section 8 covers what to do about that.
3. Orders - Orders → Exportwith the default template. You'll want this even if you don't plan to import order history, because it's your permanent record once the BigCommerce subscription ends.
4. Everything with no export button.Product reviews, blog posts, web pages, and gift certificate balances have no CSV export in the control panel. Reviews can be pulled via the API (or a reviews app's own export) - do it before you cancel the plan. Blog posts and web pages are copy-paste jobs. Gift certificates: export the list from Marketing → Gift Certificates so you can re-issue balances as Shopify gift cards.

Two details people miss. First, image columns in the Bulk Edit CSV contain paths on BigCommerce's CDN - those URLs keep working only while your BigCommerce store exists. Any import that references them (rather than copying the files) breaks the day you cancel. Every serious tool copies the images across; just don't hand-roll an import that hotlinks. Second, if you want to see exactly how BigCommerce structures product, SKU, and image data before you export, our free BigCommerce product CSV template shows the format with three worked examples.

The BigCommerce → Shopify field mapping

Here's the full column map from the Bulk Edit export to Shopify's product fields (the same columns you'd see in a Shopify product CSV). Most of it is mechanical; the price fields are the trap, so they get their own box below.

Variants, options, and the modifier problem

BigCommerce splits product options into two kinds, and only one of them exists on Shopify.

Variant options(the ones that generate SKUs - Size, Color) map cleanly. Since October 2025 Shopify supports up to 2,048 variants per product on every plan, so BigCommerce's 600-SKU ceiling fits with room to spare. The one hard wall is Shopify's 3-option maximum: a BigCommerce product with four option dimensions cannot be represented directly. Your choices are to split it into multiple products, to merge two dimensions into one combined option ("Color / Trim"), or to demote the least-SKU-relevant dimension to a line item property.

Modifiers- text personalization, checkboxes, file uploads, "no thanks / add for $5" pick lists - are the real gap. They aren't SKUs, they aren't in the CSV export, and Shopify has no native feature for them. The honest options:

• Line item properties - free, built into Liquid themes as custom form fields on the product page. Fine for a plain engraving text box; you (or your theme developer) add the field to the product template.
• A product options app (Infinite Options, Globo, Bold) - the app-store answer, from about $10/month. Choose this when modifiers carry price adjustments, conditional logic, or file uploads.
• Restructure- sometimes a checkbox modifier ("add gift wrap +$5") is better modeled as a separate product added by an upsell block. More honest inventory, cleaner reporting.

Whatever you choose, rebuild modifiers beforelaunch and test an order through checkout for each modifier-heavy product. This is the migration's most common silent revenue leak.

Step 2 - Pick a migration tool

There are four serious paths, and unusually for a migration, the free first-party one is genuinely viable here - Shopify's Store importer lists BigCommerce as a source right in the drop-down.

Step 3 - Run the import

1. Import products first, alone. Verify before touching customers or orders. Check the count against your audit screenshot, then spot-check twenty products: one multi-variant, one with many images, one that was hidden, one with a Sale Price, one with custom fields.
2. Check the price mapping explicitly.Filter your new Shopify catalog for products where Compare-at ≤ Price - that's the three-price trap surfacing. Zero results is what correct looks like.
3. Rebuild the category tree as collections. BigCommerce categories nest; Shopify collections don't. The usual pattern: each leaf category becomes a collection, and parent categories become either navigation menus or collections populated by tag rules. Your main menu does the nesting work that the category tree used to do.
4. Watch the media cap. Shopify allows 250 media items per product. Catalogs that used BigCommerce image rows aggressively (one image per SKU on big-variant products) can brush against it - the importer will drop the overflow silently, so diff image counts on your most image-heavy products.
5. Leave everything in Draft until redirects are ready. You control the go-live moment in Step 8, not the importer.

Step 4 - Customers, orders, and gift certificates

Customersimport cleanly from the CSV - names, emails, addresses, and tags for their old customer group. Two things don't come: passwords (hashed on both platforms; nobody can move them) and group pricing rules. Plan a re-activation email for launch week inviting customers to set a new password - frame it as the upgrade it is, not an apology. If you had wholesale groups, have the Shopify-side equivalent (B2B catalogs, tagged automatic discounts, or an app) live before that email goes out.

Ordersimport as historical records - they show in customer profiles and reports but aren't re-charged or re-fulfilled. The Store importer and Cart2Cart both handle this. If you skip order import entirely (plenty of stores do), keep the BigCommerce order export archived; tax authorities don't care which platform you were on.

Gift certificatesare the sneaky liability. Outstanding BigCommerce certificate balances don't transfer - but your customers are still legally holding them. Export the list, then issue equivalent Shopify gift cards (available on all plans) to the same emails. Do this on launch day, not when the first angry email arrives.

Step 5 - The SEO redirect map

This is the step that decides whether your organic traffic survives, and BigCommerce → Shopify is the migration where it's least optional. BigCommerce puts products, categories, and pages at the domain root: /blue-widget/, /widgets/, /about-us/. Shopify enforces its prefixes: /products/blue-widget, /collections/widgets, /pages/about-us. There is no overlap. Every URL on your site changes.

1. Build a two-column CSV: old path, new path. Your Screaming Frog crawl is the left column; the product/collection/page handles you just created are the right. For most stores the mapping is mechanical: /blue-widget/ → /products/blue-widget.
2. Upload it in Shopify under Online Store → Navigation → View URL Redirects → Import. Shopify applies them as 301s.
3. Cross-check against your GSC top-pages export - every URL with clicks in the last 16 months must resolve. Then check the long tail from your crawl: old paginated category pages, brand pages, and the /xmlsitemap.phpsitemap URL itself (Shopify's lives at /sitemap.xml).
4. After launch, watch GSC's Coverage report for 404s weekly for a month. Each one you find is a redirect you missed while it still has rankings to save.

Step 6 - Theme rebuild (Stencil doesn't come with you)

There is no path from a Stencil theme to a Shopify theme - the templating languages, section models, and asset pipelines share nothing. Treat the storefront as a rebuild and time-box it: pick an Online Store 2.0 theme close to your current layout (Dawn is the free default and a fine starting point), port your brand tokens - logo, palette, type - then rebuild the homepage and product template before anything else. Your category landing pages become collection pages; if you leaned on BigCommerce's faceted search, Shopify's free Search & Discovery app provides the filter facets on collection pages.

The upside nobody mentions: the rebuild is the one moment you'll ever audit ten years of accumulated homepage widgets honestly. Most stores launch on Shopify visibly cleaner than they left.

Step 7 - Apps, shipping, tax, and payments

• Apps.For each BigCommerce app, find the Shopify equivalent before launch - but check the native feature list first. Reviews need an app on Shopify (Judge.me is the usual pick - import the review CSV you exported in Step 1). Faceted search is covered by Search & Discovery. Abandoned-cart email is native on both.
• Shipping. Zones, rates, and free-shipping thresholds re-enter by hand in Settings → Shipping and delivery. BigCommerce per-product fixed shipping prices have no direct Shopify field - model them with shipping profiles.
• Tax.Shopify Tax handles US sales tax natively. If you used Avalara on BigCommerce, decide whether you still need it - many stores under the economic-nexus thresholds don't.
• Payments.Shopify Payments takes minutes to enable and removes the extra transaction fee third-party gateways carry. If you keep PayPal, reconnect it fresh - don't assume settings carried over, because nothing did.

Step 8 - Switching the domain and verifying

1. Publish the theme; flip imported products from Draft to Active.
2. Point the domain at Shopify (Settings → Domains - connect or transfer; Shopify handles SSL automatically).
3. Immediately place a real test order with a real card - through a modifier product if you have them - then refund it.
4. Verify the redirect map on the live domain: spot-check your top 20 GSC URLs by hand.
5. Submit /sitemap.xmlin Search Console (same property - the domain didn't change, just the platform).
6. Keep the BigCommerce store paid up for at least a month, storefront hidden. It's your reference copy for the products, images, and settings you'll discover you need. Cancel only after the image copy is verified.

How much does it cost? How long does it take?

A realistic budget for a store doing it in-house: the software cost is trivial (the Store importer is free; Matrixify or Cart2Cart run tens to a few hundred dollars), the real spend is time. Catalog export, import, and verification is a two-to-four-day job for most stores. The theme rebuild is one to six weeks depending on how custom your Stencil theme was. The redirect map is a day of honest spreadsheet work. Agencies quote $2,000–$15,000+ for the whole package, and most of that is the theme.

End to end: a focused small store lands in two to three weeks; a store with heavy modifiers, wholesale pricing, and a custom theme should plan for six to eight. The catalog is never the long pole - the storefront and the edge cases are.

What breaks: the 10 most common pitfalls

1. The whole store shows "on sale." The three-price mapping done naively. Fix the mapping, not the products.
2. Modifiers silently dropped.They're not in the CSV. Personalization revenue disappears without an error message.
3. Redirects only cover products. BigCommerce category, brand, and web-page URLs were root-level too. All of them changed.
4. Images hotlinked to the BigCommerce CDN. They work all through testing, then the subscription ends and the catalog goes blank. Verify files were copied, not referenced.
5. Four-option products imported wrong. Shopify's 3-option cap truncates or scrambles them. Restructure before import, not after.
6. Wholesale customers see retail prices. Customer-group pricing doesn't migrate. Have the B2B equivalent live before the password-reset email lands.
7. Gift certificate balances stranded. A legal obligation, not a feature. Re-issue as Shopify gift cards on day one.
8. Reviews left behind.No export button; once the store closes they're gone. Pull them via the API or a reviews app before cancelling.
9. Blog posts and web pages forgotten.Also no export. They're usually your oldest, most-linked URLs - move and redirect them.
10. Out-of-stock variants hidden by theme settings. BigCommerce and Shopify themes make different default choices about showing unavailable options - check a product you know has stockouts.

If you hit any of these after the fact, you rarely need to re-run the whole migration - fix the mapping for the affected products and re-import just those, or pull them fresh from the still-live BigCommerce storefront with Product Upload. And if you're weighing other routes off BigCommerce or comparing platforms first, the store migration hub has the companion guides.