Migrate from Symplify Communication to Odoo CRM

Symplify Contacts map to either Odoo crm.lead (prospect stage) or res.partner (customer stage) depending on the customer's segmentation strategy. We use Symplify list membership and campaign engagement signals to determine the split. Unqualified contacts landing as Odoo Leads use the partner_id as a Many2one to res.partner once the Lead is converted. The Symplify originalId is preserved in a custom field symplify_original_id__c on both crm.lead and res.partner for cross-reference during reconciliation.

Symplify Companies map to Odoo res.partner records with is_company=True. The Symplify company domain becomes the partner's website field. We resolve parent-company relationships from Symplify's hierarchical data and apply them to Odoo's child_partner cascade. Company is created before any Contact import so that the partner_id lookup is satisfied at Contact insertion.

Symplify Lists (static contact groupings) map to Odoo crm.tag records, with TagAssignment linking contacts to their list memberships. The Symplify list name becomes the tag name, and list description becomes the tag description. If the customer uses Symplify lists for segmentation by lifecycle stage or engagement tier, we map those to Odoo crm.lead.stage_id values instead and create the corresponding stage record type in the destination.

Symplify Campaigns map to Odoo crm.opportunity records. Campaign name becomes opportunity name, and campaign send date becomes the opportunity create_date. We preserve campaign-level metrics (total sent, total opens, total clicks) as custom fields on the opportunity: symplify_sent_count__c, symplify_open_count__c, symplify_click_count__c. The campaign channel (email, SMS, push) is stored in a symplify_channel__c field.

Symplify Messages (individual sendouts within a campaign) map to Odoo mail.mailing records. Message subject and body transfer as mailing subject and body_html. We preserve the message send timestamp, sender address, and reply-to address. Message-level stats (opens, clicks, bounces) attach to the mailing as mail.mail.statistics records linked by mailing_id.

Symplify Open records map to Odoo mail.mail.statistics entries with stat_type=open. Each open event links to the correct Contact (res.partner) and Message (mail.mailing) using the Symplify originalId as a foreign key. Open timestamps are preserved as last_open_date on the statistics record. If the same contact opened the same message multiple times, we retain the earliest and latest open timestamps.

Symplify Click records map to Odoo mail.mail.statistics entries with stat_type=click. We preserve the clicked URL, click timestamp, and link ID if available from Symplify's export. Multiple clicks by the same contact on the same message create separate statistics records. We store the original Symplify click record identifier in symplify_click_id__c for reconciliation.

Symplify Sent records map to Odoo mail.mail.statistics entries with stat_type=sent. Each sent event links to the correct Contact and Message. Delivery status (delivered, bounced, soft-bounced) is stored as a symplify_delivery_status__c field. Sent records are the parent of open and click records in the Symplify export, and we preserve that parent-child linkage via the mail.mailing and res.partner references.

Symplify Hard Bounce records map to Odoo mail.blacklist entries with the contact's email address as the key. We set the blacklisted flag on the res.partner record (opt_out=True) to prevent Odoo from sending to those addresses. Hard bounce timestamps and bounce codes are preserved in a symplify_bounce_history__c custom field on the partner record.

Symplify Soft Bounce records indicate temporary delivery failures. We preserve soft bounce events as mail.mail.statistics entries and add a warning note to the res.partner record noting the soft bounce type and timestamp. Soft bounces do not blacklisting the address in Odoo, but we flag the record so the customer's admin can review before re-engaging.

Symplify Optout records map directly to Odoo res.partner with opt_out=True set on the partner record. We preserve the optout timestamp in symplify_optout_date__c and the original Symplify unsubscribe source in symplify_unsubscribe_source__c for compliance documentation. All opted-out contacts are excluded from any mailing import batch unless specifically requested by the customer.

Symplify DataDocs store relational data (purchase history, bookings, events) linked to Contacts by originalId. We audit each Document Type during discovery to extract its JSON Schema. DataDocs with flat, single-valued fields map to custom Char, Float, Date, or Selection fields on res.partner. DataDocs with nested JSON structures or array fields map to ir.attachment records with the JSON stored as a binary attachment and the Symplify document ID preserved in the attachment's description field for retrieval.

Symplify Projects (organizational containers for campaigns) map to Odoo crm.team records. Project name becomes the team name, and project-level settings map to team configuration. If the customer used Symplify projects to segment campaigns by brand, region, or business unit, we map those segments to separate Odoo crm.team records and assign the corresponding opportunities and contacts to the correct team during migration.