Migrate from Dialytica - Marketing Automation Platform to Salesforce Sales Cloud

Dialytica Contact records map directly to Salesforce Contact. We preserve the full name, phone number (mobile, work, home), email, custom field values, and campaign assignment history. The Dialytica contact_id becomes a custom external ID field (dialytica_contact_id__c) on Salesforce Contact for deduplication and cross-reference. Any Dialytica contact properties that have no Salesforce standard equivalent become custom fields on Contact.

Dialytica Call Campaigns map to Salesforce Campaign records. Campaign Name, status (active/paused/completed), scheduled start and end dates, targeting criteria text, and script reference migrate as Campaign fields. We map Dialytica campaign targeting rules (the AI-driven contact selection outcome, not the logic itself) as Campaign Member status records so that the selected contacts appear as Campaign Members in Salesforce. Dialytica does not export the AI targeting algorithm; we migrate the resulting assignment data only.

Dialytica SMS Campaigns map to a separate Salesforce Campaign or to the same Campaign as Call Campaigns when the customer uses a unified campaign structure. We apply a campaign type distinction (Outbound Call vs SMS) using the Salesforce Campaign Type picklist. SMS template body text migrates to Campaign Custom Fields (sms_body__c) since Salesforce standard Campaigns do not natively store SMS content.

Dialytica Call Records map to Salesforce Task with TaskSubtype set to Call. Duration, disposition code, agent assignment (mapped to Salesforce User by email lookup), call recording URL, and AI-evaluated metadata (sentiment scores, talk-to-listen ratio where available) migrate as custom fields on Task. ActivityDate is set to the original Dialytica call timestamp to preserve timeline ordering. The WhoId on Task points to the migrated Contact record.

Dialytica QA Reviews (supervisor scorecards tied to call records) map to either Salesforce Case (if the org has Service Cloud) or a custom QA_Review__c object we create during schema design. The review criteria and scores migrate as custom fields on the chosen object, and the related Call Record migrates as the parent Task lookup. Free-text supervisor notes migrate as Description or as a separate Long Text Area field. If the destination org has no Service Cloud license, we recommend the custom object approach to avoid Case license constraints.

Individual SMS message events from Dialytica (message body, delivery status, timestamp, phone number) map to Salesforce Task records with a custom sms_type__c flag set to 'Inbound' or 'Outbound'. We set Task.ActivityType to 'SMS' if the org has Sales Engagement licensed, or use the custom field approach otherwise. The WhoId on Task links to the migrated Contact. Delivery status maps to a custom sms_delivery_status__c picklist field.

Dialytica SMS message templates with variable placeholders migrate as Salesforce Custom Fields on the Contact or Campaign object (sms_template_body__c), or as Salesforce Content records if the customer uses Content. Merge field structures are preserved as bracketed variable names (e.g., {{first_name}}) in the migrated template text.

Dialytica Agent and User accounts export with roles and permissions. We resolve agents by email match against the destination Salesforce org's User table. Any Dialytica agent without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active status and agent permissions do not map directly to Salesforce profiles and permission sets — these require manual admin configuration post-migration.

Dialytica Payment records (transaction amounts, statuses, timestamps tied to campaigns or contacts) migrate to a custom Payment__c object or to Opportunity records depending on whether the customer uses Salesforce Opportunity as their revenue tracking object. We assess this during scoping. Payment__c uses a Lookup to Contact and optionally to Campaign. We flag that Dialytica payment data schema may be limited and recommend a data quality review before migration.

Dialytica Agent Schedules (shift configurations and availability) migrate to a custom Agent_Schedule__c object or to Salesforce Event records with a custom schedule_type__c flag. Availability windows, shift start/end times, and agent assignment migrate as custom fields. This object is often partially structured in Dialytica exports; we extract what is available and flag gaps for the customer to supplement manually if needed.

Dialytica Call Scripts and dial plan logic (agent workflow text and sequence) migrate as Salesforce Content Documents (ContentVersion) or as long-text Custom Fields on the Campaign object. We extract the script body text and sequence order but note that branching conditions, conditional logic, and dynamic routing rules are not stored as structured exportable data in Dialytica. The script document is provided as a reference file for the customer's admin to use when rebuilding Salesforce Flow or Sales Engagement cadences.

Dialytica maintains Call Campaigns and SMS Campaigns as separate objects, but a single contact's journey often spans both channels. We stitch cross-channel activity by merging Dialytica call engagement history and SMS engagement history into Salesforce Campaign Member records on the same Campaign, so that the migrated contact shows both call and SMS touchpoints in Salesforce's campaign timeline. This requires a deduplication step during transformation to avoid duplicate Campaign Member records for contacts targeted in both campaign types.