Migrate from Dashly to Twenty CRM

Dashly Leads map to Twenty CRM People records. Standard properties (name, email, phone, city) migrate directly. Custom Lead properties (custom_attributes in the Dashly API) require pre-creation as custom fields in Twenty Settings → Data Model before import; we inventory all custom properties during discovery, create the equivalent Twenty fields during the schema phase, then map values during load. The dashly_lead_id is preserved in a custom field for source reference and future sync.

Dashly Conversations are top-level threads with status, assignee, source channel, and timestamps. Each conversation maps to a Twenty Task record linked to the corresponding People record. Conversation status (open, resolved, pending) maps to Twenty Task status values. Assignee maps via email lookup to the Twenty User (member) who must be invited before import. Source channel and first-contact timestamp are preserved as custom fields on the Task.

Dashly Messages are embedded within Conversations. Each message records sender type (agent or visitor), body content, timestamp, and delivery channel. Messages are exploded from their parent Conversation into individual Task activity entries in Twenty, preserving thread order via the original timestamp. We maintain the participant attribution (agent name, visitor identifier) in the message body and a custom field for sender_type.

Dashly Company records (name, domain, industry, and custom properties) map directly to Twenty CRM Company records. The Company must exist before any Lead import that references it via the company association field. We resolve company lookups during the transform phase by matching domain or name against the Company table before Leads are loaded.

Dashly User accounts (agents and admins with email, role, and availability) map to Twenty CRM Members. We resolve by email match. Per Twenty's migration documentation, Members must be invited and accept their invitation before Owner lookups can resolve on imported records. We flag any Dashly User without a matching Twenty Member for the customer's admin to provision before record import resumes.

Dashly Leadbots are automation configs with trigger conditions, dialogue trees, and action sequences stored in JSON. We export each Leadbot configuration as structured JSON with its trigger rules, decision branches, and message sequences. There is no equivalent bot-builder in Twenty CRM, so we cannot auto-migrate these. We deliver the exported JSON config files with a mapping guide that describes the trigger conditions and recommended Twenty Workflow equivalents for the customer's admin to rebuild 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. We cannot auto-migrate these to Twenty because Twenty's Workflow model uses different trigger types and action definitions. We deliver a written inventory of every active Triggered Message with its behavioral trigger, audience conditions, message template, and a recommended Twenty Workflow configuration for the customer's admin to recreate.

Dashly Knowledge Base articles (title, body content, SEO settings, category associations) export as structured text with metadata. Twenty CRM has no native knowledge base module, so articles do not migrate as navigable pages. We export articles as formatted documents (HTML or Markdown) that the customer can host in their own documentation system or as Note records in Twenty for reference. Deep SEO field mapping is not applicable in Twenty's schema.

Tags applied to Leads, Conversations, or Companies in Dashly export as flat label arrays. We preserve all tag assignments and map them to Twenty custom fields configured as multi-select picklists or text fields, depending on the customer's tagging strategy decision during scoping. Tags used for conversation categorization map to Task tags; tags used for lead segmentation map to People custom fields.

Custom fields defined on Dashly Leads are inventoried during discovery with their data types. We create the equivalent custom fields in Twenty Settings → Data Model before import begins. Per Twenty's migration documentation, fields must exist before import; we coordinate the schema creation sequence so that every Dashly custom property has a corresponding Twenty field ready at load time. Data type mapping follows standard conventions (text to text, number to number, date to date).