Migrate from Dashly to monday CRM

Dashly Leads map to Monday.com CRM People items on a Contact board. Standard properties (name, email, phone) become text columns; custom Lead properties map to Monday.com Column types (text, date, number, dropdown, checkbox). The email address serves as the dedupe key during import. We preserve all custom field values as-is and create matching columns in Monday.com before migration begins.

Dashly Company records map to Monday.com CRM Company items (or an Account-equivalent board). Domain from Dashly maps to a Website text column. Standard and custom company properties map to Monday.com columns matching their data type. Companies are created before Leads so that any Lead-Company association can be resolved as a LookUp column relationship in Monday.com.

Dashly Conversations are top-level threads linked to Leads. Monday.com has no native conversation thread model, so we create a board (or board section) for conversation history and map each Dashly Conversation to an Item. The conversation status (open, pending, resolved) maps to a Status column; the assignee maps to a Person column. The conversation ID is stored in a text column for traceability.

Dashly Messages within Conversations carry sender attribution, body content, timestamp, and delivery channel. We flatten the message thread into a chronological notes entry per message on the related Item in Monday.com, preserving the agent name, timestamp, and channel (chat, email). The message content becomes a structured text block appended to the Item's notes section in date-sorted order.

Dashly User accounts (agents, admins) are exported with email, name, and role. We map Dashly Users to Monday.com team members by email match. Any Dashly User without a matching Monday.com account is flagged in a reconciliation queue for the customer to provision before Leads and Conversations are imported, since assignee references require a valid Monday.com User.

Dashly Leadbots store automation configs with trigger conditions, dialogue trees, and action sequences in a JSON schema. Monday.com Automations support basic if-then triggers but do not replicate the dialog-tree branching model. We export the Leadbot configuration as structured JSON and deliver it alongside a mapping guide that describes the trigger logic and recommended Monday.com Automations equivalent. The automation rebuild is not automated; the customer's admin recreates the logic manually.

Dashly Triggered Messages define automated outbound sequences tied to visitor behavior or time delays. The trigger rules and message content are exported as structured automation data. Monday.com does not have a behavioral-triggered message sequence equivalent. We deliver the exported rule set and message content so that the customer's team can recreate sequences using Monday.com Automations or WorkMotion; this is not automated migration scope.

Dashly Knowledge Base articles carry title, body content, category, and SEO settings (meta title, meta description). We export articles as structured text and import them into Monday Docs, preserving title, body, and category as tags or labels. Deep SEO field mapping (meta title, meta description) requires manual transfer since Monday Docs does not expose per-article SEO fields natively.

Dashly Tags applied to Leads, Conversations, or Companies are exported as flat label arrays. We map each tag to Monday.com Labels or a Tags column on the relevant board item. All tag assignments are preserved against the corresponding Lead, Conversation, or Company Item in Monday.com.

Dashly custom properties on Leads and Companies are defined per-account via the API. We inventory all custom properties with their data types during discovery, then create matching custom columns in Monday.com before data import. Text properties become text columns, dates become date columns, numeric values become number columns, and multi-select or checkbox properties become dropdown or checkbox columns respectively.