Migrate from Espresso Agent to Microsoft Dynamics 365 Sales

Espresso Agent stores contacts with an embedded company object. FlitStack AI splits this into a separate Account record first, then links the Contact to it via the AccountId lookup. The primary company name and domain become the Account name and website; secondary associations surface as Account Contact Relationships in Dynamics 365.

Contacts in Espresso Agent without an associated deal are treated as Prospects. These migrate as Dynamics 365 Lead records. Leads that subsequently receive a deal in Espresso Agent are re-processed as Contact + Opportunity. The Lead Status field is populated from the source contact's stage value.

Contacts carrying a live deal in Espresso Agent map directly to Dynamics 365 Contact records. The contact retains its email, phone, address, and owner information from the source system. Dialer metrics are preserved as custom columns on the Contact record: new_dialer_calls (Integer) stores the total outbound call count, and new_conversation_minutes (Decimal) stores the aggregate conversation duration accumulated in the Espresso Agent dialer history. This ensures agent performance data remains queryable in Dynamics 365 reports without needing to reference the legacy system.

Espresso Agent deals migrate as Dynamics 365 Opportunity records with the estimated value preserved as Amount, the close date as CloseDate, and the stage name mapped via a value-mapping table to the nearest Dynamics 365 stage (New, Qualification, Proposal, Negotiation, Closed Won, Closed Lost).

Each dialer call in Espresso Agent creates a Dynamics 365 Task record with Type='Phone Call', Subject containing the contact name and call date, and the original call duration in minutes stored as a custom field (new_call_duration_minutes). Disposition data maps to a custom pick-list (new_call_disposition).

Logged email activities migrate as Dynamics 365 Task records with Type='Email'. The Subject, Body (plain text or HTML), and original timestamp are preserved. The Regarding lookup links the Task to the parent Contact or Lead record by email address matching.

Notes attached to contacts or deals in Espresso Agent migrate as Dynamics 365 Annotations (Note or Email — whichever matches the source format). The original note text, created timestamp, and author are preserved. Rich-text formatting is retained where the source format supports it.

Espresso Agent categorizes leads as Expired Listing, FSBO, FRBO, Preforeclosure, Neighborhood Search, or Absentee Owner. Dynamics 365 Sales has no native real estate lead-type field. We create a custom pick-list column (new_espresso_leadtype) on both Contact and Lead, preserving the exact source value so reporting continuity is maintained.

Espresso Agent's power dialer tracks per-contact call counts and total conversation minutes. Dynamics 365 Sales has no native dialer-metrics equivalent. We create new_dialer_calls (Integer) and new_conversation_minutes (Decimal) as custom columns on Contact, populated from the source dialer history aggregated per contact.

FlitStack AI resolves Espresso Agent agents to Dynamics 365 users by matching the email address. Unmatched agents are flagged before migration; your team either invites them to Dynamics 365 first or assigns their records to a fallback owner. No record lands in Dynamics 365 without a resolved OwnerId.

Espresso Agent's neighborhood search feature stores property targeting criteria (streets, zip codes, property types). This is user preference data, not a contact attribute. We preserve it as new_neighborhood_search on Contact as a text field, noting that it is reference data — the property records themselves do not exist as structured objects in Espresso Agent.

The primary company associated with a contact migrates as a Dynamics 365 Account. The Account name, website (domain), industry pick-list value, and employee count map directly. Parent-child company hierarchies in Espresso Agent translate to Account.ParentId lookups in Dynamics 365, with circular references flagged during validation.