Migrate from Dashly to Microsoft Dynamics 365 Sales

Dashly Leads map to Salesforce-style Lead and Contact in Microsoft Dynamics 365 Sales . We use Dashly lead properties (lifecycle stage, lead score, conversation count) to determine the split: prospects with no closed deal map to Lead; leads with active conversations or sales-accepted status map to Contact with an Account parent. We preserve all Dashly custom properties as custom fields on the destination record, and tag assignments migrate as custom fields or text arrays depending on the Dynamics field type configured during schema design.

Dashly conversations are top-level threads with metadata (status, assignee, source channel, timestamps) and a message array. We split each conversation into a parent Task record holding the conversation metadata and status, with child EmailMessage records for each message. The Task's Subject is derived from the conversation's first message or the lead's name. Assignee resolution maps Dashly owner email to the Dynamics User record by email match.

Each Dashly message is migrated as an EmailMessage record linked to the parent Task. The message sender maps to the EmailMessage From field (agent or visitor), the body to the EmailMessage Body field, and the timestamp to EmailMessage CreatedOn. Participant attribution is preserved in EmailMessage To (the lead) and From (the agent user) fields. Thread ordering is maintained by the parent Task's ActivityId.

Dashly Company records map directly to Microsoft Dynamics 365 Sales Account. Standard fields (name, domain, industry) migrate to Account Name, Website, and Industry. Any custom company properties migrate as custom Account fields. The Account record is created before Contact import so that the parent Account lookup is satisfied at insert time.

Dashly user accounts (agents and admins with roles and email addresses) are resolved by email match against the Microsoft Dynamics 365 Sales User table. Any Dashly user without a matching Dynamics User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Conversation assignee data then resolves correctly against the provisioned User records.

Dashly Leadbots are structured automation configurations (trigger conditions, dialogue trees, action sequences) stored as JSON. We export the complete bot configuration and deliver it as a structured JSON file with a mapping guide describing the trigger logic, branching conditions, and recommended Power Automate or Dynamics workflow equivalents. The automation rebuild is manual and outside the automated migration scope.

Triggered message rules define automated outbound sequences tied to visitor behavior or time delays. The trigger rules and message content are exported as structured automation data. Because Microsoft Dynamics 365 Sales and Power Automate use different event models (record-change vs visitor-behavior-triggered), we document the current trigger conditions and message content for manual rebuild in the target system.

Dashly articles (title, body content, SEO settings, category) are exported as structured text with metadata. We map them to Microsoft Dynamics 365 Sales Knowledge Article entities where the customer's org has the knowledge base feature enabled. Deep SEO field mapping depends on whether the destination Dynamics org includes the knowledge management module; if not, articles are delivered as a structured export for manual import into the customer's preferred knowledge base platform.

Tags applied to Leads, Conversations, or Companies are exported as flat label arrays. We preserve all tag assignments and map them to a multi-select text field on the destination record, or to a custom tagging entity if the customer requires tag-based segmentation in Dynamics. The tag strategy is confirmed during scoping based on how tags are used in Dashly reporting.

Dashly custom fields on Leads and Companies are inventoried during discovery with their data types and values. We map each custom property to an equivalent custom field in Microsoft Dynamics 365 Sales , creating the field in the destination org before migration begins. Custom property data types (text, number, date, checkbox, dropdown) are mapped to the closest Dynamics field type (single-line text, whole number, date and time, two options, option set).