Migrate from Dialytica - Marketing Automation Platform to Twenty CRM

Dialytica Contacts map 1:1 to Twenty CRM Person records. Phone numbers, names, email addresses, and campaign assignment history migrate directly. We preserve any custom fields on the Contact as custom fields on the Person object. The Person object in Twenty serves as the primary contact record and can be linked to a Company for account-context tracking.

Dialytica Call Campaigns do not have a direct Twenty CRM equivalent because Twenty does not include a native campaign dialing module. We map Call Campaigns to Twenty Opportunities if the campaign has associated revenue or pipeline context, or to Tasks with custom fields capturing campaign name, schedule, and targeting logic. The customer chooses the strategy during scoping based on how they use campaigns operationally.

SMS Campaigns similarly lack a direct Twenty CRM equivalent. We map SMS campaign content and targeting configuration to a Custom Object (e.g., SMSCampaign__c) with fields for campaign name, template references, and scheduling. Individual SMS message logs map to Activities linked to the Person record, preserving the campaign-to-message relationship.

Call logs migrate as Tasks with TaskSubtype set to Call and custom fields for CallDurationInSeconds, Disposition, and AgentAssignment. The original Dialytica timestamp becomes the Task due date to preserve activity ordering. AI-generated sentiment or quality scores from Dialytica migrate as custom fields if the values are numeric or categorical; free-text AI notes may map to the Task description.

QA Reviews in Dialytica are tied to specific call records and contain structured scorecard criteria and supervisor free-text notes. We map the review as a linked Task or a custom QA Review object (QA_Review__c) with a lookup to the corresponding Call Task. Scorecard criteria become individual custom fields; the supervisor notes field migrates as a long-text area.

SMS log records migrate as Twenty Tasks scoped to the Person record. Each SMS Activity carries its delivery status, timestamp, and phone number. We preserve campaign context from Dialytica by setting a custom campaign reference field on each SMS Task when the activity is linked to a mapped Call Campaign or SMS Campaign.

Dialytica Payment records map to a Twenty CRM custom object Payment__c with fields for amount, status, timestamp, and related Person. Payment__c links to Person via a lookup relationship. If the customer uses Twenty's Opportunities, payments can alternatively attach to an Opportunity if a revenue context exists.

Dialytica Agent and user accounts map to Twenty CRM User records. We resolve by matching the email address. Active status and role assignments migrate as User custom fields. Agent schedules and shift configurations are not standard Twenty objects and may require supplementary manual capture or a custom Schedule__c object scoped during migration.

SMS template body text and merge field structures migrate as custom fields on the SMSCampaign__c custom object or as Note records linked to the campaign. Variable placeholders are preserved as-is; the customer reconciles merge field syntax with the target SMS delivery tool post-migration.

Call scripts and dial plan text content migrate as Note records or long-text custom fields on the corresponding Call Campaign object in Twenty. Branching conditions and dynamic routing logic in Dialytica are opaque and cannot be exported; we capture the script text and sequence only. The customer's admin rebuilds branching logic as a decision tree in their chosen telephony tool.