Migrate from Copper to Pipedrive

Copper People map directly to Pipedrive Person records. Email, phone, address, and name fields migrate 1:1. The Copper People-to-Company relationship migrates as a Person-to-Organization link in Pipedrive, resolved at migration time using the Company slug. We use Person email address as the dedupe key to prevent duplicate Person records during import.

Copper Companies map to Pipedrive Organizations. The Company domain name populates the Organization's website field. Organization is created before any Person import so the Organization lookup is satisfied at Person insert time. Copper's Industry, phone, and address fields map to Pipedrive Organization standard fields.

Copper Opportunities migrate to Pipedrive Deals. The Opportunity name becomes the Deal title, monetary value maps to Pipedrive's weighted value field, and the Copper Pipeline Stage maps to a Pipedrive Stage within the destination pipeline. We pre-create Pipedrive pipelines and stages to match Copper's pipeline configuration before migration begins.

Each Copper pipeline becomes a Pipedrive Pipeline. Copper's stage names, order, and stage-specific probability percentages map to Pipedrive Stage names, positions, and probability values. If Copper uses multiple pipelines (Basic tier and above), we replicate each as a separate Pipedrive Pipeline with its own stage set. Stage probability values round to Pipedrive's integer range.

Copper's separate Leads object has no direct Pipedrive equivalent since Pipedrive Persons serve as both leads and contacts. We map Copper Lead records to Pipedrive Person records and preserve the original Copper Lead_Status in a custom field copper_lead_status__c. If the customer used Copper's Lead scoring, we map it to a custom field copper_lead_score__c on Person.

Copper Tasks migrate to Pipedrive Activity records of type Task. Due date, assignee (resolved via email match to Pipedrive User), status, and related record (Person, Organization, or Deal) map directly. The Copper Task-to-Project relationship does not transfer because Pipedrive has no native Projects object; we flag Tasks that were Project-linked for customer review.

Copper Projects have no native Pipedrive equivalent. We map Projects to a Pipedrive Activities-based grouping using Activities with a custom field project_name__c to retain the project context. Associated Copper Tasks link to the corresponding project Activity. The customer may alternatively choose to treat Projects as Pipedrive Deal labels or to use a third-party project integration post-migration.

Copper Activities map by type: call engagements become Pipedrive Activity type Call, meeting engagements become Activity type Meeting, note engagements become Activity type Note, and email engagements become Activity type Email. Each Activity is linked to its parent Person or Organization in Pipedrive. We preserve the original Copper activity timestamp and body text. Email content migrates as Activity notes where Pipedrive plan supports it.

Copper custom fields on People, Companies, Opportunities, Leads, and Tasks migrate to Pipedrive custom fields. We inspect Copper's Custom Field Definitions API during discovery to enumerate all custom fields, determine Pipedrive-compatible field types (text, number, date, dropdown, checkbox, etc.), pre-create them in Pipedrive via API before record import, and map values field by field. Custom field API names from Copper carry over as Pipedrive field keys with a copper_ prefix to avoid naming collisions.

Copper tags are flat labels applied to People, Companies, and Opportunities. We map them to Pipedrive Activity label fields on the target record. If the customer uses tags for segmentation, we may alternatively map them to a multi-select custom field in Pipedrive. The customer chooses tag strategy during scoping.

Copper Owners map to Pipedrive User records. We resolve by email match. Any Copper Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Pipedrive's User must be active and assigned the correct role for Activity ownership to resolve correctly.