Migrate from Dialytica - Marketing Automation Platform to Microsoft Dynamics 365 Sales

Dialytica Contacts map to Microsoft Dynamics 365 Sales Contacts when the record represents an identified person with phone and name data. If the Dialytica contact has not been qualified into a sales relationship (no deal association), we map to Lead for Dynamics customers using the Lead-to-Contact convert model. We preserve Dialytica custom fields (phone numbers, campaign assignment dates, disposition codes) as custom fields on the Dynamics Contact or Lead. Phone numbers migrate to the Telephone1, Telephone2, or Mobile fields per type, and campaign assignment history migrates as Note records or custom activity fields.

Dialytica Call Campaign objects map to Microsoft Dynamics 365 Sales Campaign. We preserve campaign name, status (active/paused/completed), scheduled start and end dates, targeting criteria (as text in the Campaign Description or a custom field), and the number of contacts assigned. Call scripts and dial plan text from Dialytica migrate as Note records attached to the Dynamics Campaign. Note that Dynamics Campaigns track marketing activities but do not execute outbound dialing; the customer rebuilds dial sequences in a compatible dialer or Power Automate flow post-migration.

Dialytica SMS Campaigns map to a separate Microsoft Dynamics 365 Sales Campaign to preserve the distinction between call and SMS channels. We link both campaigns to the same Dialytica contact set so that contacts touched by both channels are associated with both Dynamics Campaigns. SMS template body text and merge field structures migrate as Note records attached to the SMS Campaign; variable placeholders are preserved as-is for the customer's admin to re-apply in the SMS routing tool.

Dialytica Call Records migrate to Microsoft Dynamics 365 Sales Task with TaskSubtype set to Call. Duration (CallDurationInSeconds), disposition code, agent assignment (mapped to Dynamics User), and the Dialytica call timestamp migrate to custom Task fields. AI-evaluated call metadata (sentiment scores, talk-to-listen ratios generated by Dialytica's LLMs) cannot be stored in standard Dynamics fields; we create custom fields on the Task entity to preserve these values. Call recording URLs do not migrate as playable files; we store the URL as a text field for manual reference if the recordings are accessible.

Dialytica QA Reviews are supervisor evaluations tied to specific Call Records. We map review scorecards and free-text supervisor notes to Dynamics Note records attached to the corresponding Task (the Call Record). For customers with high QA review volume, we recommend a custom QA_Review entity in Dynamics with a lookup to Task, structured score fields (numeric), and a long-text notes field, rather than relying on generic Notes. The custom entity approach requires schema deployment in the Dynamics environment before migration and is scoped as a configuration task during discovery.

Dialytica SMS Activity logs (individual message events with delivery status, timestamp, phone number, and campaign reference) migrate to Dynamics Activity records. Since Microsoft Dynamics 365 Sales does not have a native SMS activity type in standard objects, we map SMS to Task with TaskSubtype=Task and a custom field sms_direction__c (inbound/outbound) plus sms_status__c (delivered/failed/pending). Campaign linkage is preserved via a custom campaign lookup on the Task record. SMS template merge field usage migrates as a Note attached to the campaign for reference.

Dialytica Agent and user accounts map to Microsoft Dynamics 365 Sales User records. We match by email address. Agent roles and active/inactive status migrate as Dynamics Security Roles and IsActive flag. Any Dialytica Agent without a matching email in the destination Dynamics org is held in a reconciliation queue for the customer's admin to provision the corresponding User account before record import proceeds, since OwnerId references on Call Records and QA Reviews require a valid Dynamics User.

Dialytica SMS Templates export with their body text and merge field placeholders. These map to Dynamics Email Template records (Dynamics supports templates for email; for SMS, we store the template body and merge syntax in a Note attached to the corresponding SMS Campaign for the customer's admin to copy into their SMS routing tool). We preserve the variable placeholder structure so that the replacement workflow can be reconstructed at the destination.