Skip to content

Product Meta Migration

Product Meta Migration allows you to preserve custom product metadata when migrating from WooCommerce® to BigCommerce. This feature copies Advanced Custom Fields (ACF) values from your WooCommerce® products to matching BigCommerce-synced products using SKU as the matching key.

By default, Product Meta Migration copies Google Product Feed (GPF) fields from WooCommerce® to BigCommerce products:

  • GTIN (Global Trade Item Number)
  • Brand
  • MPN (Manufacturer Part Number)
  • Google Product Category
  • Product Type
  • Availability (In Stock, Backorder, Out of Stock)
  • Delivery Label
  • Custom Labels
  • Product Exclusions

Custom ACF fields attached to WooCommerce® products can also be migrated using developer hooks.

Use this feature if you:

  • Have WooCommerce® products with custom ACF fields
  • Use Google Shopping integration (WooCommerce® GPF plugin)
  • Added custom product metadata that needs to carry over to BigCommerce
  • Want to preserve product-specific settings during migration

Skip this feature if:

  • You don’t have custom ACF fields on WooCommerce® products
  • All your product data is already in BigCommerce
  • You’re setting up a fresh store without WooCommerce®

Before running meta migration, ensure you’ve synced products from BigCommerce:

  1. Go to Commerce Connect > Settings > Data
  2. Click Sync data to pull products from BigCommerce
  3. Wait for sync to complete (timestamp shows last successful sync)

Settings page showing Sync data button

  1. On the same Data tab, scroll to WooCommerce® Data section
  2. Under Migrate product meta data, click Migrate Product Meta Data

Migration button showing description text

  1. A progress spinner displays while migration runs (may take several minutes for large catalogs)

Migration in progress with spinner

When migration completes, results display showing:

Migration complete showing results

  • X product(s) migrated - Products successfully matched by SKU and updated
  • X skipped — duplicate SKU - Products with duplicate SKUs that need manual review
  • X not found in WooCommerce® - BigCommerce products with no matching WooCommerce® product
  1. Go to Products in WordPress® admin
  2. Edit a BigCommerce-synced product
  3. Scroll to Google Shopping & Product Data section
  4. Verify migrated field values appear correctly

Product editor showing migrated GTIN value

In this example, the GTIN (Feed Override) field shows 885634059880 — the value migrated from WooCommerce® GPF data.

Products are successfully migrated when:

  • WooCommerce® product and BigCommerce product share the same SKU
  • WooCommerce® product has ACF field values to copy
  • Migration writes values to matching ACF fields on BigCommerce product

Example: 5,311 products migrated successfully.

Products are skipped when:

  • Multiple WooCommerce® products share the same SKU
  • Migration cannot determine which WooCommerce® product to use as source

How to resolve:

  1. Review WooCommerce® products to identify duplicate SKUs
  2. Update SKUs to be unique
  3. Run migration again

Example: 4 skipped — duplicate SKU

BigCommerce products are marked “not found” when:

  • BigCommerce product has a SKU with no matching WooCommerce® product
  • BigCommerce product was created directly in BigCommerce
  • BigCommerce product SKU doesn’t match any WooCommerce® SKU

This is normal if:

  • You added new products directly in BigCommerce
  • You intentionally have BigCommerce-only products
  • SKUs differ between WooCommerce® and BigCommerce

Example: 45 not found in WooCommerce®

To run migration again after initial completion:

  1. Click Migrate again button (appears after first migration completes)
  2. Migration re-runs, processing all products again
  3. Existing migrated values are overwritten with current WooCommerce® values

When to re-run migration:

  • After updating WooCommerce® product metadata
  • After fixing duplicate SKU issues
  • After adding new custom fields to WooCommerce® products

Cause: Migration may have timed out or encountered an error.

Solution:

  1. Check for PHP errors in WordPress® debug log
  2. Verify WooCommerce® and BigCommerce products both exist
  3. Confirm products have matching SKUs
  4. Try again with a smaller product set (filter in BigCommerce)

Migrated Fields Don’t Appear in Product Editor

Section titled “Migrated Fields Don’t Appear in Product Editor”

Cause: ACF fields may not be registered or visible.

Solution:

  1. Verify ACF plugin is active
  2. Check that GPF field group is assigned to “Product” post type
  3. Re-save ACF field group to refresh field registration

All Products Show “Not Found in WooCommerce®”

Section titled “All Products Show “Not Found in WooCommerce®””

Cause: SKU mismatch between WooCommerce® and BigCommerce.

Solution:

  1. Verify WooCommerce® products have SKUs set
  2. Confirm BigCommerce products have matching SKUs
  3. Check for case sensitivity differences (SKUs are case-sensitive)
  4. Export SKUs from both systems and compare in spreadsheet

Cause: Multiple WooCommerce® products share the same SKU.

Solution:

  1. Go to Products in WordPress® admin
  2. Search for products by the duplicate SKU
  3. Update one or more products to use unique SKUs
  4. Run migration again

Product Meta Migration fires a hook after each successful product migration, allowing developers to migrate custom meta fields beyond the default GPF fields.

See Product Meta Migration Hooks for code examples and extensibility patterns.

Use this checklist to ensure successful product meta migration:

  • Sync products from BigCommerce (Settings > Data > Sync data)
  • Verify WooCommerce® products have SKUs set
  • Verify BigCommerce products have matching SKUs
  • Run Product Meta Migration (Settings > Data > Migrate Product Meta Data)
  • Review migration results (migrated/skipped/not found counts)
  • Resolve duplicate SKU errors if any
  • Verify migrated data in product editor
  • Re-run migration if needed (after fixing SKU issues)
  • DO NOT delete WooCommerce® products until migration is complete