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

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 APIs twice, once with V2 and then later with V3.
  • Migrating to MSF: Merchants consolidating V2 store(s) to multi-storefront that requires V3 product experience.
  • Adding New Store(s): New stores come with V3 only. Merchants may want to upgrade existing V2 stores to standardize all store product experiences for efficiency.
  • Better Features: For faster APIs, metafield visibility, ability to attach options and modifiers directly to products (i.e., no need to create Option Sets thus simplifying new product setups), new V3 only API resources like Cart API, Payments API, & Widgets.
  • Migrate before V2 support ends: Merchants want to migrate to V3 now and not be caught by surprise if BigCommerce sunsets V2. That may happen eventually.
  • Skills / Knowhow: Hiring talent that is familiar with V2 to maintain BC stores may become more difficult. If you’re referring to just the V3 UI layout vs V2 UI layout, I guess it is what it is. I know it takes fewer clicks to set up a product in V3 UI compared with V2.

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

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

    • Do we need to contact BigCommerce support during the migration?

      Hopefully not. In some cases, BigCommerce database can have some abandoned IDs that needs to be flushed out and due to which the prompt required to update the UI to V3 experience does not show up. As BigCommerce is aware of this issue, they clean ...

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