Table of Contents
IMPORTANT: The best place to find information about Data Imports in Fleetio is the New Data Import Overview article. This resource includes step-by-step instructions, training videos, and guidance on how to prepare your import data file.
This guide provides an overview of the file requirements and supported values for importing Service Tasks.
Service Tasks Import Template
We recommend using the Service Tasks Import Template.
- Go to the + Quick Add menu and select Import Data.
- Click Browse Import Templates.
- Select the Service template type in the column on the left.
- Click the Download drop-down for Service Task, and select Empty 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
service_task_name is a required field; description is optional.
IMPORTANT: Unlike with NEW data imports, you do NOT need to include required fields if you are updating data, as long as you include the fleetio_id. During the mapping process, it is essential to map the fleetio_id column from the source file to the Id field in the Fleetio Field Mapping drop-down box. The Id field is what notifies Fleetio that the import is intended to "update" data, and not create NEW records. Reference the Update Existing Data via Import File article for more details.
Columns & Values
Required Fields
These fields are required for Service Task imports unless otherwise noted.
| Column | Required? | Notes |
|---|---|---|
| fleetio_id | * See Below |
This field is NOT required and should be left blank for all NEW vehicles being added. This field is ONLY required when updating existing vehicles in Fleetio.
|
| service_task_name | Yes | Each Service Task must have a unique name. |
* fleetio_id is required only when updating existing vehicles. It is NOT required when adding new vehicles.
Other Fields
These fields are not required but are recommended when possible to ensure the accuracy of your data in Fleetio.
| Column | Required? | Notes |
|---|---|---|
| description | No | |
| default_category_code | No | You must enter the # (digit) of the VMRS code and not the description. NOTE: Category codes only have one digit, whereas System, Assembly, and component codes use three. For example, 1 and not 001. |
| default_system_code | No | This sets the default System Code for the Service Task. System code must be the code number NOT the code description in the format of the following example: 001 and not "1". |
| default_assembly_code | No | This sets the default Assembly Code for the Service Task. System code must be the code number NOT the code description in the format of the following example: 001 and not "1". |
| default_component_code | No | This sets the default Component Code for the Service Task. System code must be the code number NOT the code description in the format of the following example: 001 and not "1". |
| default_reason_for_repair_code | No | This sets the default Reason for Repair Code for the Service Task. |
| expected_duration_in_hours | No | This sets the expected Labor Hours for the Service Task. This value must be a number greater than or equal to 0, such as "2.5" for 2 and 1/2 hours. |
| Field ONLY available via the Prefilled Template | ||
| update_historical_line_items | No | When TRUE, Fleetio will update historical line items with that Service Task used by applying the VMRS code defaults that have been updated via this import. If you would like the updated VMRS defaults to only take effect going forward, then leave this field blank or set this value to FALSE. |
Service Task Import Process
For detailed step-by-step instructions for importing new Service Task data, refer to the New Data Import Overview article.
Update Service Task Data via Import
For detailed step-by-step instructions for updating existing Service Task data, refer to the Update Existing Data via Import File article.
