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 V2 data to the V3 sandbox. The progress on transformation will be displayed in the text Status message.

b. CLICK on the "Download Catalog Reports" button. Reports will be enabled once the transfer of product data is completed.

c. REVIEW reports: Configurable Fields Report, Option Report, Option Set Report, Product Exception Report, Product Option Report, Product Rule Report NOTE: We process standard product data from V2 to V3 sandbox store for your review.

Step 2: Process Option Set rules to V3 Sandbox

a. CLICK the "Start" button to process the option set rules to V3 sandbox and generate V3 SKU adjusted values.

b. VIEW "Status Message" section that displays the progress on processing option set rules.

Note: If this is not applicable to you. Simply CLICK the "Skip" button to proceed.

Step 3: Unlink V2 Option Sets & Delete V2 Configurable Fields

a. CLICK the "Start" button to unlink all options and option sets of the products and delete configurable field data associated with them.

b. VIEW "Status Message" section that displays the details of unlinking/deletion of option sets/configurable products.

c. CLICK the "Download Error Report" button. This will be enabled once unlinking and deletions are completed.

Step 4: Update Current User V2 Interface to V3 Experience 

a. CLICK the “Update Now” button on the banner shown at an individual product level screen in your BigCommerce V2 store to update the UI to the V3 experience.

b. CLICK on the "Update Completed" button once your UI is updated to the V3 experience.

Note: If you're still unable to see the banner after performing step 3, contact support@striketru.com for help. 

Step 5: Convert V2 Products to V3

a. CLICK the "Convert" button to convert product data from V2 to V3 (Variant option, Variants, and Modifiers).

b. VIEW the "Status Message" section that displays the count of converted products.

c. CLICK the "Download Conversion Report" button. This will be enabled once product conversion is completed. 

• Related Articles

• Which V2 catalog elements are migrated?

  We migrate products, options, option images, option sets, SKUs, product rules, option set rules and configurable fields. Rest of data like product images, categories, brands, categories, bulk pricing, pricelists, custom fields etc. are retained as ...

• For how long will StrikeTru hold on to V2 store data?

  Your product data will be stored for a period of 1 month in JSON formats.

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

• Can you migrate customers, orders, themes, etc.?

  No. Considering that the app is used to upgrade products to V3 experience in the same store, it does not migrate customers, orders, themes, etc. If you want to migrate your catalog to a separate V3 store, you will then need to migrate customers, ...