You are here:
Using Site Import/Export for Development Testing in B2C Commerce
When multiple developers work on one or more sites, make sure that they all have the same data in their systems. They can use Site Import/Export to set up multiple sandboxes with the same configuration.
Sometimes, developers want to import some of the data from production into the sandbox. Sometimes, importing all the site information from production isn’t desirable for security or other reasons. For example, a merchant doesn’t want a developer to import customer data for security reasons. In this case, they can use Site Import/Export to export only the portion of the site data that is available.
Site Import/Export is only intended for setting up identical sites (same names and IDs) and the same organization-level data across instances. However, the Business Manager UI also lets you export a subset of the instance data.
-
Log in to Business Manager with an account that has import and export
privileges for the site. Administrators can check account privileges by clicking
App Launcher
, and then selecting .
-
Click App Launcher
, and then select .
-
In the Export field, enter a name for your export file. Enter a name, not a
path.
We recommend that you use the following syntax:
yyyymmdd-ModuleNames-version
For example: 20101231-Catalogs-Pricebooks-17-1
- Check the Save in the global export directorybox.
- Check the boxes for data you want to export.
- In the Export field, click Export.
-
Check the Status section of the page for your export process. It includes the
name of the export file you provided in parentheses. For example,
Site Export (preferences)produces apreferences.zipfile. When the status for your process indicates success, refresh the page. The name of your export file appears in the list of files under the Import section of the page. - In the Import section, select your export file and click Import to download the file.
If an instance export or backup fails for any reason, the system still generates a .zip file, but appends the suffix "-invalid" to the filename. Salesforce recommends that you establish a mechanism to detect if an invalid file is produced.
