Migrate from Azuga Fleet to Freshsales

Azuga alert rules have no native Freshsales equivalent and must be rebuilt from scratch

Azuga speed alerts, geofence entry/exit triggers, and maintenance reminders are automation rules configured within Azuga's platform — they evaluate thresholds against live telematics data and fire notifications to drivers or fleet managers. Freshsales has no telematics event evaluation engine; its Workflows trigger on CRM record field changes (e.g., a field value crossing a threshold on a Contact or Account). The migration cannot carry Azuga rule logic because Freshsales has no trigger condition equivalent for OBD-II data streams. We export your Azuga alert rule definitions — thresholds, notification recipients, escalation paths — as a configuration reference document so your Freshsales admin can rebuild them as Freshsales Workflows with custom fields capturing the alert data migrated from Azuga.

Azuga's device-to-vehicle binding requires custom field tracking in Freshsales since no CRM field stores hardware serial numbers

Azuga OBD-II trackers are bound to specific vehicles by serial number — this binding drives diagnostic alerts, firmware update targeting, and replacement workflows. Freshsales Accounts have no native field for device serial numbers, firmware versions, or last-seen timestamps. We create custom text fields (Device_Serial__c, Firmware_Version__c, Last_Seen__c) on the Account record to preserve this binding. However, these fields are passive — they won't update automatically. If your team relies on real-time device health monitoring tied to CRM records, you will need a middleware integration or a Freshsales-compatible telematics connector to keep those fields current post-migration. This is not a data loss issue; it is a real-time synchronization gap that must be addressed separately.

Azuga fuel card transactions and IFTA mileage tracking have no Freshsales native equivalent

Azuga integrates with fuel card providers (WEX, PAPCO, EFS) and logs IFTA-eligible miles by state — data that feeds tax reporting and fuel cost allocation. Freshsales has no native fuel transaction object, mileage log, or IFTA reporting module. We migrate fuel transaction records as Notes with custom fields (gallons, cost, odometer, state) attached to the Account. But Freshsales reporting does not natively aggregate fuel spend or generate IFTA mileage reports. Your team will need to either export Freshsales data into a spreadsheet for IFTA calculations or connect a dedicated fuel card reporting tool post-migration. We document the fuel transaction field mapping so any third-party tool can import the data cleanly.

Freshsales lifecycle stages and Freddy AI scoring operate independently from Azuga safety scores

Freshsales lifecycle stages (Lead → Marketing Qualified → Sales Qualified → Customer) track the commercial relationship progression and drive Freddy AI scoring and sales automation. Azuga safety scores (0–100 per driver) track operational driving behavior. These two scoring systems are orthogonal and do not interact. When driver records migrate as Contacts, the lifecycle stage defaults to 'Lead' or the configured default for new Contacts. Your Freshsales admin must configure lifecycle stage progression logic — typically tied to a deal stage change or a manual update — independently of the Driver_Safety_Score__c field. We set both fields correctly on import; the workflow automation to update lifecycle stage based on driving behavior (e.g., 'Customer' driver with high safety score) requires Freshsales Workflow configuration post-migration.

Azuga driver-app-only users may not have email addresses and require admin decisions before migration

Azuga FleetMobile users (drivers using the mobile app) may have accounts in Azuga that are tied to phone numbers or device IDs rather than email addresses. Freshsales requires an email address to create a Contact record with login capability. Drivers without email addresses in Azuga will be flagged before migration. Your team decides whether to: (a) create placeholder email addresses for driver Contacts, (b) import them as Contacts without Freshsales user accounts, or (c) exclude pure driver-app records from the Freshsales migration and maintain them in a separate fleet operations system. We surface all driver records without email addresses in the pre-migration report so this decision is made before data lands.