Migration

Run controlled, restartable migration batches.

Idle

Run configuration

Migration profile

Content

Records per batch Batches per run

WordPress user ID (optional: import only this registered customer's profile and orders)

User-specific runs support Customers and Orders only and do not advance the regular migration cursor. A customer must have at least one WooCommerce order.

Force Password Reset for Imported Customers

Applies only when WBCM creates a new BigCommerce customer. Existing matched customers keep their login settings.

Reconcile customer tax exemptions with WooCommerce and TBE

Checks each imported customer's WooCommerce verification and, when a TBE ID exists, the TBE Customer V3 schema. Requires TBE settings in the profile. Customers missing Woo tax fields in the Woo API require the bundled WordPress tax reader and application password.

Import WooCommerce shipment tracking

Requires WooCommerce Shipment Tracking. BigCommerce may send shipment confirmation emails when shipments are created. Test with a sandbox first.

When Woo has multiple tracking numbers, WBCM creates or matches one BigCommerce shipment using the first tracking entry and records the remaining numbers and shipping providers in order staff notes. Review those extra packages after import; Woo does not identify which order lines belong to each tracking number.

Create hidden products for missing order SKUs

If an order SKU has no exact BigCommerce match, create a hidden, unavailable product with that SKU and the order line price. For a blank Woo SKU, first check its Woo product or variation; if none has a SKU, generate a stable placeholder SKU. Requires Products modify API permission. Review the created products before making them visible. Dry runs only report what would be created.

Continue from saved migration cursor Dry run — read and validate without writing Run continuously, one batch at a time

For an unattended order migration, Batches per run is the maximum number of pages. The cursor is saved after each completed page. Skipped records are logged in History and the run continues; failed records stop the run for review. Requires Write mode and Continue from saved migration cursor.

Run controls

Pause and Abort take effect safely between records. Abort does not remove records already migrated.

StatusIdle

Run ID—

Current module—

Started—

Modules completed0

Customers0

Guest customers created0

Guest customers planned (dry run)0

Orders0

Products0

Customers skipped0

Orders skipped0

Module progress

No active run.

Recent events

No events yet.

Connections

Store encrypted source and destination API profiles.

Saved profiles

No profiles configured.

Profile

Profile name

WooCommerce

Site URL Consumer key Consumer secret

BigCommerce

Store hash Access token Channel ID (optional) TBE customer field name

TBE tax lookup

TBE API URL

Authentication Customer V3 schema ID

Entity TBE username TBE password TBE token (only if applicable)

Optional WordPress content credentials

WordPress URL Username Application password

Run history

Persisted migration runs and outcomes.

Started	Status	Mode	Modules	Run ID	Error	Results

Full run results

Module Action Download all results (CSV)

Time	Source ID	BigCommerce ID	Action	Result	Message / warnings

Administrators

Individual dashboard accounts.

Existing admins

Add administrator

Migration setup guide

Configure least-privilege API access before a production migration.

WooCommerce / WordPress

In WordPress, open WooCommerce → Settings → Advanced → REST API.
Create a dedicated migration key for an administrative service account.
Use Read access for dry runs and validation. A normal Woo→BigCommerce migration only reads WooCommerce.
For tracking import, confirm the key can read /wp-json/wc-shipment-tracking/v3/orders/{id}/shipment-trackings.
Copy the Consumer Key and Consumer Secret into a migration profile.
If migrating WordPress pages/posts, create a WordPress Application Password with read access and add it under the optional WordPress credentials.

Customer rule: WBCM validates that every migrated WooCommerce customer has at least one actual WooCommerce order.

BigCommerce

Create a dedicated API account in the BigCommerce control panel.
Grant the scopes required for the content you plan to migrate: Customers, Orders, Products, and Store Content as applicable.
Enter the Store Hash and Access Token in the migration profile.
Confirm the customer form field named TBE ID exists, or change the field name in the profile to match your store.
Use Test connection before any run.
For shipment tracking import, grant Orders: Modify and review shipment confirmation email settings before a historical import.

Order safety: product and variant association is resolved by exact SKU. When hidden product creation is enabled, blank Woo SKUs are recovered or assigned a stable placeholder; otherwise they skip the order and count as intentional omissions so the next batch can continue. Ambiguous BigCommerce SKU matches and failed orders still hold the cursor for retry.

Recommended migration sequence

Create and test a migration profile.
Run a dry run with 5–10 orders. WBCM scopes the customer dependency only to customers needed by those orders.
Review module errors for missing SKUs, duplicate SKUs, customer email issues, and BigCommerce validation failures.
Run the same small batch with Dry Run disabled.
Verify representative customers, TBE IDs, order staff notes, product/variant links, totals, addresses, and order status in BigCommerce.
Increase batch size gradually. Keep Continue from saved migration cursor enabled.

Migration Console

Migration

Run configuration

Run controls

Module progress

Recent events

Connections

Saved profiles

Profile

WooCommerce

BigCommerce

TBE tax lookup

Run history

Full run results

Administrators

Existing admins

Add administrator

Migration setup guide

WooCommerce / WordPress

BigCommerce

Recommended migration sequence