bigcommerce · chris-nowicki · Sep 22, 2025 · Sep 23, 2025 · Sep 23, 2025 · Sep 23, 2025
diff --git a/docs/start/migration/4_errors.md → docs/start/migration/error-handling.md b/docs/start/migration/4_errors.md → docs/start/migration/error-handling.md
diff --git a/docs/start/migration/overview.mdx b/docs/start/migration/overview.mdx
@@ -1,52 +1,58 @@
 ---
-title: Product data migration overview
+title: Transferring Your Catalog to BigCommerce
 ---
 
-# Product data migration: Best practices and process overview
+# Catalog 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.
+Migrating catalog data is a foundational part of launching or replatforming an ecommerce store. This section provides practical guidance and best practices for migrating your catalog into BigCommerce, focusing on accuracy, efficiency, and minimizing common migration errors.
+
+There are several methods to migrating your catalog data into BigCommerce. These sections focus on using our APIs. For other methods like CSV import,
+Data Migration Apps, and Managed Transfer Services, please refer to our knowledge base article, [Transferring Your Catalog to BigCommerce](https://support.bigcommerce.com/s/article/Transferring-Your-Catalog-to-BigCommerce?language=en_US).
 
 ## 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.
+Catalog data migration affects products, categories, customers, orders, 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 using our APIs to support a smooth transition.
+
+## Migration order
 
-## Migration workflow pages
+We recommend migrating your data in the following order:
 
-- [Prepare Your Migration Data](/docs/start/migration/prepare-data)
-- [Test a Limited Dataset](/docs/start/migration/test-data)
-- [Error Handling](/docs/start/migration/error-handling)
-- [Load Complete Data](/docs/start/migration/complete-migration)
-- [Go Live and Delta Migration](/docs/start/migration/delta-migration)
+- Categories
+- Brands
+- Products
+- Customers
+- B2B Properties
+- Orders
 
 ## Getting started
 
-<Callout type="info">
-Data migration is complex and impacts your entire store setup. You should plan for it early in your project timeline to prevent setbacks.
+<Callout type='info'>
+	Data migration is complex and impacts your entire store setup. You should plan
+	for it early in your project timeline to prevent setbacks.
 </Callout>
 
 ### Recommended preparatory tasks
 
-- **Test your migration workflow early**  
+{/* TODO: List of 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](https://support.bigcommerce.com/s/article/Store-Settings) including product weight units, dimensions, currency, and timezone. Check that your source data matches these settings to avoid inconsistencies.
+- **Align store settings and source data**
+  Before importing product data, configure your store's [store settings](https://support.bigcommerce.com/s/article/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**  
+- **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](/docs/rest-catalog) for details.
 
-<Callout type="info">
-Category and brand IDs are not accessible by name, so create and cache a mapping schema to guarantee your catalog is properly configured.
-</Callout>
-
 ## Additional resources
 
 For more technical details and API documentation, see:
 
 - [Catalog API Reference](/docs/rest-catalog)
 - [API best practices](/docs/start/best-practices)
 - [API rate limits](/docs/start/best-practices/api-rate-limits)
-- [WebDAV file access](https://support.bigcommerce.com/s/article/File-Access-WebDAV)
 - [Data migration services](https://www.bigcommerce.com/services/launch/#data-migration-services)
+- [Transferring Your Catalog to BigCommerce KB article](https://support.bigcommerce.com/s/article/Transferring-Your-Catalog-to-BigCommerce?language=en_US)
 
-By following these recommendations and the linked migration workflow pages, you can manage your BigCommerce product migration with greater confidence and fewer disruptions.
+By following these recommendations and the linked migration workflow pages, you can manage your BigCommerce catalog migration with greater confidence and fewer disruptions.
diff --git a/docs/start/migration/1-2_setup.md → docs/start/migration/products/1-2_setup.md b/docs/start/migration/1-2_setup.md → docs/start/migration/products/1-2_setup.md
diff --git a/docs/start/migration/3_testing.md → docs/start/migration/products/3_testing.md b/docs/start/migration/3_testing.md → docs/start/migration/products/3_testing.md
diff --git a/docs/start/migration/5_migrate.md → docs/start/migration/products/5_migrate.md b/docs/start/migration/5_migrate.md → docs/start/migration/products/5_migrate.md
diff --git a/docs/start/migration/6_delta.md → docs/start/migration/products/6_delta.md b/docs/start/migration/6_delta.md → docs/start/migration/products/6_delta.md
diff --git a/docs/start/migration/products/overview.mdx b/docs/start/migration/products/overview.mdx
@@ -0,0 +1,52 @@
+---
+title: Product data migration overview
+---
+
+# 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](/docs/start/migration/prepare-data)
+- [Test a Limited Dataset](/docs/start/migration/test-data)
+- [Error Handling](/docs/start/migration/error-handling)
+- [Load Complete Data](/docs/start/migration/complete-migration)
+- [Go Live and Delta Migration](/docs/start/migration/delta-migration)
+
+## Getting started
+
+<Callout type="info">
+Data migration is complex and impacts your entire store setup. You should plan for it early in your project timeline to prevent setbacks.
+</Callout>
+
+### 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](https://support.bigcommerce.com/s/article/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](/docs/rest-catalog) for details.
+
+<Callout type="info">
+Category and brand IDs are not accessible by name, so create and cache a mapping schema to guarantee your catalog is properly configured.
+</Callout>
+
+## Additional resources
+
+For more technical details and API documentation, see:
+
+- [Catalog API Reference](/docs/rest-catalog)
+- [API best practices](/docs/start/best-practices)
+- [API rate limits](/docs/start/best-practices/api-rate-limits)
+- [WebDAV file access](https://support.bigcommerce.com/s/article/File-Access-WebDAV)
+- [Data migration services](https://www.bigcommerce.com/services/launch/#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.