Skip to main content
Bulk Content Migration is the StagingPro screen you use when the destination environment is empty (or you intend to overwrite most of it) and you want to copy your full BigCommerce catalogue from one environment to another. It runs on a dedicated high-performance migration platform with parallel processing, checkpoint resumability, idempotent upserts, and automatic BigCommerce API rate-limit handling.

​
When to use Bulk Content Migration

The bulk migration options are as follows: The assumption underneath Bulk is “destination should look like source for the entities I selected”. If that is not your intent, switch to selective.

​
The interface

Bulk Migration 2 Pick the source environment (store and storefront), pick the destination environment (store and storefront), tick the entities you want to move, and click Start Migration. Once submitted, switch to the history and rollback tab to monitor progress.
Channel Mapping: You can map the source store channels with the destination store channels prior to the migration (when both the source and destination stores are multi-storefront enabled) so as to enable you to migrate the entities to corresponding destination channels/storefronts. To do this, click the source store’s channel drop down selector and select all storefronts option, map the channels and click Save mapping.
Channel Mapping
“Get Entity Counts” button → Optionally get entity counts to preview totals on the entities before you migrate.
Moreover, “Check Forecast & ETA” button gives you the calculated estimate time required to migrate the entities so that you can plan your migration accordingly.

​
Product Bulk Migration

Product bulk migration processes each product through multiple component steps:
  1. Base product creation (name, description, price, SKU)
  2. Options and Modifiers setup
  3. Variants generation
  4. Images and Videos upload
  5. Reviews, Custom Fields, and Bulk Pricing Rules
  6. Complex Rules and Related Products associations
  7. Channel Assignments and Metafields (product and variant level)
  8. Content (widgets and template associations)
  9. Locale (multi-language product data via GraphQL)
Products can be migrated in bulk (all products) or selective (specific product IDs) mode. A failure in any step is logged but does not block subsequent steps for the same product. Failed components show up in the migration error summary with categorised errors and a CSV download.

​
Category bulk migration

Category migration automatically includes parent categories, ensuring that the category hierarchy is preserved correctly. This helps eliminate the “parent category not found” errors that are commonly encountered with manual or custom-built BigCommerce category imports.

​
Order Data Migration

Under the Order Data Migration section, enable:
  • Anonymise Customer Data
This option scrambles customer data from the source environment before migrating it to the destination environment, ensuring data security for testing purposes. Click Start Migration to run with these semantics.
If you want a clean-slate destination instead, delete the destination catalogue first via the BigCommerce control panel, then run Bulk migration.

​
Entity Dependencies

  • Entities with the info-circle icon have dependencies.
    Example: Migrating Products also migrates Brands and Categories.
  • Entities without the icon have no dependencies and can be migrated independently.

​
Monitoring Migration Progress

During bulk migration, you can monitor progress through:
  • Monitoring Dashboard (Home tab) for overall migration status
  • History and Rollback tab for detailed migration metrics and health