---
schema_version: "1"
id: 1e31d1692106860c13f8286580fe07f6571e811c3d7306519d784afb7d3945dd
title: Archiving in B2C Commerce
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_archiving.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_archiving.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a9c56d7e85fbca03e5963e243a1cacbdaff206650a900c188cc4734ef37f46ec
description: You can't automatically roll back instances impacted by data import. Therefore, it’s a good practice to create an archive of your existing site that you can roll back to if the import fails.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Archiving in B2C Commerce

You can't automatically roll back instances impacted by data import. Therefore, it’s a good practice to create an archive of your existing site that you can roll back to if the import fails.

Salesforce recommends that you keep import feeds for a specified period and regularly export and archive data that only exists in the Business Manager. Exported data is also useful if users make a mistake in Business Manager and change or eliminate data inappropriately.

B2C Commerce scripts can archive import feeds and remove out-of-date files. Alternatively, archive feeds on your backend system.