Migrate from Agencyzoom to HubSpot

AgencyZoom leads map directly to HubSpot Contacts when the lead is associated with a contact record. If AgencyZoom stores leads separately from contacts, they migrate as HubSpot Contacts with lifecycle_stage set based on the lead's pipeline status. Original create date and owner preserved.

AgencyZoom contacts migrate 1:1 to HubSpot Contacts. Email, phone, name, address, and custom contact properties map to HubSpot custom properties. Owner resolved by email match to HubSpot users. Original create timestamp preserved as a custom datetime field. Additional steps include verifying duplicate detection, mapping lead source and territory data, and ensuring that any secondary addresses are stored in HubSpot’s address sub‑objects for accurate routing.

AgencyZoom company records migrate as HubSpot Companies. Company name, domain, industry, employee count, and annual revenue map to HubSpot standard fields. Parent‑company relationships migrate as HubSpot parent‑company associations. During migration we also map industry pick‑list values to HubSpot’s allowed set, preserve multiple office locations as separate address records, and validate that the hierarchy of parent and subsidiary companies reconstructs correctly in HubSpot.

AgencyZoom policies do not have a direct HubSpot equivalent. We map them to HubSpot Deals with insurance-specific fields (carrier, policy type, policy number, premium, effective date) stored as custom properties on the Deal. Each policy becomes a Deal linked to the insured Company and Contact.

AgencyZoom Sales Pipeline maps to a HubSpot Deal Pipeline. Pipeline stages (New Lead, Quote Sent, Sold, etc.) map to HubSpot Deal stages. We preserve stage‑entered timestamps as custom datetime fields for reporting continuity. For custom stage names we create matching HubSpot stages and maintain their order, and any stage‑specific properties are transferred as custom fields on the Deal so historical reporting reflects the original workflow.

AgencyZoom Service Center pipelines map to HubSpot Ticket pipelines. Service ticket priorities, categories, and statuses map to HubSpot Ticket properties and pipeline stages. Requires a HubSpot Service Hub subscription for full ticket functionality. We also map any custom category pick‑lists, preserve SLA timers as custom datetime fields, and replicate assign‑group logic using HubSpot Teams or individual users so tickets route correctly after migration.

AgencyZoom service tickets migrate as HubSpot Tickets with original priority, category, assign group, and resolution status preserved. Service ticket description and resolution notes migrate to HubSpot Ticket properties. We also transfer any inline attachments as HubSpot file links, map custom priority levels to HubSpot’s standard set, and retain the original ticket subject so that history remains searchable and audit‑ready.

AgencyZoom tasks migrate as HubSpot Tasks with original due dates, owners, completion status, and subject preserved. Tasks linked to specific contacts or deals maintain their association in HubSpot. We also map any reminder settings as HubSpot task notifications, preserve task categories if used, and ensure that completed tasks retain their completion timestamp so historical workload reports remain accurate.

AgencyZoom carrier names have no native HubSpot equivalent. We create a Carrier__c custom pick-list property on Deals and map carrier values from AgencyZoom. Carriers not matching existing values are flagged for review before migration. During mapping we also standardize carrier naming conventions, map inactive carriers to a generic “Other” option, and ensure that each carrier’s historical premium totals are preserved in custom numeric fields on the Deal for reporting.

AgencyZoom policy‑level custom fields (e.g., policy_sub_type, renewal_date, commission_rate) map to HubSpot custom properties on the Deal object. We create the properties in HubSpot before migration and map values directly. For each field we match data types (text, date, number), apply any required validation rules, and preserve the original AgencyZoom field label as a description in HubSpot so administrators can trace the source of each custom property.

AgencyZoom owner IDs resolve to HubSpot users by email match. Unmatched owners are flagged before migration — your team either invites them to HubSpot or assigns their records to a fallback owner before the migration runs. We also generate a mismatch report listing each unresolved owner, map any inactive AgencyZoom users to a “Legacy Owner” placeholder, and preserve the original owner name in a custom text field so reporting still reflects the pre‑migration assignment.

AgencyZoom workflows, lifecycle automation sequences, and content library templates (email/text templates) do not migrate to HubSpot. We export workflow definitions as a structured rebuild reference. Your team rebuilds automations in HubSpot's workflow builder using the exported definitions. The export includes trigger conditions, action steps, time delays, and field references, along with a step‑by‑step guide to recreate each workflow in HubSpot so the rebuild effort is straightforward.