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

ScenarioUse Bulk Content Migration
New sandbox provisioned, need a copy of Production catalogueYes
Refreshing a stale Staging environment with current Production dataYes
Standing up a fresh UAT for a major releaseYes
Moving one or two products between environmentsNo, use selective content migration
Trying to merge changes without overwritingNo, use selective migration
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 content migration screen Pick the source environment (store and storefront), pick the destination environment (store and storefront), tick the entities you want to move, and click Start the Migration. Once submitted, switch to the history and rollback tab to monitor progress.

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. !!! Recommended: Always tick Anonymise Customer Data when migrating to a Staging or UAT environment. Skip it only when migrating between two Production-equivalent environments where the data security boundary is the same.

Product migration popup, Add or Update mode

When you tick Products on a Bulk migration, a popup appears asking how to handle existing destination data: Product migration popup, add or update mode The default behaviour, Add/Update Products Data:
  • Does not delete any existing products, brands, or categories at the destination.
  • Adds missing products from the source.
  • Ignores items that already exist with matching SKU and Name.
Click Continue 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

!!! note
  • Entities with the black 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:
  • History and Rollback tab for overall migration status
  • Monitoring Dashboard for detailed migration metrics and health

Scale plan features

  • Schedule Migration, schedule the bulk job for an off-peak window.
  • B2B Migration, include B2B Edition entities (companies, addresses, users, quotes, invoices).

To view our Onboarding steps, please access the following article → StagingPro Onboarding