Migrate from Dashly to Salesforce Sales Cloud

Dashly Leads with qualification indicators (company name populated, multiple conversations, meeting booked) map to Salesforce Contact attached to an Account. Leads without qualification signals (anonymous or single-message visitors) map to Salesforce Lead. We compute the split using Dashly's conversation_count, company_association, and any custom qualification score properties, and preserve the original Dashly Lead ID in a custom field dashly_lead_id__c on both Lead and Contact for audit and reconciliation.

Dashly Company records map directly to Salesforce Account. The company domain and industry fields map to Account Website and Industry. Custom company properties migrate to Account custom fields. We create the Account before any Contact import so that the AccountId Lookup is satisfied at insert time.

Dashly Conversations migrate to Salesforce Case if the destination org includes Service Cloud licensing, using Case Status and Record Type to represent conversation state (open, pending, resolved). If Service Cloud is not licensed, Conversations migrate as Activity Task records with a custom conversation_status__c picklist. Conversation metadata (source channel, assignee, created timestamp) transfers as Case or Task fields.

Dashly Messages embedded within Conversations migrate to Salesforce EmailMessage records (for chat-to-email continuity) or Task records (for activity timeline display). Author attribution (agent vs visitor) preserves in the sender field. We link each Message to the parent Case or Task by resolving the Dashly conversation_id at migration time. Timestamps are preserved on ActivityDate or CreatedDate as applicable.

Dashly User accounts (agents and admins) map to Salesforce User by email address match. Agent roles and permission levels export as structured metadata. Any Dashly User without a matching Salesforce User is held in a reconciliation queue 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 Dashly's JSON schema. We export the full bot configuration as structured JSON including trigger rules, conditional branches, message content, and delay actions. There is no direct Salesforce Flow equivalent for visitor-facing chatbot logic; the exported config and mapping guide serve as the blueprint for rebuilding in Salesforce Einstein Bots, Flow, or a third-party bot platform.

Triggered messages define automated outbound sequences tied to visitor behavior or time delays. We export the trigger rules, message content, delay settings, and audience filters as structured automation data. Salesforce Flow or Sales Engagement tools (High Velocity Sales, Sales Cloud Engagement) serve as the rebuild target; the exported config documents the intent and sequencing for the customer's admin or a Salesforce partner to implement.

Dashly Knowledge Base articles (title, body content, SEO settings, category associations) migrate to Salesforce Knowledge Articles if Service Cloud is licensed, using Article Type and custom fields to preserve SEO metadata and category structure. If Knowledge is not available, articles migrate as a custom object with rich-text body and category picklists. Deep SEO field mapping (meta title, meta description, URL slug) is preserved as custom fields on the destination article record.

Tags applied to Leads, Conversations, or Companies export as flat label arrays. We map them to Salesforce custom multi-select picklist fields on the target object. For tagging strategies used for content classification, we map to Salesforce Topics with TopicAssignment records. The customer chooses the tag strategy during scoping.

Dashly per-account custom properties on Leads are inventoried during discovery with data type, values, and usage frequency. We map them to Salesforce custom fields using type-appropriate Salesforce field types (text, number, date, picklist, checkbox, URL). Custom properties present on more than 30 percent of records are flagged as high-priority mappings; low-frequency or empty custom properties are mapped but flagged for the customer's admin to validate post-migration.

Dashly custom company properties map to Salesforce Account custom fields. Domain and industry standard fields serve as anchors; custom fields carry over as typed Salesforce fields. Dedupe is handled by domain match to Account Website.

Dashly conversation assignee data and routing rules export as configuration data. We map assignee email to Salesforce User and routing conditions to Assignment Rules on Case (or Task if no Service Cloud). The exported routing config documents the original condition logic (round-robin, load-based, skill-based) for the customer's admin to implement as Salesforce Case Assignment Rules or Omni-Channel Routing.

Visitor session data (page views, referrer, UTM parameters, session duration) is ephemeral analytics aggregated by Dashly's engine and is not migratable as structured records. We flag this as out-of-scope in the discovery document. Customers needing visitor behavior data retain it in Dashly for reporting until contract expiry or configure a separate analytics integration (Google Analytics 4, Mixpanel) to the Salesforce-powered website.