> For the complete documentation index, see [llms.txt](https://docs.changeup.com/salesforce/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.changeup.com/salesforce/salesforce-b2c-commerce/cartridge-installation/data-import.md).

# Data Import

Locate the **metadata > changeup\_import** directory within the distribution. We’re going to have to make a few changes to the data files within.

1. Rename the **metadata > changeup\_import > sites > \[MERCHANT-SITE-ID]** directory to be the ID of the site the cartridge is being installed for.
   1. If the site is assigned to a shared library, open **library.xml** for editing and in the primary \<library> node, add the attribute **library-id**, making its value the ID of the shared library to import the content assets into.
   2. `<library xmlns=“http://www.demandware.com/xml/impex/library/2006-10-31"`` `<mark style="color:red;">**`library-id=“site-lib-id`**</mark>**`”`**`>`
2. Open **metadata > changeup\_import > inventory-lists > inventory.xml** for editing. Modify the list- id value in the \<header> node to be the ID of the inventory list the site is assigned to.
   1. `<header list-id="`<mark style="color:red;">**`MERCHANT-LIST-ID`**</mark>`">`

{% hint style="danger" %}
NOTICE: If your recurring inventory import is using the REPLACE method, you will need to include the donation product’s inventory within that feed so it is always present. For reference of the inventory setup, look at the inventory.xml file included in the distribution.
{% endhint %}

3. Open **metadata > changeup\_import > catalogs > storefront-catalog > catalog.xml** for editing. Modify the catalog-id value in the node to be the ID of the storefront catalog the site is using for categorization.
   1. `code <catalog xmlns="http://www.demandware.com/xml/impex/catalog/2006-10-31" catalog-id="`<mark style="color:red;">**`MERCHANT-STOREFRONT-CATALOG-ID`**</mark>`">`&#x20;
4. Open **metadata > changeup\_import > jobs.xml** for editing. Modify the **site-id** value in the context node to be the ID of the site the cartridge is being installed for.

{% code lineNumbers="true" %}

```xml
<?xml version="1.0" encoding="UTF-8"?>
<jobs xmlns="http://www.demandware.com/xml/impex/jobs/2015-07-01">
    <job job-id="ChangeUp" priority="0">
        <description>Calls the ChangeUp donation api and flags the order as imported into ChangeUp.</description>
        <parameters/>
        <flow>
            <context site-id="RefArch"/>
            <step step-id="ChangeUpExportOrders" type="ExecuteScriptModule" enforce-restart="false">
                <description/>
                <parameters>
                    <parameter name="ExecuteScriptModule.Module">bm_changeup/cartridge/controllers/ChangeUp.js</parameter>
                    <parameter name="ExecuteScriptModule.FunctionName">SendDonations</parameter>
                    <parameter name="ExecuteScriptModule.Transactional">true</parameter>
                </parameters>
            </step>
        </flow>
```

{% endcode %}

{% hint style="danger" %}
NOTICE: If your recurring storefront catalog import is using the REPLACE method, you will need to include the donation product within that feed so it is always present. For reference of the inventory setup, look at the catalog.xml file under the storefront-catalog directory included in the distribution.
{% endhint %}

5. Now create a zip file from the **changeup\_import** directory, ensuring the zip file is named **changeup\_import.zip**
6. On the B2C Commerce instance, you are installing the data on, navigate to **Administration > Site Development > Site Import & Export** and upload the **changeup\_import.zip** file you created in the last step.
7. Import the data. Select the **changeup\_import.zip** archive and click the **Import** button.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.changeup.com/salesforce/salesforce-b2c-commerce/cartridge-installation/data-import.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.