Migrate your Agencyzoom data

Leads are the primary acquisition object in AgencyZoom's sales pipeline. The platform supports lead source categories, recycle events, and lifecycle stages. We map Leads to the destination CRM's equivalent object and preserve lead status, source, and activity dates at import time.

Contacts are the core customer record. The API exposes batch-create endpoints (added Jan 2024) and supports search by last activity date. We export contacts as CSV or pull via API and map standard fields directly to the destination CRM.

Policies represent active or historical insurance coverage tied to a Contact. The API supports policy retrieval tied to leads and contacts. We preserve the policy-to-contact relationship during migration and map carrier and coverage details to the destination schema.

AgencyZoom has three pipeline types. Pipeline stages are configurable per agency. We capture stage names, ordering, and any custom stage statuses. Mapping to a destination CRM requires aligning stage labels to the target pipeline's stage schema since terminology varies.

Tasks are created, updated, completed, and batch-deleted via the API. We migrate task records with assignee, due date, status, and body text. Completed and open task states are preserved.

Service tickets represent service requests in the Service Center pipeline. The API supports create, update, complete, and list operations. We migrate open and closed tickets, preserving priority, category, resolution status, and linked contact or policy references.

Custom fields are configurable per agency via MyAgency → Manage Custom Fields. The API exposes a custom fields list endpoint. We catalog all custom field names and types during scoping and map them to destination custom properties, noting any that may require manual recreation in the target CRM.

Lifecycle automations in AgencyZoom consist of email templates, text templates, reminders, and task triggers tied to pipeline stages. The automation logic itself is not exposed via the public API. We can export the content library—email and text templates—but the automation rules must be manually rebuilt on the destination platform.

Quotes are associated with Leads via the API endpoint POST v1/api/leads/{leadId}/quotes. We extract quote data where present. Mapping depends on whether the destination CRM has a native Quotes object or requires quotes to land as custom fields on the Deal or Policy record.

Carriers are reference data listing the insurance carriers the agency works with. We export the carrier list during migration and map it to the destination CRM's Companies/Accounts object or carrier-specific field, depending on the destination schema.

Notes, emails, texts, and tasks logged against a Contact or Lead are captured as activity history. We export activity records and map them to the destination CRM's activity/engagement timeline, preserving timestamps and owner attribution.

Users and group assignments control pipeline routing and task ownership. Permissions are tied to the logged-in user account via JWT. We map AgencyZoom users to the destination CRM's Owner/User object, noting that the calling integration account needs agency-owner-level access to see all records.