Migrate from Azuga Fleet to HubSpot

Azuga driver records resolve to HubSpot contacts by email match. first_name + last_name map to firstname + lastname, phone to phone, email to email. The Azuga driver_id is stored as Source_Driver_ID__c for traceability and delta-run de-duplication. Drivers without a HubSpot-matching email are imported as new contact records.

HubSpot contacts do not include a native license_number property, so we add three custom fields: Driver_License_Number__c as a text field, Driver_License_State__c as a picklist of US state abbreviations, and Driver_License_Expiry__c as a date field. These preserve the license number, issuing state, and expiration date from each Azuga driver record, enabling compliance reporting directly within HubSpot.

HubSpot lacks a built‑in driver‑scoring attribute, so we create a custom Number field called Driver_Score__c on the contact to store Azuga’s integer score. We also map Azuga’s risk_tier to a custom picklist field Risk_Tier__c with options Low, Medium, High, and Critical. These fields give you a performance baseline and risk classification for each driver directly in HubSpot, supporting targeted outreach and safety‑focused workflows.

Azuga's reward_points credit balance has no HubSpot equivalent. We preserve the value as Reward_Points__c (Number) on the contact as a snapshot reference. The full rewards program (points, badges, leaderboards) requires rebuild in HubSpot workflows and is flagged for manual reconstruction.

HubSpot has no native vehicle object. We create a Fleet_Vehicle__c custom object to hold vin, license_plate, year, make, model, trim, fuel_type, current_odometer, and trip_tags. The Azuga vehicleId is stored as Source_Vehicle_ID__c. This custom object is linked to driver contacts via a Fleet_Vehicle_Assignment__c junction.

Azuga stores categorical route labels on each vehicle as trip_tags, indicating whether a truck runs long‑haul, short‑haul, local, or specialty routes. We map these to a multi‑select picklist Trip_Tags__c on the Fleet_Vehicle__c custom object, enabling you to filter and segment vehicles by route type in HubSpot reports and workflows. Multi‑select picklists are natively supported on HubSpot Enterprise; lower tiers use a text field or separate boolean flags.

Azuga trip records contain start/end timestamps, distance, duration, fuel_used, average_speed, max_speed, idle_time, hard_brake_count, and route summary data. HubSpot's contact timeline holds recent activity only — trip history requires a Fleet_Trip__c custom object with foreign keys to the driver Contact and Fleet_Vehicle__c record.

Azuga geofences store name, type (circle or polygon), center coordinates (lat/lng), radius_meters, and associated address. HubSpot has no native geofence or spatial object. We create a Geofence__c custom object with latitude, longitude, radius, geofence_type, and address fields, linked to the relevant vehicle or driver contact.

Azuga alerts (speeding, hard_brake, geofence_violation, harsh_acceleration, panic_alert) include type, timestamp, speed, GPS coordinates, severity, and resolved status. HubSpot activities (calls, emails, meetings) attach to contacts but don't store GPS coordinates. We create Safety_Alert__c with type, timestamp, speed, latitude, longitude, severity, and status, linked to driver contact and vehicle record.

Azuga captures maintenance details such as work_order_number, type, description, scheduled_date, completed_date, cost, and vendor for each vehicle event. HubSpot does not have a built‑in maintenance object, so we define a Maintenance_Record__c custom object with corresponding properties and link it to the Fleet_Vehicle__c record via a lookup relationship. This allows maintenance history, cost, and scheduling information to appear on the vehicle profile in HubSpot for reporting and workflow follow‑up.

Azuga assigns drivers to vehicles natively in its schema. HubSpot has no built-in driver-vehicle association object. We create a Fleet_Vehicle_Assignment__c custom object with driver (Contact lookup) and vehicle (Fleet_Vehicle__c lookup) fields plus assignment start/end dates, supporting one active driver per vehicle at a time with a full assignment history.

Azuga equipment records track non-vehicle assets with name, serial_number, type, and current location. HubSpot's native Asset object (available with Operations Hub) can hold serial_number, name, and custom properties. Equipment type maps to Asset_Type__c and current location is preserved as Location__c text. Active HubSpot subscription required for the Asset object.