Migrate from LionDesk to Microsoft Dynamics 365 Sales

LionDesk contacts migrate as Dynamics 365 Contact records. The primary company_id from LionDesk maps to Contact.ParentAccountId — the target Account must be created first so the lookup resolves. LionDesk contacts without a primary company land as Contacts with no ParentAccountId assigned; a default 'Unassigned' account record can be created to prevent orphaned contact scenarios.

LionDesk contacts whose status field reads 'Lead' or who have not yet transacted map to the Dynamics 365 Lead entity. Contacts who have a closed-won deal or a stage-value indicating a customer status map to Contact instead. The split logic uses the LionDesk deal stage history — if any associated deal reached 'Closed Won', the contact routes to Contact; otherwise, it routes to Lead for further Dynamics 365 qualification.

LionDesk company records migrate as Dynamics 365 Account records. The company's address fields map to Account.Address1_* address fields. LionDesk's parent_company_id relationship maps to Account.ParentAccountId, preserving company hierarchies. Where LionDesk allows multiple parent companies, Dynamics 365's single-parent model means we assign the most recently modified parent and surface additional parents as Account Contact Relationships.

LionDesk deal records map to Dynamics 365 Opportunity entities. The deal's pipeline field determines the Opportunity.SalesProcessId or Business Process Flow assignment. Each pipeline's stage values are mapped to the corresponding Opportunity Stage picklist options on the target Business Process Flow — if the destination Dynamics environment uses a standard Sales Process, stage values are mapped via the StageCode picklist. Probability and forecast category fields are re-applied based on Dynamics 365 stage definitions.

LionDesk's pipeline object becomes a Dynamics 365 Sales Process or Business Process Flow. Teams with multiple LionDesk pipelines may need corresponding Business Process Flows in Dynamics 365 to isolate stage sets per deal type. We deliver a pipeline-to-BPF mapping plan before migration runs so your Dynamics admin can pre-create the Business Process Flows and associate them with the appropriate entity (typically Opportunity).

LionDesk tasks migrate as Dynamics 365 Task records. The task's status field maps to the Dynamics Task.StatusCode picklist (values like 'Open', 'Completed', 'Deferred'). Original create timestamps are preserved in a custom datetime field since Dynamics 365 Task.CreatedOn is set at migration time. The task's regardingobjectid is set by matching the LionDesk record_id to the target entity in Dynamics.

LionDesk notes migrate as Dynamics 365 Annotation records (the 'Note' entity). The note's body text maps to Annotation.NoteText, and any file attachments are re-uploaded as Annotation.Attachment. Rich-text formatting in LionDesk notes is preserved as plain text in Dynamics 365 since Annotation does not support full HTML rendering. If the note contains embedded images, FlitStack downloads and rehosts them as Attachment documents.

LionDesk email engagement records map to the Dynamics 365 Email (activity) entity. The email's subject, body, from-address, and to-address fields migrate. LionDesk tracks emails sent via the platform's drip sequence engine; these migrate as Email records with a custom source field 'LionDesk_Drip_Sequence' for identification. Email body content is preserved but email templates used in sequences cannot be transferred — FlitStack exports the template definitions as HTML files for Power Automate rebuilds.

LionDesk's built-in calling and video email features produce engagement records that map to Dynamics 365 PhoneCall activity entities. Video email records (LionDesk's unique differentiator) are stored as ActivityMimeAttachment records linked to the PhoneCall or as custom Annotation records with a 'LionDesk_VideoEmail' type flag, since Dynamics 365 does not have a native video email construct. The original call duration and recording link are preserved in custom fields.

LionDesk SMS conversations migrate as Dynamics 365 PhoneCall records with a custom 'SMS' type field. The text content maps to PhoneCall.Description. Since Dynamics 365 Sales does not have a native SMS threading model, we preserve conversation context by grouping SMS records under a custom entity or by linking them to the parent Contact. SMS history is valuable for agent accountability and compliance audits.

LionDesk custom fields are created as solution-scoped custom fields in Dynamics 365 Sales with a 'new_' publisher prefix (or your organization's solution publisher prefix). The field data type from LionDesk (Text, Number, Date, Dollar Amt) determines the Dynamics 365 field type (Single-Line Text, Whole Number, Date and Time, or Currency). Custom fields are created in the target solution before the data load; we deliver a custom field creation manifest as part of the migration plan.

LionDesk drip campaigns and text sequences are automation logic with no direct Dynamics 365 equivalent. Dynamics 365 Sales does not include a native sequence engine — sequences are implemented via Power Automate flows or third-party sequence tools. FlitStack exports your LionDesk campaign definitions (step order, delay intervals, step types, content) as a structured JSON reference document that your Dynamics admin or Power Automate developer can use to rebuild sequences in the Microsoft ecosystem.

LionDesk workflow automations (task triggers, status-change rules, notification rules) do not migrate. Dynamics 365's automation engine is Power Automate (cloud flows) or the legacy Workflow tool — neither shares configuration patterns with LionDesk. We provide a workflow audit export listing every active LionDesk workflow with its trigger conditions and actions so your Dynamics team can rebuild them as Power Automate flows post-migration.