📥 Exporting Your Data (CSV, JSON, .adarchive)

The Export Data page (under Account → Data Management) lets you download a copy of your AutoDrive data. Exports run entirely in the browser — nothing is queued or stored server-side.

Pick what to export

Multi-select drivers, vehicles, drives, fuel logs, charging logs, AutoCare vendors, AutoCare service visits (with line items embedded inline), Glovebox documents, and LiveDrive geofence zones. The buttons under the grid select all or clear in one click. The same group / driver-mode scoping that applies on every other page applies here, so a driver-role member only sees their own rows. LiveDrive zones require the LiveDrive add-on + owner/admin role; on accounts without those, the zones entity simply exports as empty rather than failing the whole export.

Pick a format

• AutoDrive Archive (.adarchive) — a single JSON-based file that round-trips into another AutoDrive account through the Import page. UUIDs are preserved, so the same archive can be re-imported safely. Cross-references between entities (a service visit's vehicle_uuid and vendor_uuid, for instance) survive the round-trip because vehicles and vendors import before visits.
• CSV — one CSV per selected entity. Pick a single entity and you get a .csv; pick more than one and AutoDrive bundles them into a single .zip with one CSV per entity. Useful for spreadsheet work or sharing with a CPA. Service-visit records are emitted as a JSON array in the records cell; LiveDrive polygon zones store the polygon as JSON in polygon_geojson.
• JSON — raw API response shape keyed by entity. Best for scripting and ad-hoc analysis.

Migrating between AutoDrive accounts

Export as .adarchive on the source account, then on the destination account go to Account → Data Management → Import Data, pick the AutoDrive Archive card, and drop the file. You'll get a per-entity checklist with row counts before anything is written. AutoCare, Glovebox, and LiveDrive rows ride along automatically alongside the legacy entities.

Build & save confirmations

Once your data finishes loading, AutoDrive builds the file in the browser and shows a Build success prompt with a row / entity count and the exact filename(s) about to be saved — click Download to send them to your computer or Cancel to bail out without saving anything. After the download fires, a second prompt confirms the file landed in your Downloads folder. Inside the AutoDrive Online macOS app the second prompt is a native dialog with a Reveal in Finder button.

File names

Exports are named autodrive_YYYYMMDD_<group>.adarchive (or .json / .csv), where <group> is the snake-case version of your active account group's name. Switching groups before exporting changes the filename so you can tell archives from different groups apart at a glance. CSV exports add the entity name (e.g. autodrive_20260427_my_fleet_service_visits.csv).