Documentation

Import data

Use import tools to bring existing users, inventory, IPAM and hardware records into DCIM before normal operations start.
Import data lives under Tools > Import data. It is designed for one-time or controlled migrations from an existing source of truth into DCIM.
DCIM prepares a preview first. Nothing is inserted until an admin reviews the counts and confirms the import.

Sources

TenantOS

TenantOS imports require an active IMPORT integration with the TENANTOS provider. If the integration is missing or inactive, it is not available as an import source.
Create and test the integration first in Integrations.

JSON

JSON import is native and does not require an integration. Upload a JSON file, prepare the import, review the preview and confirm only when the counts look correct.

Import flow

Start

Select the source, the target datacenter and the record types to import. Leave unchecked anything that should stay manual.

Preview

DCIM fetches the source data and shows how many records are ready to import, already exist or will be skipped. Large imports are prepared in the background, so keep the page open until the preview is ready.

Confirm

Confirm only after reviewing the preview. DCIM then inserts the prepared data into the database and records the import result.

Cancel

Cancel discards the prepared import session before it is inserted. If the page is refreshed, DCIM reloads the session while it is still available.

What can be imported

Supported records depend on the source, but DCIM can import users, subnets, servers, BMC connection records, switches, IP assignments and hardware parts.

BMC records

BMC records are imported only when the source provides the connection fields required by DCIM. Incomplete BMC data is skipped instead of creating unusable credentials.

Parts

Imported parts are useful for inventory records. For reinstall workflows, disk targeting still requires discovery data with real serial, WWN or hint values.

JSON example

The JSON file can include only the sections you want to import. Keep field names predictable and avoid adding secrets that are not needed by DCIM.
{
  "users": [
    {
      "name": "Example Customer",
      "email": "[email protected]",
      "phone": "+351000000000"
    }
  ],
  "subnets": [
    {
      "cidr": "192.0.2.0/24",
      "gateway": "192.0.2.1"
    }
  ],
  "servers": [
    {
      "name": "srv-01",
      "hostname": "srv-01.example.com",
      "mac": "00:11:22:33:44:55",
      "bmc": {
        "host": "192.0.2.10",
        "username": "admin",
        "password": "secret"
      },
      "ips": ["192.0.2.20"],
      "parts": [
        {
          "component_type": "CPU",
          "vendor": "Intel",
          "model": "Xeon Silver",
          "value": "16 cores"
        }
      ]
    }
  ],
  "switches": [
    {
      "name": "sw-01",
      "hostname": "sw-01.example.com"
    }
  ]
}