Migrate from Espresso Agent to Freshsales

Real-estate lead types require custom field recreation in Freshsales

Espresso Agent classifies leads by real-estate type (Expired, FSBO, FRBO, Neighborhood Search) as built-in contact properties. Freshsales has no native equivalent — these types do not map to any standard Freshsales field. We create custom pick-list fields (Expired_Listing__c, FSBO__c, FRBO__c) on the Freshsales Lead object and set the appropriate flag per contact during migration. If you use these flags in Espresso Agent workflows, you will need to rebuild equivalent logic in Freshsales workflows on the Pro plan or above. The custom fields are created before data lands, and the migration plan surfaces the full field list for your Freshsales admin to review.

Dialer call transcripts and recordings need custom field or external storage

Espresso Agent's integrated dialer stores AI-generated call transcripts and recording URLs per contact. Freshsales Sales Activities do not natively store call transcripts — the standard activity record holds outcome, duration, and notes. We preserve Espresso Agent transcripts in a custom Transcript__c field on Freshsales Sales Activities and the recording URL in a custom URL field. If you need full playback inside Freshsales rather than linking out, Freshcaller (Freshworks telephony add-on) must be configured separately after migration — the recording URL from Espresso Agent does not auto-import into Freshcaller.

Espresso Agent workflows and sequences do not migrate and cannot be exported as a reusable artifact

Espresso Agent CRM workflows that trigger follow-up actions based on lead type, neighborhood search results, or dialer outcomes are platform-native and not accessible via API export in a reusable format. Freshsales Pro and Enterprise plans offer workflows and sales sequences, but these must be rebuilt manually. We can provide a written inventory of every active Espresso Agent workflow — trigger condition, action, and filter logic — to assist your Freshsales admin with the rebuild. This is the most common source of post-migration friction when teams do not plan the rebuild alongside the migration.

Owner resolution by email is required — inactive Espresso Agent users create orphaned records

Espresso Agent owner records (agents, admins) map to Freshsales users by email address match. If an Espresso Agent owner account uses an email address that does not correspond to an active Freshsales user at migration time, their records land under an unassigned or fallback user. This affects activity history attribution, deal ownership, and Freshsales reporting. We flag all unmatched owners before the migration runs and require your team to either create Freshsales user accounts or designate a fallback owner. The ownership audit report is part of the pre-migration deliverable.

Freshsales contact deduplication by email can merge Espresso Agent contacts unexpectedly

Freshsales merges Contacts and Leads by email address when duplicate prevention is enabled. If your Espresso Agent data has multiple contacts sharing the same email address (common with spouse co-owners on a property), Freshsales may merge them into a single Contact record, collapsing distinct Espresso Agent records. We disable Freshsales auto-deduplication before migration runs and surface duplicate contacts in the pre-migration audit. Your admin decides whether to merge before migration or accept separate records in Freshsales.