Migrate from Espresso Agent to Odoo CRM

Espresso Agent user accounts (your agents) map to Odoo CRM res.users for login and team assignment. Their agent profile data (name, email, phone, license number) maps to a res.partner record — linked via partner_id on the user record so their contact card appears in Odoo's address book.

Each Espresso Agent contact record is split into two Odoo objects: a res.partner holds the contact's name, email, phone, and address. A crm.lead record is created for each lead-type instance (an expired-listing lead and an FSBO lead for the same person become two separate crm.lead records linked to the same partner).

Espresso Agent's 'Expired Listing' lead type has no Odoo CRM native equivalent. We create a custom Char field Lead_Source_Type__c and set it to 'expired_listing'. Additionally, an Odoo stage pipeline named 'Expired Listings' is configured with the standard Odoo stage sequence so these leads appear in a dedicated Kanban view.

For-Sale-By-Owner (FSBO) leads are routed into a dedicated Odoo CRM stage pipeline named 'FSBO' using the custom Char field Lead_Source_Type__c. The pipeline is built with stages New, Contacted, Qualified, Quote Sent, Won, and Lost, each with default probabilities aligned to a typical FSBO sales cycle. Stage assignments are driven by the lead's status in Espresso Agent, preserving the original progression through the follow‑up workflow.

Preforeclosure leads are assigned a distinct Lead_Source_Type__c value of 'preforeclosure' and placed in a dedicated Odoo CRM pipeline named 'Preforeclosure'. Each stage in this pipeline is configured with probability values that reflect the faster timeline typical of distressed‑property sales, such as Quick Offer, Negotiation, and Closed. The mapping preserves the original lead status from Espresso Agent so the progression appears in Odoo.

Espresso Agent's Neighborhood Search generates prospects flagged as high‑equity or likely‑to‑list. In Odoo CRM these records receive a Lead_Source_Type__c value of 'neighborhood_search' and are placed in a dedicated pipeline. A custom Char field Source_Subtype__c captures the underlying criteria such as absentee_owner, empty_nester, or free_and_clear, allowing you to filter and prioritize leads based on the original search parameters.

Espresso Agent call logs — including duration, outcome, and AI-generated transcription summary — migrate to Odoo CRM crm.phone.call records linked to the corresponding crm.lead. The original timestamp and outcome status are preserved in custom fields if the native Odoo crm.phone.call schema does not accommodate all fields. If a call recording URL is stored in Espresso Agent, it is saved as a hyperlink in the crm.phone.call record for future reference.

Espresso Agent call logs — including duration, outcome, and AI-generated transcription summary — migrate to Odoo CRM crm.phone.call records linked to the corresponding crm.lead. The original timestamp and outcome status are preserved in custom fields if the native Odoo crm.phone.call schema does not accommodate all fields. If a call recording URL is stored in Espresso Agent, it is saved as a hyperlink in the crm.phone.call record for future reference.

Free-text notes attached to Espresso Agent contacts or leads are transferred to Odoo CRM as mail.message records with the subtype set to 'note'. The original note body, including any inline formatting, is preserved, and the author is identified by matching the Espresso Agent user email to an Odoo res.users record. The creation timestamp is stored in the message's date field, maintaining the original chronology for audit and follow‑up purposes.

Espresso Agent links each lead to a property record (address, MLS number, estimated value). In Odoo CRM, the property address is stored in the crm.lead description field. A custom field Property_Address__c holds the full address string for reporting; MLS number is stored in Property_MLS__c.

Espresso Agent's Do-Not-Call flag on a contact is mapped to the standard opt_out Boolean field on the Odoo res.partner record. When opt_out is true, Odoo CRM suppresses the contact from outbound calling lists generated by the telephony integration, ensuring compliance with contact preferences. The flag can be cleared in Odoo if the contact later consents to calls, and the change is logged in the partner's chatter for audit purposes.

Espresso Agent tag labels—such as 'investor', 'vacation_rental', or 'absentee_owner'—are migrated as Odoo CRM tags using the crm.tag model. Each tag is created if it does not already exist, then linked to the corresponding crm.lead via a many2many relationship, allowing a single lead to retain labels from Espresso Agent. In Odoo, tags can be used for filtering, segmentation, and reporting, giving you the same view you relied on in Espresso Agent.