Migrate your Dashly data

Leads are the core contact records in Dashly, holding standard properties (name, email, phone) and custom attributes. We migrate all standard and custom Lead fields 1:1, preserving property values and metadata.

Conversations are top-level threads linked to Leads. Each conversation carries metadata (status, assignee, source channel, timestamps). We preserve the full conversation hierarchy and thread order during export.

Messages are embedded within Conversations. Each message records the sender (agent or visitor), body content, timestamp, and delivery channel. We migrate all messages preserving author attribution and chronological order.

Dashly supports Company records that can be associated with Leads. Standard fields (name, domain, industry) and any custom company properties are migrated as flat or nested records depending on the destination schema.

User accounts represent support agents and admins with roles, email addresses, and availability settings. We export user records including their assigned conversations and permission levels.

Leadbots are automation configs with trigger conditions, dialogue trees, and action sequences defined in Dashly's JSON schema. We export the bot configuration as structured JSON and map it to equivalent automation constructs in the destination platform.

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. Manual mapping to the destination's automation engine is required.

Articles are stored with title, body content, SEO settings, and category associations. We export articles as structured text with metadata. Deep SEO field mapping depends on whether the destination platform supports equivalent fields.

Visitor session data (page views, referrer, UTM parameters, session duration) is ephemeral and aggregated by Dashly's analytics engine. It is not meaningfully migratable as structured records to a destination CRM and is excluded from migration scope.

Tags applied to Leads, Conversations, or Companies are exported as flat label arrays. We preserve all tag assignments and map them to the destination's tagging or labeling system.

Custom fields on Leads and Companies are defined per-account. We inventory all custom properties, their data types, and values during the discovery phase, then map them to equivalent custom fields in the destination.

Conversation assignee data maps to agent ownership or team assignment fields in the destination. Routing rules (which assign conversations to specific agents or teams) are exported as configuration data and manually rebuilt.