Issues Import Guide

TIP: Please view our training video to learn more about Imports

New to importing data into Fleetio? Be sure to read the overview article first or watch our video on how to prepare your import data file.

This guide provides an overview of the of the file requirements and supported values for importing Issues in Fleetio.

IMPORTANT: All import files must be in the .csv format and meet .csv file standards. Go to http://csvlint.io/ to validate the .csv file if necessary.

If you have issues with Importing your data using a .csv file created by Excel, please try using Google Sheets or Apple's Numbers.  Excel can sometimes cause data issues when saving .csv files.

Issues Import File: Columns & Values

When importing meter data, Fleetio recommends using the Issues Import template found under Imports in the Settings area. 

NOTE: If using a custom template from another system, modifications to the file may be needed to ensure the data is in the proper format and can be matched up to data in Fleetio.


Column Required? Notes
vehicle_name Yes Nickname or number to distinguish vehicle in Fleetio. Must match Vehicle Name in Fleetio exactly. SEE:  Vehicle Naming Conventions
reported_at Yes Date when the Issue should be displayed as being reported. Must be in the Short Date Format specified for the account under Account Settings. Date format must be consistent throughout the file.
  • Example: 08/13/2015
  • Example: 13/08/2015
summary Yes  

A short subject/name for the Issue

description No

Provide additional details about the Issue

label_list No Useful for prioritizing and categorizing the type of work being done, or areas of the vehicle that are being services. SEE:  Using Labels

NOTE: Must match existing Labels exactly, or a new Label will be created.

  • Examples: Priority: Low, Paint, Battery, etc
meter_value No    
Most updated meter reading for a vehicle (no commas)
  • Example: 150000
meter_void No Marking a meter entry as void allows you to save an invalid meter value but tells Fleetio to ignore it for events that depend on meter values (i.e. Service Reminders)
  • true = marks meter as "voided"
secondary_meter_value No    
Most updated secondary meter reading for a vehicle (no commas)    
  • Example: 147550
secondary_meter_void No Marking a meter entry as void allows you to save an invalid meter value but tells Fleetio to ignore it for events that depend on meter values (i.e. Service Reminders)
  • true = marks meter as "voided"
due_date No    
Date when the Issue should be considered overdue. Must be in the Short Date Format specified for the account under Account Settings. Date format must be consistent throughout the file. 
  • Example: 08/13/2015
  • Example: 13/08/2015
due_meter_value No Meter value when the Issue should be considered overdue.
due_secondary_meter_value No    
Secondary meter value when the Issue should be considered overdue.
*Custom Fields No Any  Custom Fields setup with the "Issues" record type are available for importing data into.

Still need help? Contact Us Contact Us