Migrate from Azuga Fleet to Twenty CRM

Azuga Driver records map directly to Twenty People. Each driver becomes a Person record with name, email, phone, and job title fields populated from Azuga driver profile data. Driver license number, state, and expiration date migrate as custom fields on the People record.

Azuga Vehicle records map to Twenty Companies as a base mapping. If your team needs to track vehicle-specific telemetry (VIN, make, model, odometer, diagnostic codes), we create a custom Vehicle object in Twenty and map Azuga vehicles there instead, linking each to the driver-assigned People record via a relation field.

Azuga trip records — including start/end timestamps, mileage, route, and driver assignment — migrate as Twenty Tasks linked to the corresponding People record. Trip status (completed, in-progress) maps to Task status values in Twenty. Additional trip metadata such as idle time, average speed, and fuel consumption migrate as custom fields on the Task so historical trip performance remains queryable post-migration.

Azuga safety alerts (speeding, hard braking, geofence violations) migrate as Twenty Tasks with the alert type as Task subject and the alert details in the task body. Owner is assigned to the driver or fleet administrator who owned the alert in Azuga.

Azuga maintenance records (service type, date, cost, odometer at service) migrate as Twenty Notes attached to the corresponding Vehicle Company record. Service receipts and work order numbers are stored in the Note body or as attachments. Each maintenance Note links to the People record of the driver assigned to that vehicle at the time of service, preserving accountability context for service history reviews.

Azuga equipment tracker records require a custom Equipment object in Twenty, since neither Twenty's standard objects nor Companies natively represent non-vehicle assets. We create the object with fields for equipment name, type, serial number, and assigned vehicle link. The custom object supports Twenty's workflow builder, so your team can automate service alerts, link equipment to maintenance Notes, and generate utilization reports without relying on Azuga's telematics stack.

Azuga's driver safety score (a composite of speeding events, hard braking, distracted driving) has no native equivalent in Twenty. We migrate it as a custom Number field on the People record called Driver_Safety_Score__c so managers can still sort and filter by driver performance.

Azuga geofence definitions (name, polygon coordinates, entry/exit rules) cannot map to any standard Twenty object. We store geofence configuration as a custom field on the relevant Company or Vehicle record for reference — your team rebuilds the active geofence logic in Twenty's workflow builder post-migration.

Azuga's driver-to-vehicle assignment is a foreign-key relationship. We preserve this as a People-to-Vehicle (Company) relation in Twenty. Multiple drivers per vehicle in Azuga map to multiple People records all linked to the same Vehicle Company. If a driver in Azuga has a primary vehicle plus occasional access to pool vehicles, each assignment appears as a separate relation record in Twenty, maintaining the full assignment history.

Azuga fuel card transaction records (date, volume, cost, odometer) migrate as Notes attached to the corresponding Vehicle Company record. Transaction totals and odometer readings at fill-up are preserved in the Note body for reporting continuity. We also map fuel type and payment method to custom fields on the Note so your team can build cost-per-mile and fuel-efficiency reports directly in Twenty without Azuga's reporting interface.

Azuga administrator accounts map to Twenty Workspace Members by email match. FlitStack resolves owner assignments during migration so tasks and notes inherit the correct Twenty user rather than landing as unassigned. If an Azuga admin email has no corresponding Twenty Workspace Member, FlitStack flags the record for your team to assign manually or create the missing user account before the final import phase.