> ## 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.
# StagingPro B2B Edition Support, Coupons, Promotions, and Data Dependencies
This page combines three closely-related migration topics: BigCommerce B2B Edition staging support, the rules around coupon and promotion migration, and the broader data dependency map you need to read before running any partial migration.
## B2B Edition support
B2B Edition (formerly Bundle B2B) adds a parallel data model on top of standard BigCommerce: companies, addresses, users, quotes, invoices, super admins, shopping lists. StagingPro can stage all of it, but the connection to B2B is separate from the standard StagingPro install because B2B credentials are stored independently.
### Prerequisite, B2B Edition activated by BigCommerce
Before connecting B2B, confirm the B2B Edition app is installed and activated on the store. Reach out to your BigCommerce account executive or support contact if the activation is not in place yet.
### Use a fresh email for the B2B connection
For a clean connection, use a fresh dedicated email that has never been used on the BigCommerce control panel. Example: `b2b@yourdomain.com`. This email becomes the B2B Edition admin user that StagingPro authenticates as.
### Step 1, create the B2B user manually
The connection only works with a manually created B2B user (not a SaaS-imported one):
1. In the B2B Edition control panel, go to **Settings, System users and roles**.
2. Open the **Users** tab.
3. Click **Add User**.
4. Available in both **All** and **Sales staff** sections.
When you add a user email, BigCommerce sends an automated email asking that user to set a password.
### Step 2, set the password
When the email arrives, set the password. The email plus password is what StagingPro will use to authenticate.
### Step 3, connect each environment in StagingPro
1. Open **Settings, B2B Edition** in StagingPro. The tab lists every linked environment.
2. For each environment, enter the B2B user email and password.
3. Click **Connect**.
The button changes to **Connected** in green when the link succeeds. You must see Connected on every environment you intend to migrate B2B data to or from, otherwise the B2B entities will not appear on the Bulk Content Migration tab.
### Troubleshooting B2B connections
If Connect fails:
* Confirm the B2B Edition app is activated by BigCommerce on that environment.
* Confirm the B2B user was created via the manual flow above (not bulk-imported).
* Confirm the password was set via the automated email (not via API).
* Optionally also create the same email as a BigCommerce control panel user using the same email; it can help with diagnostics although it is not required.
* If the connection still fails, delete the B2B user, recreate, reset the password, and try again.
### B2B entity dependencies
When you migrate a B2B entity, StagingPro pulls these dependent entities along automatically:
| B2B migrating entity | Dependent entities migrated automatically |
| -------------------- | ----------------------------------------- |
| Companies | Customer Groups, Price Lists |
| Addresses | B2B Companies |
| Users | Customers, B2B Companies |
| Orders | Orders, B2B Companies |
| SuperAdmins | B2B Companies |
| Quotes | Products, Orders, B2B Orders |
| ShoppingLists | B2B Companies, B2B Users |
| Invoices | Products, Orders, B2B Companies |
This is why connecting B2B credentials per environment matters: missing connections mean missing dependencies.
## Coupons and promotions
Coupon codes in BigCommerce are part of the Promotions system. When you migrate a Promotion via StagingPro:
* StagingPro locates the SKUs and category names referenced by the promotion on the source store.
* It creates the matching products and categories on the destination if they do not already exist.
* Once those exist, the promotion itself is created on the destination and attached to the same SKU and category references.
Two important details:
1. **Coupon code associations are by SKU, not by Product ID.** Product IDs differ between BigCommerce instances, so SKU is the only stable identifier. Make sure your source and destination use the same SKUs.
2. **Category associations are by exact Name plus hierarchy, not by Category ID.** Same reason: IDs are not stable across stores. Naming consistency matters.
### Promotions migrate in their entirety
There is no partial migration of an individual promotion's rules. Each promotion moves as a complete unit including all conditions, actions, schedule, and notifications.
### Promotions created via API cannot be edited after creation
This is a BigCommerce constraint. If a promotion was originally created via the API and you discover the rules need adjusting on the destination, the workaround is to delete the promotion in the source, recreate it correctly, and re-migrate. We will surface manual editing once BigCommerce supports it natively.
## Data dependencies, the full map
When you run a partial migration, some entities are incomplete unless their dependencies have already been migrated (or are being migrated together). The dependency map:
| Migrating entity | Dependencies migrated automatically |
| ----------------------------- | ------------------------------------------------------------- |
| Products | Brands, Categories |
| Product Reviews | Brands, Categories, Products |
| Bulk Pricing Rules | Products (with their Brand and Category dependencies) |
| Channel Assignments | Products and configured destination channels |
| Product Locale / Localisation | Products and configured destination channel |
| Category Metafields | Categories |
| Price List Records | Brands, Categories, Products, Price Lists |
| Price List Assignments | Price Lists, Customer Groups |
| Customers | Customer Groups |
| Shipping Methods | Shipping Zones |
| Promotions | Brands, Categories, Products, Customer Groups, Shipping Zones |
Items with a black info-circle icon on the migration screen carry dependencies. Items without the icon are independent of others.
### Why this matters
If you tick **Promotions** alone on the Bulk Content Migration tab, StagingPro will also migrate Brands, Categories, Products, Customer Groups, and Shipping Zones, because those are dependencies. This is intentional and correct, but it means the migration will take longer and touch more of the destination than you might naively expect.
If you only want to move the promotion configuration without touching the catalogue, the products and categories must already exist on the destination with matching SKUs and category names.
## Data type reference, what gets migrated per entity
A condensed reference of what each major entity type covers in StagingPro.
| Entity | What is included |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Products** | Base data, options, variants, modifiers, images, videos, reviews, custom fields, bulk pricing, complex rules, related products, channel assignments, metafields (product and variant), content, locale |
| **Categories** | Name, description, hierarchy, sort order, visibility, image, metafields, custom template associations, page widgets |
| **Brands** | Name, page title, meta keywords, meta description, image URL, search keywords, custom URL |
| **Customers** | Account profile, contact, addresses, customer group, form fields, store credit, channel associations |
| **Orders** | Order records and history, line items, shipping, billing (Pending status on destination by default) |
| **Promotions** | Discount rules, coupon codes, conditions, restrictions, dates, customer eligibility |
| **Themes** | Design templates, layouts, styling, custom code modifications, theme configuration |
| **Pages** | Custom page content, title, URL, visibility, channel assignments |
| **Page Templates** | Layout structure for homepage, account pages, checkout, product listing, search |
For the field-by-field migration mechanics on Products, see [selective product migration](/vortex-apps/staging-pro/selective-product-migration). For everything else, the migration moves the canonical fields BigCommerce exposes via its public APIs.