How to Migrate from BigCommerce to Shopify Without Losing Your Product Data

A homewares merchant exports their BigCommerce catalogue: 800 products, clean rows, all the expected columns. They import the file into Shopify using the standard CSV importer. Shopify creates 2,400 products.

No error message appears. The import completes successfully. The problem is structural: BigCommerce exports each variant as a separate row with a unique Product ID. Shopify expects variant rows grouped under a shared Handle value. Without that grouping, every row becomes its own product.

This is the bigcommerce to shopify migration problem that no migration guide addresses. Guides covering theme setup, domain transfer, and URL redirects are widely available. The product catalogue step (where most migrations actually stall) gets treated as a footnote. This guide covers the data problems that appear in every BigCommerce export and how to fix them before a single product goes live on Shopify.

Why BigCommerce Product Data Doesn't Import Cleanly into Shopify

BigCommerce and Shopify store product data differently at a structural level. Three specific incompatibilities appear in every bigcommerce to shopify migration, regardless of catalogue size or product category.

The first is variant structure. BigCommerce's Option Set system assigns each variant combination a unique row in the export, identified by a Product ID. Shopify's import format expects variants grouped under a shared Handle value. When a BigCommerce export with 10 products and 4 colour options arrives in Shopify without restructuring, Shopify reads 40 rows and creates 40 separate products.

The second is category taxonomy. BigCommerce uses a tree hierarchy of custom categories. Shopify uses a standardised product taxonomy mapped to metafields. There is no conversion table that maps BigCommerce categories to Shopify metafield values. A direct import carries category names across as plain text, with no connection to Shopify's taxonomy system and no feed into Google Shopping categories.

The third is description quality. BigCommerce descriptions often include platform-specific formatting such as inline styles, <br> tags, and div wrappers that render inconsistently in Shopify's product template. Many BigCommerce merchants also carry supplier copy or manufacturer descriptions, which appear word-for-word across every other retailer stocking the same products. That duplicate content problem follows the migration to Shopify unchanged.

What the BigCommerce CSV Export Contains

The BigCommerce product export includes everything you need to reconstruct a product listing, and several columns that don't map to any Shopify field. Understanding the export structure is the first practical step in a bigcommerce to shopify migration.

Columns present in most BigCommerce exports: Product ID, Product Name, SKU, Description (HTML), Brand, Weight, Price, Sale Price, Category, Option Set Name, and Option Value. Some exports include full image URLs; others reference images by filename without a URL path, which requires a separate image import step.

What is absent or incorrectly formatted for Shopify: Handle (does not exist in BigCommerce exports), Shopify-format variant inventory columns, HS codes, country of origin, and any metafield columns aligned to Shopify's product taxonomy. Weight units also vary; BigCommerce stores may be configured for lbs, kg, or oz, and Shopify defaults to kg without automatic conversion. If weight was entered in lbs on BigCommerce, it arrives in Shopify as the same number with the wrong unit.

The practical consequence is that the export looks complete, but it needs variant restructuring, field remapping, and data enrichment before Shopify can use it correctly.

The Manual Approach and Where It Breaks

Manual BigCommerce CSV cleanup is achievable for catalogues under 50 products. Beyond that, the time cost scales quickly enough to make it impractical for most merchants.

Variant restructuring requires identifying every product group in the export, assigning matching Handle values to each row in the group, and adding Option Name and Option Value columns in the format Shopify expects. For a 500-product catalogue with an average of 4 variants, that is 2,000 rows to reassign, with no validation step that confirms every Handle was entered consistently. A single typo splits a variant group into two separate products, with no indication of which row caused the problem until the merchant reviews the Shopify catalogue manually.

Data research for missing fields compounds the work. HS codes for international shipping, correct weight units, and country of origin take 5 to 15 minutes per product to find and verify. At that rate, filling missing fields for 200 products takes 20 to 50 hours.

Descriptions add another layer. Stripping BigCommerce-specific formatting, removing inline styles, and rewriting supplier copy into retail-quality text takes 20 to 30 minutes per product for a careful writer. A 200-product migration runs 70 to 100 hours of writing.

The situation mirrors migrating from WooCommerce closely. The surface export formats differ, but the underlying problems are the same: variant structure mismatch, missing compliance fields, and imported descriptions that carry duplicate content into the new store. The manual time cost follows a similar curve on both platforms.

Step-by-Step: BigCommerce to Shopify Product Migration

1. 01
   Export your BigCommerce catalogue

   Use the BigCommerce export tool to download your product catalogue as a CSV. Include all fields; you can filter and remap them during the import
2. 02
   Upload to Importier

   Import the raw BigCommerce CSV without any pre-processing. The import wizard auto-maps BigCommerce column names like 'Product Name', 'Option Set Name', and 'Option Value' to the correct Shopify fields
3. 03
   Review column mapping

   The wizard proposes a mapping for each column in the file. Review the suggestions and correct any mismatches before proceeding. Most BigCommerce exports map correctly in under 3 minutes
4. 04
   Confirm variant groupings

   Smart Variant Detection analyses the export and proposes variant groups based on product name and option patterns. The preview shows each proposed product with its option names, option values, and variant count
5. 05
   Review enriched data

   The wizard fills missing weight, HS codes, country of origin, and barcodes automatically. Enriched values appear in the preview for merchant review before any product is committed
6. 06
   Generate descriptions

   Select a description style appropriate for the catalogue range and generate AI descriptions for the full batch. This replaces any imported BigCommerce copy during the same run
7. 07
   Import to Shopify

   Confirm the import. Products arrive in Shopify with correct variant groupings, complete data fields, and new descriptions in a single operation

Fixing Variant Structure: BigCommerce Option Sets vs Shopify Handles

BigCommerce's Option Set system is the source of the variant problem in every bigcommerce to shopify migration. An Option Set defines the variant dimensions for a product (Size, Colour, Material) and each combination appears as a separate row in the export with a distinct Product ID. There is no Handle equivalent: no shared identifier groups related rows together.

Importier's Smart Variant Detection reads the raw BigCommerce export and proposes variant groups without requiring any pre-processing. The pattern library covers 150+ variant types across 15+ industries: size ranges (S/M/L/XL, numeric UK and EU sizing), colour names and supplier codes (BLK/NVY/WHT), storage capacities, pack sizes, materials, and flavours. For fashion and apparel catalogues (one of BigCommerce's most common merchant categories), detection accuracy on Size and Colour combinations is consistently high.

The import preview shows proposed groupings before any product is committed to Shopify. A merchant can review the proposals, split any incorrectly merged groups, and confirm the results in one step. For variant grouping during migration, this preview step is where most catalogues need a handful of manual corrections, typically on products where the supplier uses non-standard size naming or abbreviated colour codes outside the pattern library.

Category Taxonomy and Shopify Metafields

BigCommerce categories do not map to Shopify's product taxonomy. This is one of the most overlooked data problems in a BigCommerce to Shopify migration, and it carries real consequences for Google Shopping performance after the move.

BigCommerce categories are custom text labels arranged in a tree hierarchy. When imported, they appear in Shopify as plain tags or vendor names; they do not populate Shopify's standardised taxonomy system. Shopify's taxonomy drives Shopify category metafields, which feed directly into Google's product type classification and Shopping category matching.

Products without correct taxonomy values qualify for fewer Shopping placements and appear without the structured attributes (Size, Material, Age Group) that Google displays in product listings.

Importier's category metafield system covers 22 industry packs and 3,758 attribute types aligned to Shopify's Standard Product Taxonomy. After the product import, the category metafield step assigns standardised taxonomy values based on each product's type, title, and description.

For a BigCommerce fashion store migrating apparel: Size Type, Age Group, Material, Pattern, and Care Instructions populate automatically without any manual taxonomy mapping. For homewares: Material, Colour Family, Shape, and Care Instructions fill at the same stage.

This step is worth completing before launching Google Shopping on Shopify. Products with complete metafields qualify for richer product listings in Shopping results from the first day the feed goes live.

Handling Descriptions After Migration

BigCommerce descriptions fail on Shopify for two distinct reasons. Formatting is the visible one: BigCommerce's rich text editor produces HTML with inline styles, class names from BigCommerce's template system, and line break tags that Shopify's product template renders inconsistently.

Content quality is the less visible but more lasting problem: most merchants either use supplier copy verbatim or wrote descriptions once for BigCommerce's page layout. That copy rarely performs well in Shopify's SEO context, and it creates duplicate content if several retailers import from the same supplier.

Importier's description generation replaces imported copy during the same import run. 7 description styles (Standard, Technical Gadget, Emotional Storytelling, Benefits-First, Sensory-Rich, Ingredient Spotlight, and Custom) cover the range of products typically hosted on BigCommerce. 156 expert personas across 43 industry categories ensure that a sporting goods catalogue generates descriptions with different vocabulary and emphasis than a luxury homeware catalogue.

For AI-generated descriptions that reflect a specific brand voice, the Brand Voice field carries consistent tone, vocabulary, and any required disclaimers across every description in the catalogue. 18+ AI models are available across Importier's plan tiers, with no per-token charges on any tier. The configuration is set once and applies to the full migration run.

“

A BigCommerce catalogue with supplier copy is a duplicate content liability. One import run can fix the variant structure, the data fields, and the descriptions at the same time.

Safety Net: Import History and Undo

One-time migrations are higher stakes than recurring supplier imports. A variant grouping error on a 500-product catalogue produces 2,000 incorrectly structured products; without an undo function, correcting that requires manually unpublishing or deleting each one individually, then running the import again from scratch.

Import History logs every run with the file name, date, product count, and a breakdown of new products created versus existing products updated. Import Undo reverts every product from a selected batch in one operation. Up to 20 import snapshots are retained, and the source CSV remains available for download for 60 days.

In practice, this changes the risk calculation before confirming a large import. Reviewing the preview carefully before committing is still worth doing. But knowing that a full undo is available in one click makes it reasonable to run a 1,000-product migration without spending an additional hour rechecking every mapped column.

If the merchant also needs to load a supplier catalogue after migration to stock the newly migrated Shopify store with incoming inventory, the same import workflow handles that as a follow-on step, with its own import session and a separate History snapshot to track it independently.

Key Takeaways

• BigCommerce exports each variant as a separate row. Without restructuring, a 500-product catalogue with 4 variants creates 2,000 separate Shopify products and no import error appears during the process.
• The manual cleanup approach is viable for under 50 products. For larger catalogues, variant restructuring, data research, and description rewriting combined run to dozens of hours before a single product is correctly live on Shopify.
• Smart Variant Detection handles variant grouping from the raw BigCommerce export without pre-processing. 150+ patterns across 15+ industries cover the variant types found in most BigCommerce catalogues.
• BigCommerce categories do not map to Shopify taxonomy. The category metafield step assigns standardised values to every product after import; this is what feeds Google Shopping correctly after the migration completes.
• Import Undo makes a large one-time migration significantly less risky. A full batch revert is available in one click for up to 20 snapshots, which removes the pressure to get every detail right before confirming a large import run.

Try Importier free at importier.app

Related Articles

• How to Migrate from WooCommerce to Shopify
• How to Import Product Variants in Shopify Without Restructuring Your Supplier CSV
• Shopify AI Product Descriptions: The Complete Guide
• What Are Shopify Category Metafields and Why They Matter
• Shopify Wholesale Product Import: Add Your Supplier Catalogue Without Manual Entry