BigCommerce v2 to v3 Migration Guide: When Is It the Right Time to Migrate?

In 2019, BigCommerce updated its product functionality to improve API accessibility, boost omnichannel sales, and make variant and other SKU-level attributes easier to manage. 

The products on BigCommerce now use the platform’s Catalog v3 API. The Catalog v3 API varies from the v2 API in terms of functionality and usability, and there are some clear markers that indicate that some merchants should migrate to the new version – whereas others might be better served by v2. 

Here’s a high-level view of what you need to know.

BigCommerce v2 vs. v3: What They Offer 

There are several differences between BigCommerce v2 and v3 which can make a substantial impact on the user experience. These can be broken down into several sets of categories: 

• User Experience: In v2, product details are split across multiple tabs. In v3, details can be edited on a single page; a custom view of frequently-used or edited sections can be pinned to the sidebar for ease of product entry/management.
• Customs Information: In v2 customs information can only be added through the API; in v3 it can be added through the API or directly to products through the control panel. 
• Option Organization: In v2, options are organized into sets that can be set as optional or required. In v3, there are two tops of options, variant and modifier options, which can be applied either to individual products or to groups of products. 
• Option Data: In v2 Option Data is based on parent product data and can be applied either individually or using the option set. In v3, price and weight can be directly assigned to variant options without rules; there are also modifier options that allow for several display formats.
• SKU Management: In v2, SKUs can be added manually or automatically generated using the Auto-SKU Generator. In v3, SKUs are automatically generated when creating variant options. 
• Bulk Product Updates: BigCommerce v2’s Bulk Edit feature allows certain product details to be edited in bulk. A CSV import can be used to create or apply products, options, option sets, or rules. In v3, the Bulk Edit feature remains, and products, variant options, and rules can be applied via CVS import, but to make individual modifier options, shared variant options, or shared modifier options, you’ll need to use the Catalog API.

These are some of the main differences between the BigCommerce v2 and v3 experience. Some other noteworthy differences include: 

• Navigation: In BigCommerce v2, navigation functionality is placed at the top of the screen. In v3, however, navigation runs through a sidebar at the left of the screen. 
• Creating new categories is a little easier: One good feature about the v3 experience is that if you start creating products and forgot to create a separate category for them, you can go back and make one without leaving the product edit section of the backend.
• V3 requires you to assign SKUs to each variant: BigCommerce v2 didn’t require the assignment of SKUs to each variant, but BigCommerce v3 does. 

Who Should Migrate to BigCommerce v3?

Given the updates relevant to the BigCommerce v3 experience, there are some indicators that a move will be in your favor. 

You should consider migrating from BigCommerce v2 to v3 if you want to be able to view and edit all product details on a single page, instead of through multiple different tabs. 

For international sellers, adding customs information in v3 is easier and does not require you to use the platform API.

You should move to v3 if you want to be able to auto-generate SKUs for each variant instead of having to do it manually. 

You should also consider moving to BigCommerce v3 if the parent-data-import function associated with product data values is more of a headache than a time saver. 

You should also move to v3 if you want to be able to manually adjust or enter MSRP or sale prices for each product variant. 

What About Staying on BigCommerce v2?

For some merchants, it makes the most sense to stick with the BigCommerce v2 experience. 

You should stay on v2 if you already have a fully-built catalog of products and variants and you don’t wish to make any changes to it. 

If importing and exporting product option sets via CSV works for you, you should also stay on v2. 

If you prefer to add images via the control panel’s “Image Manager,” then staying on v2 is probably a good choice for you as well. 

If you’re big on selectively creating variants for products, you should stay on v2, as well as if you prefer to manage the catalog through the API.

One more thing: if you manage the fields used in automatic SKU generation through the Auto-SKU Generator, you should stay on v2. 

If you’re not entirely sure, you can test out the features and functionality of the v3 experience by creating a trial store beforehand. 

Requirements for Upgrading to BigCommerce v3

There are main three requirements your store will have to satisfy before upgrading to BigCommerce v3.

To do so, your store: 

• Must not have option sets associated with products or options present on products.
• Cannot have “Configurable Fields” enabled.
• Cannot have Google Shopping fields enabled on any products or categories. 

If your store meets all of these requirements, you will see an “Opt-In” banner for v3 whenever you add or edit a product. 

BigCommerce Development and Website Support Services 

Not sure whether or not you want to upgrade yet to BigCommerce v3? Our BigCommerce developers can help. We are BigCommerce Elite Certified, have an excellent relationship with BigCommerce, and have ten years of experience working with and customizing the platform.

If you have questions about the benefits of the new v3 experience or would like help planning for the upgrade, contact our BigCommerce developers at 888-982-8269.