Migrate from Azuga Fleet to HighLevel

Azuga vehicles have no direct HighLevel equivalent. FlitStack creates a Vehicle_Record__c custom object in HighLevel with fields for VIN, license plate, make, model, and year. The assigned driver becomes a Contact lookup on the vehicle record. Vehicle odometer, fuel, and last-service data map as custom fields on the vehicle object.

Azuga driver records map directly to HighLevel Contacts when an email address is present. The driver's Azuga safety score, total trips, and lifetime miles driven become custom numeric fields on the contact. Driver name and contact info (phone, email) transfer as standard contact fields. Drivers without email become Companies in HighLevel with a Driver_NoEmail__c flag.

Azuga fleet accounts (the business entity that owns the vehicles) map to HighLevel Companies. Company name, address, and industry classification transfer directly. If multiple vehicles belong to one Azuga company, HighLevel creates one Company record with all assigned vehicles linked via the Vehicle_Record__c object.

Azuga trips contain start/end coordinates, distance, duration, route geometry, and fuel consumed. Because HighLevel has no trip or route object, FlitStack creates a Note on the driver Contact with trip summary fields: distance_miles, duration_minutes, start_location, end_location, and trip_date. Full route geometry is exported as a JSON attachment for reference.

Azuga alert records map to HighLevel Tasks attached to the relevant driver or vehicle Contact with a structured Type pick-list capturing the specific alert category: Speeding, Harsh_Braking, Geofence_Violation, or Maintenance_Required. The priority field maps directly from Azuga severity levels where Low translates to Normal, Medium maps to High, and High severity events become Urgent priority. The task description captures the full alert context including event type, precise timestamp, detected speed or location details, and any associated vehicle or driver identifiers from Azuga's event payload.

Azuga geofences define circular or polygon zones with addresses and radius. HighLevel has no native geofence or spatial object. FlitStack exports geofences as a structured JSON field (Geofence_List__c) on the vehicle record — name, address, radius_meters, and type (circle/polygon) — for manual recreation in any mapping tool.

Azuga's driver safety score (0–100 scale) and gamification tiers (Bronze, Silver, Gold, Platinum) have no HighLevel equivalent. FlitStack creates Driver_Safety_Score__c (Number) and Reward_Tier__c (Picklist) on the Contact object. Score history across multiple time periods is stored as separate numeric fields.

Azuga fuel records contain gallons/liters consumed, cost, odometer at fill-up, and fuel type. HighLevel has no native fuel field. FlitStack aggregates fuel data per vehicle into a Fuel_Summary__c text area field with total gallons, total cost, and average MPG — a snapshot for reporting rather than a transactional fuel ledger.

Azuga maintenance records (service type, date, cost, odometer) become Notes attached to the vehicle contact record. The most recent service date also populates Last_Service_Date__c as a custom Date field on the vehicle record for filtering and workflow triggers in HighLevel.

Azuga stores inspection forms, DVIRs, insurance documents, and driver photos. These are re-uploaded to HighLevel's Files section and linked to the corresponding Contact or Vehicle_Record__c object. File size limits of the destination apply — documents over 25MB are flagged for chunking.