CRM migration
Field-level mapping, validation, and rollback between Azuga Fleet and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Azuga Fleet
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Azuga Fleet and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Azuga Fleet stores vehicle telemetry, driver behavior scores, GPS tracks, and equipment records — a fundamentally different data model from Nutshell's people, companies, leads, and deals structure. The migration is non-trivial because there is no native equivalent for driver scores, vehicle diagnostics, or route history in Nutshell. We extract Azuga data through the v4 REST API (authenticated via OAuth 2.0, rate-limited to 200 TPS with per-endpoint caps), map driver records to Nutshell People, vehicle-to-customer associations to Nutshell Companies with a custom fleet_id link, and preserve odometer readings, maintenance alerts, and safety scores as custom fields on the respective Person or Company record. Trip history and geofence violations have no Nutshell equivalent — these are surfaced in a supplementary export file for reference. Nutshell's JSON-RPC API (HTTPS only, Basic auth with API token) receives the migrated records. Automation rules, alert configurations, and driver rewards programs do not migrate and must be rebuilt in Nutshell or documented for manual re-entry.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Azuga Fleet object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Azuga Fleet
Vehicle (Azuga /vehicles endpoint)
Nutshell
Company or Person (Nutshell custom field group)
1:1Azuga vehicles have no direct Nutshell equivalent. We create a custom field group (Fleet_Vehicle__c) on Nutshell's Person object. Vehicle ID, make/model, license plate, and current odometer migrate as custom fields. If the vehicle is a company asset, we link it to the owning Nutshell Company via a custom lookup field.
Azuga Fleet
Driver (Azuga /drivers endpoint)
Nutshell
Person (Nutshell People)
1:1Driver records map directly to Nutshell Person records. Name, email, phone, and driver license number migrate as standard Person fields. Driver ID from Azuga is stored as Source_Driver_ID__c for traceability. The driver's Azuga Safety Score migrates as a custom Number field on the Person record.
Azuga Fleet
Driver-Vehicle Assignment
Nutshell
Person-Company Relationship (Nutshell native)
1:1Azuga assigns drivers to vehicles via the /driverVehicleMap endpoint. We resolve the driver to a Nutshell Person and the vehicle's owning organization to a Nutshell Company, then create a Person-Company relationship with a role of 'Fleet Driver' in Nutshell. Historical assignments are preserved as activity notes.
Azuga Fleet
Trip Record (Azuga /trips endpoint)
Nutshell
Activity (Nutshell Notes on Person/Company)
1:1Trip records (start/end location, distance, duration, fuel consumed) have no native Nutshell object. We export full trip history as a supplementary JSON file linked by driver Person ID. In Nutshell, we create a summary note on the Person record noting total trips and mileage for the past 12 months.
Azuga Fleet
Alert / Geofence Violation (Azuga /alerts endpoint)
Nutshell
Activity (Nutshell Tasks)
1:1Speed alerts, geofence entry/exit events, and hard-braking notifications are exported as a reference file. In Nutshell, we create a single summary Task per driver listing alert count by type for the last 90 days. Nutshell has no real-time alert engine, so alert workflows must be rebuilt using Nutshell Tasks or external tooling.
Azuga Fleet
Equipment (Azuga /equipment endpoint)
Nutshell
Company (Nutshell custom field group)
1:1Equipment tracker records (beacon ID, equipment type, last known location) have no Nutshell equivalent. We create custom fields on the owning Nutshell Company record: Equipment_Count__c, Last_Service_Date__c, and Equipment_Summary__c (text summary of all tracked assets). Full equipment detail is exported separately.
Azuga Fleet
Maintenance Record (Azuga service alerts)
Nutshell
Activity (Nutshell Notes on Company/Person)
1:1Scheduled maintenance alerts and odometer-based service reminders do not map to any Nutshell object. We create a Note on the associated Company or Person record summarizing open and completed maintenance items. The full maintenance log is exported as a supplementary CSV for reference.
Azuga Fleet
Group / Customer Account (Azuga internal grouping)
Nutshell
Company (Nutshell Companies)
1:1Azuga's internal account/group structure that groups vehicles and drivers maps directly to Nutshell Companies. Company name, address, and contact person (if stored in Azuga) migrate as standard Nutshell Company fields. All vehicles and drivers linked to this group become custom fields on and relationships to this Company.
Azuga Fleet
Safety Score (Azuga per-driver composite)
Nutshell
Custom Number Field on Person
1:1Azuga's Safety Score (0–100, derived from speeding, hard braking, idle time, seatbelt events) has no Nutshell native field. We create Driver_Safety_Score__c as a custom Number field on Nutshell Person. Score history (monthly snapshots) is preserved in a supplementary export file linked by driver email.
Azuga Fleet
Fuel Transaction (Azuga fuel card integration data)
Nutshell
Custom Field on Company
1:1Fuel purchase records from Azuga's fuel card integration do not map to Nutshell objects. We export fuel transaction history as a separate CSV linked by vehicle ID. A summary (total gallons, total cost, average MPG for the past 12 months) is stored as a text custom field on the owning Company for reference.
Azuga Fleet
User / Owner (Azuga admin user)
Nutshell
User (Nutshell user account)
1:1Azuga admin and fleet manager accounts resolve by email match against Nutshell user accounts. If a Nutshell user exists for the email, records are assigned to that user. Unmatched Azuga owners are flagged and assigned to a fallback Nutshell admin user. Azuga role/permission sets do not migrate — Nutshell roles are assigned manually post-migration.
Azuga Fleet
Dash Cam Footage Reference (Azuga SafetyCam)
Nutshell
No equivalent
1:1Azuga SafetyCam video clips and incident footage are stored in Azuga's cloud and have no Nutshell equivalent. We preserve clip URLs and incident timestamps as a reference export linked by driver Person ID. Nutshell does not store media files natively — footage must remain in Azuga or a separate video storage system.
| Azuga Fleet | Nutshell | Compatibility | |
|---|---|---|---|
| Vehicle (Azuga /vehicles endpoint) | Company or Person (Nutshell custom field group)1:1 | Fully supported | |
| Driver (Azuga /drivers endpoint) | Person (Nutshell People)1:1 | Fully supported | |
| Driver-Vehicle Assignment | Person-Company Relationship (Nutshell native)1:1 | Fully supported | |
| Trip Record (Azuga /trips endpoint) | Activity (Nutshell Notes on Person/Company)1:1 | Fully supported | |
| Alert / Geofence Violation (Azuga /alerts endpoint) | Activity (Nutshell Tasks)1:1 | Fully supported | |
| Equipment (Azuga /equipment endpoint) | Company (Nutshell custom field group)1:1 | Fully supported | |
| Maintenance Record (Azuga service alerts) | Activity (Nutshell Notes on Company/Person)1:1 | Fully supported | |
| Group / Customer Account (Azuga internal grouping) | Company (Nutshell Companies)1:1 | Fully supported | |
| Safety Score (Azuga per-driver composite) | Custom Number Field on Person1:1 | Fully supported | |
| Fuel Transaction (Azuga fuel card integration data) | Custom Field on Company1:1 | Fully supported | |
| User / Owner (Azuga admin user) | User (Nutshell user account)1:1 | Fully supported | |
| Dash Cam Footage Reference (Azuga SafetyCam) | No equivalent1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Azuga Fleet gotchas
API v1 deprecation with unannounced v4 sunset date
SafetyCam video files not accessible via API
Driver score algorithms differ across platforms
Per-vehicle pricing creates billing unit complexity
No documented bulk export for trip point logs
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Extract Azuga data via v4 REST API
FlitStack authenticates to Azuga using OAuth 2.0 client credentials (client_id and client_secret obtained from [email protected]). We pull vehicle records, driver records, trip summaries, alert histories, equipment tracker data, and driver-vehicle assignment maps from the /vehicles, /drivers, /trips, /alerts, /equipment, and /driverVehicleMap endpoints. Data is extracted in page batches using cursor-based pagination where supported. We extract the full safety score history (monthly snapshots) for each driver. If any required data is only available in v1 endpoints, we fall back to Basic auth (API key) and pace requests to comply with the 1-request-per-minute limit.
Resolve drivers to Nutshell Person records by email match
Azuga driver email addresses are matched against Nutshell user accounts by email. If a matching Nutshell user exists, the driver record is linked to that user for ownership. Drivers without a matching Nutshell user are created as new Nutshell Person records. Unmatched or duplicate emails are flagged in the pre-migration validation report. Safety scores, license numbers, and alert summaries are attached as custom fields on each Person record during this step.
Map vehicles and equipment to Nutshell Companies with custom fields
Each Azuga vehicle is associated with a parent Azuga account/group. We map that group to a Nutshell Company record, creating one if it does not exist. Vehicle data (VIN, license plate, make/model, current odometer, last service odometer, status) is stored as custom fields on the Company record. Equipment tracker records (beacon ID, equipment type) are summarized and stored as custom fields on the same Company. All vehicles and equipment are linked to the Company via custom lookup fields.
Create driver-vehicle relationships and trip/alert summaries
Using the Azuga driver-vehicle assignment map, we create Nutshell Person-Company relationships with role 'Fleet Driver' for each active assignment. Historical assignments are preserved as notes on the Person record. Trip summary data (total distance, total trips for past 12 months) and alert summary data (alert count by type for past 90 days) are computed and stored as custom text fields on the Person record. Full trip history and alert detail are exported as JSON and CSV files linked by driver ID.
Run sample migration with field-level diff and validation
A representative slice of records (typically 50–100 drivers and their linked vehicles/companies) migrates first. We generate a field-level diff report comparing source Azuga values against the migrated Nutshell custom field values. You verify safety score mapping, vehicle-to-company linkage, driver-person resolution, and the trip/alert summary text before the full run commits. Any mapping corrections are applied before the production migration. This validation step helps catch field mapping errors early, ensuring data transforms correctly before committing to a full run.
Full migration with delta-pickup and rollback plan
The full migration runs against Nutshell's JSON-RPC API (authenticated with the API token for your Nutshell account). A delta-pickup window of 24–48 hours captures any driver records modified in Azuga during the cutover. Nutshell's open API allows us to update records in place. An audit log records every create and update operation. One-click rollback reverts all Nutshell changes if reconciliation fails. Post-migration, we deliver the supplementary trip history JSON and alert detail CSV as separate exports for your records.
Platform deep dives
Azuga Fleet
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Azuga Fleet and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Azuga Fleet: 200 TPS maximum (per-endpoint, per-module, and global limits documented).
Data volume sensitivity
Azuga Fleet doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Azuga Fleet to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Azuga Fleet to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Azuga Fleet
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.