Migrate from Concord CRM to Pipedrive

Concord CRM Company records map directly to Pipedrive Organization. The Concord company name becomes the Organization name field. We export Companies first in the migration sequence because Concord Contacts reference company_id as a foreign key; resolving that lookup before Contact import prevents orphaned organization associations. Website, industry, phone, and address fields map to their Pipedrive Organization equivalents. Multiple Concord Companies per customer domain are flagged for deduplication review during scoping.

Concord CRM Contact records map to Pipedrive Person. We resolve the Concord company_id to the corresponding Pipedrive Organization id using the pre-exported company mapping table. Name, email, phone, job title, tags, and custom fields migrate directly. Concord's contact_type or tags field maps to Pipedrive Person label or the label API endpoint. Any Contact without a matching Organization is linked to a default organization or held in a reconciliation queue for the customer's admin to resolve.

Concord CRM Deals map to Pipedrive Deals with pipeline and stage name reconciliation. Concord's deal stage names (e.g. Prospecting, Qualification, Proposal) must map to the target Pipedrive pipeline's stage labels. We configure the Pipedrive pipeline and stages before migration so that the stage name mapping is deterministic at import time. Deal value, expected close date, owner (by email resolution to Pipedrive User), and custom fields migrate directly.

Concord's pipeline stages are stored as deal properties and export as stage names. We pre-create a Pipedrive pipeline matching the Concord stage sequence and configure each stage with the correct name and probability percentage. If the customer uses multiple Concord pipelines, we create corresponding Pipedrive pipelines and assign the correct pipeline to each Deal during import using the pipeline_id field.

Concord supports multiple deal pipelines. We map each Concord pipeline to a Pipedrive pipeline with matching stage sequence and probability assumptions. Pipedrive's visual pipeline interface and drag-to-move deal cards replace Concord's table-based deal view. Pipeline configuration happens before any Deal data is imported to ensure all Deals land in the correct pipeline.

Concord CRM Products (name, price, SKU, description) map to Pipedrive Products. Product items can be linked to Deals in Pipedrive as line items. We export Concord Products before Deals so that product references resolve at Deal import time. Products without a Deals association migrate as standalone product catalog entries.

Concord CRM Activities (calls, meetings, tasks, notes) map to Pipedrive Activities with the type field determining the Pipedrive activity_type (call, meeting, task, note). We reconstruct the association back to the parent resource using Concord's resource_type and resource_id fields, mapping to the corresponding Pipedrive Person, Organization, or Deal. Activity date and notes migrate directly. Large activity histories (over 50,000 records) are chunked and sequenced with rate-limit handling against Pipedrive's API.

Concord CRM custom fields are fully accessible via API using field UUID as the key in request payloads. Boolean, date, select, text, and number field types have different payload formats that we transform to Pipedrive field types during import. We pre-create all custom fields in Pipedrive before migration begins, matching field labels and selecting the equivalent Pipedrive field type. Multi-select fields in Concord become multi-select picklist or checkbox fields in Pipedrive.

Concord CRM Users export via API with email, name, and role data. We resolve each Concord user by email to the corresponding Pipedrive User. Any Concord user without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on Deals, Contacts, and Activities resolve through this User mapping.

Concord CRM tags on Contacts, Companies, and Deals map to Pipedrive Labels. Tags export as comma-separated or multi-checkbox values and are split into individual Pipedrive Labels at import time. Labels are applied to the corresponding Person, Organization, or Deal record. Concord's tags used for segmentation or reporting are preserved as Pipedrive Labels for equivalent filtering.