How do you migrate option that are reused by multiple option sets when active option values are a subset of the original option?
Our approach involves identifying the active option values for the option and creating only those values per option for the products linked to the option set. (e.g., Optionset-1 is using the Option: Size with values S,M, L and Optionset-2 is reusing the Option: Size with values S, L then all products associated with Optionset-2 will have the size option only with S, L as values)
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 ...
How are option sets with more than one option display type migrated? (e.g., radio button, drop down, checkbox, pick list)
Assuming the option set is linked to multiple products, all options within the set are created as individual options for applicable product. Options involved in SKU generation are created as Variant Options and others are created 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 option without SKU as Variant Option?
No. V3 requires you to have SKUs created for all options that need to be migrated as Variant Options.
Can you migrate V2 options as Shared Variants or Shared Modifiers?
No, it’s not possible to migrate V2 options as Shared Variants or Shared Modifiers. All options will be created as individual options on the products.