Migrate from Azuga Fleet to Salesforce Sales Cloud

Azuga vehicle records map directly to Salesforce Assets. The Asset Name field receives the Azuga vehicle_id or unit number. Make, model, year, and VIN populate Asset standard fields. Azuga vehicle status (active/inactive) maps to Status pick-list on Asset. Asset's AccountId links to the fleet-operations account representing the company vehicle fleet.

Azuga driver profiles become Salesforce Contacts. The driver's first name, last name, email, and phone map directly to Contact standard fields. Azuga driver license number and license expiration date migrate to custom fields (Driver_License__c, License_Expiration__c) on Contact. The Contact's AccountId points to the fleet-operations account or the driver's employer account depending on whether drivers are employed by the company or contracted.

Azuga trip records (start location, end location, distance, duration, start time, end time) map to Salesforce Tasks with Subject='Trip: [origin] to [destination]'. Trip distance in miles or kilometers becomes a custom Number field (Trip_Mileage__c). The related Asset (vehicle) and Contact (driver) attach via WhatId and WhoId on the Task. Multiple trip segments within a single Azuga trip can become a Campaign with Campaign Members representing individual stops.

Azuga safety alerts — speeding, harsh braking, collision detection, geofence violation — become Salesforce Cases. Case Origin='Azuga Fleet', Type='Safety Alert', and Priority='High' or 'Medium' based on Azuga severity level. The Case is linked to the Asset (vehicle) and Contact (driver) for full context. Case description includes the alert details: speed vs. speed limit, deceleration force in Gs, timestamp. After migration, Salesforce Flow rebuilds the alert-to-case assignment routing that Azuga handled natively.

Azuga fuel_card_transactions have no direct Salesforce equivalent. We map them to a custom Fuel_Transaction__c object linked to the Asset (vehicle) with fields: transaction_date__c, gallons__c, cost_per_gallon__c, odometer__c, station_name__c, and location__c (latitude/longitude). This gives finance teams fuel spend visibility inside Salesforce alongside the Asset record without polluting the standard object schema.

Azuga maintenance records (oil change, tire rotation, inspection, recall) become Salesforce Cases with Type='Maintenance' and Asset linked. For recurring preventive maintenance schedules, we create Cases with the due date in Case.Due_Date__c and map Azuga's service_type pick-list to Case.Service_Type__c. If the customer uses Salesforce Field Service, these Cases dispatch to Field Service work orders without schema changes.

Azuga geofences (circular/polygon zones with names, center coordinates, radius) have no Salesforce standard equivalent. We create Azuga_Geofence__c with Name, Latitude__c, Longitude__c, Radius_Miles__c, Zone_Type__c (customer_site, restricted_area, depot), and Active__c. For active geofence monitoring in Salesforce, your admin configures Salesforce Maps territory rules against these custom records. Geofence alert history (entries/exits) maps to Tasks linked to the related Asset.

Azuga's driver_score (0–100 scale, updated per trip or weekly) maps to a custom Number field on Contact: Driver_Score__c. We also preserve the score trend as Driver_Score_Trend__c (improving, stable, declining) and last_updated timestamp as Driver_Score_Last_Updated__c. Salesforce reports can reference these fields in account roll-ups so managers see fleet safety aggregated per customer or territory.

Azuga groups organize vehicles by fleet or region. If groups represent physical depots or branches with addresses, we map them to Account records (one Account per Azuga group). Vehicles (Assets) and drivers (Contacts) within the group link via their AccountId. If groups are virtual collections without address data, a custom Azuga_Fleet_Group__c object with a junction to Assets and Contacts handles the relationship without creating misleading Account records.

Azuga equipment_tracker objects — trailers, generators, tools — map to Salesforce Assets with Type='Equipment'. Serial number, make, and model populate standard Asset fields. The equipment's assigned vehicle from Azuga links via the Asset's Parent_Asset__c custom field (self-referential lookup for asset hierarchies). Equipment maintenance history follows the same Case-as-service-record pattern as vehicle maintenance.

Azuga time_card records (driver hours, duty status changes for DOT compliance) need a custom Driver_Hours__c object: Date__c, Driver__c (Contact lookup), Hours_Worked__c, On_Duty_Time__c, Driving_Time__c, Off_Duty_Time__c, and Duty_Status__c (on_duty, driving, sleeper_berth, off_duty). This preserves HOS data for audit trails and FMCSA compliance reporting — Salesforce standard objects do not model duty status.

Azuga route_plan objects (planned routes with stop sequences) migrate as Route__c with Name, Route_Date__c, Assigned_Driver__c (Contact), Assigned_Vehicle__c (Asset), and estimated_distance__c. Individual stops within the route become Task records with Route__c in a custom lookup field, with Task.Subject='Stop: [address]' and the stop sequence in Stop_Order__c. For Salesforce Maps users, Route__c is the seed data for territory and routing optimization.

Azuga SafetyCam footage clips are stored in Azuga's cloud with URLs referencing the video blob. Salesforce Files store documents and attachments but not video streams. We preserve Azuga's video_url__c as a custom Text field on the related Case or Asset so the link remains accessible. Rebuilding SafetyCam-equivalent functionality requires a Salesforce partner app from AppExchange (Lytx, Motive, Samsara integrations) — those are third-party rebuilds not covered by data migration.

Azuga user accounts (fleet managers, dispatchers, admin) are system accounts, not customer records. Salesforce User records are the destination-side equivalent for login access. We match Azuga users to Salesforce Users by email address. If no matching User exists, the Azuga user record is flagged and the admin creates the Salesforce User before migration to avoid orphaned ownership on Assets, Cases, and Tasks.

Azuga Enterprise plans support custom objects via their API's /objects endpoint. Custom object schemas export via Azuga API v4 and map 1:1 to Salesforce custom objects. The custom object name in Azuga becomes the API name in Salesforce (App__c). Fields preserve their data types (text, number, picklist, date, datetime) with __c suffix. Relationships between custom objects map via Salesforce lookup fields — N:N relationships require junction objects.