> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/assets/update-asset-metadata-by-csv.md).

# Update Asset Metadata by CSV

Update asset metadata for hundreds of existing assets simultaneously from a CSV file instead of manual entry

Update Asset Metadata by CSV allows you to update multiple existing assets in HIVO simultaneously using a CSV file. Instead of opening each asset to edit it manually, you can:

* Export your asset data -> edit the data in the CSV -> import it back into HIVO with **Bulk Import Asset Data**.
* Update an asset's **Name**, **Folder Path**, **Production Date**, **Location**, **Tags** and **Metadata** fields.

{% hint style="info" %}
This feature only updates assets that already exist in HIVO. It can't create new assets: to add assets, upload them as usual.
{% endhint %}

⚠️  **Who can use it:** Client Admins who have permission to edit assets. The import and export pages are in **Client Profile -> Settings -> Reporting & Data**.

### 1. Export Asset Data to get the Internal Asset ID

The safest way to update assets is to match them by their **Internal Asset ID**. Do not create Asset IDs manually. Instead, export your asset data from HIVO so you have the correct IDs.

#### 🔹 Step 1. Export Asset Data

👉 Go to Client Profile -> Settings -> **Reporting & Data** -> **Export Data via CSV**, then select the **Assets** tab.

* Click the **Select folder path** field to choose the folder containing the assets you wish to export. Tick **Include all results in sub-folders** to include assets in its sub-folders too.
* You can use filters to narrow down the assets you want to export:
  * Created from / Created to
  * Last modified from / Last modified to
* Then select **Export Assets**. HIVO prepares the CSV in the background and sends you a notification with the download link when it's ready.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2F0CvrRGSnCZr4FCvlBMyj%2FGroup%20832.png?alt=media&amp;token=624e5ba1-2e16-4e7d-86c5-d6f76ed7b04d" alt=""><figcaption></figcaption></figure>

The exported CSV contains these columns: ID (the Internal Asset ID), name, location, tag, createAt, SKUs... (if you can see Products), and one column per metadata field.

#### 🔹 Step 2. Prepare the CSV File

* Open the exported CSV file.
* **Keep the ID column intact**. This is the Internal Asset ID that HIVO uses to find each asset during the import.
* Edit the columns you want to update, or add new columns for metadata fields. You can delete any columns you don't want to change.
* The first row must contain the column headers. The file can be up to **50 MB**.

{% hint style="warning" %}
**How updates are applied**

* **Tags are added, not replaced.** The tags in the CSV are added to each asset's existing tags. You can't remove tags with a CSV import.
* **Metadata is updated field by field.** Only the metadata fields in your CSV change. Other metadata on the asset stays as it is.
* **Blank cells don't clear values.** If a cell is empty, the asset keeps its current value for that field.
* **The Product (SKUs) column can't be imported.** It's included in the export for reference only.
  {% endhint %}

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FvGTpsgYddQveEQJ4kTqV%2FGroup%20836.png?alt=media&amp;token=bd777f46-0ab1-44c5-a9da-b06e2a579477" alt=""><figcaption></figcaption></figure>

### 2. Import the CSV File

👉 Go to Client Profile -> Settings -> **Reporting & Data** -> **Import Data via CSV**. The import has four steps: **Upload CSV**, **Map Columns**, **Confirm and Import** and **Review Results**.

#### 🔹 Step 3. Upload your CSV File

* Set **Target** to **Assets**. **Import Mode** is always **Update Only** for assets.
* Drag and drop the CSV file into the upload area, or click **Choose CSV File** to browse your computer.
* HIVO reads the file and moves on to the next step automatically.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FnaZ6eISWEMHZDgkzH9Sj%2FGroup%20840.png?alt=media&amp;token=cfe77fb6-d02e-4a6b-a103-26eb43362bf9" alt=""><figcaption></figcaption></figure>

#### 🔹 Step 4. Map Columns

For each column in your CSV, choose the HIVO field it should update, or choose **Ignore** to skip it. Click **Auto-map Columns** to let HIVO match columns to fields by their headers, and **Reset mappings** to start again.

* The fields you can map are **ID**, **Name**, **Folder Path**, **Production Date**, **Location**, **Tags**, an existing **Metadata** field, or **New Metadata Field**.
* You also need to choose how HIVO finds each asset. Tick **Select as matching field** on one of these columns:
  * **ID** (recommended): map the `_id` column to **ID**. It's automatically used as the only matching field, and each row updates exactly one asset.
  * **Name** and/or **Folder Path**: assets are found by their current name and/or folder. A column used for matching is only used to find assets; it isn't updated.

{% hint style="danger" %}
When you match by **Name** or **Folder Path**, every asset that matches the row is updated. For example, matching by Folder Path alone updates every asset in that folder. Use the ID to update one asset at a time.
{% endhint %}

* Click **Next** when the mapping is done. You can't continue until a matching field is selected.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FL27vIepKnZRbqjBkDTcj%2FGroup%20837.png?alt=media&amp;token=49e6aefe-ceb3-4237-986a-d12a6209ea7d" alt=""><figcaption></figcaption></figure>

#### 🔹 Step 5. Confirm and Import

Check the summary before importing:

* the matching fields that will be used to find the assets,
* the column mappings, and
* a preview of the first rows of your data.

Click **Import** to start updating the assets. Large files are imported in batches, so this can take a few minutes.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FAl1Ypnt9dGml162PnEdS%2FGroup%20838.png?alt=media&amp;token=01d19de3-a6dd-41d2-ad85-6cd04e2792e7" alt=""><figcaption></figcaption></figure>

#### 🔹 Step 6. Review Results

When the import finishes, HIVO shows how many rows were processed, how many assets were updated, and how many rows were skipped or failed. Common reasons a row is skipped:

* **Upload not found**: no asset in your account has that ID.
* **No matching upload found**: no asset matches the Name or Folder Path in that row.
* **No changes to make**: the row has no values to update.

If some rows failed, click **Download Error Records** to get a CSV of those rows with the error for each one. Fix them and import that file again.&#x20;

* Click **Start New Import** to import another file.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FduuY752stXne6flCgstZ%2FGroup%20834.png?alt=media&amp;token=7391ce4a-f5e7-4b11-af4b-f2efebac12bc" alt=""><figcaption></figcaption></figure>

* **Error Records preview**

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2FYi5e5iOZlhsyOL6cPzxq%2Fimage%2018.png?alt=media&amp;token=527b1cf9-f283-4f10-84e7-91eaa0eaccbd" alt=""><figcaption></figcaption></figure>

If you have any questions, don't hesitate to ask, we're always here to help!


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.hivo.co/assets/update-asset-metadata-by-csv.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
