BigCommerce is a SaaS e-commerce platform that enables businesses to build and manage online stores. Commvault protects your complete BigCommerce store data, including product catalogs, customer records, orders, marketing assets, storefront themes, content pages, and fulfillment configuration, enabling full store recovery to the same store or a different target store.
What's supported
BigCommerce requirements
BigCommerce API v2 and v3 (both used; v3 preferred where available) is required. For API documentation, see the BigCommerce Developer Documentation.
Supported resources and data
Commvault backs up the following BigCommerce store resources:
| Category | Resources backed up |
|---|---|
| Store | Store information, active storefront theme, currencies, tax classes, customer groups |
| Catalog | Brands (with images), category trees, categories (with images), products (with variants, images, options, bulk pricing), price lists |
| Customers | Customer accounts and addresses |
| Orders | Orders with line items and shipping addresses |
| Marketing | Coupons, promotions, gift certificates |
| Content | Content pages, blog posts, URL redirects |
| Fulfillment | Shipping zones, inventory (locations and stock levels) |
The hierarchy is flat. Every backup task backs up resource-level metadata. Backups can be browsed and restored at the resource type level (for example, Products, Customers, Orders).
Backup and restore capabilities
| Capability | Details |
|---|---|
| Backup scope | Full store backup. Every backup captures all 20 resource types. |
| Backup levels | Full backup only. Incremental backup is not supported because the BigCommerce API does not expose a change-delta or event log. |
| Restore destinations | Restore to the same BigCommerce store (in place) or to a different BigCommerce store (out of place). |
| Restore modes | Three modes: missing-only (create items that do not exist), full-overwrite (create or update items), wipe-and-restore (delete all existing data before restoring). |
| Cross-store restore | Supported. You can restore from one BigCommerce store to a different store with appropriate credentials. |
| Selective restore | You can restore individual resource types (for example, Products only, Customers only) after a full backup. |
| Dependency handling | Restore proceeds in parent-first order. IDs are remapped automatically (for example, customer groups, brands, categories, products) to maintain relationships in the target store. |
Data flow and storage
The Commvault access node calls the BigCommerce REST API to retrieve store data and writes it to Commvault-managed object storage. The BigCommerce API returns JSON metadata and image binaries, which the access node stores in S3-compatible, Azure Blob, or Google Cloud Storage buckets configured in your backup plan.
What isn't supported
- Incremental backups. Every backup is a full backup of the entire store.
- Restoration of customer passwords. Customer passwords are not available through the BigCommerce API and cannot be backed up or restored. Affected customers must reset their passwords after a restore.
- Email templates and third-party app configurations. These are outside the scope of the BigCommerce API and are not included in backups.
- Payment gateway credentials. These must be reconfigured manually after a restore.
Limitations
- Original order IDs differ after restore. BigCommerce assigns new IDs when orders are created during a restore.
- Tax class IDs are read-only in BigCommerce. Cross-store restores can reference mismatched tax class IDs in products and orders if the target store has a different tax class configuration.
- Variant images are restored using the original CDN image URL only. The BigCommerce variant image endpoint rejects direct binary uploads. If the source image URL has expired, the variant image cannot be restored. Product, brand, and category images are restored via direct binary upload and are not affected.
- Content-selection tree (machineBrowse) in the UI is not implemented. Backup scope selection and selective restore are managed through configuration or command-line options.