Migrate from Espresso Agent to Pipedrive

Espresso Agent contact records map directly to Pipedrive Persons. Each Person record receives the contact's name, email, phone, address, and owner assignment. Custom fields on the Espresso Agent contact (FSBO flag, expired-listing flag, listing type) migrate as Pipedrive custom fields keyed to the Person record. Multiple Espresso Agent contacts can share one Organization in Pipedrive when they represent agents working at the same brokerage.

Espresso Agent company records (brokerages, property management firms) map to Pipedrive Organizations. Organization name, domain, industry, phone, and address fields transfer directly. Parent-child company hierarchies in Espresso Agent map to Pipedrive's parent Organization field. Pipedrive's Organization ID becomes the foreign key linking to Person records — Organizations must migrate before Persons for relationship resolution.

Espresso Agent deals tied to property listings map to Pipedrive Deals. Deal name, value, stage (mapped to Pipedrive pipeline stage), close date, and owner transfer directly. Espresso Agent's listing-status stages (active, pending, sold, expired) map to Pipedrive pipeline stage values — each listing type may represent a separate Pipedrive pipeline if your team uses distinct workflows per property type. Pipedrive requires that a Person or Organization is associated with every Deal, so person_id must resolve before deal migration runs.

Espresso Agent contacts without an assigned deal route to Pipedrive's Lead object rather than Person. Pipedrive Leads inherit all custom fields defined on Deals, so Espresso Agent real estate flags (FSBO, expired, preforeclosure) carry over as Pipedrive Lead custom fields. Once a Lead converts in Pipedrive, it creates a Person and optionally a Deal — this mirrors Espresso Agent's behavior of converting a prospecting contact to an active listing deal.

Espresso Agent dialer call logs (including AI-generated summaries, talk-time ratios, and outcome flags) migrate as Pipedrive Activity records with type='Call'. The original call duration, timestamp, and owner transfer as custom fields on the Pipedrive Activity since native Pipedrive Activities do not preserve all Espresso Agent call metadata. FlitStack AI maps the dialer outcome field to the Pipedrive Activity's result field.

Espresso Agent email activities map to Pipedrive Email Activities. Subject, body, sender, recipient, timestamp, and owner transfer directly. Pipedrive's email sync integration (available on Advanced plan and above) must be configured post-migration to maintain ongoing email logging — historical emails from Espresso Agent are preserved as Activity records but future email logging requires the Pipedrive email sync setup.

Espresso Agent meeting records (showing appointments with clients, open house events, listing presentations) map to Pipedrive Meeting Activities with original start/end times preserved. Espresso Agent notes attached to contacts or deals migrate as Pipedrive Notes linked to the corresponding Person, Organization, or Deal record. Rich text formatting in Espresso Agent notes converts to Pipedrive's note format.

Espresso Agent's listing_type flag (FSBO, expired, preforeclosure, FRBO, neighborhood search) has no native Pipedrive equivalent. FlitStack AI creates a Pipedrive custom field (keyed by the 40-character hash) on both Person and Deal objects and maps the listing type value directly. Value-mapping applies where Espresso Agent uses pick-list values — each distinct listing type becomes a Pipedrive pick-list option.

Espresso Agent's neighborhood search criteria fields (equity tier, owner-occupancy flag, likely-to-list score) migrate as Pipedrive custom fields on the Person record. These are numeric or pick-list fields in Espresso Agent and map to Pipedrive's number or set_of_options field types respectively. Pipedrive's field-key hash is generated per-account — the migration plan specifies the exact hash for each custom field so the API import targets the correct field.

Espresso Agent dialer outcomes (contacted, no answer, voicemail, busy, DNC) have no native Pipedrive Activity field equivalent. FlitStack creates a Pipedrive custom field on Activity records to store the dialer outcome string, preserving the full outcome history for reporting continuity. This custom field is added to the Activity object via Pipedrive's ActivityFields API before the migration runs.

Espresso Agent owner_id on contacts, organizations, and deals resolves to Pipedrive OwnerId by email match. FlitStack AI compares the Espresso Agent owner email against Pipedrive user emails — matched users receive record ownership directly. Unmatched owners are flagged before migration and can be assigned to a fallback Pipedrive user or created as new Pipedrive users before the migration commits. No record lands without an OwnerId in Pipedrive.

Pipedrive's created_time and update_time fields are set at migration time, not preserved from Espresso Agent. FlitStack AI captures the original Espresso Agent createdate and updatedate as custom datetime fields on each object (Person, Organization, Deal, Activity) so historical reporting continuity is maintained. These custom fields are named Original_Created_Time__c and Original_Updated_Time__c and are created before migration runs.