Migrate from Espresso Agent to Twenty CRM

Espresso Agent contacts map 1:1 to Twenty People. The email field serves as the unique identifier for relation resolution. Contacts without a primary company attach to a placeholder company record to satisfy Twenty's required companyId relation. If a contact has multiple company affiliations, the most recently updated association is used as the primary companyId, and other companies are added as secondary relation records.

Espresso Agent users (agents) map to Twenty WorkspaceMembers via email match. Twenty requires users to accept workspace invitations before user references can resolve — we flag unmatched owners before migration so invitations can be sent proactively. Unmatched owners remain in a staging queue until their email is added to the workspace.

Espresso Agent company records map to Twenty Companies with domain preserved as the unique lookup key. Parent-company hierarchies map via Twenty's parentId field; circular references are flagged and must be resolved before the migration run commits. If a parent company does not yet exist in Twenty, the migration defers the child record until the parent loads, preserving hierarchy integrity.

Espresso Agent lead records — categorized by property type — map to Twenty Opportunities. The original lead category (expired_listing_flag, fsbo_flag, frbo_flag, preforeclosure_flag) becomes a custom select field (Lead_Source_Type__c) on the Twenty Opportunity so the category is preserved for reporting. This mapping allows pipeline reports to filter by original lead source without requiring manual data entry.

Espresso Agent's lead_score property (numeric 0–100) has no native Twenty equivalent. We create a custom number field (Lead_Score__c) on Twenty's Opportunity object. Scores transfer as-is; FlitStack generates a field-level diff so you can verify the distribution matches before the full run.

Espresso Agent's neighborhood_search_criteria (absentee_owner, high_equity, likely_to_list, free_and_clear) has no Twenty equivalent. We create a custom multi-select field (Search_Criteria__c) on Opportunity and map each active criterion flag to a selected value in the multi-select set. If a lead has multiple active criteria, all are included as selected values, preserving the full search profile for future analysis.

Espresso Agent stores a property_address on each lead record. Twenty Opportunities do not have a native address field. We create custom text fields (Property_Street__c, Property_City__c, Property_State__c, Property_Zip__c) on the Opportunity so property context travels with the deal. These four fields are populated from the corresponding components of the original property address, ensuring complete address traceability across records.

Espresso Agent dialer activity — call timestamps, duration, disposition, outcome notes — migrates as Twenty Tasks linked to the corresponding Person record. Call disposition (contacted, no_answer, voicemail, do_not_call) becomes the Task subject, with disposition notes stored in the Task body.

Espresso Agent email engagement records map to Twenty Tasks with Type='Email'. Original timestamps, sender, and subject line are preserved. Body content migrates as the Task description field. If the email contains attachments, the attachment file names are recorded in a separate custom field to preserve reference without moving file blobs.

Espresso Agent supports N:1 contact-to-company associations (a contact can belong to multiple companies). Twenty supports one primary company per Person via companyId, with additional company relations handled via the relation system. The primary company resolves to companyId; secondary companies are surfaced as relation records.

Any Espresso Agent custom properties not covered above migrate as Twenty custom fields on the equivalent object. Custom fields must exist in Twenty's Data Model (Settings → Data Model) before the import runs — FlitStack generates a field-creation checklist as part of the pre-migration setup plan.

Espresso Agent sequences and automated outreach rules are platform-native automations that cannot export in a transferable format. We export the sequence definition (step order, delay intervals, message templates) as a JSON reference document so your Twenty admin can rebuild the logic in Twenty's workflow builder. This is the most manual part of any Espresso Agent to Twenty migration.