CRM migration

Migrate from Agencyzoom to Nutshell

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

Agencyzoom logo

Agencyzoom

Source

Nutshell

Destination

Nutshell logo

Compatibility

83%

10 of 12

objects map 1:1 between Agencyzoom and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

AgencyZoom is built around the insurance sales lifecycle — leads flow through pipelines tied to carriers, policies, quotes, vehicles, and drivers. Nutshell operates a conventional SMB CRM model: People (contacts), Companies (accounts), Leads, Deals, and Tasks, with custom fields scoped per object. The migration maps AgencyZoom's lead records to Nutshell Leads or People depending on the record state, customers with policy detail to People linked to Companies, and AgencyZoom's carrier/product/policy lineage to custom fields on Nutshell's deal records. AgencyZoom's Smart Cycle recycle dates, producer assignments, and carrier integrations have no direct Nutshell equivalent — those are surfaced as custom fields and re-created workflows. FlitStack uses AgencyZoom's API (30 calls/min daytime rate limit) to extract records in ordered batches, resolves owner emails against Nutshell users, and loads data via Nutshell's JSON-RPC API with a field-level diff before committing the full migration. This migration process handles the fundamental difference between an insurance-centric data model and a general-purpose CRM by flattening hierarchical relationships into custom fields and rebuilding automation logic.

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

Agencyzoom logo

Agencyzoom

What's pushing teams away

  • Rising pricing is a consistent complaint—customers report ongoing price increases that erode satisfaction and drive consideration of lower-cost alternatives.
  • Automation complexity creates a steep learning curve; users struggle with excessive clicking through prewritten email and text sequences tied to automated workflows.
  • Email hygiene limitations frustrate users—bulk deletion of invalid email addresses and management of auto campaigns for bad addresses require significant manual effort.
  • Search functionality is unreliable; users report the search bar fails to locate clients regularly, with inconsistent results across the user base.
  • Sales Center and Service Center operate as disconnected modules—notes and files from a sold pipeline do not automatically transfer into the service pipeline within AgencyZoom.

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 Agencyzoom objects map to Nutshell

Each row shows how a Agencyzoom 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.

Agencyzoom

Lead

maps to

Nutshell

Lead / Person

1:many
Fully supported

AgencyZoom leads that have been converted to customers land as Nutshell People records. Unconverted leads with active pipeline status route directly to Nutshell Leads. The split is determined by AgencyZoom's customer_type field: a value of 'Customer' routes the record to Person, while any other value routes it to Lead. This preserves the conversion state from AgencyZoom in the target CRM structure.

Agencyzoom

Customer

maps to

Nutshell

Person + Company

many:1
Fully supported

AgencyZoom customers carry both person-level fields (first name, last name, email, phone) and organization fields (business entity, FEIN, annual revenue, number of employees). We split these: person fields map to Nutshell Person; organization fields map to a Nutshell Company that the Person is associated with.

Agencyzoom

Policy

maps to

Nutshell

Deal + Custom Fields

1:1
Fully supported

AgencyZoom policies store carrier, product line, policy number, effective date, expiration date, premium, and prior premium. These map to a Nutshell Deal with custom fields: Carrier__c, Policy_Number__c, Effective_Date__c, Expiration_Date__c, Premium__c, and Prior_Premium__c. The Deal's name uses the policy number or customer name for identification.

Agencyzoom

Quote

maps to

Nutshell

Deal (secondary)

1:1
Fully supported

AgencyZoom quotes carrying carrier, product, line items, and premium amounts attach to the related Policy/Deal record in Nutshell. Quote-level fields are stored as a secondary set of custom fields on the same Deal if the quote has not yet been bound to a policy. Bound quotes reference the parent policy Deal record.

Agencyzoom

Vehicle / Vehicle 2

maps to

Nutshell

Custom Fields on Deal

1:1
Fully supported

AgencyZoom vehicle records (VIN, make, year, model, ownership) have no Nutshell equivalent. Each vehicle maps to a group of custom text fields on the Deal: Vehicle_VIN__c, Vehicle_Make__c, Vehicle_Year__c, Vehicle_Model__c, Vehicle_Ownership__c. Multiple vehicles on one policy become separate field groups with a numeric suffix.

Agencyzoom

Driver / Driver 2

maps to

Nutshell

Custom Fields on Deal

1:1
Fully supported

AgencyZoom driver records (first name, DOB, relationship, gender, license state, driver license number) map to custom fields on the Deal: Driver1_FirstName__c, Driver1_DOB__c, Driver1_License__c, and so on. Driver-to-vehicle assignment is not structurally represented in Nutshell and is noted as a manual setup step.

Agencyzoom

Pipeline

maps to

Nutshell

Pipeline (Kanban)

1:1
Fully supported

AgencyZoom pipelines (Sales, Service, Onboarding) map directly to Nutshell Pipelines. Each pipeline's stages (New, Contacted, Quoted, Sold, or custom names) map value-by-value to Nutshell stage names. Automation triggers attached to stages do not migrate and must be rebuilt in Nutshell.

Agencyzoom

Smart Cycle

maps to

Nutshell

Custom Fields + Workflow

1:1
Fully supported

AgencyZoom Smart Cycle manages recycle dates and follow-up intervals for each lead. The recycle date transfers as a custom date field (Next_Recycle_Date__c) on the Nutshell Lead record, preserving the next-touch date in the new CRM. The automatic follow-up cadence that drove Smart Cycles in AgencyZoom requires a rebuilt Nutshell workflow or task sequence to replicate.

Agencyzoom

Producer / CSR

maps to

Nutshell

Nutshell User

1:1
Fully supported

AgencyZoom producers and CSRs are named users who own leads and customers. FlitStack resolves each producer's email address against Nutshell users — matched users receive the record as Owner. Unresolved producers are flagged before migration for team invitation or fallback assignment.

Agencyzoom

Organization

maps to

Nutshell

Company

1:1
Fully supported

AgencyZoom organization records (business entity, FEIN, NAICS code, business classification, year started) map to Nutshell Company fields. Where AgencyZoom stores multiple phone types (primary, secondary), these map to Nutshell's phone and additional_phones custom fields.

Agencyzoom

Note / Activity

maps to

Nutshell

Note / Task

1:1
Fully supported

AgencyZoom notes and activity entries, including create date, owner, and body text, migrate to Nutshell Notes attached to the relevant Person, Company, or Deal record. Both timestamps and owning user information are preserved during migration when the user can be matched to an existing Nutshell user account.

Agencyzoom

Custom Field

maps to

Nutshell

Custom Field

1:1
Fully supported

AgencyZoom custom fields (text, number, date, single-choice, multi-choice) created via MyAgency > Manage Custom Fields are enumerated via API and mapped to Nutshell custom fields on the equivalent object (Lead, Person, or Deal). Multi-choice fields map to Nutshell multi-select dropdowns.

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.

Agencyzoom logo

Agencyzoom gotchas

High

API rate limit of 30 calls per minute constrains migration throughput

High

Lifecycle automations are not exposed via the public API

Medium

Integration account needs agency-owner permissions to see all data

Medium

Custom fields are per-agency and require manual cataloging before migration

Low

Search and data integrity issues can surface silently in exported data

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

  • Policy-level detail requires a flat custom-field model

    AgencyZoom's policy sub-objects — Vehicles, Drivers, Quotes — are first-class entities with their own records. Nutshell has no equivalent hierarchy; a policy with three vehicles and two drivers produces up to five groups of custom fields on a single Deal. This flattens the relationships that AgencyZoom stores structurally, and driver-to-vehicle assignments cannot be preserved as a relational link in Nutshell. We document every custom field created and the ordering logic used so your team can validate the resulting Deal record.

  • AgencyZoom API rate limit throttles extraction speed

    AgencyZoom's API enforces a hard cap of 30 calls per minute during daytime hours (60 at night CT). Large books of business with tens of thousands of records require batched extraction runs with pause-and-resume logic. We schedule extraction during the 60-calls-per-minute window where possible and pre-stage the data so the Nutshell load step is not throttled by the source. This extends the discovery phase but prevents API 429 errors mid-migration.

  • Smart Cycle recycle dates map to a static date field, not a live cadence

    AgencyZoom Smart Cycles drive automatic follow-up reminders on a rolling schedule — the recycle date updates each time a lead is touched. In Nutshell, there is no equivalent cadence engine. We migrate the current recycle date as a custom field (Next_Recycle_Date__c) on the Lead so the next-touch date is visible, but the automated cycling must be rebuilt as a Nutshell workflow or task sequence. We provide a rebuild reference document listing every Smart Cycle trigger and interval.

  • Carrier and product pick-list values need explicit value mapping

    AgencyZoom carriers and product lines are stored as pick-list values set by the agency. Nutshell custom dropdowns for Carrier__c and Product__c must be populated with the exact same values to preserve reporting continuity. We enumerate all carrier and product values from the AgencyZoom export, compare them against Nutshell's target field options, and add missing values to Nutshell's field configuration before the load runs. This step adds one to two hours of setup time for agencies with more than 15 unique carriers.

  • Unmatched producers and CSRs create unowned records

    AgencyZoom producer and CSR assignments are named-user references. When the migration resolves producer email addresses against Nutshell users, any producer without a corresponding Nutshell account is flagged in the pre-flight report. Records owned by unmatched producers land with a designated fallback owner or are flagged as unassigned. Your team must either invite those producers to Nutshell before migration or confirm the fallback assignment rule — records cannot be loaded without an owner reference in Nutshell.

Migration approach

Six steps for a successful Agencyzoom to Nutshell data migration

  1. Enumerate AgencyZoom objects via API and export schema

    FlitStack connects to AgencyZoom using an owner-level API key and enumerates all object types — leads, customers, contacts, organizations, policies, vehicles, drivers, and custom fields — via the REST endpoints under /v1/api/. We capture field names, pick-list values, and relationship metadata to build the migration schema before touching any record data. AgencyZoom's 30-calls-per-minute daytime rate limit is respected by pacing requests and batching reads.

  2. Build Nutshell custom field configuration from AgencyZoom schema

    Using the enumerated AgencyZoom schema, FlitStack creates all required custom fields in Nutshell on the People, Companies, Leads, and Deals objects before any data loads. Carrier and product pick-list values are added to the corresponding custom dropdown fields. Vehicle and driver field groups are created as sequential custom fields with naming suffixes to support multiple vehicles per policy. Producer email-to-user resolution runs against Nutshell's user list at this stage to surface any unmatched owners.

  3. Export and sequence data from AgencyZoom: Organizations first, then Customers, then Policies

    Data extraction follows a parent-first sequence to satisfy referential integrity. AgencyZoom Organizations (companies) export first and map to Nutshell Companies. Customers and their contacts export second and associate to the newly created Companies. Policies export third and attach to the customer record, with Vehicle and Driver sub-records appended as custom field groups on the corresponding Deal. All extraction runs during the 60-calls-per-minute nighttime window where possible to avoid daytime throttling.

  4. Run sample migration with field-level diff against Nutshell

    A representative slice — typically 100–300 records spanning leads, customers, policies, and vehicles — migrates to Nutshell first. FlitStack generates a field-level diff comparing source values against the resulting Nutshell record, covering every standard and custom field. You review the diff to confirm that carrier values populated correctly, policy effective dates are preserved, vehicle fields are ordered as expected, and producer ownership resolved correctly before the full run commits.

  5. Full migration with delta pickup and audit log

    The full AgencyZoom dataset loads into Nutshell following the validated mapping. A delta-pickup window of 24–48 hours captures any records modified or created in AgencyZoom during the cutover period. FlitStack produces a complete audit log of every record created, every custom field populated, and every owner assignment made. If reconciliation reveals discrepancies, one-click rollback reverts the Nutshell state to pre-migration. After cutover, your team manages all new activity in Nutshell; AgencyZoom remains read-only for 30 days.

Platform deep dives

Context on both ends of the pair

Agencyzoom logo

Agencyzoom

Source

Strengths

  • Specialized for insurance agencies with industry-specific pipelines, lifecycle stages, and carrier integrations.
  • Pre-built integrations with HawkSoft AMS360 and other agency management systems reduce double data entry.
  • Google review automation built in, supporting organic client acquisition and retention workflows.
  • Mobile app available so producers can track goals and manage tasks on the go.
  • Growth Plan at $99/month adds enhanced support and automation for scaling small-to-mid agencies.

Weaknesses

  • Learning curve is steep for new users—pipelines and automation require significant training investment.
  • API rate limits of 30 calls per minute during business hours constrain migration throughput for large data sets.
  • Rising pricing is a recurring complaint across G2 reviews, with no clear ceiling on annual increases.
  • Lifecycle automations cannot be exported—only the content library is accessible; automation rules must be rebuilt manually elsewhere.
  • Sales Center and Service Center do not automatically share notes or files between modules.
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. 2 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 Agencyzoom and Nutshell.

  • Object compatibility

    B

    2 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

    Agencyzoom: 30 calls/min (standard hours); 60 calls/min from 10PM CT to 4AM CT.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Agencyzoom 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 Agencyzoom to Nutshell data migrations

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

Can't find your answer?

Walk through your Agencyzoom to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most AgencyZoom-to-Nutshell migrations complete in 48–72 hours of clock time for accounts under 25,000 records. Larger books of business — particularly those with vehicle and driver sub-records on each policy — extend to 5–8 days because AgencyZoom's 30-calls-per-minute API rate limit requires batched extraction. Field configuration and value mapping for carrier and product pick-lists add 1–2 hours of setup time before the load begins.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Agencyzoom.
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