Migrate from Dashly to Mailchimp

Dashly Leads map to Mailchimp Contacts in a single Audience. Standard properties (name, email, phone, company) map directly to Mailchimp's First Name, Last Name, Email Address, and Phone merge fields. Custom Lead properties migrate to Audience-specific merge fields. We validate all email addresses against RFC 5322 format before import and flag bounces or malformed addresses for the customer to resolve. The Dashly Lead created_at and updated_at timestamps migrate as custom merge fields for audit purposes.

Dashly Tags (applied to Leads, Companies, or Conversations) migrate as flat label arrays into Mailchimp Tags. We preserve all tag assignments per contact. Mailchimp Tags are per-Audience, so if the migration targets a single Audience, all tags land in one namespace. Tagging logic (what gets tagged at import time) is preserved as a tag-assignment map delivered alongside the contact import.

Dashly custom Lead properties map to Mailchimp merge fields scoped to the target Audience. We inventory all Dashly custom properties during discovery, map their data types to Mailchimp-supported types (text, number, date, phone, address, URL), and flag any properties that exceed Mailchimp's type constraints. Array-type Dashly properties (e.g., multi-select) convert to comma-separated text in Mailchimp. Object-type properties flatten to text or split across multiple merge fields.

Dashly Company records (name, domain, industry, custom company properties) do not have a native Mailchimp equivalent. We denormalize company data onto the Contact record, mapping company name to a Company merge field and any custom company properties to additional merge fields. Multiple Dashly Leads associated with one Company share the same denormalized company fields in Mailchimp. If the customer requires a company-level data model, we recommend Mailchimp's standalone CRM integration or a third-party CRM sync post-migration.

Dashly Conversation threads (the top-level inbox threads linked to Leads) have no Mailchimp equivalent. Mailchimp tracks email engagement events (opens, clicks, unsubscribes) per contact but does not store conversation history or message threads. We do not migrate conversations. This is a known data loss item that we flag during scoping. The customer should archive conversation export files from Dashly before account deactivation if conversation history retention is required.

Dashly Messages (individual exchanges within Conversations, with sender attribution, body content, and timestamp) have no Mailchimp equivalent. Mailchimp does not support chat or messaging history. We do not migrate message records. Agent-to-visitor conversation logs and visitor message history are excluded from the migration scope.

Dashly Leadbot configurations (automation rules with trigger conditions, dialogue trees, and action sequences defined in Dashly's JSON schema) have no Mailchimp equivalent. Mailchimp's Customer Journey automations use a different trigger and action model. We export the Leadbot configuration as structured JSON for the customer's admin to use as a reference when rebuilding logic in Mailchimp Automations. The automation rebuild is not automated and falls outside migration scope.

Dashly Triggered Message rules (automated outbound sequences tied to visitor behavior or time delays) have no direct Mailchimp equivalent despite Mailchimp also using the term automation. Dashly triggers fire within a live chat session context; Mailchimp triggers fire email sends within an audience journey. We export the triggered message rules as structured automation data and deliver a mapping guide to Mailchimp's Customer Journey Builder for manual rebuild. Rebuild scope is excluded from the migration contract.

Dashly Knowledge Base Articles (with title, body content, SEO settings, and category associations) have no Mailchimp equivalent. Mailchimp does not host article or knowledge base content. We export articles as structured text files for the customer's admin to republish on a dedicated knowledge base platform (e.g., Notion, Zendesk, HelpCenter) if required.

Dashly Visitor Session data (page views, referrer, UTM parameters, session duration, behavioral flags) is ephemeral and aggregated by Dashly's analytics engine. It is not migratable as structured records to Mailchimp. We do not export visitor sessions. Email engagement data (opens, clicks, unsubscribes) recorded within Mailchimp after migration provides a fresh behavioral dataset.