Migrate from Azuga Fleet to Zoho CRM

Azuga vehicles map to Zoho Accounts using the vehicle name or VIN as Account Name. If the fleet operates equipment alongside vehicles, we recommend a custom Fleet_Assets__c module with a Vehicle_Type__c picklist to distinguish service trucks from pool cars. VIN and license plate become custom fields on the Account record.

Azuga drivers map to Zoho Contacts. Driver name splits into First Name and Last Name. The Azuga DriverID becomes Source_System_ID__c for traceability. Assigned vehicle links via Contact.AccountId lookup. License number and expiry migrate as custom fields on the Contact record.

Azuga trip logs have rich embedded data: start/end GPS coordinates, distance, duration, fuel consumed, average speed, max speed. Zoho Tasks have Subject, Status, and Due Date but not the payload depth. We recommend a custom Trip_Log__c module with fields for Start_Lat__c, Start_Long__c, End_Lat__c, End_Long__c, Distance_Miles__c, Fuel_Used_Gallons__c, and Max_Speed__c. Subject line carries trip date and vehicle name.

Azuga speeding, harsh braking, geofence exit, and maintenance alerts map to Zoho Tasks with Type='Alert' and Category='Fleet'. Alert timestamp becomes Task Due Date. Description carries the full alert message. Vehicle and driver linked via AccountId and WhoId on the Task. Severity maps to Priority ('High' for critical, 'Normal' for warning).

Azuga fuel entries contain date, gallons, cost, odometer, station, and location. Zoho subforms on Accounts support date, number, and currency fields — ideal for per-fill records. We create a Fuel_Subform subform on the Account module with Date, Gallons, Cost_Per_Gallon__c, Total_Cost__c, Odometer__c, and Station__c fields. Each subform row links to the vehicle Account automatically.

Azuga maintenance entries (oil change, tire rotation, inspection, repair) map to Zoho Tasks with Type='Maintenance' linked to the vehicle Account. Description carries service details. Cost migrates as a custom currency field. Vendor name and invoice number become text fields on the record. Status ('Scheduled', 'Completed', 'Cancelled') maps directly to Task Status.

Azuga geofences store name, type (circle/polygon), center coordinates, and radius. Zoho CRM has no native geofence object. We create a custom Geofence__c module with Latitude__c, Longitude__c, Radius_Meters__c, Geofence_Type__c picklist, and Associated_Vehicles__c multi-select. Zoho workflows can trigger on Location updates against these coordinates using Deluge functions.

Azuga assigns a composite driver score plus breakdowns: violations, harsh braking count, speeding events, harsh cornering. We create Score__c (number), Violations__c (number), Harsh_Braking__c (number), Speeding_Events__c (number), and Last_Score_Date__c (date) on the Contact record. Score history from Azuga's DriverScoreHistory endpoint migrates as a related custom object if multiple historical records exist.

Azuga SafetyCam events store event type (collision, distracted driving, speeding), video clip URL, thumbnail URL, timestamp, vehicle speed, and location. Zoho has no native dashcam event object. We create a Safety_Event__c custom module with Event_Type__c picklist, Video_URL__c (URL field), Thumbnail_URL__c (URL field), Speed__c, Latitude__c, Longitude__c, and a ContactId lookup back to the driver record. Video files themselves stay hosted at Azuga; URL fields maintain the reference.

Azuga equipment tracked via Equipment API — serial number, type, status, assigned vehicle — maps to Zoho Products if equipment is billable or stockable. If equipment is non-inventory (attached tools, trailers), a custom Equipment__c module with Serial_Number__c, Type__c, Status__c, and Assigned_Vehicle__c lookup serves better.

Azuga's Social Telematics reward platform tracks points earned, rewards redeemed, and leaderboard position. Zoho CRM has no native gamification engine. We preserve reward balance and redemption history as custom fields on the Contact (Driver) record. Rebuiliding reward logic requires Zoho Blueprint + custom Deluge functions, documented in the export-for-rebuild file.