Export-Import

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:

EntityExportImport
DevicesYesYes
AssetsYesYes
DriversYesYes
GeofencesYesYes
TrailersYesYes
FuelNoYes
Maintenance (v1)NoYes
Maintenance Work orders (v2)NoYes
SimsNoYes (update only)
OdometerNoYes
UsersYesYes
Available entities

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
FieldImportableNotes
IdYesUnique ID used to match with existing entity. When left blank a new entity will be created.
DeviceIdYes
AssignmentStartYes
AssignmentEndYes
NameYes
CodeYes
ColorYes
PlateNumberYes
VINYes
YearYes
AssetTypeIdYesDatabase ID
BrandYes
ModelYes
VehicleTypeYesDatabase ID
IconYesInteger value indicating the type of icon
CommentYes
Hierarchy groupsYesA 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
Available fields for ‘Asset’
Device
FieldImportableNotes
IdYesUnique ID used to match with existing entity. When left blank a new entity will be created.
DeviceTypeIdYesDatabase ID
NameYesCan be ignored, not visible in UI
UnitIdNoImport not implemented
ImsiNoImport not implemented, for future use
MsisdnNoImport not implemented, for future use
Available fields for ‘Device’
Geofence
FieldImportableNotes
IdYesUnique ID used to match with existing entity. When left blank a new entity will be created.
UserIdYesDatabase ID
NameYes
ColorYesRGB Hex code
GeoJsonYes
KmlYesAlternative for GeoJson. Either GeoJson or KML needs to be mapped. Continue reading below for more information about importing KML.
ReferenceIdYesFree text field
Hierarchy GroupsYesA 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.
Available fields for ‘Geofence’
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
FieldImportableNotes
IdYesUnique ID used to match with existing entity. When left blank a new entity will be created.
FirstNameYesDatabase ID
LastNameYes
DateOfBirthYesFormatted as YYYY-MM-DD
TagYes
Hierarchy GroupsYesA 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
Available fields for ‘Drivers’
Maintenance (v1)
FieldImportableNotes
Asset IdentifierYesAsset ID used to match with existing entity
MaintenanceTypeId
Occurrence DateFormatted as YYYY-MM-DD
Description 
Cost 
Reference (Optional)
Supplier Name (Optional)
Date of calibration (Optional)YesFormatted as YYYY-MM-DD HH:mm
Odo (Optional)YesIn kilometers
Available fields for ‘Maintenance’
Maintenance Work orders (v2)
FieldImportableNotes
Reference IDYesAssign a unique ID to the work order and the related items to ensure they are properly grouped
DescriptionYes
AssetYesUse the name, code or plate number of the asset
OdoYes
Engine hoursYes
Service date startYesFormatted as YYYY-MM-DD
Service date endYesFormatted as YYYY-MM-DD
CompletedYesPossible values:
– True
– False
Service ItemYesA lookup will be performed so the name entered should exist in your account.
Item descriptionYes
Remaining fields documentation skipped
Available fields for ‘Work orders’
Odometer
FieldImportableNotes
Asset Identifier YesAsset ID used to match with existing entity
Date of calibrationYesFormatted as YYYY-MM-DD HH:mm
Odo YesIn kilometers
Available fields for ‘Odometer’
Users
FieldImportableNotes
User IDYesUnique ID used to match with existing entity. When left blank a new entity will be created.
Username / EmailYes
FirstnameYes
Lastname
LanguageYesFormatted in locale code (i.e. en-US, ar-AE or nl-NL)
TimezoneYesFormatted in IANA (i.e. Asia/Dubai or Europe/Amsterdam)
WhitelabelYesA lookup will be performed so the name entered should exist in your account.
User RoleYesA lookup will be performed so the name entered should exist in your account.
Asset display nameYesPossible values:
– Asset Code
– Client Handle: Asset Code
– Asset plate number
– Client Handle: Asset plate Number
– Asset Name
– Client Handle: Asset Name
Distance UnitYesPossible values:
– Km
– Miles
Volume UnitYesPossible values:
– Liter
– Imperial Gallon
– US Liquid Gallon
Hierarchy groupsYesA 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.
Available fields for ‘Users’
Updated on May 6, 2025

Related Articles

Leave a Comment