Migrate from Dialytica - Marketing Automation Platform to Odoo CRM

Dialytica Contacts map 1:1 to Odoo CRM Contacts. We preserve phone numbers (dialytica_phone), campaign assignment history, custom field values, and contact-level notes. The contact's email and name fields map to Odoo's standard email and name fields. If Dialytica contacts reference agents or owners, we resolve those by email match against the Odoo Users table. Dialytica custom fields map to Odoo custom contact fields of the matching type (char, text, selection, date, etc.).

Dialytica Call Campaigns map to an Odoo CRM Marketing Campaign record with a custom tag 'call_campaign' stored in a tag_ids field. The campaign name, schedule, targeting criteria, and script reference migrate as structured fields on the Odoo Campaign. Because Odoo does not have a native call campaign object, we use the Campaign's description and a linked Note to hold the dialing configuration context that Dialytica stored. We also tag all affected Dialytica Contacts with the corresponding Odoo Campaign membership record.

Dialytica SMS Campaigns map to a separate Odoo CRM Marketing Campaign with tag 'sms_campaign'. The SMS template body, variable placeholders, and send schedule migrate to the Odoo Campaign's mailing configuration. We preserve the campaign-scoped grouping of SMS activities by linking each migrated SMS Activity to the corresponding Odoo Campaign membership record. Dialytica's SMS campaign and Call campaign targeting the same contact list are kept separate in Odoo but share the same contact segment.

Dialytica Call Records map to an Odoo Note record linked to the Contact. The Note body holds call metadata (duration, disposition, agent assignment, timestamp, recording URL if available). We also create custom fields on the Note object (call_duration__c, call_disposition__c, call_agent__c, call_recording_url__c) to enable structured reporting in Odoo without parsing Note text. Dialytica's AI-evaluated sentiment or score data on calls cannot be migrated as structured fields because the LLM output is not exposed in exportable form; we capture it as plain text in the Note body.

Dialytica QA Reviews map to an Odoo Note linked to the original Contact. The QA scorecard criteria (structured ratings) migrate to custom fields on the Note (qa_score__c, qa_criteria_1__c through qa_criteria_n__c depending on the scorecard width). Free-text supervisor notes migrate to the Note body. Each QA Review Note is tagged with a 'qa_review' tag so that supervisors can filter for QA records separately from general notes.

Dialytica SMS Activities map to Odoo Mail Message records linked to the Contact. The message body, delivery status (sent, delivered, failed), phone number, and timestamp migrate as structured Mail Message fields. Delivery status maps to Odoo's mail.message tracking values where available. We group SMS logs by the source Dialytica SMS Campaign and link them to the corresponding Odoo Campaign membership.

Dialytica Payment records map to Odoo Account Move records (invoices or customer payments depending on type). The payment amount, status, timestamp, and associated contact reference migrate to the invoice. If Dialytica associates payments with specific campaigns, we record the campaign name in the invoice reference or a custom invoice field. We do not migrate payment processing configuration (payment gateway settings, webhook endpoints) because these are platform-specific integrations that must be reconfigured in Odoo Payments.

Dialytica Agent and User accounts map to Odoo Users by email match. We preserve the agent's name, email, active status, and role (dialytica_role) as a custom field on the Odoo User. Agent assignment on Call Records and QA Reviews resolves through this user mapping. If a Dialytica agent has no corresponding Odoo User, we hold the mapping in a reconciliation queue for the customer's admin to provision the Odoo user before contact migration begins.

Dialytica SMS Templates map 1:1 to Odoo SMS Templates. Template body text and merge field placeholders (e.g., {{contact.name}}, {{contact.phone}}) migrate as-is. We flag any Dialytica-specific merge field syntax for the customer's admin to reformat to Odoo's template variable format before activating the template in Odoo. The template name and active/paused status migrate directly.

Dialytica Call Scripts and Dial Plans migrate as Odoo Notes linked to the Contact or Campaign they were associated with. The script text and sequence migrate to the Note body. We extract branching conditions as plain text within the Note, but we flag that branching logic is not structurally preserved because Dialytica does not expose this as structured export data. For customers who used Dialytica's script feature as a knowledge base, we recommend creating Odoo Knowledge Articles as a parallel step outside migration scope.

Dialytica Agent Schedules are captured as structured data during discovery. If schedules are stored as recurring time blocks with agent, day-of-week, and shift start/end, we map them to Odoo Resource Calendar records. Availability blocks migrate as Odoo calendar events of type 'block_time' linked to the corresponding agent's Odoo User. This is a best-effort mapping because agent scheduling is often stored outside the standard Dialytica export schema and may require supplementary API calls or manual capture.

Any custom fields on Dialytica Contacts (beyond name, email, phone) are mapped to Odoo CRM custom contact fields. We match by field name and data type. Char fields map to Odoo char, text fields to text, date fields to date, selection fields to selection, and multi-select to many2many tags. The field value migrates directly. If Dialytica uses a data type that Odoo does not support (e.g., Dialytica-specific enumerated types), we map to the closest Odoo equivalent and flag the conversion for the customer's admin.