Bulk Importing Assets in Telematics Guru
Learn how to efficiently bulk import assets into Telematics Guru, streamlining your asset management process.
Written by Digital Matter Authors
Updated at November 13th, 2026
Table of Contents
Bulk Importing Assets in Telematics Guru
Use Bulk Asset Import to create multiple assets from a CSV file. The template covers asset identification, organisation assignments, device details, custom fields, vehicle information and starting usage readings.
Before You Begin
Select the organisation in which the assets should be created.
Use the current template from Admin > Bulk Import. Device types in the template reflect those available to your account, including any custom device names.
Prepare the actual asset and device details for your import. Replace the example rows rather than importing them as real assets.
BLE Tags Use Import Tags
BLE tag assets cannot be imported through Bulk Asset Import. Use the separate Import Tags function for BLE tags. Do not use this asset CSV template as a tag import template.
Prepare the CSV File
Go to Admin > Bulk Import and obtain the current Bulk Asset Import CSV template.
Keep the column headers unchanged. Enter one asset per row, using the field reference below.
Use a DeviceType supplied by your account's current template. If your account uses custom device names, use those names rather than substituting default Digital Matter names.
Save the completed file as CSV and upload it on the bulk import page.
CSV Field Reference
The template contains the following columns. Preserve their exact spelling. Example values illustrate the supplied template's format, not a complete list of permitted values or a statement that every field is required.
| Column | Purpose | Entry Guidance |
|---|---|---|
AssetName |
The asset's name in Telematics Guru. | Enter the name used to identify the asset. |
Description |
A description of the asset. | For example, its role or use. |
AssetType |
The asset's category, rather than its tracking device type. | The supplied template includes examples such as Car, Truck and SUV. |
Department |
The asset's department assignment. | Use the department intended for the asset in the target organisation. |
Project |
The asset's project assignment. | Use the project intended for the asset in the target organisation. |
DeviceSerial |
The serial number of the tracking device. | Enter the actual device serial. Omit leading zeros, as in individual asset creation. |
Custom1 |
The first custom asset field. | Use the value appropriate to your organisation's first custom field. |
Custom2 |
The second custom asset field. | Use the value appropriate to your organisation's second custom field. |
Custom3 |
The third custom asset field. | Use the value appropriate to your organisation's third custom field. |
DeviceType |
The tracking device type. | Use the account-specific device type name from the current template. Do not substitute AssetType. |
AssetCode |
The asset's code or reference. | Enter the reference used by your organisation. |
AssetHealthTrackingEnabled |
Whether asset health tracking is enabled. | The supplied template uses 0 and 1 for this flag. |
Manufacturer |
The manufacturer of the asset. | For example, the vehicle manufacturer. |
Model |
The asset's model. | Enter the model associated with the asset. |
Vin |
The vehicle identification number. | Enter the asset's actual VIN, where applicable. |
RegistrationNumber |
The asset's registration number. | Enter the registration identifier, where applicable. |
ChassisNumber |
The asset's chassis number. | Enter the chassis identifier, where applicable. |
OdometerReading |
The asset's starting odometer reading. | Use with UnitOfMeasurement to identify the distance unit. |
UnitOfMeasurement |
The distance unit for the odometer reading. | The supplied template uses km and mi. |
RunHours |
The asset's starting run hour reading. | The supplied template includes decimal readings, for example 8145.3. |
Year |
The year associated with the asset. | The supplied template uses four-digit years, for example 2004. |
For how odometer and run hour readings are used and calculated, see Run Hours + Odometer in TG.
Validate and Create the Assets
Upload your completed CSV file.
Review validation results. Validation runs on upload: columns appear green when they pass and red, with a reason, when they fail.
Correct the reported errors before completing the import. Check unchanged column names, device type names and duplicate entries.
Once validation passes, save to create the assets.
Troubleshooting
The Device Type Is Not Accepted
Use the name provided by the template for your account. Do not rely on a device list copied from another organisation or use a BLE tag type in the asset import.
The File Fails Validation
Read the reason shown for each red validation result. Check that the headers have not been renamed, each value is in its intended column and the file has no unintended duplicate entries.
Next Steps
For individual asset setup and post-creation checks, see Creating Assets in Telematics Guru.
To change multiple existing assets rather than create new ones, use Asset Bulk Update.
