Migrate from Prophet CRM to Pipedrive

Prophet Company records map to Pipedrive Organization. Standard fields including company name, industry, address, employee count, and revenue export cleanly. Industry classification from Prophet maps to a custom picklist field in Pipedrive since Pipedrive's default industry list differs from Prophet's. We use the company name as the dedupe key during import. Organization must be created before any Contact import so that the organization_id field is available at Contact insert time.

Prophet Contact records map to Pipedrive Person. Standard fields including name, email, phone, title, and address migrate directly. Prophet's bidirectional Outlook sync means Contacts may carry Outlook-sourced profile photos and contact details; we migrate the contact fields but not the Outlook photo attachment unless a file URL is accessible via the OData export. The organization_id reference resolves to the Organization created from the parent Company record. We freeze Outlook sync before migration to prevent duplicate contacts reappearing after import.

Prophet Opportunity records map to Pipedrive Deal. The opportunity name, value, close date, probability, and owner transfer directly. Stage mapping requires the full Prophet stage list captured during scoping because stages vary per department template. We map each Prophet stage value to a Pipedrive stage within the designated pipeline. Owner resolution uses email matching against Pipedrive Users, with unresolved owners held in a reconciliation queue.

Prophet pipeline stages are configurable per department, meaning the same stage name may have different meanings or probability values across departments. We capture the complete stage list per department during the scoping audit and map each stage to a Pipedrive stage within a pre-created pipeline. Stage probability percentages transfer from Prophet to Pipedrive. If the customer uses multiple Prophet pipelines, we create multiple Pipedrive pipelines and assign the appropriate pipeline to each Deal import batch.

Prophet email tracking activities migrate to Pipedrive Activity records of type email. The email subject, body, timestamp, and participant list transfer. In Pipedrive, activities are linked to a Person (WhoId) and optionally a Deal (WhatId). We resolve the WhoId by matching the Prophet Contact email against the imported Pipedrive Person records. If the email is linked to a Company-level activity with no specific contact, it attaches to the Organization instead.

Prophet call log activities migrate to Pipedrive Activity records of type call. Call duration, disposition, and timestamp transfer to custom fields on the Pipedrive activity. WhoId and WhatId resolution follows the same pattern as email activities. If the Prophet call record includes a recording URL, we attach it as a file link on the activity record.

Prophet appointment activities migrate to Pipedrive Activity records of type meeting. Start time, end time, location, and attendee list transfer. Attendee resolution matches against the imported Pipedrive Person records by email. If an attendee is not found in Pipedrive, the activity records the meeting without a linked Person.

Prophet task activities migrate to Pipedrive Activity records of type task. Task subject, due date, status, and priority transfer. Owner assignment resolves by email match against imported Pipedrive Users. Task completion status maps directly to Pipedrive's done flag.

Prophet custom fields on Companies, Contacts, and Opportunities migrate to Pipedrive custom fields on Organization, Person, and Deal respectively. We pre-create all destination custom fields in Pipedrive before any data import so that field names and data types are locked and serve as valid mapping targets during import. Data type mapping follows: text fields to Pipedrive text, date fields to Pipedrive date, numeric fields to Pipedrive integer or float, picklist fields to Pipedrive enum. Multi-department custom field templates require a full schema audit to enumerate every field used across departments; we do not assume the default view captures all fields.

Prophet file attachments on Companies, Contacts, and Opportunities are extracted as metadata (filename, URL, file type, associated record) from the OData export. Files are uploaded to Pipedrive via the file attachment API and linked to the corresponding Organization, Person, or Deal record. We do not migrate email body attachments that are stored as inline content within activity records; those remain part of the activity body migration.