Migrate from Espresso Agent to Salesforce Sales Cloud

Espresso Agent contacts map directly to Salesforce Contacts. Salesforce requires an AccountId on each Contact — contacts without a primary brokerage or company association in Espresso Agent are attached to a default 'Individual' Account or a designated 'Unassigned' Account during migration. All standard fields (name, email, phone, address) transfer as direct field mappings.

Espresso Agent contacts sourced from expired listings, FSBO, and FRBO are evaluated for routing based on lifecycle stage. If the contact has not been worked (no call log, no appointment), Salesforce routes them as a Lead. Contacts with at least one logged call or meeting activity route to Salesforce Contact with the lead source preserved in a custom field (Lead_Source_Detail__c).

Espresso Agent stores a contact's affiliated brokerage or company. These map to Salesforce Account records. Account hierarchy (parent/child brokerages) maps to Salesforce's ParentId field. If Espresso Agent stores multiple affiliations per contact (rare), the primary affiliation becomes AccountId and additional affiliations migrate as Account Contact Relations.

Espresso Agent's neighborhood search criteria (absentee_owner, high_equity, likely_to_list, preforeclosure, empty_nester) have no Salesforce standard object equivalent. FlitStack creates a Property_Search__c custom object with a lookup to Contact. Each search record preserves the criteria values, search date, and property address as custom fields on the object.

Expired listing leads, FSBO leads, and FRBO leads in Espresso Agent contain property-specific data (listing address, MLS number, listing price, days on market) that does not fit Salesforce's standard Contact or Lead schema. A Listing_Lead__c custom object with a Contact lookup preserves property address, listing status, original list price, and expiration date from Espresso Agent.

Espresso Agent's dialer produces call records with disposition (connected, no_answer, voicemail, dnc), call duration, and timestamp. Each call becomes a Salesforce Task with Type='Call', Subject containing the disposition, and ActivityDateTime set to the original call timestamp. Owner (agent) resolves via email match to Salesforce users.

Espresso Agent's AI-generated call transcription and summary do not map to any Salesforce standard field. FlitStack stores the full transcript in a custom long-text area field (Call_Transcript__c) on the Task record, and the AI summary in Call_Summary__c. This preserves the full call record for Einstein Conversation Intelligence or manual review in Salesforce.

Logged activities beyond calls — emails sent through Espresso Agent, appointments, and notes — map to Salesforce Tasks (Type='Email' or 'Task') and Events respectively. Original timestamps and owners are preserved. Notes become Salesforce Notes (the modern object, not legacy Note) with Body and ParentId linking back to the Contact.

Espresso Agent subscription tiers (Lead Tier, Neighborhood Search package) and billing cycle data have no Salesforce CRM equivalent. FlitStack exports this as a Subscription__c custom object linked to the Contact, storing package_name, billing_cycle, and start_date. Billing reconciliation and subscription management must be handled in Espresso Agent or your billing system during the transition.

Espresso Agent may track a contact's engagement score based on call activity, email opens, and listing interest signals. This score migrates as a custom Number field (Engagement_Score__c) on both Contact and Lead for parity. FlitStack maps the most recent score value — historical score trending is not preserved unless requested as a custom object.

Espresso Agent owner records (agent name, email) resolve to Salesforce Users by email address match. Unmatched owners are flagged before migration — your team either provisions Salesforce users for them or assigns their records to a designated fallback owner. No record lands in Salesforce without a resolved OwnerId.

Files attached to Espresso Agent contact records (e.g., CMA PDFs, listing flyers) are downloaded and re-uploaded to Salesforce Files, linked to the corresponding Contact or Account record via ContentDocumentLink. File size limits apply (Salesforce default 25MB per file); files exceeding the limit are flagged for manual handling.