Migrate from Dashly to Freshsales

Dashly Leads map directly to Freshsales Contacts. Standard properties (name, email, phone) migrate to Freshsales Contact fields. Custom Lead properties are inventoried during discovery, typed (text, number, date, dropdown), and created as Freshsales custom fields before migration. Email is used as the dedupe key. Dashly tags on Leads map to Freshsales Contact tags.

Each Dashly Conversation thread is decomposed into a Freshsales Task record holding conversation metadata (status, assignee, source channel, timestamps). The conversation's original status (open, resolved, pending) maps to Freshsales Task status values. The Dashly assignee maps to Freshsales Owner by email resolution. One Task is created per Conversation rather than one per message.

Individual Messages within a Conversation migrate as Freshsales Note records attached to the parent Task (via ContentDocumentLink). Each Note records sender (agent or visitor), body content, timestamp, and delivery channel as Note metadata. Author attribution is preserved in the Note title field. Message ordering is preserved by setting Note CreatedDate to the original Dashly timestamp.

Dashly Company records map directly to Freshsales Accounts. Standard fields (name, domain, industry) migrate to Account fields. Custom company properties are mapped to Freshsales custom Account fields. Dashly leads linked to a Company are associated to the migrated Account via Freshsales link_contact_to_account after Contact migration completes.

Dashly agent and admin accounts map to Freshsales Users by email match. Role and permission data is exported as a configuration record. Any Dashly agent without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import proceeds.

Dashly tags applied to Leads, Conversations, or Companies migrate as flat label arrays. Freshsales stores tags at the object level (Contact tags, Account tags, Deal tags) and we preserve all tag assignments per record. Tags used across multiple object types are exported separately per object type.

Dashly custom fields on Leads and Companies are inventoried during discovery with their data types and value distributions. We create matching Freshsales custom fields (custom_contact_fields, custom_account_fields) before migration, then map values during import. Custom properties with picklist-style values are created as Freshsales dropdown fields; multi-value properties become multi-select picklists.

Dashly Leadbots are exported as structured JSON configs containing trigger conditions, dialogue trees, and action sequences. We provide the exported config file and a mapping guide describing how each bot trigger and action maps to an equivalent Freshsales Workflow. The workflow rebuild is manual and outside automated migration scope.

Triggered message rules (behavior-based outbound sequences) are exported as JSON automation data. Freshsales Workflows use a different trigger-action model and must be rebuilt manually. We deliver the exported config and a step-by-step mapping guide for each triggered message sequence.

Dashly knowledge base articles (title, body, SEO settings, category) are exported as structured text with metadata. Freshsales does not include a native knowledge base; articles intended for agent reference should be migrated to Freshdesk if the customer licenses Freshdesk, or to a third-party knowledge base tool. We flag this decision during scoping.