> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/platform-core/bulk-import.md).

# Importing

Using Bulk Import, you can import asset types, assets, and tags into BuildingPro Suites from a JSON file. Check the recognized entities and run a test import before starting the import.

## Procedure

<figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FMxEBfxNM7sfn9apSntnZ%2FDocs_Bulk_Import_1.png?alt=media&#x26;token=9ee10fd1-0b9d-4eba-8cea-d2f8492bc004" alt=""><figcaption></figcaption></figure>

1. Click on Engineering **\[A]**
2. Click on Importing **\[B]**
3. Drag and drop a .json file into **\[B1]**
4. Click on **\[B2]**\
   ▷ The window **\[C]** opens
5. Check the entered .json file in **\[C1]**
6. Click on **\[C2]**
7. The window **\[D]** opens
8. Via **\[D1]** and **\[D7]**, select the entities you want to import. ✙ Details on these options can be found below.
9. Click on Test Import **\[D4]**\
   ▷ The window **\[E]** opens. ✙ In window **\[E]**, you will see any error messages.
10. Click on **\[E1]**\
    ▷ The window **\[E]** closes.
11. Optional: Fix any error messages in the .json file.
12. Click on **\[D8]**\
    ▷ The import is started

## Import Options

<div data-full-width="true"><figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FqQ5afr1Jx8EGIJEjGamE%2FDocs_Bulk_Import_2.png?alt=media&#x26;token=2d1bb533-540d-4f2f-85df-b934f3216392" alt=""><figcaption></figcaption></figure></div>

<table data-full-width="true"><thead><tr><th width="86.39996337890625">Element</th><th width="220">Title</th><th>Details</th></tr></thead><tbody><tr><td><strong>[D1]</strong></td><td>Entity type</td><td>Shows the entities recognized in the .json file, filtered by type.</td></tr><tr><td><strong>[D2]</strong></td><td>"Overwrite" switch</td><td>When this switch is activated, duplicate entries are overwritten</td></tr><tr><td><strong>[D3]</strong></td><td>"Mark duplicates" switch</td><td>When this switch is activated, duplicate entries are marked</td></tr><tr><td><strong>[D4]</strong></td><td>Test Import</td><td>Click to perform a test import. A test import must be performed before every import.</td></tr><tr><td><strong>[D5]</strong></td><td>Guide</td><td>Open online help</td></tr><tr><td><strong>[D6]</strong></td><td>Recognized entities</td><td>Entities that were recognized in the .json file.</td></tr><tr><td><strong>[D7]</strong></td><td>Entity selection</td><td>Check to activate an asset for import. Only checked entities are imported.</td></tr><tr><td><strong>[D8]</strong></td><td>Import</td><td>Click to start the import. This option is only available after a test import has been performed.</td></tr></tbody></table>

## Notes on Functionality and Syntax

### Example Syntax

This example combines asset types, assets, and tags without a `projects` wrapper. Replace the example values with values for your tenant and run **Test Import** before importing.

```json
{
    "tags": [
        {
            "resourceId": "d1f0e4b3-2a6c-4f8b-b9c3-7a2f5e8c3344",
            "tagName": "BLE",
            "colorId": 5
        }
    ],
    "types": [
        {
            "Field Test Device": {
                "custom": false,
                "payloadFunction": "Adeunis",
                "vendor": "Adeunis",
                "model": "Adeunis FTD Network Tester",
                "translation": { "en": "Adeunis FTD Network Tester" },
                "urldoc": "https://www.adeunis.com/en/produit/ftd-network-tester/",
                "allowedInactivity": "01:00:00",
                "icon": null,
                "attributes": [
                    {
                        "battery_level": {
                            "attributeType": "battery-voltage",
                            "subtype": "status",
                            "translation": { "en": "Battery Level" },
                            "isDigital": false,
                            "unit": "%",
                            "scale": null,
                            "zero": null,
                            "precision": null,
                            "map": null,
                            "pipelineMode": "avg",
                            "pipelineRaster": ["M15", "H1", "DAY"],
                            "viewer": false,
                            "ar": false,
                            "sourcePath": ["payload", "voltage"]
                        }
                    }
                ]
            }
        }
    ],
    "assets": [
        {
            "resourceId": "123e4567-e89b-12d3-a456-42665544001a",
            "globalAssetIdentifier": "GAI 4719",
            "name": "Example asset",
            "deviceIds": ["f6d488a8126a"],
            "assetType": "Field Test Device",
            "tags": ["BLE"]
        }
    ]
}
```

The asset's `assetType` and `tags` values refer to the type and tag defined in the same file. Test the import to catch missing references and other validation errors before you start it.


---

# 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://docs.buildings.ability.abb/collection/platform/platform-core/bulk-import.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.
