📤 Importing Drivers, Vehicles, Drives, Fuel, Charging, AutoCare, and LiveDrive Zones

If you're coming from another mileage tracker or a spreadsheet you've been keeping by hand, AutoDrive can import the lot. Go to Account → Import Data in the online app.

What you can import

• Drivers (name, email, taxpayer / IRS fields)
• Vehicles (nickname, VIN, year/make/model, fuel type, mileage)
• Drives / trips (start time, distance, addresses, vehicle + driver links)
• Fuel logs (date, gallons, cost, vehicle)
• Charging logs (date, kWh, cost, vehicle)
• AutoCare vendors (shop name, address, contact info, default labor rate)
• AutoCare service visits (vehicle, date, vendor, odometer, line-item records, receipt URL)
• LiveDrive geofence zones (name, kind, circle center/radius or polygon GeoJSON, alert triggers)

File format

CSV or TXT. The importer auto-detects commas, tabs, pipes, and semicolons, so most exports from Excel / Google Sheets / other trackers work without reformatting. The first row must be a header with column names that match the fields shown on each entity's card.

Download a template

Pick the entity you're importing, then click Download template. You get a tiny CSV with the right header row + one sample row — fill it in with your data and import it back.

Preview before anything is saved

Every import is a two-step flow. Upload the file, review the parsed preview table, and only then click Import. If a required column is missing, the preview warns you. If a row fails validation server-side, it's listed individually in the result summary; the other rows still go through.

Account-group caps still apply

Importing uses the same rules as creating one row at a time. If your plan caps vehicles at 2 and your file has 20 rows, the first 2 land and the rest get rejected with cap_reached. Upgrade your plan (or use the Subscription page to buy vehicle add-ons) first if you're expecting to go past the cap.

Vehicle and driver references

For fuel, charging, drive, and service-visit rows, you'll want to reference the related vehicle. The preferred way is a vehicle_uuid column (the 36-character UUID from the vehicle row). A numeric vehicle_id also works for fuel / charging / drives if you have it. If you leave both blank on a fuel / charging / drive row, the log imports without a vehicle assigned — you can fix that after. Service visits require vehicle_uuid and will reject rows where it's missing or doesn't resolve to a vehicle in the active group.

AutoCare records column

Service visits use a records column that holds the line items as a JSON array, e.g. [{"custom_type_label":"Oil change","cost_cents":8995,"is_tax_deductible":true}]. Each record needs either a service_type_uuid (matched against the AutoCare catalog) or a custom_type_label. Wrap the cell in double quotes so embedded commas and brackets survive the CSV parser. The downloadable template shows the shape.

LiveDrive zones need the add-on

Importing geofence zones requires an active LiveDrive add-on on the active account group and an owner / admin role. Rows imported from an archive on a free-tier account will be rejected with a 402 error; the rest of the archive still imports. Polygon zones carry the boundary in polygon_geojson (a GeoJSON Polygon object); circle zones carry center_lat, center_lng, and radius_m.

Importing an AutoDrive Archive (.adarchive)

If you exported a .adarchive file from another AutoDrive account, pick the AutoDrive Archive card on the Import page and drop the file. You'll see a checklist of every entity in the archive with row counts — check the ones you want to bring over and click Import. Drivers and vehicles import first so drives, fuel, charging, and service visits can resolve their vehicle/driver references; AutoCare vendors import before visits so vendor_uuid resolves; LiveDrive zones import last so unrelated entities still land if the LiveDrive entitlement check fails. UUIDs are preserved, so re-importing the same archive over an existing dataset is safe (rows already on file are deduped).