Products
Products without a channel assignment Products with no storefront assignment migrate normally: an All-Storefronts run includes them, and they arrive unassigned on the destination, mirroring the source. The Selective screen’s Advanced Filters include a “Not on any storefront” finder to locate them. (The old limitation where unassigned products were excluded from migration no longer applies.) Shared Modifier Options and Shared Variant Options StagingPro does not currently support migration of Shared Modifier Options or Shared Variant Options. As a result, the destination store’s Control Panel (under Products → Product Options) will display empty datasets under the Shared Options and Shared Modifiers tabs because these option types are not migrated. However, regular modifier options and regular variant options for products are supported and will migrate successfully under the current implementation. BigCommerce’s engineering team is reportedly working on providing an API to support Shared Options migration, but no confirmed ETA is available yet. Customs Information is not included in the standard Product API of BigCommerce, hence, they do not get migrated.Orders
Order IDs in BigCommerce are incremental, so StagingPro cannot keep the original order number. It will still migrate the order, but it will have a different order number. Because of this incremental behaviour, records in the destination store cannot be deleted, thus having the effect of the destination store continually growing with each migration that occurs. It is therefore recommended not to migrate orders unless it is necessary. The ability to store the original order number in the order notes field is on the roadmap for a future release. All orders are now migrated with their order statuses ‘as-is’. When migrating orders and customers to a destination store, BigCommerce recommend in general, you can disable the notifications directly in Marketing -> Transaction Emails. If you disable the emails there, the default notifications will not be sent to customers.Widgets
If you are migrating widgets, ensure to have WebDAV enabled on both the stores. Also select Page Builder Widgets and Widget Images before starting the migration.Blog-type pages
Blog posts migrate in StagingPro V2 (theBlog posts option), including blog-post redirects, and the store’s built-in Blog page is handled.
What remains a BigCommerce API constraint: a new page with page type ‘blog’ cannot be created via the API — so a custom blog-index page that does not already exist on the destination must be created in the Store Control Panel. Please refer to → https://developer.bigcommerce.com/docs/rest-content/pages Additional note (Feb-2025): BigCommerce recently made a change so that a web page with the type of “blog index page” cannot be changed to a different web page type. This operation was not supported in the BigCommerce Control Panel and consequently, is now also prevented via API.
‘The url is duplicate’ API notification (Pages, Categories and Products)
**For Pages and Categories: ** If you see this API error when migrating Pages, then it is likely because you have Category urls at the destination store with the same url value. And vice versa, check if when migrating Categories, if there are conflicting Page urls on the destination store. As long as you ensure there is no url conflict between Category and Page urls by using unique url values, the migration will work without issue. **For Products: ** If you see this API error when migrating Products and if you dont see any Product with matching url value in the destination store, then BigCommerce support may need to run an orphan url cleanup tool, removing any unseen/remnant url links from your store data tables, to fix this issue. After the cleanup tool is used by BigCommerce support, the migration will work without any conflict on retry, after clearing the remnant url links.Multi-Shipment Orders
Shipment records (tracking numbers, shipped-item breakdowns) are not migrated for any order, single- or multi-shipment. Shipping addresses — including multiple destinations — and their shipping method do migrate. The source order’s payment-method label is copied to the destination. If BigCommerce rejects it, the field is dropped on retry and the order lands without one. Live payment gateways and transactions are never migrated.Incorrect Order Count
On rare occasions, selected orders are not able to be created. We are working with BigCommerce in the hope of finding a solution soon.Migrating Apps Channel data is migrated successfully between stores only if the information is stored within BigCommerce however, the apps or extensions to which this data belongs do not get migrated. Any data stored within an installed app itself can also not be migrated.
Migrating Custom Scripts Script Manager scripts do migrate in StagingPro V2 (the
Scripts option) — with one BigCommerce API constraint: only API-created scripts are visible to the API. Scripts installed by third-party apps, or created directly in the control panel, cannot be read and must be reinstalled or recreated on the destination.
Migrating Meta fields
This feature request is implemented. Customers can now choose Metafields at the Brand, Category and Product levels and migrate the same to the destination environment.Related Products
Related Products migration is implemented in Staging Pro.Migrating Custom Fields
Product custom fields migrate with their products, identified by name and value — so duplicate-name fields (for example two “Material” rows) are preserved without loss. For customers, distinguish two things: Customer Attributes (Customers → Attributes) are migrated — StagingPro creates the attribute definitions and their per-customer values via the API. Customer form-field values also migrate, but their definitions cannot be created via the BigCommerce API, so the same form fields must already exist on the destination (see the next section). For Companies (only in relation to B2B), the attribute name is ‘Extra Fields’.Migrating ‘Custom Form’ Fields for Customers
This option is also available in StagingPro. Please note that the custom form fields must exist in the destination store as well, not just in the source store, for the migration to work.BigCommerce does not provide an API to create customer custom fields; it only supports migrating customer’s custom form field values.
Payment Methods
The payment methods in a store are not publicly available and, therefore cannot be migrated at this time.Gift Certificates
Gift certificates can be migrated but only if the “Enable Gift Certificate” option is enabled within BigCommerce on the destination store (for its currency). Remaining balances are carried over; fully-redeemed certificates (zero balance) are deliberately skipped.Social Media Links
The BigCommerce API does not currently support the migration of Social Media links.Category Landing Pages & Brand Landing Pages
The BigCommerce API does not currently support the migration of Category Landing pages and Brand Landing pages. The workaround is to perform a Bulk Content Migration of Categories, Brands, Widgets, Widget Templates and Pages.Category Template Layout File selection that is present in Product Categories
Layout_file, which is a visible attribute on Product Categories (e.g. category.html) is picked up from the Theme file, specifically Template>Pages>Custom folder. Example setting is as follows: “layout_file”: “category.html” When performing a Category migration, the layout_file value is migrated to the destination store. You need to ensure the layout file is present on the destination store which can done by i) migrating the active theme and ii) followed by Selective Migration of Categories.Data Dependencies
There are many cases where data migration may cause a conflict unless related data is migrated simultaneously. An example of this is the relationship between a product and its variations or a product and its categories. A summary list of dependencies can be found on B2B, coupons, and data dependencies.Tax Classes
When Tax settings is selected, StagingPro creates missing tax classes on the destination via the v3 tax-classes API. That endpoint is not available on all BigCommerce plans (it returns 404 on standard-plan stores) — in that case classes are matched by name, so make sure identically-named tax classes exist on the destination for rates and products to attach correctly. Tax settings, tax zones, and tax rates migrate.Page Redirects
301 URL redirects migrate in StagingPro V2 (the301 redirects option). Redirects that point at a product, category, brand, or page are re-pointed at the matching destination item (product by SKU, brand/category by name, page by URL) — migrate those entities in the same run, or run redirects afterwards against an already-populated destination. A redirect whose target can’t be found is skipped with a reason (“obsolete redirect” vs “migrate the target first”), and blog-post redirects are supported.
Themes
Themes activate per storefront: the targeted storefront switches automatically and is verified by reading back which theme is live, and other storefronts are restored to their original themes. Every migration uploads a new theme copy — StagingPro never deletes or overwrites a destination theme, so superseded copies remain as a rollback path (BigCommerce caps a store at ~20 themes; clean up manually under Storefront → My Themes). A manual one-time apply step (Storefront → My Themes) is only needed when a safety rule refused an unsafe switch — the run detail names it.BigCommerce Product API issues when recreating products with high variant count
In some instances when recreating products with very high variant counts, BigCommerce returns an Internal Server 500 error. Adjusting the product variant count and listing it shows success. Another related error type is with product URL’s redirecting to 404 Webpage not found. In such cases a ticket needs to be raised with the BigCommerce developer team for further investigation.API Rate limits by plan type
BigCommerce aims to provide outstanding platform reliability by implementing safeguards in the form of rate limits for our REST APIs. Apps using OAuth are rate-limited based on a quota that’s refreshed every 30 seconds. The maximum quota varies by store plan and requested resources.
For more information, please refer to the BigCommerce’s article.
Customer Segmentation
Customer segments migrate in StagingPro V2 (theCustomer segments option), and promotions that target segments keep working.
Coupon Codes
Coupon codes attached to a promotion travel with the promotion (they are not duplicated as legacy coupons). When performing a Bulk Migration of legacy Coupon Codes, also select Categories if there is a category dependency.Promotions
Marketing > Promotions (automatic promotions and coupon promotions) can be migrated using StagingPro. Please remember, these are different from Marketing > Coupon codes.IMPORTANT: Be advised that Promotions (created using the API / using legacy editor) cannot be edited in the destination. Workaround is to delete the promotion in the source, recreate it correctly in source i.e., using standard editor and then migrate so it transfers across correctly. Once BigCommerce allows for such Promotions to be edited manually, we will be able to provide the functionality.