Migrate from Pro-Sales CRM to Pipedrive

Pro-Sales CRM Contacts map directly to Pipedrive People. Name, email, phone, company association, lifecycle stage, and owner migrate as standard fields. We map the company association to a Pipedrive Organization lookup by matching the organization name or domain from the Pro-Sales CRM Company record. Custom fields on the Contact object migrate as Pipedrive custom fields on the Person entity.

Pro-Sales CRM Company records map to Pipedrive Organization. Address, industry, and company size fields migrate to the equivalent Pipedrive Organization fields. Organization is created before the related Person import so that the organization_id lookup is satisfied at Person insert time. If the customer's Pro-Sales CRM has multiple addresses per Company, we flag this during scoping and the customer decides whether to create multiple Organizations or store the full address list in a text custom field.

Pro-Sales CRM Deals map to Pipedrive Deals with a stage mapping table applied before import. We extract the active pipeline configuration from Pro-Sales CRM (stage names and probability weights) and create matching stages in the destination Pipedrive pipeline before migration. Deal value and close date migrate directly. Lost and won status maps from Pro-Sales CRM's closed-stage flags to Pipedrive's status field.

Pro-Sales CRM allows custom stage names and per-stage probability weights that vary by customer configuration. We extract the active stage list during discovery, map each stage name to a Pipedrive stage with the same probability percentage, and create any missing stages in the destination pipeline before Deal import begins. Stage ordering is preserved to match the Pro-Sales CRM pipeline layout.

Pro-Sales CRM call log entries map to Pipedrive Activity records with activity_type = Call. Duration, disposition, and call direction migrate to custom activity fields. ActivityDate and timestamps are normalized from the source timezone to UTC before writing to Pipedrive. The Activity is linked to the corresponding Person and Organization via the Pipedrive activity API's person_id and org_id references.

Pro-Sales CRM note entries map to Pipedrive Activity records with activity_type = Note. The note body migrates as the activity's subject or as a note attached to the activity record. Notes linked to specific Contacts or Companies reference the corresponding Pipedrive Person or Organization ID resolved during migration.

Pro-Sales CRM task completions map to Pipedrive Activity records with activity_type = Task. Task status (complete/incomplete) maps to Pipedrive's done flag. The due date and assignee from Pro-Sales CRM migrate to the corresponding Pipedrive Activity fields. Assignee resolution uses the owner mapping table to convert Pro-Sales CRM owner IDs to Pipedrive user IDs.

Pro-Sales CRM custom fields on Contacts and Deals are inspected during discovery. We create equivalent custom fields in Pipedrive before migration, matching field types where possible (text, number, date, dropdown). Pipedrive does not support custom objects, so any Pro-Sales CRM custom field that references a non-standard entity is flagged as a limitation and must be flattened to text or dropped with customer sign-off. Pipedrive's five standard entities (deal, person, organization, product, project) each have independent custom field space.

Pro-Sales CRM tag assignments on Contacts and Deals migrate to Pipedrive Labels. We preserve the tag strings as label names and apply them to the corresponding migrated records after the base object import is complete. If a Pro-Sales CRM record has multiple tags, each tag becomes a separate Pipedrive label on that record. Label color is assigned by default unless the customer specifies a color scheme during scoping.

Pro-Sales CRM assigns a single owner per record. We extract every distinct owner ID referenced on Contact, Company, and Deal records and match by email against the destination Pipedrive user table. Any Pro-Sales CRM owner without a matching Pipedrive user is flagged and reassigned to a designated fallback user. The customer's admin provisions missing Pipedrive users before migration if the original owner should retain the records.