After migrating to the V3 product experience, can I switch back to V2 again?

• Related Articles

• 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 ...

• When migrating products from V2 to V3, do you retain the same Product ID?

  Yes. your product IDs are retained. However, your SKU IDs (system created) will be regenerated as we are deleting V2 options/SKUs and recreating them in V3 formats.

• 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 ...

• Once I address the product exceptions after Step 1, do I have to restart the process?

  Yes, we will rerun Step 1 to make sure there are no product exceptions.

• 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.