Migrate from Listrak to Odoo CRM

Listrak Contacts map to Odoo CRM Contacts. The Listrak email address becomes the Contact email field (used as the primary identifier and dedupe key during import). Opt-in status and opt-in date migrate to a custom Boolean field and date field respectively. Lifecycle stage from Listrak maps to a custom selection field on Contact so that the customer's original stage taxonomy is preserved for reporting. Original Listrak contact_id is stored in a custom field for source-reference audit. Odoo's XML-RPC API is used for batch contact creation, with chunking to stay within Odoo's API rate limits.

Listrak mobile subscribers require special handling. Mobile numbers must import as text-formatted phone strings (not numeric-only strings) to preserve leading zeros and country codes. Opt-in date migrates to the same custom opt-in date field as email contacts. Acquisition keyword and campaign source data (tracked in Listrak's separate acquisition export) must be joined on mobile number and preserved as custom fields on the Odoo Contact. We validate that all mobile numbers are text type before loading and flag any records with ambiguous opt-in status for customer review before import.

Listrak Companies map to Odoo CRM Companies. The company name becomes the Company name field, and the Listrak domain field maps to the Company website field. Companies are created before Contacts so that the Contact-Company lookup relationship (Many2one field in Odoo) is satisfied at Contact import time. If a Listrak Contact has no associated Company, we create a Company record using the contact's email domain as a placeholder, with a flag marking it as a solo-contact company.

Listrak Deals map to Odoo CRM Opportunities. The Listrak dealstage maps to an Odoo stage within the configured sales pipeline, and the Listrak pipeline name maps to a separate Odoo sales team (crm.team) or a custom pipeline identifier field. Closed-Won and Closed-Lost reasons from Listrak custom fields map to Odoo Opportunity fields (win_reason, lost_reason custom fields). Expected revenue and quantity from Listrak Deals migrate to Odoo's expected_revenue and planned_revenue fields.

Each Listrak pipeline becomes a named Odoo sales team or a custom pipeline identifier field on Opportunity. Listrak stage names map to Odoo stage names in the same sequence. We configure stage probability percentages to match the customer's Listrak stage probabilities, using Odoo's stage configuration to set probability auto-update behavior per stage.

Listrak email engagement history (sends, opens, clicks, bounces) migrates to Odoo CRM as mail.message records linked to the Contact via Odoo's mail.thread model. Each engagement type (sent, opened, clicked, bounced) is stored as a subtype and body text. Email content from Listrak's engagement export migrates as plain-text body in the mail.message. Odoo CRM does not have a native marketing email send function; the engagement history serves as an audit log rather than a campaign analytics dashboard.

Listrak call engagements migrate to Odoo CRM Phone Call records linked to the Contact. Call duration, disposition, and recording URL (if available) migrate to custom fields on the phone call. Activity dates preserve the original Listrak call timestamp for timeline ordering. If Odoo VoIP integration is not active, call records function as logged activity entries.

Listrak meeting engagements migrate to Odoo Calendar Events linked to the Contact. Start datetime, end datetime, location, and attendee list migrate. Attendees are resolved to Odoo Partner records and linked via EventRelation. Meeting body (notes, agenda) migrates as the event description field.

Listrak task engagements (action items, reminders, to-dos) migrate to Odoo CRM Tasks linked to the Contact or Opportunity. Task status, priority, due date, and assigned user migrate with Odoo OwnerId resolved by email match against the Odoo User table. Any task assigned to a HubSpot owner without a matching Odoo user is placed in a reconciliation queue.

Listrak note engagements migrate to Odoo Notes linked to the Contact, Company, or Opportunity via the generic attachement.model and attachment.res_id fields. Note body (rich text or plain text) migrates directly. Note author and timestamp are preserved.

Listrak suppression and unsubscribe lists must load into Odoo before any active contact import to ensure opt-out compliance is maintained from day one. We load suppressions first, setting a custom opt_out field to True on each matching Contact record (or creating the Contact as suppressed if no active record exists). Odoo CRM does not have a native suppression list management UI; we configure a shared opt-out field and recommend a process for the admin to maintain it going forward.

Listrak audience segments filter by email behavior, SMS engagement, and channel subscription status. We translate each Listrak segment's filter logic into an Odoo-compatible domain expression or tag set. Segments that rely on real-time behavioral signals (opens in last 30 days, SMS clicks) cannot be represented as static Odoo Groups—these are documented with a recommendation to use Odoo Automated Actions triggered by mail.message events for dynamic re-evaluation. Static segments (based on opt-in date, acquisition source, or demographic fields) become Odoo Tags or Groups that are maintained manually post-migration.

Journey Hub automations (cart abandonment, browse recovery, replenishment, win-back sequences) are not transferable objects. We deliver a written inventory of every active Journey: the trigger event, each condition branch, every time delay, and the full channel sequence (email step 1, SMS step 2, push step 3, for example). Each step is mapped to an equivalent Odoo Server Action or Automated Action, with the customer's Odoo admin or developer responsible for rebuild. The inventory includes trigger event mapping (Listrak event name to Odoo model and field), condition translation (Listrak filter operator to Odoo domain operator), and delay configuration (Listrak delay step to Odoo Automated Action scheduled delay).

Listrak email templates export as raw HTML or require manual rebuild in the destination platform's editor. We do not import raw HTML as Odoo email templates because rendering inconsistencies, embedded styles, and Listrak-specific variable syntax do not carry over cleanly. We deliver a template inventory documenting the subject line, from name, body structure, and dynamic field placeholders for each Listrak template so that the customer's Odoo admin rebuilds them using Odoo's QWeb-based email template editor with correct Mail Merge field syntax.

Listrak custom contact properties that appear in the API export migrate to Odoo custom fields on the relevant model (res.partner for Contacts, crm.lead for Opportunities). We flag any custom fields that exist only in the Listrak UI and not in the API export, as these require the customer to export them manually via the Listrak UI or configure an API query for the specific field ID. Field type mapping: Listrak text becomes Odoo char; Listrak numeric becomes Odoo float or integer; Listrak date becomes Odoo date; Listrak boolean becomes Odoo boolean; Listrak multi-select becomes Odoo char (comma-separated) or many2many tags field.