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. Go to top 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. Go to top Widgets Widget migration is supported for BigCommerce stores whitelisted to use the new Page Widgets API through Selective Migration (Custom Pages and Page Templates). If needed, please raise a Helpdesk portal request, to ensure your stores are properly whitelisted for use with Selective Page Migrations. If you are migrating widgets, also please select pages, widget templates and theme (if the theme hasn’t been migrated already) Multi-column layout widget migration is currently not supported through the BigCommerce API. Although BigCommerce don’t have a specific ETA, we are actively working with BigCommerce on a solution for this for a release at a later date. Go to top Blog-type pages A page that contains blog posts cannot be migrated as BigCommerce API’s currently does not support any ‘Page Type’ with the attribute value_ ‘blog’_. At present, blog-type pages can only be created in the Store Control Panel. This holds true, even with the new Page Widgets API Please refer to the following url → 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 it via API. Go to top ‘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. Go to top Multi-Shipment Orders Even though permitted through the UI, the BigCommerce API does not allow an order to contain more than one shipment, thus causing some missing shipment information. The payment type on the source reflects an unknown payment method. There is currently no mechanism to move the payment type on orders. BigCommerce automatically inserts a “Manual” payment method when creating the order in the new store. 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. Complex Rules Migration of complex rules (product rules attached to multiple SKUs allowing merchants to set up conditions & actions based on shopper option selections on the storefront) is currently not supported in StagingPro and will be considered as roadmap item for future release. Go to top 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 Currently, StagingPro does not migrate custom scripts that are in Script Manager. 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. Go to top Migrating Custom Fields Generally speaking, BigCommerce stores have custom fields only for Products and is implemented in StagingPro. To clarify, Custom Fields don’t exist for Customers or Customer Groups. For Companies, (only in relation to B2B) and the attribute name is ‘Extra Fields’. Migrating ‘Custom Form’ Fields for Customers This option is also available in StagingPro. Please note that the custom 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** _custom form** field values_. Payment Methods The payment methods in a store are not publicly available and, therefore cannot be migrated at this time. Go to top Gift Certificates Gift certificates can be migrated but only if the “Enable Gift Certificate” option is enabled within BigCommerce. For instructions on how to use the content migration settings to migrate gift certificates, please go Moving Gift Certificateshere. Images There is currently no BigCommerce API to move banners and home page carousel images. We are looking at alternative migration methods and hope to have a solution shortly. It is worth noting that images outside of the THEME/ Template folder cannot be migrated as of now. BigCommerce has no API to move images from WEBDAV and Image Manager. Any images such as Carousel images used in the Cornerstone theme, will not automatically move using StagingPro. Those images can be moved manually from your side. There is currently no BigCommerce API available for moving category image URLs. Once such an API becomes available, it will be considered for inclusion in our implementation roadmap. notee8907ff9-8f07-4c31-9692-101214d85c61 Note: For product images to get migrated successfully, the image should not have any ‘spaces’ or ’&’ character in the name of the image file.
Social Media Links The BigCommerce API does not currently support the migration of Social Media links. Go to top 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. Go to top 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 here - Data DependenciesData Dependencies Tax Classes Please note that tax classes are not yet available. We will endeavour to add this as soon as APIs are available. Go to top Page Redirects 301 url redirects are currently not migrated but will be considered for a future release. If you need 301 redirect values to be migrated, please log a ticket with the Helpdesk portal Themes Currently themes are applied to the default store. BigCommerce Product API issues when recreating products with high variant count In some instances when recreating products with high variant count (e.g. a product with more than 600 variants), 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. Go to top 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.
Go to top
Customer Segmentation
Customer segmentation for targeted promotions is a planned roadmap release item.
Coupon Codes
When performing a Bulk Migration of Coupon Codes, also select Categories if there is 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.