Migrate from Acoustic Campaign to Odoo CRM

Acoustic Contacts map to Odoo res.partner records. Each Contact from the primary Database becomes a Partner with partner_type set to 'contact' (or 'lead' if the Acoustic Contact is pre-qualification). Email address is the dedupe key. We resolve the original Acoustic Database identifier into an Odoo tag (e.g., Database_Original_Name) so the source split is auditable post-migration.

Acoustic allows multiple Databases with different schemas. We map each Database to an Odoo Contact Tags (res.partner.category) record, applying the tag to all Partners migrated from that Database. Where Databases share the same email address, we keep the most recently modified record as authoritative and flag duplicates in a migration reconciliation report.

Relational Table rows are denormalised onto the Contact as Odoo custom fields (char, float, date, selection) when the join is simple and the column count is low. For wide or complex Relational Tables with multiple joins, we create a custom Odoo model (e.g., acoustic_relational_data) with a many2one link back to res.partner, preserving the table structure as a related record rather than flattening it.

Acoustic Queries are saved filter definitions whose current membership we snapshot as a static list. We export each Query's current membership and create an Odoo static Partner Set (using the CRM module's tagging or a custom Partner Set model) so the customer can recreate the audience manually in Odoo Marketing Automation or as a manual filter. The query logic itself is not transferable because Odoo has no saved query equivalent.

Acoustic Programs with enrollment state, branching logic, and timer offsets are documented but not migrated as code. We export the Program definition (steps, conditions, branches, timer values) and deliver a written rebuild guide mapping each Program step to an equivalent Odoo Marketing Automation action. Programs are paused during cutover; Odoo Marketing Automation takes over the automation function post-migration with a fresh timer clock.

Acoustic Mailing metadata (name, subject, sender address, HTML body, sent date) migrates to Odoo Mass Mailing (mailing.mailing). Acoustic $contact.field$ personalisation tags are translated to Jinja2 {{partner.field}} syntax. Email content is imported as HTML; images are stored as IR attachments and referenced by URL. We flag Mailings with complex Acoustic-specific conditional content blocks that require manual reconstruction.

Acoustic Suppression Lists migrate to Odoo's mail.blacklist table and to the opt_out field on res.partner. We load the suppression entries first in the migration sequence, before any Partner import, so that Odoo's blacklist is populated before sending capability is enabled. Bounce classification (hard bounce, soft bounce, unsubscribed) maps to mail.blacklist.reason values (bounce, false) and partner.opt_out accordingly.

Acoustic email templates and reusable content blocks export as HTML and are loaded into Odoo mail.template records. Acoustic personalisation tags ($contact.field$) are replaced with Odoo Jinja2 equivalents ({{object.field}}). Templates with Acoustic-specific conditional blocks (e.g., multiple version rendering based on contact attributes) require manual reconstruction in Odoo.

Acoustic Web Tracking event history (page visits, on-site behaviour tied to Contacts) is exported as a dataset and can be loaded into Odoo as a custom tracking model or as text notes on the related Partner record. Odoo CRM has no native behavioural event timeline; we recommend a custom model (e.g., website.event) with a many2one to res.partner if behavioural continuity is a business requirement.

Acoustic custom Contact fields (per-Database schema) are pre-created in Odoo as custom fields on res.partner before migration begins. Field type mapping: text to char or text, numeric to float or integer, date to date, picklist to selection, multi-select to char (comma-separated). Fields are deployed via Odoo data migration script or custom module before Partner records are imported.

Acoustic cross-channel campaigns (SMS, push, WhatsApp) export with schedule, audience, and content. The underlying messaging provider credentials (Twilio, WhatsApp Business API) do not carry across; we document the channel configuration requirements for Odoo. SMS content migrates to mailing.mailing with mailing_type='sms'; push and WhatsApp require separate Odoo integration configuration.

Acoustic email status (OPT_IN, OPT_OUT, BOUNCE, DO_NOT_EMAIL) maps directly to Odoo's opt_out flag on Partner and to mail.blacklist. We preserve the original Acoustic status value in a custom Char field (acoustic_email_status__c) for audit. DO_NOT_EMAIL entries route to mail.blacklist immediately.