Migrate from CRM Service to Pipedrive

CRM Service Account records map directly to Pipedrive Organization. The Account Name becomes the Organization name, and Account Site becomes the address field. We use the Account external ID (if populated) as the dedupe key during import to prevent duplicate Organizations. Organization records are imported before any Person records so that the CRM Service Account-to-Contact lookup is resolved at insert time.

CRM Service Contact maps to Pipedrive Person, preserving the Contact-to-Account linkage via the Organization ID. Email, phone, title, and department transfer directly. We map the CRM Service isPrimary__c flag to the Person's primary contact status in Pipedrive. Person records are inserted after Organization records to satisfy the org_id foreign key.

CRM Service Leads require a mapping decision because Pipedrive does not have a separate Lead object. We import CRM Service Leads as Person records with a custom field crm_service_lead_source__c preserving the original LeadSource value, and a custom field crm_service_is_converted__c set to false for all imported Leads. The customer's admin decides during scoping whether converted CRM Service Leads (that were previously in a Contact or Opportunity) should be imported as Leads or skipped.

CRM Service Opportunity maps to Pipedrive Deal. The Opportunity Amount transfers to Deal value, CloseDate to close_date, and StageName to the corresponding Pipedrive stage. We use external IDs to preserve the Opportunity-to-Account relationship, resolving AccountId to Organization ID at migration time. Stage probability percentages migrate as a custom numeric field deal_probability__c.

CRM Service pipeline stages map to Pipedrive pipeline stages within the configured Pipeline. We create the Pipedrive Pipeline and stage structure before importing any Deals, matching CRM Service stage names to Pipedrive stage labels and preserving probability values as a custom field. Pipedrive supports multiple pipelines at all paid tiers; we configure one Pipeline per CRM Service sales process or record type.

CRM Service User records map to Pipedrive User by email address match. Any CRM Service User referenced as an Opportunity or Contact owner without a matching Pipedrive User is held in a reconciliation queue. The customer's Pipedrive admin provisions matching Users before the production migration runs. Inactive CRM Service Users can be imported as inactive Pipedrive Users or excluded per the customer's preference.

CRM Service Tasks map to Pipedrive Activity records with type=task. We preserve Status (Open vs Completed), Priority, ActivityDate, and the subject as the Activity title. Task assignment resolves by matching the CRM Service owner_id to the mapped Pipedrive User. Open tasks are imported as open Activities; completed tasks migrate with their original completion timestamp.

CRM Service Events map to Pipedrive Activity records with type=meeting. StartDateTime and EndDateTime transfer to the Activity start and end timestamps, and Location transfers to the location field. Attendee associations migrate as Person Activity participants linked by email match.

CRM Service Notes map to Pipedrive Notes attached to the parent Person or Organization. We resolve the parent object by matching the Note's WhatId or WhoId to the migrated CRM Service record. Note body and rich text content migrate as-is; image attachments in CRM Service Notes require separate ContentDocument export and re-attach in Pipedrive.

CRM Service Attachments (stored as Attachment or ContentDocument objects) require separate export via API to a staging location before import. Files are uploaded to Pipedrive using the Files API and linked to the parent Person or Organization via the object_id reference. We flag files exceeding Pipedrive's storage limits during scoping and recommend archiving large files externally.

CRM Service Campaign records do not have a native Pipedrive equivalent. We map Campaigns to a custom field crm_service_campaign__c on Person records, populating it with the Campaign Name. Campaign Member status (Sent, Responded, Converted) migrates as additional custom fields on the Person. For organizations using Campaigns for reporting, we recommend rebuilding them as Pipedrive Filters.

CRM Service custom objects with independent schemas map to Pipedrive custom fields on Person, Organization, or Deal depending on the object's primary relationship. We create custom fields in Pipedrive matching the data type of the source field, with the original field label preserved in the field name. Fields that reference other CRM Service objects require a custom field lookup approach in Pipedrive or denormalization to a text field. All custom field definitions are deployed to Pipedrive before any data import.

CRM Service multi-select picklist values that exceed Pipedrive's 255-character concatenated limit require a special mapping strategy. We export the full value set during scoping, flag fields where the concatenated length exceeds the limit, and prioritize active values. Excluded values are documented in the mapping notes for manual handling by the customer's admin post-migration.