Migrate from Dashly to HighLevel

Dashly Leads map directly to GoHighLevel Contacts. Standard properties (name, email, phone, custom fields) migrate 1:1 to Contact fields. Dashly's conversation history attaches to the Lead as threaded Messages; we reconstruct this as a series of Notes and Tasks in GoHighLevel's Contact activity timeline, preserving the original message timestamps and participant attribution. Dashly tags on Leads migrate to GoHighLevel Contact tags.

Dashly Conversations are top-level threads with metadata (status, assignee, source channel, timestamps). Since GoHighLevel has no Conversation object, we store conversation metadata as Notes on the Contact record with a structured body (channel, assignee, status, opened_at, closed_at) and thread each message under the same Note or as a related Task sequence. We use the Dashly conversation ID as a reference in the Note body for auditability.

Each Dashly Message (sender, body, timestamp, delivery channel) migrates to a GoHighLevel Note attached to the parent Contact. We preserve sender attribution (agent name or visitor identifier), message body, and timestamp. For multi-message threads, we order Notes by created_at timestamp to maintain conversation flow. Agent-sent messages are flagged in the Note body so the customer's team can distinguish inbound from outbound.

Dashly Company records map to GoHighLevel Companies with standard fields (name, domain, industry, custom properties) migrated 1:1. We use the Dashly Company ID as an external reference field and link associated Contacts to the Company via GoHighLevel's Contact-to-Company relationship. If no matching Company exists in GoHighLevel at migration time, we create it before Contact import.

Dashly User accounts (support agents and admins) map to GoHighLevel Users by email match. We extract every distinct Dashly user referenced on Conversation assignees and Message sender fields, match by email against the GoHighLevel destination User table, and flag any Dashly users without a matching GoHighLevel User for the customer's admin to provision before migration completes.

Dashly Leadbots are automation configs with trigger conditions, dialogue trees, and action sequences stored in Dashly's JSON schema. We export the complete bot configuration as structured JSON, but because no destination platform shares the same automation schema, the logic must be manually recreated in GoHighLevel's workflow builder. We provide the exported config files and a mapping guide that maps each Dashly trigger type (page visit, time on site, button click) to an equivalent GoHighLevel workflow trigger (Form Submitted, Tag Added, Custom Value Changed).

Dashly triggered message rules define automated outbound sequences tied to visitor behavior or time delays. We export the trigger rules and message content as structured JSON, but the automation must be manually rebuilt in GoHighLevel's workflow builder. We provide a written inventory of each triggered message with its trigger conditions, delay logic, message body, and recommended GoHighLevel equivalent (e.g., Workflow with Time Delay + Send Email/SMS action).

Tags applied to Dashly Leads, Conversations, or Companies export as flat label arrays. We preserve all tag assignments and map them to GoHighLevel's tagging system on the corresponding record type. If a tag does not exist in GoHighLevel at migration time, we create it during migration.

Dashly custom fields on Leads and Companies are defined per-account. We inventory all custom properties during discovery, including data types (text, number, date, checkbox, dropdown). We pre-create equivalent custom fields in GoHighLevel before data import, matching data types as closely as GoHighLevel's field types allow (text maps to Text, number to Number, date to Date, checkbox to Checkbox, dropdown to Dropdown).