b2c-site-import-export

To import a local directory as a Salesforce B2C site archive, run the b2c job import command with your local path and use the --wait flag to pause execution until the import job completes successfully.

The standard B2C site archive directory structure organizes data into specific folders including sites/, meta/, catalogs/, pricebooks/, and customobjects/ to ensure metadata XML patterns and site preferences are correctly mapped during import and export operations.

Yes, you can import a remote site archive already located on the B2C instance by executing the b2c job import command with the --remote flag, targeting the existing archive without needing a local upload.

You can export site data by running the b2c job export command, which packages site preferences, catalog assets, and metadata XML patterns into a structured archive suitable for version control.

Yes, the b2c CLI workflow enforces the standard site-archive directory layout, structuring metadata XML patterns, site preferences, and catalog assets so they can be easily tracked and managed in version control systems.

The best way to manage B2C site archives for automated deployments is using a CLI-driven workflow with the b2c CLI, executing job import and export commands while maintaining strict directory structure compliance for consistent metadata processing.