> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Selective Product Migration in StagingPro for BigCommerce, Field Mapping and Update Mode

Using **Selective Migration**, you can migrate a single Product or few products to the destination environment (store or storefront).

## What gets migrated, top level

When you migrate a product, following option are also migrated depending upon your selections:

* Images
* Variants
* Options
* Modifiers
* Complex Rules
* Custom Fields
* Bulk Pricing Rules
* Reviews
* Metafields
* Videos
* Channel Assignments
* Locale
* Brand
* Categories
* Related Products (select either product entities or product relationships)
  * Product Entities (In addition to the selected products, any products listed as related products will also be imported.)
  * Product Relationships (Related products will not be imported. Relationships will be created only if a matching SKU exists in the destination. If no match is found, the relationship is skipped.)
* Migrate Inventory Level
* Migrate Price
* Assign All Products to Destination Channel

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.

> **<kbd>Note:</kbd>** Products are migrated by matching either the **product name** or the **SKU**. If either value matches an existing product in the destination store, the existing product is updated. If neither the product name nor the SKU matches, a new product is created in the destination store.

***

## 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 and visibility.
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.

## Same-store channel migration (multi-storefront)

When source and destination stores are the same but the channels differ (source channel ID not equal to destination channel ID), StagingPro automatically uses a simplified workflow because the product already exists in the store. Only channel-specific content moves:

| Migrated                                          | Not migrated                              |
| ------------------------------------------------- | ----------------------------------------- |
| Categories assigned to destination channel's tree | Product base data (already exists)        |
| Channel assignment (makes product visible)        | Options and variants (store-level)        |
| Widget templates                                  | Modifiers and complex rules (store-level) |
| Custom template associations                      | Images and videos (store-level)           |
| Locale data for the destination channel           | Custom fields, bulk pricing, reviews      |

This mode is significantly faster than full migration because no components are recreated and only selective data items are migrated.

## Brands and categories handling

**Brands** are matched by name. If "AudioTech" exists in the destination, StagingPro uses the existing brand ID. Otherwise, it creates a new brand with the same name.

**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 the leaf category. Category metafields are migrated when the destination category is created or matched.