Migrate from EspoCRM to Pipedrive

EspoCRM Contact records map to Pipedrive Person with name, email, phone, address, and custom fields translated to Pipedrive custom fields. Multi-email fields in EspoCRM (if configured) map to multiple email address fields in Pipedrive. We resolve duplicate Persons during import using email as the dedupe key and flag any Contacts with no email address for manual review.

EspoCRM Account records (representing companies) map to Pipedrive Organization. The Account name becomes the Organization name, website migrates directly, and any industry, employee count, or annual revenue custom fields map to Pipedrive custom fields. Organization must be created before Person import so that the relationship link is satisfied at insert time.

EspoCRM Lead records map to Pipedrive Lead with conversion status preserved. We carry the EspoCRM lead status, source, and conversion date into Pipedrive Lead fields. If the EspoCRM Lead was already converted to a Contact and Account, we map those records to Person and Organization in Pipedrive and link them rather than duplicating as unconverted Leads.

EspoCRM Opportunity records map to Pipedrive Deal with amount, stage, probability, expected close date, and lost-reason fields translated to Pipedrive Deal fields. EspoCRM pipeline stages map to Pipedrive pipeline stages; we create the Pipedrive pipeline structure before migration so that stage assignments are valid at import time.

EspoCRM Case records have no direct Pipedrive equivalent because Pipedrive is sales-centric and lacks a native service-desk object. Cases migrate as Activity records of type note attached to the related Organization or Person, with case status, priority, and resolution preserved in custom fields. If the customer needs full case management, we flag this as a separate Service Cloud or Help Scout consideration.

EspoCRM Campaign records contain marketing campaign metadata and target lists. Pipedrive has no native campaign management object. We migrate campaign records as Activity notes attached to the relevant Organization or Person with campaign name, type, and status preserved in custom fields. Target list membership does not map to Pipedrive lists natively.

EspoCRM Documents are stored as Attachment records, and on self-hosted instances the actual files live on the server filesystem under data/files/. We extract referenced files from the filesystem archive, map each to the parent entity in Pipedrive, and upload via the Pipedrive API as Activity attachments. The parent entity is resolved using the link-multiple relationship metadata from EspoCRM.

EspoCRM custom entity types created via Entity Manager are analyzed during discovery. If a custom entity has a many-to-one relationship to Contact or Account (e.g., a Subscription linked to Account), we flatten it into custom fields on the target Person or Organization. If it has a many-to-many relationship, we create a custom field on the target and store serialized references. We do not create Pipedrive custom objects; we document any entities that cannot be flattened and advise the customer on manual alternatives.

EspoCRM Activities (Calls, Emails, Meetings, Tasks) map to Pipedrive Activities with type, date, duration, subject, and body preserved. We link each Activity to the parent Person or Organization using the EspoCRM stream relationship metadata. Activity assignment resolves the EspoCRM assigned_user_id to the corresponding Pipedrive user by email match.

EspoCRM Attachment records link to parent entities via foreign key. On cloud instances attachments may be database-stored; on self-hosted instances they are filesystem-stored. We identify all Attachment records during discovery, extract files from the filesystem if self-hosted, and upload to Pipedrive via the API linked to the parent Person, Organization, or Deal.

EspoCRM User records map to Pipedrive Users by email address. We resolve the EspoCRM role and team membership from the source data and flag any role that cannot be mapped to a Pipedrive role for manual reconciliation. Users without a matching Pipedrive account go to a queue for the customer admin to provision before record migration continues.

EspoCRM multi-enum fields (capped at 20 options by default) map to Pipedrive multi-select picklist fields. If a multi-enum field exceeds 20 options, we split into two or more Pipedrive picklist fields and document the split. Multi-enum fields with fewer than 20 options map directly to Pipedrive multi-select picklists.