This article explains how you can import and export data from our platform.
For importing data, either use an Excel sheet or CSV file. If you use CSV, make sure your first row contains the column names. This will be used for mapping them later on.
imei;sim;msisdn
350317170431234;8931440302043841234;31629661234
...Note: Editing a CSV file in Excel is not recommended, as it can change the formatting of data. This may cause issues for mapping the data correctly.
The following entities are available for:
| Entity | Export | Import |
| Devices | Yes | Yes |
| Assets | Yes | Yes |
| Drivers | Yes | Yes |
| Geofences | Yes | Yes |
| Trailers | Yes | Yes |
| Fuel | No | Yes |
| Maintenance (v1) | No | Yes |
| Maintenance Work orders (v2) | No | Yes |
| Sims | No | Yes (update only) |
| Odometer | No | Yes |
| Users | Yes | Yes |
For each entity, the fields below are available. When an import will be performed and you don’t want to import data for a certain field, please leave it empty in your Excel/CSV file.
Asset
| Field | Importable | Notes |
| Id | Yes | Unique ID used to match with existing entity. When left blank a new entity will be created. |
| DeviceId | Yes | |
| AssignmentStart | Yes | |
| AssignmentEnd | Yes | |
| Name | Yes | |
| Code | Yes | |
| Color | Yes | |
| PlateNumber | Yes | |
| VIN | Yes | |
| Year | Yes | |
| AssetTypeId | Yes | Database ID |
| Brand | Yes | |
| Model | Yes | |
| VehicleType | Yes | Database ID |
| Icon | Yes | Integer value indicating the type of icon |
| Comment | Yes | |
| Hierarchy groups | Yes | A lookup will be performed so the name entered should exist in your account. When assigning an asset to multiple hierarchy groups, separate the groups with commas in your file. Example: HierarchyGroup1, HierarchyGroup2, etc… Only if feature flag is enabled. |
| … | … | Remaining fields documentation skipped |
Device
| Field | Importable | Notes |
| Id | Yes | Unique ID used to match with existing entity. When left blank a new entity will be created. |
| DeviceTypeId | Yes | Database ID |
| Name | Yes | Can be ignored, not visible in UI |
| UnitId | No | Import not implemented |
| Imsi | No | Import not implemented, for future use |
| Msisdn | No | Import not implemented, for future use |
Geofence
| Field | Importable | Notes |
| Id | Yes | Unique ID used to match with existing entity. When left blank a new entity will be created. |
| UserId | Yes | Database ID |
| Name | Yes | |
| Color | Yes | RGB Hex code |
| GeoJson | Yes | |
| Kml | Yes | Alternative for GeoJson. Either GeoJson or KML needs to be mapped. Continue reading below for more information about importing KML. |
| ReferenceId | Yes | Free text field |
| Hierarchy Groups | Yes | A lookup will be performed so the name entered should exist in your account. When assigning a geofence to multiple hierarchy groups, separate the groups with commas in your file. Example: HierarchyGroup1, HierarchyGroup2, etc… Only if feature flag is enabled. |
Importing KML
When importing KML data, there are a few things to keep in mind for the import to go smoothly:
- For a correct import, it is recommended to use a CSV file. Make sure all of the KML data is between quotes.
- KML data usually contains multiple geofences. This is supported by our import system. There is no need to put each geofence in its own row in your CSV file.
- Unlike the option to import KML data using the FleetManagement API, you should not escape your KML string. Please keep the structure as it is.
Example CSV:
Name,Color,Kml
Example Geofence,#0000FF,"<kml>
<Document>
Your geofences...
</Document>
</kml>"Drivers
| Field | Importable | Notes |
| Id | Yes | Unique ID used to match with existing entity. When left blank a new entity will be created. |
| FirstName | Yes | Database ID |
| LastName | Yes | |
| DateOfBirth | Yes | Formatted as YYYY-MM-DD |
| Tag | Yes | |
| Hierarchy Groups | Yes | A lookup will be performed so the name entered should exist in your account. When assigning a driver to multiple hierarchy groups, separate the groups with commas in your file. Example: HierarchyGroup1, HierarchyGroup2, etc… Only if feature flag is enabled. |
| … | … | Remaining fields documentation skipped |
Maintenance (v1)
| Field | Importable | Notes |
| Asset Identifier | Yes | Asset ID used to match with existing entity |
| MaintenanceTypeId | ||
| Occurrence Date | Formatted as YYYY-MM-DD | |
| Description | ||
| Cost | ||
| Reference (Optional) | ||
| Supplier Name (Optional) | ||
| Date of calibration (Optional) | Yes | Formatted as YYYY-MM-DD HH:mm |
| Odo (Optional) | Yes | In kilometers |
Maintenance Work orders (v2)
| Field | Importable | Notes |
| Reference ID | Yes | Assign a unique ID to the work order and the related items to ensure they are properly grouped |
| Description | Yes | |
| Asset | Yes | Use the name, code or plate number of the asset |
| Odo | Yes | |
| Engine hours | Yes | |
| Service date start | Yes | Formatted as YYYY-MM-DD |
| Service date end | Yes | Formatted as YYYY-MM-DD |
| Completed | Yes | Possible values: – True – False |
| Service Item | Yes | A lookup will be performed so the name entered should exist in your account. |
| Item description | Yes | |
| … | … | Remaining fields documentation skipped |
Odometer
| Field | Importable | Notes |
| Asset Identifier | Yes | Asset ID used to match with existing entity |
| Date of calibration | Yes | Formatted as YYYY-MM-DD HH:mm |
| Odo | Yes | In kilometers |
Users
| Field | Importable | Notes |
| User ID | Yes | Unique ID used to match with existing entity. When left blank a new entity will be created. |
| Username / Email | Yes | |
| Firstname | Yes | |
| Lastname | ||
| Language | Yes | Formatted in locale code (i.e. en-US, ar-AE or nl-NL) |
| Timezone | Yes | Formatted in IANA (i.e. Asia/Dubai or Europe/Amsterdam) |
| Whitelabel | Yes | A lookup will be performed so the name entered should exist in your account. |
| User Role | Yes | A lookup will be performed so the name entered should exist in your account. |
| Asset display name | Yes | Possible values: – Asset Code – Client Handle: Asset Code – Asset plate number – Client Handle: Asset plate Number – Asset Name – Client Handle: Asset Name |
| Distance Unit | Yes | Possible values: – Km – Miles |
| Volume Unit | Yes | Possible values: – Liter – Imperial Gallon – US Liquid Gallon |
| Hierarchy groups | Yes | A lookup will be performed so the name entered should exist in your account. When assigning a user to multiple hierarchy groups, separate the groups with commas in your file. Example: HierarchyGroup1, HierarchyGroup2, etc… Only if feature flag is enabled. |