# B2c Site Import Export > Import and export site archives containing metadata XML on B2C Commerce instances using the b2c CLI. Use this skill whenever the user needs to import a site archive directory or zip to an instance, export site configuration as XML, structure a site archive folder (sites/site_template/meta/), write or debug metadata XML files (system-objecttype-extensions.xml, custom-objecttype-definitions.xml, pr… - **Type:** Skill - **Install:** `agentstack add skill-salesforcecommercecloud-b2c-developer-tooling-b2c-site-import-export` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [SalesforceCommerceCloud](https://agentstack.voostack.com/s/salesforcecommercecloud) - **Installs:** 0 - **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills) - **Latest version:** 0.1.0 - **License:** Apache-2.0 - **Upstream author:** [SalesforceCommerceCloud](https://github.com/SalesforceCommerceCloud) - **Source:** https://github.com/SalesforceCommerceCloud/b2c-developer-tooling/tree/main/skills/b2c-cli/skills/b2c-site-import-export - **Website:** https://salesforcecommercecloud.github.io/b2c-developer-tooling/ ## Install ```sh agentstack add skill-salesforcecommercecloud-b2c-developer-tooling-b2c-site-import-export ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Site Import/Export Skill Use the `b2c` CLI plugin to import and export site archives on Salesforce B2C Commerce instances. > **Tip:** If `b2c` is not installed globally, use `npx @salesforce/b2c-cli` instead (e.g., `npx @salesforce/b2c-cli job import`). ## Configuration & Authentication The CLI auto-discovers the target instance and credentials from `SFCC_*` environment variables, `dw.json` in the current or parent directories, `~/.mobify`, `package.json`, and configuration plugins. **Flags like `--server`, `--client-id`, `--client-secret`, `--username`, and `--password` are usually unnecessary** — only pass them to override what's auto-detected. Run `b2c setup inspect` to see the resolved configuration and which source provided each value (use `--json` for scripting, `--unmask` to reveal secrets). For precedence rules and troubleshooting, see the `b2c-cli:b2c-config` skill. ## Import Commands ### Import Local Directory ```bash # Import a local directory as a site archive (waits for completion by default) b2c job import ./my-site-data # Import and return immediately without waiting b2c job import ./my-site-data --no-wait # Import a local zip file b2c job import ./export.zip # Keep the archive on the instance after import b2c job import ./my-site-data --keep-archive # Show job log if the import fails b2c job import ./my-site-data --show-log ``` ### Import Remote Archive ```bash # Import an archive that already exists on the instance (in Impex/src/instance/) b2c job import existing-archive.zip --remote ``` ### Import Archives Larger Than the Instance Limit An instance rejects a single import archive above its size limit (typically 200 MB). Use `--split` on a directory import to import the data in multiple smaller parts: ```bash # Split a large directory import into multiple archive parts b2c job import ./big-site-data --split # Tune the per-archive size limit (default 190mb; bare number is MiB) b2c job import ./big-site-data --split --max-size 150mb ``` How splitting works: - **Metadata/XML is imported first**, kept together in one archive when it fits (so internal references and dependency ordering resolve within a single import). If the XML alone is too large, it splits at top-level data-unit boundaries (`catalogs`, `libraries`, `sites`, `meta`, …) in dependency order — never splitting a single unit. - **Static assets** (files under a `static/` folder) are deferred into later archive parts, packed by compressed size. They attach to the catalogs/libraries created by the metadata import. - Parts import sequentially; the command stops on the first failure. If a single file, or a single data unit's XML, is larger than `--max-size` on its own, the command errors (a file is never split across archives). A normal directory import that exceeds the limit warns and recommends `--split`. `--split` cannot be combined with `--remote`, subset paths, or `--no-wait`. ## Export Commands ```bash # Export global metadata (waits for completion by default) b2c job export --global-data meta_data # Export a site with specific data units b2c job export --site RefArch --site-data content,site_preferences ``` ## Common Workflows ### Adding a Custom Attribute to Products 1. Create the metadata XML file: **meta/system-objecttype-extensions.xml:** ```xml Vendor SKU string false true Custom Attributes ``` 2. Create the directory structure: ``` my-import/ └── meta/ └── system-objecttype-extensions.xml ``` 3. Import: ```bash b2c job import ./my-import ``` ### Adding Site Preferences 1. Create metadata for the preference: **meta/system-objecttype-extensions.xml:** ```xml Enable Feature X boolean false ``` 2. Create preference values: **sites/MySite/preferences.xml:** ```xml true ``` 3. Directory structure: ``` my-import/ ├── meta/ │ └── system-objecttype-extensions.xml └── sites/ └── MySite/ └── preferences.xml ``` 4. Import: ```bash b2c job import ./my-import ``` ### Creating a Custom Object Type 1. Define the custom object: **meta/custom-objecttype-definitions.xml:** ```xml API Configuration source-to-target site Config ID string 1 API Endpoint string API Key password Active boolean true ``` 2. Import: ```bash b2c job import ./my-import ``` ### Importing Custom Object Data **customobjects/APIConfiguration.xml:** ```xml https://api.payment.com/v2 true ``` ## Site Archive Structure ``` site-archive/ ├── services.xml # Service configurations (credentials, profiles, services) ├── meta/ │ ├── system-objecttype-extensions.xml # Custom attributes on system objects │ └── custom-objecttype-definitions.xml # Custom object type definitions ├── sites/ │ └── {SiteID}/ │ ├── preferences.xml # Site preference values │ └── library/ │ └── content/ │ └── content.xml # Content assets ├── catalogs/ │ └── {CatalogID}/ │ └── catalog.xml # Products and categories ├── pricebooks/ │ └── {PriceBookID}/ │ └── pricebook.xml # Price definitions ├── customobjects/ │ └── {ObjectTypeID}.xml # Custom object instances └── inventory-lists/ └── {InventoryListID}/ └── inventory.xml # Inventory records ``` ## Tips ### Checking Job Status ```bash # Search for recent job executions b2c job search # Wait for a specific job execution b2c job wait # View job logs on failure b2c job import ./my-data --show-log ``` ### Best Practices 1. **Test imports on sandbox first** before importing to staging/production 2. Import waits for completion by default — use `--no-wait` only when you want to return immediately 3. **Use `--show-log`** to debug failed imports 4. **Keep archives organized** by feature or change type 5. **Version control your metadata** XML files ### Configuring External Services For service configurations (HTTP, FTP, SOAP services), see the `b2c:b2c-webservices` skill which includes: - Complete services.xml examples - Credential, profile, and service element patterns - Import/export workflows Quick example: ```bash # Import service configuration b2c job import ./services-folder ``` Where `services-folder/services.xml` follows the patterns in the `b2c:b2c-webservices` skill. ## Detailed Reference - [Metadata XML Patterns](references/METADATA-XML.md) - Common XML patterns for imports ## Related Skills - `b2c:b2c-webservices` - Service configurations (HTTP, FTP, SOAP), services.xml format - `b2c:b2c-metadata` - System object extensions and custom object definitions - `b2c-cli:b2c-job` - Running jobs and monitoring import status ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [SalesforceCommerceCloud](https://github.com/SalesforceCommerceCloud) - **Source:** [SalesforceCommerceCloud/b2c-developer-tooling](https://github.com/SalesforceCommerceCloud/b2c-developer-tooling) - **License:** Apache-2.0 - **Homepage:** https://salesforcecommercecloud.github.io/b2c-developer-tooling/ Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-salesforcecommercecloud-b2c-developer-tooling-b2c-site-import-export - Seller: https://agentstack.voostack.com/s/salesforcecommercecloud - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.