> Software > Protect > SaaS apps > BigCommerce

Restore BigCommerce data

You can restore BigCommerce content to recover from deletion or corruption. You can restore content to the same store (in place) or to a different BigCommerce store (out of place).

Restore destinations

Destination When to use
In place Recovering from accidental deletion, corruption, or ransomware on the original BigCommerce store
Out of place Migration, disaster recovery to a new store, or restoring to a test or sandbox store

Permissions and prerequisites

Before you restore:

  • For in-place restores, the API access token used for backups must have Modify permission on all required scopes. If the token used for backups has only Read-only permission, update it to include Modify permission before proceeding.
  • For out-of-place restores (restoring to a different BigCommerce store), create a separate V2/V3 API token on the target store with Modify permission on all required scopes. For the list of required scopes, see Configure BigCommerce user and permissions.

Restore in place

You can restore BigCommerce content to the original store. Choose the restore mode based on your recovery scenario.

Use this mode to restore only items that do not exist in the store. Existing items are skipped. This mode is safe to run multiple times and is useful for recovering accidentally deleted data without affecting items that are already in good shape.

  1. From the Command Center navigation pane, go to Protect > SaaS applications.
  2. Click the BigCommerce store configuration.
  3. On the Backups tab, select the recovery point you want to restore.
  4. Click Restore.
  5. Select the resource types to restore (for example, restore only Products and Customers, or restore all 20 resource types).
  6. Set the restore mode to missing-only (default).
  7. Click Restore.
  8. Monitor the restore job in the Jobs view.

Restore proceeds in parent-first order: store information, theme, currencies, tax classes, customer groups, brands, category trees, categories, products, price lists, customers, orders, marketing assets, content pages, shipping zones, and inventory. IDs are remapped automatically to maintain relationships in the target store.

Use this mode to restore all items from the backup and update existing items with backup data. This mode is useful when you want the store to exactly reflect the backup snapshot.

  1. From the Command Center navigation pane, go to Protect > SaaS applications.
  2. Click the BigCommerce store configuration.
  3. On the Backups tab, select the recovery point you want to restore.
  4. Click Restore.
  5. Select the resource types to restore.
  6. Set the restore mode to full-overwrite.
  7. Click Restore.
  8. Monitor the restore job in the Jobs view.

Restore proceeds in parent-first order: store information, theme, currencies, tax classes, customer groups, brands, category trees, categories, products, price lists, customers, orders, marketing assets, content pages, shipping zones, and inventory. IDs are remapped automatically to maintain relationships in the target store.

Use this mode to completely rebuild the store from a known good backup. This mode deletes all existing data before restoring. Use with caution.

/// warning This mode is destructive. All existing store data is deleted before restoring. Use this mode only for disaster recovery or complete store rebuild scenarios.

  1. From the Command Center navigation pane, go to Protect > SaaS applications.
  2. Click the BigCommerce store configuration.
  3. On the Backups tab, select the recovery point you want to restore.
  4. Click Restore.
  5. Select the resource types to restore.
  6. Set the restore mode to wipe-and-restore.
  7. Confirm the destructive operation.
  8. Click Restore.
  9. Monitor the restore job in the Jobs view.

The restore deletes all existing store data in reverse dependency order, then restores the backup in parent-first order. Resource types that do not have a delete endpoint in the BigCommerce API (tax classes, store information, currencies, shipping zones, themes) are left in place and overwritten.

Restore proceeds in parent-first order: store information, theme, currencies, tax classes, customer groups, brands, category trees, categories, products, price lists, customers, orders, marketing assets, content pages, shipping zones, and inventory. IDs are remapped automatically to maintain relationships in the target store. ///

Restore out of place

You can restore BigCommerce content to a different BigCommerce store. This is useful for migration, disaster recovery, or restoring to a test or sandbox store.

Use this mode to restore only items that do not exist in the target store. Existing items are skipped.

  1. From the Command Center navigation pane, go to Protect > SaaS applications.
  2. Click the source BigCommerce store configuration (the store you backed up).
  3. On the Backups tab, select the recovery point you want to restore.
  4. Click Restore.
  5. Select Restore to a different store (out of place).
  6. Provide the target store credentials:
  7. Target Store Hash: The store hash of the target BigCommerce store.
  8. Target API Access Token: The V2/V3 API access token for the target store with Modify permission on all required scopes.
  9. Select the resource types to restore.
  10. Set the restore mode to missing-only.
  11. Click Restore.
  12. Monitor the restore job in the Jobs view.

Restore proceeds in parent-first order: store information, theme, currencies, tax classes, customer groups, brands, category trees, categories, products, price lists, customers, orders, marketing assets, content pages, shipping zones, and inventory. IDs are remapped automatically to maintain relationships in the target store.

Use this mode to restore all items from the backup and update existing items in the target store with backup data.

  1. From the Command Center navigation pane, go to Protect > SaaS applications.
  2. Click the source BigCommerce store configuration (the store you backed up).
  3. On the Backups tab, select the recovery point you want to restore.
  4. Click Restore.
  5. Select Restore to a different store (out of place).
  6. Provide the target store credentials:
  7. Target Store Hash: The store hash of the target BigCommerce store.
  8. Target API Access Token: The V2/V3 API access token for the target store with Modify permission on all required scopes.
  9. Select the resource types to restore.
  10. Set the restore mode to full-overwrite.
  11. Click Restore.
  12. Monitor the restore job in the Jobs view.

Restore proceeds in parent-first order: store information, theme, currencies, tax classes, customer groups, brands, category trees, categories, products, price lists, customers, orders, marketing assets, content pages, shipping zones, and inventory. IDs are remapped automatically to maintain relationships in the target store.

Use this mode to completely rebuild the target store from the backup. This mode deletes all existing data in the target store before restoring.

/// warning This mode is destructive. All existing data in the target store is deleted before restoring. Use this mode only for disaster recovery or complete store rebuild scenarios.

  1. From the Command Center navigation pane, go to Protect > SaaS applications.
  2. Click the source BigCommerce store configuration (the store you backed up).
  3. On the Backups tab, select the recovery point you want to restore.
  4. Click Restore.
  5. Select Restore to a different store (out of place).
  6. Provide the target store credentials:
  7. Target Store Hash: The store hash of the target BigCommerce store.
  8. Target API Access Token: The V2/V3 API access token for the target store with Modify permission on all required scopes.
  9. Select the resource types to restore.
  10. Set the restore mode to wipe-and-restore.
  11. Confirm the destructive operation.
  12. Click Restore.
  13. Monitor the restore job in the Jobs view.

The restore deletes all existing data in the target store in reverse dependency order, then restores the backup in parent-first order. Resource types that do not have a delete endpoint in the BigCommerce API (tax classes, store information, currencies, shipping zones, themes) are left in place and overwritten.

Restore proceeds in parent-first order: store information, theme, currencies, tax classes, customer groups, brands, category trees, categories, products, price lists, customers, orders, marketing assets, content pages, shipping zones, and inventory. IDs are remapped automatically to maintain relationships in the target store. ///

×

Loading...