...
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.
‘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.
‘Shared Modifier Options’ and ‘Shared Variant Options’ for Products
...
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.
Social Media Links
The BigCommerce API does not currently support the migration of Social Media links.
...
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.
...
Currently themes are applied to the default store. Manual selection is needed for association with a different storefront.
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.
...
To view our onboarding steps, please access the following article → StagingPro Onboarding