Migrate your Azuga Fleet data

Vehicles are the primary unit of Azuga's data model. The /vehicles endpoint in API v4 exposes vehicle ID, status, make, model, year, and assigned driver. We extract vehicle records 1:1; destination mapping is straightforward as most platforms use an equivalent asset or vehicle object.

Drivers are referenced by ID across trips, alerts, and score endpoints. Azuga API v4 exposes driver name, contact info, and license details. We migrate driver profiles directly; reassignment to vehicles at the destination requires a mapping step between Azuga driver IDs and destination user records.

Trip records include start/end timestamps, mileage, route geometry, and fuel consumption. API v4 provides paginated trip data; Azuga does not expose raw GPS point logs via standard endpoints. We extract trip summaries and map them to destination trip or activity objects, noting that granular point-level history may require a separate telemetry export.

Alert types include speeding, harsh braking, geofence violations, and engine fault codes. The /alerts endpoint in v4 returns structured events with severity, timestamp, vehicle ID, and driver ID. We migrate alert history 1:1, preserving type and severity fields at the destination.

Geofences are defined as named zones with polygon or circular boundaries and associated vehicle/driver rules. The /geofences endpoint exposes zone metadata and active/inactive status. We transfer geofence definitions as structured location data and note that polygon reprojection may be needed depending on the destination's geo format.

Azuga's Equipment Tracker object covers non-vehicle assets. The /equipment and /equipment/locations endpoints expose asset ID, status, last known location, and assignment. Equipment migrates as a standalone object in most destinations or as a custom asset record.

Fuel consumption and cost data are available via API v4 as part of vehicle telemetry. Azuga does not expose a dedicated fuel transaction object; fuel data is embedded in trip or vehicle summary records. We extract and normalize these values, mapping them to destination fuel or expense objects.

SafetyCam hardware generates event clips with metadata (timestamp, vehicle, trigger type, clip ID). Azuga API v4 exposes event metadata but not the actual video blob. We extract all event metadata via API and note that video files require a separate download workflow through the Azuga Fleet web interface.

Azuga calculates composite safety scores per driver based on events, speed, and braking patterns. The score API is available on higher tiers. We export score history and map it to destination custom fields or a dedicated driver performance object. Note that score algorithms differ between platforms, so percentile rankings may shift at the destination.

Azuga FleetMobile and some tiers include shift-based timecard tracking tied to vehicle usage. Timecard data is not exposed via the public API v4. We cannot automate timecard migration; if timecard history is required, we recommend exporting from the Azuga web dashboard manually and importing as a CSV at the destination.

Maintenance scheduling and alert data are available in Azuga Fleet. API v4 exposes maintenance alerts and vehicle health status. Full service history records, including completed work orders and costs, are typically managed in external systems and integrated via fuel card or maintenance partner data. We extract available maintenance alerts and map them to destination vehicle service records.

Azuga supports grouping vehicles and drivers into organizational subgroups. The groups API allows filtering and bulk operations on group members. We preserve group membership as a tag or custom property at the destination, mapping Azuga group names to equivalent folder, team, or tag structures.

As of October 2025, Azuga introduced a new Assets module accessible via Admin > Assets > Assets New with direct CSV export support. We can use this endpoint to extract asset records including location, status, and assignment metadata. The new module improves on prior ad-hoc asset handling.