Can you migrate V2 options as Shared Variants or Shared Modifiers?

• Related Articles

• Migrate Product Data

  The migration process involves 5 steps. NOTE: Before starting the migration process, DELETE existing product data in the V3 sandbox store. Step 1: Profile Catalog Data & Migrate Products to V3 Sandbox a. CLICK on the "Start" button. App will transfer ...

• Do you migrate rules applied to the options without SKUs?

  Yes, rules (price & weight) applied to options without SKUs will get created as Modifier rules. Assumption: Options without SKUs need to be migrated as Modifier Options.

• Why should I migrate my BigCommerce products from V2 to V3 experience?

  Here is why you should migrate from V2 to V3: Modernizing Tech Stack: Merchants implementing new systems (ERP, OMS, PIM, Marketplace Listing Tools like Feedonomics and ChannelAdvisor, etc.) want to avoid integrating those systems with BigCommerce ...

• Can you migrate products with 600+ SKUs?

  In BigCommerce V3, you must create explicit SKUs (i.e., variant options). BigCommerce allows you to create a maximum of 600 SKUs. V2 did not have the restriction as it did not require you to create explicit SKUs. Our app reports which of your V2 ...

• Can you migrate a product that uses an unequal number of options to generate a SKU? (e.g., SKU1: color, size, SKU2: color, SKU3: size)

  No, we identify such product as an exception in our reports. BigCommerce V3 expects all your Variant Options to participate in the SKU generation, hence such product setup is not compatible with V3. You can rebuild these product pre/post migration.