Migrate from Dashly to Pipedrive

Dashly Lead records map to Pipedrive Person. Standard properties (name, email, phone, company) migrate directly. Dashly custom properties on Leads map to Pipedrive custom Person fields, which can be created during import via the mapping step. Email address serves as the dedupe key. The Person is created before any related Organization import so the Organization lookup is satisfied at insert time.

Dashly Company records map to Pipedrive Organization. Standard fields (name, domain, industry) migrate directly. Dashly custom company properties map to Pipedrive custom Organization fields. The Organization is inserted before related Person records so that the person_org_id lookup is resolved at migration time. Companies with no name default to the domain value.

Dashly Conversations attached to a Lead map to Pipedrive Activities linked to the migrated Person. Each conversation's status, assignee, source channel, and creation timestamp map to Activity subject, status, owner, and due date. Multiple Dashly conversations for a single Lead become multiple Activity records on the same Person in Pipedrive. The conversation thread metadata (total message count, first response time) migrates as custom Activity fields.

Dashly Messages within a Conversation map to Pipedrive Note records attached to the migrated Person. Each message's sender type (agent or visitor), body content, timestamp, and channel migrate as Note fields. Notes are linked to the Person via ContentDocumentLink. Message author attribution is preserved in a custom Note field. Messages are ordered by timestamp to maintain conversation sequence.

Dashly User accounts (agents and admins) map to Pipedrive User records by email address match. We resolve Dashly assignee data on Conversations and Messages to the corresponding Pipedrive User. Any Dashly User without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Dashly supports associating a Company with a Lead. In Pipedrive, this maps to the Person-Organization relationship (person_org_id). We resolve the association at migration time using the company_id on the Dashly Lead record and the migrated Organization ID. This is a configuration step that requires both Lead and Company records to be inserted first.

Tags applied to Dashly Leads, Companies, or Conversations are exported as flat label arrays. We map these to Pipedrive Labels (person_label, org_label, deal_label) or custom multi-select picklist fields depending on which Dashly object the tag originates from. The customer chooses the labeling strategy during scoping. Tags with no Pipedrive equivalent are preserved in a custom text field.

Dashly custom properties defined on Lead records are inventoried during discovery, including data type (string, number, date, boolean, dropdown). We create matching Pipedrive Person custom fields before migration and map all values during import. Dropdown-type custom properties in Dashly map to Pipedrive select or multiselect fields with the same option set.

Dashly custom properties defined on Company records follow the same process as Lead custom properties but map to Pipedrive Organization custom fields. Data type mapping is consistent: string becomes text, number becomes numeric, date becomes date, boolean becomes checkbox.

Dashly Leadbots are structured automation configs stored as JSON with trigger conditions, dialogue trees, and action sequences. We export the full bot configuration as a structured JSON file. Because Pipedrive's automation schema is different, the Leadbot logic cannot be migrated automatically. We deliver the exported config and a mapping guide describing which Pipedrive Workflow triggers, conditions, and actions correspond to each Leadbot component. The customer's admin rebuilds Leadbots in Pipedrive Workflows post-migration.