AutoDriveAutoDrive Launch AutoDrive Online
Help Center Getting Started Importing Drivers, Vehicles, Drives, Fuel, and Charging
🚀 Getting Started

📤 Importing Drivers, Vehicles, Drives, Fuel, and Charging

Bring existing data in from a CSV or TXT file. Account → Import Data.

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)

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 5 and your file has 20 rows, the first 4 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, and drive 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 if you have it. If you leave both blank, the log imports without a vehicle assigned — you can fix that after.

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, and charging can resolve their vehicle/driver references. UUIDs are preserved, so re-importing the same archive over an existing dataset is safe (rows already on file are deduped).

Was this article helpful?

Yes, helpful Not helpful

Still need help?

Our support team is here to assist you.

Contact Support