Migrate from Agencyzoom to Twenty CRM

AgencyZoom Leads map directly to Twenty People records. The lead's current pipeline stage, assigned producer, and lead source category transfer as custom fields. The AgencyZoom lead ID is stored as sourceAgencyzoomId__c for delta-run de-duplication and traceability back to the source system.

AgencyZoom Customer records (policyholders with an active or expired policy) map to Twenty People with a customerType__c custom field set to 'Customer'. The original customer record type from AgencyZoom is preserved as a text value in the custom field so the distinction between lead and customer is recoverable after migration.

AgencyZoom Contacts — individuals attached to leads or customers — map to Twenty People directly. Email, phone, job title, and address fields transfer as-is. The contact's parent lead or customer association is preserved as a People relation in Twenty, maintaining the hierarchical context from AgencyZoom's data structure.

AgencyZoom's agency and company records map to Twenty Companies. Agency name, domain, address, and carrier affiliations transfer. Parent/child agency hierarchies map to the Companies parentId field — the parent company must migrate first to resolve the foreign key, which FlitStack sequences automatically.

AgencyZoom Quote records have no native Twenty CRM equivalent. We create a Quote__c custom object with fields for quote number, carrier, coverage type, premium amount, effective date, expiration date, and status. Quote records link to the associated People (customer) and Companies (agency) records via relation fields.

AgencyZoom Policy records — the core insurance product records — migrate to a Policy__c custom object in Twenty. Fields include policy number, carrier, line of business (property, casualty, health, etc.), policy status, premium, deductible, effective date, expiration date, and renewal date. The policy links to the People (policyholder) and Company (agency) records.

AgencyZoom Service Tickets do not have a direct Twenty CRM equivalent. We create a ServiceTicket__c custom object with fields for ticket number, priority, status, service category, assigned group, resolution, and closed date. Tickets link to the associated People (customer contact) and Policy__c record when applicable.

AgencyZoom deal records from the Sales pipeline map to Twenty Opportunities. The pipeline stage name transfers as a custom field (pipelineStage__c) since Twenty Opportunities use a single unified stage pick-list. Multiple AgencyZoom pipelines (Sales, Service, Onboarding) each produce separate Twenty Opportunity records scoped by the pipelineStage__c value.

AgencyZoom tasks map to Twenty Tasks directly. Task subject, due date, assignee, status, and description transfer. Tasks linked to specific People, Companies, or Opportunities retain their relation in Twenty. Recurring tasks in AgencyZoom become individual task records with a recurringFlag__c custom field set to true for manual rebuild reference.

AgencyZoom notes migrate to Twenty Notes. The note body, associated record (People, Companies, Opportunities), creating user, and original creation timestamp all transfer. Notes attached to Service Tickets link to the corresponding ServiceTicket__c record after the custom object is created, preserving the full context from AgencyZoom's service documentation.

AgencyZoom workflow definitions, lifecycle automations, Smart-Cycle rules, and pre-written email/text templates do not migrate. These are destination-side configuration logic that requires manual rebuild in Twenty's workflow builder. FlitStack exports the full automation inventory from AgencyZoom as a structured JSON document for use as a rebuild specification.

AgencyZoom custom fields (text, number, date, single-choice, multi-select) map to identically typed Twenty custom fields on the corresponding object. The AgencyZoom field API name is preserved as the Twenty field name for traceability. Multi-select fields in AgencyZoom become comma-separated text in Twenty since Twenty's multi-select field type requires pre-defined option sets.

AgencyZoom file attachments on leads, customers, policies, and quotes are downloaded and re-uploaded as Twenty Files linked to the corresponding record. Inline images in notes are extracted and re-hosted. File size limits on the destination storage apply — files over 25MB are flagged for manual download link creation.

AgencyZoom owner and producer assignments are resolved by email match against Twenty Workspace Members. Unmatched owners are flagged before migration — your team either invites them to Twenty first or assigns their records to a fallback member. No record lands without an owner assignment.