Service Reminders 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 service reminders 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.

Service Reminder Import File: Columns & Values

Fleetio recommends using the Service Reminder Import template found under Settings > Imports when importing service reminder data.

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.

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

Column Required? Notes
id (do not edit) Yes This is the internal ID of the Service Reminder. DO NOT modify this value.
vehicle_name Yes

Nickname or number to distinguish vehicle in Fleetio. Must match Vehicle Name in Fleetio exactly. SEE:  Vehicle Naming Conventions

service_task Yes Must match an existing  Service Task exactly. If an exact match is not found during the import, a new Service Task will be created through the import.  
  • Example: A/C Diagnosis
  • Example: Oil & Filter Change
meter_interval Yes*    
The meter frequency for the service reminder; (no commas or text)
*A value is required in either the meter_interval field or time_interval field
  • Example: 51256
time_interval Yes* The time frequency for the service reminder (numerical value only)
*A value is required in either the meter_interval field or time_interval field (or both if preferred). If using the time_interval field you must also specify the time_frequency below.
  • Example: 24
time_frequency Yes* Specify if the time_interval value from above is in days, weeks, months or years.
*This field is required only if the time_interval field is being used
  • Example: days, weeks, months, years
next_due_meter_value No    
Does the starting meter need to be set for the reminder schedule?
  • If yes, enter the next meter for when this service reminder is due
  • Example: 62424 (no commas)
next_due_at No Does the next due date need to be set for the reminder schedule? 
  • If yes, enter the next date for when this service reminder is due
  • Must be in the Short Date Format specified for the account under Settings > Account Settings.
  • Example: 07/15/2014
due_soon_meter_threshold No    
The number of miles/kms/hours in advance you would like the system to consider the reminder to become "due soon".   
*Service Reminders are sent based on this threshold setting.
due_soon_time_threshold_interval No The amount of time in advance you would like the system to consider the reminder to become "due soon". Must also specify the due_soon_time_threshold_frequency as well.
*Service Reminders are sent based on this threshold setting.
due_soon_time_threshold_frequency No    
Specify if the due_soom_time_threshold_interval value from above is in days, weeks, months or years.
*This field is required only if the time_interval field is being used
  • Example: days, weeks, months, years
secondary_meter No If this Service Reminder is for the Secondary Meter, the value is TRUE.
If this Service Reminder is for the Primary Meter, the value is FALSE.
If no value is set, the Service Reminder will default to the Primary Meter (or FALSE). 

Still need help? Contact Us Contact Us