Migrate from Azuga Fleet to Microsoft Dynamics 365 Sales

Azuga vehicles map 1:1 to a custom Fleet_Vehicle__c table in Dynamics 365. Every Azuga vehicle field (VIN, make, model, year, license plate, current odometer) becomes a column in the custom table. The Azuga vehicle ID is stored as Source_System_ID__c for delta-run de-duplication. Vehicles are owned by the system user resolved from the Azuga group/zone assignment.

Azuga drivers are not Contacts in the CRM sense — they are operational personnel. FlitStack creates a custom Fleet_Driver__c table as the driver-of-record. The driver record links to one or more Fleet_Vehicle__c records via a custom many-to-many junction table (Vehicle_Driver_Assignment__c). Azuga driver fields (name, license number, phone, email, hire date) map directly.

Azuga trip records (start time, end time, start odometer, end odometer, distance, route geometry, fuel consumed, average speed) map to a custom Fleet_Trip__c table. Each trip is linked to the originating Fleet_Vehicle__c and, where the driver is identified, to Fleet_Driver__c. Trip route geometry (polyline) is stored as a custom text field since Dynamics 365 does not have a native geospatial type.

Azuga safety alerts — speeding, harsh braking, harsh acceleration, distracted driving, seatbelt off — become Fleet_Safety_Event__c records. Each event carries the event type, timestamp, vehicle reference, driver reference, speed or G-force value, and the Azuga SafetyCam clip URL as a text link. Events map to the ActivityParty model for owner tracking.

Azuga fuel fill-up events (odometer, gallons, cost, date, location) migrate to Fleet_Fuel_Event__c linked to Fleet_Vehicle__c. Fuel cost per mile is recalculated in Dynamics 365 using the Trip distance field. Dynamics 365 native currency fields handle cost — FlitStack maps Azuga's decimal cost value directly to a Currency field.

Azuga geofences are structured boundary polygons with enter/exit event logs. The geofence definition (name, type, lat/lng vertices) migrates as a custom Fleet_Geofence__c record. The boundary geometry is stored as a serialized text field (JSON) since Dynamics 365 has no native polygon type. Each geofence enter/exit event becomes a Fleet_Geofence_Event__c record linked to the geofence and the triggering vehicle.

Azuga equipment tracker records (serial number, equipment type, status, last known location, assignment) map to a custom Fleet_Equipment__c table. Equipment links to the assigned Fleet_Vehicle__c via a lookup field. Last known location is stored as separate Latitude__c and Longitude__c decimal fields for map visualization in Dynamics 365.

Azuga's 0–100 driver score has no Dynamics 365 equivalent. The current score migrates as Score_Current__c on Fleet_Driver__c. Historical score snapshots (score + snapshot date per driver) are bulk-inserted into a separate Fleet_Driver_Score_History__c table so Power BI reports can render trend lines over time. Azuga's score breakdown (speeding events, braking events, idle time percentages) is stored as child records in the history table.

Azuga groups and zones (logical collections of vehicles and geofences) map to a custom Fleet_Zone__c table. Zone assignments for vehicles are stored as a Fleet_Vehicle_Zone_Assignment__c junction record. Dynamics 365's native Territory entity is not used because Azuga zones map to operational groupings (depot, region, job site) rather than sales territories.

Azuga's notification templates (email, SMS, in-app alerts for speeding, geofence breach, maintenance due) have no Dynamics 365 counterpart. We export the template names, trigger conditions, and recipient rules as a structured JSON file. Your Dynamics 365 admin rebuilds these in Power Automate using the Fleet_Vehicle__c and Fleet_Safety_Event__c tables as triggers.

Azuga SafetyCam settings (camera type, orientation, live stream enabled, event recording threshold) are Azuga-platform configuration, not data. The SafetyCam clip URLs stored in safety event records do migrate as text links. The physical camera configuration is exported as a vehicle annotation note for reference but cannot be activated in Dynamics 365.

Azuga fleet reports (fuel cost by vehicle, driver score leaderboard, geofence compliance) are platform-stored definitions. The underlying data (vehicles, trips, fuel events, driver scores) migrates to Dataverse custom tables. Reports are rebuilt using the migrated tables as Power BI datasets — we provide a sample PBIX template linked to the Fleet_Vehicle__c and Fleet_Driver__c tables.