For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dev Portal
DocsAPI ReferenceLearnCommunityChangelog
DocsAPI ReferenceLearnCommunityChangelog
  • Overview
    • Quick Start
    • Sandboxes
    • Tools & SDKs
    • Support
  • Docs
      • Getting Started
        • Products overview
        • Contextual filters
            • Overview
            • Prepare Data
            • Test Data
            • Error Handling
            • Complete Migration
            • Delta Migration
    • Archive
    • Closed Beta Programs
Dev Portal
LogoLogo
On this page
  • Product data migration: Best practices and process overview
  • Why focus on data migration?
  • Migration workflow pages
  • Getting started
  • Recommended preparatory tasks
  • Additional resources
DocsAdminCatalog and InventoryMigrationCatalog & Data Migration Guide

Product data migration overview

Was this page helpful?
Previous

V2 to V3 Catalog Operations Comparison

Next

Prepare Your Migration Data

Built with

Product data migration: Best practices and process overview

Migrating product data is a foundational part of launching or replatforming an ecommerce store. This section provides practical guidance and best practices for migrating your product catalog into BigCommerce, focusing on accuracy, efficiency, and minimizing common migration errors.

Why focus on data migration?

Product data migration affects core areas of your storefront, including product listings, search, inventory, pricing, and overall customer experience. Early planning and process validation help reduce the risk of errors and delays during launch. The following pages walk through the technical and operational steps of migration to support a smooth transition.

Migration workflow pages

  • Prepare Your Migration Data
  • Test a Limited Dataset
  • Error Handling
  • Load Complete Data
  • Go Live and Delta Migration

Getting started

Data migration is complex and impacts your entire store setup. You should plan for it early in your project timeline to prevent setbacks.

Recommended preparatory tasks

  • Test your migration workflow early
    Once you have defined your migration plan and scope, test your migration process in a non-production environment. Address any issues found during testing before moving to a full migration.

  • Align store settings and source data
    Before importing product data, configure your store’s store settings including product weight units, dimensions, currency, and timezone. Check that your source data matches these settings to avoid inconsistencies.

  • Configure categories and brands in advance
    Categories and brands must be created in BigCommerce before importing products. Category and brand assignments are done by numeric ID, not by name. Prepare a mapping between your source data and BigCommerce IDs to ensure products are assigned correctly. See the Catalog API Reference for details.

Category and brand IDs are not accessible by name, so create and cache a mapping schema to guarantee your catalog is properly configured.

Additional resources

For more technical details and API documentation, see:

  • Catalog API Reference
  • API best practices
  • API rate limits
  • WebDAV file access
  • Data migration services

By following these recommendations and the linked migration workflow pages, you can manage your BigCommerce product migration with greater confidence and fewer disruptions.