Migrate from Espresso Agent to Nutshell

Real estate lead categories have no native Nutshell equivalent

Espresso Agent classifies leads by real estate category — Expired listings, FSBOs, FRBOs, and Neighborhood Search types — with a daily prospecting data feed behind each category. Nutshell has a standard Lead object with a status field and source field but no native pick-list for real estate lead categories. If your team relies on this classification for segmentation and follow-up routing, those categories must be recreated as a custom field in Nutshell and mapped value-by-value from Espresso Agent's data. We create a custom pick-list field (e.g., Lead_Source_Type__c) and surface the mapping plan before migration so you can confirm the value list matches your segmentation logic. The daily prospecting data itself (neighborhood search parameters, equity flags, likely-to-list scores) is Espresso-specific and cannot be regenerated in Nutshell — it can be preserved as text fields for reference, but your team should treat it as historical context, not live data.

Espresso Agent dialer functionality cannot migrate to Nutshell

Espresso Agent's integrated power dialer is a core part of the product — it enables 4x call volume with AI noise suppression, call transcription, and AI-generated summaries tied to contact records. Nutshell has no integrated power dialer and no call logging automation that replicates this workflow. Call outcome notes and duration from Espresso Agent's dialer export migrate as Notes on the corresponding Nutshell People record, preserving contact history, but call recordings are exported as audio files and must be stored separately. The dialer itself must be replaced by either Nutshell's manual calling workflow or a third-party dialer integration (such as a Zapier-connected VoIP tool) that your team sets up post-migration. This is a functional gap that requires a workflow decision before go-live, not a data-loss issue but a process-change risk if teams are dialer-dependent.

Espresso Agent's bundled pricing model does not map to Nutshell's per-seat model

Espresso Agent subscriptions ($199–$399/month on Geo, Pro, and Platinum plans) bundle prospecting data access, a power dialer, CRM functionality, and onboarding support into a single plan price. Nutshell charges per user seat ($13–$79/user/month) with contact-count tiers and separate add-on pricing for email marketing, SMS, and Nutshell IQ. Teams switching from Espresso Agent's bundled model to Nutshell may find that the line-item cost for CRM alone is lower, but they lose the bundled prospecting data and dialer that justified the Espresso Agent spend. We surface the contact-count estimate from the Espresso Agent database during scoping so you can calculate the Nutshell cost before committing to migration. This is a billing-model difference, not a data-loss risk, but it is the most common source of post-migration sticker shock if not anticipated.

Espresso Agent has no documented public bulk export API

Nutshell provides a full-account export tool, a JSON-RPC API covering all standard objects and custom fields, and per-object list exports. Espresso Agent's data portability is not documented in the same way — the platform is oriented toward daily prospecting data delivery rather than API-first data ownership. This means the export phase of the migration may require account-level data access coordination and structured file extraction rather than a clean API pull. We use available API access (where present) supplemented by structured export file processing to extract CRM records, contacts, deals, and activity history. This adds a discovery step to the migration plan that most CRM-to-CRM migrations do not require, and it can extend the scoping timeline if Espresso Agent's data export requires support-ticket coordination.

Espresso Agent workflows and drip sequences cannot migrate to Nutshell

Espresso Agent's drip sequence builder and auto-dialer workflows are plan-specific — Platinum plan includes the most aggressive sequence logic tied to lead categories. Nutshell has personal email sequences (available on Pro plan and above) but no drip campaign builder equivalent to Espresso Agent's sequence automation. Sequences and workflows must be rebuilt from scratch in Nutshell or migrated to an external automation platform (Zapier, Make, or a dedicated sequencing tool) that integrates with Nutshell's API. FlitStack exports the sequence definitions as a reference document so your team has a rebuild checklist, but the automation logic itself is not portable. This is a standard limitation for CRM-to-CRM migrations — workflows are platform-specific by design — but it is particularly impactful for Espresso Agent teams because the sequences are tightly coupled to the real estate lead-category model.