Migrate from OpenCRM to Pipedrive

OpenCRM Company records map directly to Pipedrive Organization records. The company name becomes the Organization name, domain and address fields map to their Pipedrive equivalents, and any custom fields on the Company object map by field name. Organizations must import before Contacts to satisfy the parent lookup. We validate that every Organization has a unique name or domain before insert to avoid creating duplicate Organization records during the import.

OpenCRM Contact records map to Pipedrive Person records. The primary mapping uses email address as the dedupe key. Each Person's OrganizationId is resolved at migration time by matching the Contact's parent Company name or domain to the Organization name in the destination. Contacts without a valid parent Company are flagged in a reconciliation report before the import commits; the customer decides whether to create placeholder Organizations or leave them as unlinked Persons.

OpenCRM Deals map to Pipedrive Deals. The Deal title, value, expected close date, and owner assignment migrate directly. The pipeline stage mapping is the critical step: OpenCRM's tenant-defined stage names require a mapping table we produce during scoping and apply during the import so each Deal lands in the correct Pipedrive stage. Closed-won and closed-lost statuses from OpenCRM map to Pipedrive's status field.

OpenCRM allows fully custom pipeline stage names per workflow. Pipedrive uses pipeline-specific stage names configured within each pipeline. We produce a stage-mapping table during scoping that aligns each OpenCRM stage to its Pipedrive equivalent by pipeline. Probability values migrate as integers; any OpenCRM stage without a Pipedrive counterpart is flagged for the customer to create before Deal import begins.

OpenCRM call activity records map to Pipedrive Activity records with type = Call. Call duration, disposition, and owner assignment migrate to custom fields. The Activity is linked to its parent record (Person, Organization, or Deal) by resolving the OpenCRM contact reference. Timestamps normalise to UTC before insert.

OpenCRM meeting activity records map to Pipedrive Activity records with type = Meeting. Start time, end time, location, and attendee list migrate to their Pipedrive equivalents. The meeting is linked to the parent record (Person, Organization, or Deal) via the OpenCRM reference resolution step. Attendees who are not already in Pipedrive as Persons are added to the meeting's public description field rather than as separate Person records.

OpenCRM task activity records map to Pipedrive Activity records with type = Task. Status (open, completed), due date, priority, and assignee migrate directly. Completed tasks retain their completion timestamp; open tasks inherit the OpenCRM due date. Task assignment resolves the OpenCRM owner name to a Pipedrive user by email match.

OpenCRM Notes attached to Contacts, Companies, or Deals migrate to Pipedrive Notes. We preserve the note body, creation timestamp, and author name. Notes attached to Deals link to the migrated Pipedrive Deal via the OpenCRM deal reference. Notes with no valid parent record are attached to the related Person as a fallback.

OpenCRM custom fields on Contacts, Companies, and Deals are discovered per-tenant during scoping and mapped field-by-field to Pipedrive custom fields. We create the Pipedrive custom field in the destination account before migration begins, matching the OpenCRM data type (text, number, date, picklist) to the nearest Pipedrive field type. Multi-select picklists in OpenCRM map to Pipedrive multi-select fields.

OpenCRM user records and deal and contact ownership assignments are resolved by email match against the Pipedrive User table. We extract every distinct owner referenced on migrating records and generate a user-mapping table. Any OpenCRM owner without a matching Pipedrive user goes to a reconciliation queue; the customer provisions missing users before record import resumes. Active and inactive status is preserved where possible.

OpenCRM tag-based categorisation on contacts and companies migrates to Pipedrive Labels. Tags stored as multi-checkbox properties in OpenCRM flatten to a comma-separated label string in Pipedrive. The customer confirms during scoping whether tags should become Pipedrive Labels, Person fields, or both. We do not create custom label taxonomy; the customer defines the label structure before import.