Migrate from Dashcord to Pipedrive

Dashcord Account records (standard Salesforce CRM object) map to Pipedrive Organization. The Account Name, Industry, Website, Phone, Billing Address, and any custom fields migrate directly. We use Organization name as the dedupe key. Dashcord's custom Account fields (Dashcord adds properties on top of the standard Salesforce object) are enumerated during schema discovery and created as custom fields in Pipedrive before import.

Dashcord Contact records map to Pipedrive Person objects. All standard Contact fields (Name, Email, Phone, Title, Department) migrate, as do Dashcord-specific custom fields discovered during pre-flight. Pipedrive Person supports a custom_label field which we use to store the original Dashcord lifecycle stage value so the marketing history is auditable in the destination CRM.

Dashcord Lead records (standard Salesforce Lead object with Dashcord custom fields) map to Pipedrive Lead. Pipedrive's Lead object is a separate record type that triggers automatic Person and Organization creation upon lead conversion. We preserve all custom fields including any Dashcord lead scoring fields. Note: Pipedrive API supports Lead import but not Lead export; we read from Salesforce and write into Pipedrive via the Pipedrive REST API.

Dashcord wraps Salesforce Campaigns for marketing automation. We export Campaigns and map campaign Name, Type, Status, StartDate, EndDate, and BudgetCost into Pipedrive as an Activity record with a custom campaign_type label. Campaign member rollup data (total members, responded count) is stored as custom fields on the Activity. Dashcord's campaign performance metrics (impressions, clicks) migrate as custom numeric fields if present in the Salesforce schema.

Campaign Members link Contacts and Leads to Dashcord Campaigns with status and timing data. We export all member records and create Activity records in Pipedrive linked to the corresponding Person (for Contacts) or Lead (for Leads). The campaign membership status values (Sent, Responded, Converted) are normalized and stored in a custom Activity status field. Pipedrive's Activity object does not have a native Campaign Member concept, so we implement this as a labeled Activity linked to the Person.

Dashcord stores event records as custom Salesforce objects whose field definitions vary by Dashcord package version. During pre-flight we introspect the Salesforce org metadata via the Tooling API to enumerate the active event object and its fields. We map event Name, StartDate, EndDate, Location, Event Type, and attendee count to Pipedrive Activity records with a custom event_type label. Any event-specific custom fields discovered in the schema are recreated in Pipedrive as custom Activity fields.

Dashcord assigns lifecycle stage values (Subscriber, Lead, MQL, SQL, Customer, Evangelist) stored as custom picklist fields on Lead and Contact. Pipedrive has no native lifecycle stage concept. We create a custom label field called dashcord_lifecycle_stage__c on Person and Lead, populate it with the raw stage values from Salesforce, and document the mapping so the customer's admin can assign Pipedrive label values that match their buyer journey model.

Dashcord assigns numeric or tiered lead scores stored as custom fields on Salesforce Lead records. We export the raw score values and map them to a custom Pipedrive Lead field called dashcord_lead_score__c. The Dashcord scoring model name or rule set reference (stored in a separate custom Dashcord object if present) is preserved as a text field dashcord_scoring_model__c for audit and rebuild reference.

File attachments on Dashcord records (stored in Salesforce ContentDocument or Attachment objects) are exported as binary data and re-attached to the matching Pipedrive record. Large attachments (over 10 MB) are chunked during upload via the Pipedrive API. Attachments linked to Dashcord custom event records are attached to the corresponding Pipedrive Activity record. We flag any attachment that exceeds Pipedrive's file size limits during pre-flight so the customer can decide whether to migrate or archive.

Dashcord tracks email sends, opens, and clicks via Salesforce Task and EmailMessage records linked to Contacts and Leads. We export EmailMessage body and headers, map them to Pipedrive Activity records of type email, and link each Activity to the target Person or Lead. Dashcord's campaign attribution metadata (CampaignId, CampaignMemberId) is preserved as custom fields on the Pipedrive Activity for marketing attribution continuity. Note: Pipedrive API exports emails from active users only; we flag any emails owned by inactive or departed users during pre-flight.

Dashcord surfaces Salesforce call, meeting, and task records in the activity timeline. We map Salesforce Task records (TaskSubtype = Call) to Pipedrive Activity of type call, preserving CallDurationInSeconds and disposition. Event records map to Pipedrive Activity of type meeting with StartDate, EndDate, and Location. Standard Task records map to Pipedrive Activity of type task. ActivityDate timestamps are preserved to maintain timeline ordering in Pipedrive's activity feed.

Any custom fields added by the Dashcord package or created on top of the Salesforce org are stored as Salesforce custom fields. We read field metadata via the Salesforce Tooling API during pre-flight, enumerate all custom properties on each object, create matching custom fields in Pipedrive (of appropriate type: text, number, date, dropdown, checkbox), and map the values during migration. Custom Dashcord fields that reference other Salesforce records (lookups) are resolved to Pipedrive entity IDs at migration time.