Migrate from Agencyzoom to Pipedrive

AgencyZoom leads map directly to Pipedrive People. The Person record inherits all standard fields (name, email, phone, address). Insurance context — carrier, policy type, lead source, CSR assignment — is preserved as custom fields on the Person record so agents retain the full lead context in Pipedrive's activity timeline.

AgencyZoom's lifecycle stage on leads (New, Contacted, Quoted, Sold) has no native Pipedrive equivalent. We create a custom pick-list field (Lead_Lifecycle_Stage__c) on Person and preserve the exact stage values. Stage-transition timestamps migrate as additional datetime custom fields for pipeline reporting continuity.

AgencyZoom companies map to Pipedrive Organizations — name, website, address, phone transfer directly. Carrier of record, NAICS code, agency license state, and number of employees migrate as custom fields on the Organization record. Parent-company hierarchies in AgencyZoom map to Pipedrive's Organization hierarchy via the parent_org_id field.

AgencyZoom policies are stored as related records on a Company. Each policy's carrier, policy type, coverage limits, effective date, lapse date, and commission split are extracted and mapped as custom fields on the corresponding Pipedrive Organization. For clients with multiple policies, the primary policy maps to the Organization; secondary policies are noted in a custom text field as comma-separated references.

AgencyZoom pipeline deals map to Pipedrive Deals with a one-to-one pipeline and stage mapping. Each AgencyZoom pipeline (typically Sales, Service, Onboarding) becomes a corresponding Pipedrive pipeline. The AgencyZoom stage names (New, Contacted, Quoted, Sold) map value-by-value to Pipedrive stage names — your Pipedrive admin chooses the exact Pipedrive stage names before migration.

AgencyZoom owner/producer IDs resolve by email match against Pipedrive users. If an AgencyZoom producer has no matching Pipedrive user account, their records are assigned to a fallback owner (configurable by your team) and flagged in the migration report. Producer name is preserved in a custom Owner_Name__c field on each Deal for reporting continuity.

AgencyZoom Service Center tickets have no direct Pipedrive equivalent — Pipedrive has no native ticket object. Each ticket maps to a Pipedrive Activity of type 'Task' with subject = ticket ID, body = description, due date = due_after_days. Custom fields on the Activity capture priority level, category, CSR assignment group, and resolution status. Open tickets migrate as open activities; completed tickets migrate as completed tasks with original completion dates preserved.

AgencyZoom notes and standalone tasks map to Pipedrive Activities. Notes become Activities with type 'Note'; standalone tasks become Activities with type 'Task'. Original timestamps, owners, and parent-record links (lead, company, deal) are preserved. Emails logged against AgencyZoom records migrate as Activity records linked to the corresponding Person or Deal in Pipedrive.

Files attached to AgencyZoom leads, companies, or deals are downloaded and re-uploaded to the corresponding Pipedrive record as file attachments. AgencyZoom file size limits apply during extraction; Pipedrive's per-plan storage limits (5GB/user on Essential, 10GB/user on Advanced) determine what lands cleanly. Large file batches are flagged before the full run.

AgencyZoom custom fields — Carrier, Policy Type, Coverage Limits, Lapse Date, Commission Split, NAICS Code, License State, CSR Group — are exported and created as Pipedrive custom fields on the appropriate object (Person, Organization, or Deal) before mapping. Pipedrive custom fields are referenced by API hash keys that differ per account; we create them first using the Pipedrive API and then map values by the generated field keys.

AgencyZoom lead source categories (Inbound Call, Referral, Captive Agent, Internet Lead, etc.) map to a custom pick-list field on Pipedrive Person. Each AgencyZoom source value is matched to the corresponding Pipedrive pick-list option; unmapped values are preserved as a text fallback custom field to avoid data loss.