Skip to content
Draft
Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
88d6a6d
Initial Overview Update Commit
chris-nowicki Sep 22, 2025
c421cf7
move error handling to root migration folder
chris-nowicki Sep 23, 2025
32f3315
udpate overview and rename catelog folder to products
chris-nowicki Sep 23, 2025
4f725f9
finalized initial draft of migration overview
chris-nowicki Sep 23, 2025
2a4688c
finalized initial draft of customer migration
chris-nowicki Sep 24, 2025
1f76fef
formatting fix
chris-nowicki Sep 24, 2025
e8c7e0d
fix password reset example
chris-nowicki Sep 24, 2025
4174a68
add segments and update to customer groups
chris-nowicki Sep 29, 2025
8f199a1
rename error-handling.md to error-handling.mdx
chris-nowicki Sep 30, 2025
b4bd526
Merge branch 'main' into DEVDOCS-6477
chris-nowicki Oct 2, 2025
a9dc8da
Merge branch 'main' into DEVDOCS-6477
chris-nowicki Oct 8, 2025
1c778ed
Merge branch 'main' into DEVDOCS-6477
chris-nowicki Oct 10, 2025
c7d9a33
fix: document structure based on james q feedback
chris-nowicki Oct 10, 2025
4524491
fix: remove initial header as it was redundant
chris-nowicki Oct 10, 2025
abd1c3a
fix: add additional information for channels
chris-nowicki Oct 10, 2025
d526c8a
fix: added clarity to optional fields
chris-nowicki Oct 10, 2025
6eeff1d
fix: minor introduction fix
chris-nowicki Oct 10, 2025
00c8a76
add additional context to end of api rate limits section
chris-nowicki Oct 10, 2025
a88687e
updates per james q comments
chris-nowicki Oct 13, 2025
24a59f5
Merge branch 'main' into DEVDOCS-6477
chris-nowicki Oct 14, 2025
eccadf9
Merge branch 'main' into DEVDOCS-6477
chris-nowicki Oct 29, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
52 changes: 52 additions & 0 deletions docs/start/migration/catalog/overview.mdx
Original file line number Diff line number Diff line change
@@ -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.
84 changes: 51 additions & 33 deletions docs/start/migration/overview.mdx
Original file line number Diff line number Diff line change
@@ -1,52 +1,70 @@
---
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.
Now that you've made the decision to move your store to BigCommerce, it's time to start the logistics of transferring your catalog. Recognizing that there is no single solution that will fit every business, we support several ways to migrate your data, ranging from our data migration apps to completely managed transfers through BigCommerce's Data Migration Services team.

## Why focus on data migration?
Factors such as ease of use, number of SKUs, orders and sales history, and custom product fields are key considerations to take into account before selecting a migration method.

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.
### Available Methods

## Migration workflow pages
| | Data Migration app (free, with limitations*) | CSV Import (free) | Managed Transfer | BigCommerce Apps |
|--------------|----------------------------------------------|-------------------|------------------|------------------|
| Products |||| N/A |
| Categories |||| N/A |
| Customers** |||| N/A |
| Orders || X || N/A |
| Reviews | X | X | X | [Product Review Importer & Exporter app (free)](https://www.bigcommerce.com/apps/product-review-importer/) |

- [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)
*The free version of our data migration app is limited to a combined total of 1,000 products, orders, and customers.<br/>
**Passwords cannot be migrated for PCI compliance

## Getting started
#### DATA MIGRATION APPS

<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>
Our data migration apps allow you to migrate your catalog data resources (products, categories, customers, orders) into your new BigCommerce store from the following platforms:

### Recommended preparatory tasks
- [Shopify](https://www.bigcommerce.com/apps/data-migration-services-shopify/)
- [Volusion](https://www.bigcommerce.com/apps/data-migration-volusion/)
- [WooCommerce](https://www.bigcommerce.com/apps/data-migration-services-woocommerce/)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [remark-lint] reported by reviewdog 🐶
WooCommerce is misspelt retext-spell retext-spell

- [Magento](https://www.bigcommerce.com/apps/data-migration-services-magento/)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [remark-lint] reported by reviewdog 🐶
Magento is misspelt; did you mean Magenta, Magneto? retext-spell retext-spell

- [Zen Cart](https://www.bigcommerce.com/apps/data-migration-services-zen-cart/)
- [Yahoo](https://www.bigcommerce.com/apps/data-migration-services-yahoo/)

- **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.
The demo versions of these apps are available in the App Marketplace, and are free to use for the first 1,000 resources. After this limit has been reached, there is a fee for transferring additional resources using the full app. Use the in-app contact form for more information.

- **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.
Ideal for those new to BigCommerce, the data migration apps should be the first step in relaunching your store on the BigCommerce platform. As the apps make a copy of your current store's catalog, they do not affect your live store. While each app has its own requirements specific to the hosting platform, they all require that:

- **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.
- Your current store is accessible from the Internet
- You have full administrative access to your current store's control panel

<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>
Any data stored in plug-ins or extensions will most likely not be included in the transfer, and would need to be added manually or by CSV import afterwards. If you have any data you need to preserve inside your BigCommerce store,
we suggest [exporting it](https://support.bigcommerce.com/s/article/Backing-Up-Your-Store) to create a backup copy before starting the transfer.

Basic customer details, such as name, email address, phone number, and physical addresses will be transferred.
However, since passwords can't be exported from most platforms for PCI compliance, customers are transferred with a
feature flag that requires them to reset their password the next time they attempt to log in.

#### CSV IMPORT

## Additional resources
As an alternative, you can import your [products](https://support.bigcommerce.com/s/article/Legacy-Import-Export-Overview) and [customers](https://support.bigcommerce.com/s/article/Importing-Exporting-Customers/#import) into your BigCommerce store by using a CSV file. Keep in mind that you will
likely need to reformat your source CSV file so that it can be imported successfully into your BigCommerce store. Spreadsheet programs
such as Excel or Google Sheets are necessary in order to edit CSV files. For stores with less than 10,000 SKUs,
we recommend using one of our data migration apps for migrating your products, and then using a CSV import to clean up your product data.

For more technical details and API documentation, see:
#### MANAGED DATA MIGRATION

- [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)
If you don't feel comfortable migrating your store's data using the app or CSV file, consider using a managed data transfer through BigCommerce's [Data Migration Services](https://www.bigcommerce.com/services/launch/) team. They will work directly with you to ensure that your data is securely migrated to your satisfaction, tailoring their services to match your business needs. The team is highly experienced in working with large catalogs with SKUs on more than 50 ecommerce platforms.
They are also able to handle custom migration requests to best meet the needs of your store's architecture. [Contact us](https://www.bigcommerce.com/request-quote/) to request a quote.

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

Developers can use our Catalog, Orders, and Customers API to add and modify products, orders, and customer data directly. See our [API Documentation](https://developer.bigcommerce.com/api-docs) on the Dev Center for more detailed information and examples.

<Callout>
**How do I ensure that imported historical orders aren't counted as new orders or GMV?**<br/>
When migrating orders from a previous platform, which involves [creating new orders via API](https://developer.bigcommerce.com/docs/rest-management/orders#create-an-order),
use M-MIG in the external_source field to exclude these orders from affecting your store's [trailing 12-month sales volume](https://support.bigcommerce.com/s/article/Pricing).
These orders do not deduct product stock and will bypass quantity requirements.
</Callout>