...
The ability to store the original order number in the order notes field is on the roadmap for a future release.
All orders which are now migrated have their status changed to “Pending” as keeping the original status may trigger emails to be sent out to clientswith 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
For bulk migration, StagingPro migrates Page widgets but cannot determine their location/position on the page. As per current BigCommerce implementation, widgets created in Page Builder will continue to have an empty region as they are wrapped in a Layout. To allow for ‘store-to-store’ widget transfers, BigCommerce engineers are working on changes, possibly the Layouts API. Use Selective Content migration as the alternative.
...
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
While Products are successfully migrated, links to similar or related products cannot be migrated. This will require multiple API calls and may have an impact on the Production site hence has been de-prioritised at the moment.
Migrating Custom Fields for Products
This is a planned roadmap release item.Related Products migration is implemented in Staging Pro.
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 implemented in StagingPro. Please be clear that Please note the custom fields should also be present in the destination store (not just in the source store alone) for this migration to work. There is no BigCommerce API available to create the customer custom fields, it only provides the API to migrate the 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.
...
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.
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 below.
...
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 136 more than 600 variants), BigCommerce returns an Internal Server 500 error. Reducing Adjusting the product variants to less than 30 variant count and listing it shows success. Another related error type is with product URL's redirecting to 404 Webpage not found.
...