Skip to main content
Using Selective Migration, you can migrate a single product or a few products to the destination environment (store or storefront).

​
What gets migrated, top level

When you migrate a product, the Selective Product migration options popup decides which sub-components ride along. Everything is ticked by default; untick what you don’t want:
  • Images
  • Videos
  • Variants
  • Variant Metafields (needs Variants)
  • Custom Fields
  • Bulk Pricing Rules
  • Metafields
  • Reviews
  • Related Products (link-only: related products already on the destination are connected by SKU; missing ones are never imported, the link is skipped with a reason)
  • Channel Assignments (storefront placements mirrored from the source on mapped storefronts)
  • Modifiers
  • Complex Rules (needs Modifiers)
  • Brand — always included (product-to-brand links need it; only referenced brands migrate)
  • Categories — always included (only referenced categories and their parents migrate)
  • Product Locale (multi-storefront destinations only)
  • Custom Template Associations
Product price is part of the product record and always travels with it. Existing destination stock is never overwritten; newly created products carry the source’s stock level, and per-location stock is replicated only when the Locations store setting is explicitly selected on a bulk run. Option display styles (swatch/dropdown/radio, swatch colours, display order) migrate too; image-based option swatches cannot (BigCommerce has no API for them) and are flagged for a manual re-pick. System-generated fields (Product ID, Date Created, Date Modified, Calculated Price, Variant ID, Image IDs, Metafield IDs) are not migrated, BigCommerce assigns new ones in the destination.
Note: Products are matched by SKU first, then product name. If either matches an existing destination product, that product is updated in place — matched variants and other children are reconciled to the source rather than deleted and recreated, so variant SKUs and existing references are preserved. If neither matches, a new product is created. The one un-linkable case: a product whose name and SKU were both changed on the source since the last run arrives as a new product.
A variant whose SKU clashes with a different destination product no longer blocks the product: the product migrates without that variant, and the skipped variant is reported by SKU with the owning destination product named and the fix.

​
Locale data

For multi-language stores, StagingPro migrates locale-specific data:
  1. Basic Information, translated name and description.
  2. SEO, locale-specific page title and meta description.
  3. URL, custom URL path per locale.
  4. Options, translated option names and value labels.
  5. Modifiers, translated modifier names and value labels.
  6. Custom Fields, translated field names and values.
  7. Images, locale-specific alt text, sort order, and thumbnail flag.
  8. Pre-Order, translated pre-order messages.
  9. Storefront Details, warranty, availability description, search keywords per locale.
  10. Channel Overrides, featured status per channel.
The destination store must already be configured with the relevant locales. StagingPro migrates the locale-specific content but does not provision locales themselves.

​
Multi-storefront migration

Migrations run between two different stores — a store can never migrate onto itself. For multi-storefront stores, pick the source storefront and destination storefront on the migration screen: the storefront (channel) mapping determines where channel-scoped data (category trees, channel assignments, locale overrides, widget templates) lands on the destination. Storefronts outside the mapping are never touched.

​
Brands and categories handling

Brands are matched by name (accent- and case-tolerant: a destination “Cafe” is adopted for a source “Café”, with a warning). If the brand exists, StagingPro uses the existing brand ID; otherwise it creates it. Categories are recreated with full hierarchy. For a source category path “Electronics > Audio > Headphones”, StagingPro checks the destination for each level, creating any that do not exist. The product is then assigned to every category it belongs to on the source, remapped to the destination ids. Category metafields are migrated when the destination category is created or matched.