Issues Import Guide

IMPORTANT: The best place to find information about Data Imports in Fleetio is the Data Import Overview article. This resource includes step-by-step instructions, training videos and guidance for how to prepare your import data file.

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

Issues Import Template

We recommend using the Issues Import Template.

Go to your Company drop-down menu and choose Import Data then click Import Templates > Issue Template

NOTE: If you are using a spreadsheet generated from another system, modifications to the file type and data may be needed to ensure proper format and data mapping.

Data Requirements

Columns not marked as Required may be left as blank cells in the import file and skipped during the mapping process.

Columns & Values

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 in 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 vehicle areas being serviced. Must match existing Labels exactly, or a NEW Label will be created.
SEE: Using Labels
  • 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 Reading 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 Reading 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 in 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.

Issues Custom Fields

Custom Fields can be created for Issue records in your Account Settings. Any Custom Fields with the Issue record type will also be available for import.

TIP: Learn more in the Custom Fields article.

Issues Import Process

For detailed step-by-step instructions, refer to the Data Import Overview article.

Still need help? Contact Us Contact Us