Migrate from Azuga Fleet to Odoo CRM

Azuga drivers map to Odoo res.partner contacts. Each driver's name, email, phone, license number, and driver_score migrate as standard fields plus custom fields. Multiple drivers per vehicle (common in commercial fleets) require res.partner records with a Many2many link back to the fleet.vehicle record.

Azuga vehicles map directly to Odoo fleet.vehicle using license plate as the unique key. The odometer reading, vehicle make/model/year, and VIN migrate as standard fleet.vehicle fields. Current location (latitude/longitude) is stored as a custom char field since Odoo's default location field is text-based.

Azuga's driver_score is computed per driver per trip. We map the most-recent composite score to a custom float field on fleet.vehicle for quick dashboard visibility. Historical score progression is preserved as a JSON blob in a LongText custom field Score_History__c for compliance and trend reporting.

Azuga trips (start/end GPS points, distance, fuel consumed, idle time) are not native CRM activities. We map each trip as an Odoo crm.lead activity record with a custom Trip_Distance__c and Fuel_Used__c field, linked to the relevant fleet.vehicle. Long-trip vs short-trip classification is preserved as a stage name on the activity.

Azuga alerts map to Odoo CRM activities with Type='Alert' and a custom Alert_Type__c picklist (speeding, hard_braking, geofence_entry, geofence_exit). Original alert timestamp and GPS coordinates are stored as custom datetime and char fields. Each alert activity is linked to the fleet.vehicle record so fleet managers see the full alert history on the vehicle form.

Azuga geofences are geographic boundaries attached to vehicles. We create a custom geofence JSON field on fleet.vehicle storing name, polygon coordinates, and radius. Geofence entry/exit events migrate as Odoo CRM activities with type='geofence' so managers can filter and report on location events alongside other alerts.

Azuga equipment trackers (non-vehicle assets) map to Odoo product.product as serialized inventory items. The tracker device ID, last-known GPS, and last-reported timestamp migrate as custom fields. If the Odoo Inventory app is not installed, equipment is stored as a custom model Azuga_Equipment with the same field structure.

Azuga fuel card transaction data is mapped as a custom fuel_log JSON field on fleet.vehicle for quick reference, and individual fuel expense lines are created in Odoo Accounting as account.move.line entries linked to the vehicle's analytic account for cost tracking.

Azuga maintenance records (service type, cost, date, provider) map directly to Odoo's fleet.vehicle.log.services model. Odometer at service time is preserved as the odometer field on the service log. If Azuga has multiple service records per vehicle, each creates a separate log.services entry in sequence.

Azuga SafetyCam status (online, standby, offline) and last footage timestamp are stored as custom fields on fleet.vehicle (SafetyCam_Status__c, SafetyCam_Last_Footage_Date__c). The footage itself does not migrate — video files are outside Odoo's storage model. We provide a CSV export of SafetyCam footage references pointing to Azuga's CDN URLs for re-linkage if a custom video module is built.

Azuga supports multiple sub-accounts per organization. Each Azuga sub-account maps to an Odoo res.company record. Vehicle and driver assignments are scoped per company using Odoo's multi-company security rules. This mapping requires pre-migration confirmation of which Odoo companies correspond to which Azuga sub-accounts.