CRM migration

Migrate from Azuga Fleet to Nutshell

Field-level mapping, validation, and rollback between Azuga Fleet and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Azuga Fleet logo

Azuga Fleet

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Azuga Fleet and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Azuga Fleet logo

Azuga Fleet

What's pushing teams away

  • Customers on G2 and Capterra report frequent technical glitches with location tracking accuracy and alert delays that erode confidence in data integrity ahead of a migration cutover.
  • Per-vehicle pricing plus mandatory hardware costs scale poorly for large fleets, pushing enterprise customers toward flat-rate or unlimited-vehicle competitors like Samsara or Motive.
  • The reporting and data export UI is described as limited; fleet managers moving to more analytics-capable platforms find Azuga's export tooling insufficient for comprehensive data extraction.
  • Integration with non-native accounting, ERP, or HR systems is cited as a gap, forcing operations teams to manually rekey payroll, job costing, or compliance data during or after migration.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Azuga Fleet objects map to Nutshell

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)

maps to

Nutshell

Company or Person (Nutshell custom field group)

1:1
Fully supported

Azuga 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)

maps to

Nutshell

Person (Nutshell People)

1:1
Fully supported

Driver 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

maps to

Nutshell

Person-Company Relationship (Nutshell native)

1:1
Fully supported

Azuga 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)

maps to

Nutshell

Activity (Nutshell Notes on Person/Company)

1:1
Fully supported

Trip 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)

maps to

Nutshell

Activity (Nutshell Tasks)

1:1
Fully supported

Speed 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)

maps to

Nutshell

Company (Nutshell custom field group)

1:1
Fully supported

Equipment 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)

maps to

Nutshell

Activity (Nutshell Notes on Company/Person)

1:1
Fully supported

Scheduled 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)

maps to

Nutshell

Company (Nutshell Companies)

1:1
Fully supported

Azuga'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)

maps to

Nutshell

Custom Number Field on Person

1:1
Fully supported

Azuga'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)

maps to

Nutshell

Custom Field on Company

1:1
Fully supported

Fuel 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)

maps to

Nutshell

User (Nutshell user account)

1:1
Fully supported

Azuga 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)

maps to

Nutshell

No equivalent

1:1
Fully supported

Azuga 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.

Gotchas + challenges

What specifically takes care here

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 logo

Azuga Fleet gotchas

High

API v1 deprecation with unannounced v4 sunset date

High

SafetyCam video files not accessible via API

Medium

Driver score algorithms differ across platforms

Medium

Per-vehicle pricing creates billing unit complexity

Medium

No documented bulk export for trip point logs

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Azuga API v1 rate limit blocks efficient bulk extraction

    Azuga's legacy v1 API enforces a 1-request-per-minute limit per endpoint, which makes bulk data extraction extremely slow for large fleets. API v4 supports up to 200 TPS globally, but some v1 endpoints (used by certain Azuga plan tiers) still carry the old rate limit. We extract via v4 endpoints first and fall back to v1 only when the data is unavailable in v4. If your Azuga plan still uses v1 for specific modules, extraction time scales linearly with record count — a 200-vehicle fleet on v1 could require 3+ hours for a single full pull.

  • Nutshell has no native fleet or vehicle object

    Nutshell's data model is built around people, companies, leads, and deals — there is no native vehicle, driver, or asset object. All Azuga vehicle data (VIN, make/model, odometer, license plate) must be stored as custom fields on the owning Nutshell Company record. Driver safety scores, trip history, and equipment records are similarly stored as custom fields or exported as supplementary reference files. You will need to plan which custom fields are most useful for your team's Nutshell workflow before migration.

  • Trip history and alert records cannot be queried as CRM activities

    Azuga trip records (GPS tracks with start/end location, distance, duration, fuel consumption) and alert records (speeding, geofence, hard-braking) have no equivalent construct in Nutshell. Nutshell Activities are limited to notes, emails, calls, and tasks tied to a Person or Company. We export trip and alert data as supplementary JSON/CSV files linked by driver ID. Your team should decide whether the 12-month summary stored as a custom field on the Nutshell Person record is sufficient, or whether you need to retain the full trip history in a separate system.

  • Azuga SafetyCam footage does not migrate and cannot be linked

    Azuga SafetyCam incident clips and livestream URLs are stored in Azuga's cloud infrastructure and are not accessible via the standard Azuga API. We preserve incident timestamps and clip URLs as a reference field on the Nutshell Person record, but Nutshell cannot display or host video content. If your team relies on SafetyCam footage for driver coaching, that workflow must remain in Azuga or be rebuilt in a separate video management tool. The driver safety score itself does migrate as a number field, but the underlying video evidence does not.

  • Nutshell per-user pricing means fleet-heavy customers pay twice

    If your Azuga fleet has 100 vehicles but only 10 staff users, you pay for 100 Azuga vehicle licenses but only 10 Nutshell user licenses. The migration rationalizes the CRM side but does not eliminate Azuga's per-vehicle billing — if you keep Azuga for telematics, the cost model remains vehicle-based. Review Nutshell's contact-count tiers ($13–$79/user/month) against your actual user count before committing to the switch. Some Azuga plans bundle multiple vehicles per license tier, so your effective per-vehicle cost may differ from the base $25–$30 rate advertised.

Migration approach

Six steps for a successful Azuga Fleet to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Azuga Fleet logo

Azuga Fleet

Source

Strengths

  • Plug-and-play GPS hardware reportedly installs in under 20 seconds without professional fitting.
  • Gamified driver scoring with positive reinforcement differentiates from punitive safety-only platforms.
  • Published per-vehicle pricing starting at $25/month provides budget predictability for small fleets.
  • SafetyCam dual-facing AI dashcam bundles offer a single-vendor telematics plus video solution.
  • FleetMobile app gives drivers real-time shift management, timecard, and dispatch capabilities.

Weaknesses

  • API documentation is sparse; no publicly available OpenAPI spec URL or Swagger sandbox confirmed.
  • No documented bulk export endpoint for historical telemetry; data retention limits are unclear.
  • Hardware dependency creates a physical asset recovery problem when migrating off-platform.
  • Timecard data is not accessible via public API, limiting automated HR or payroll integration.
  • Pricing beyond BasicFleet requires custom quotes, making cross-platform cost comparison difficult.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Azuga Fleet and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Azuga Fleet: 200 TPS maximum (per-endpoint, per-module, and global limits documented).

  • Data volume sensitivity

    B

    Azuga Fleet doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Azuga Fleet to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Azuga Fleet to Nutshell data migrations

Answers to the questions buyers ask most during Azuga Fleet to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Azuga-to-Nutshell migrations complete in 48–72 hours for fleets under 200 vehicles. The extraction phase is the longest step — Azuga's v1 API endpoints carry a 1-request-per-minute rate limit on some plan tiers, which extends extraction to 3–5 hours for large datasets. Nutshell's API writes are fast once data is mapped. Large fleets with 500+ vehicles, equipment records, and full trip history exports extend the timeline to 7–10 days. We always run a sample migration first to validate field mapping before the full run.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Azuga Fleet.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day