Migrate from eTrigue to Odoo CRM

eTrigue Prospects map to either Odoo CRM Contact or Lead based on qualification status. Prospects with a filled Company Name, confirmed business email domain, and any pipeline engagement map to Odoo Contact attached to a Partner record. Prospects with no company affiliation and no outbound engagement map to Odoo Lead. We flag which eTrigue custom fields indicate qualification status so the split rule is consistent with the customer's sales process. The original eTrigue prospect ID is preserved in a custom Char field etrigue_id for audit and cross-reference.

eTrigue's Company field on Prospect maps to Odoo CRM Partner. The Partner record is created with partner_type=company, the Prospect Company Name populates the name field, and the domain from the email address populates the website field as a dedupe signal. Odoo Partner functions as the Account equivalent in this migration. If multiple eTrigue Prospects share the same Company Name, we deduplicate to a single Partner with multiple Contact children.

eTrigue Campaigns map to Odoo CRM Campaign records, with the campaign name, start date, and end date migrated directly. Campaign response data (Prospects who received or engaged with the campaign) maps to Odoo Marketing Automation linked to the Campaign, or to a Mail.mass_mailing record if email send history is being preserved. Email send history is reconstructed from eTrigue's Activity History export rather than as a native Odoo object.

eTrigue's five Lead Score sub-components (Campaign Score, Activity Score, Source Score, Relationship Score, Buy Time Score) are stored as separate numeric properties on the Prospect. We export all five and create five corresponding Float fields on the Odoo CRM Lead or Contact model before import. The customer's admin decides whether to use Odoo's built-in lead scoring model, a third-party app from the Odoo Apps store, or a computed field that sums the five components. The original composite score from eTrigue's 3D Lead Scoring model is preserved as an additional custom Float field etrigue_3d_score.

eTrigue Activity History (page views, email opens, form submissions, campaign responses with timestamps) is exported as a structured log and mapped to Odoo CRM Activity records. Each activity type in eTrigue maps to a distinct subtype in Odoo: page_view and form_submit map to Note with a custom subtype; email_open maps to an Odoo Note subtype; campaign_response maps to a Log Note on the related Contact or Lead. Activity timestamps migrate directly to preserve the original engagement timeline.

eTrigue Prospect custom fields (Boolean, Text, Number, Date) defined under Settings > Prospect Settings > Prospect Fields are mapped to Odoo CRM Contact or Lead custom fields of equivalent type. Boolean fields with custom labels (e.g., has_referred, attended_webinar) map to Odoo Boolean fields with the label preserved in the field help text. We export the custom field definitions from eTrigue and pre-create the Odoo fields before any contact import begins.

eTrigue Lead Accelerator customers storing partner organization names and partner-specific campaign attribution in custom Prospect fields map these to Odoo Partner records with partner_type=company and a custom Char field partner_program populated from the eTrigue custom field value. If the customer used a separate custom field for partner tier (e.g., Gold, Silver, Bronze), this maps to a Selection field on Partner. Partner attribution to specific campaigns is stored as a Many2many relation from Partner to the migrated Campaign records.

eTrigue Tags and Content Types classify prospect engagement with content categories. These migrate as Odoo CRM Tags applied to the Contact or Lead records. Tags with eTrigue-specific naming (e.g., content_type_webinar, content_type_whitepaper) are preserved verbatim and can be reorganized post-migration using Odoo's Tags management UI.

eTrigue landing pages with progressive forms are exported as field definitions and page structure metadata. Odoo Website does not use the same form builder, and we do not migrate landing pages as code. We deliver a written document listing each eTrigue form with its field names, field types, conditional logic, and lead scoring trigger so the customer's web team or an Odoo partner can rebuild the forms in Odoo Website or Odoo Sign.

eTrigue drag-and-drop campaign workflows and nurture sequences do not migrate as code. Odoo CRM uses Automated Actions (triggered on CRM object write, create, or time-based) and Server Actions (triggered by button or menu), which are architecturally different from eTrigue's campaign-centric trigger model. We deliver a written inventory of every active eTrigue workflow with its trigger conditions, audience filter, and action sequence, along with a recommended Odoo Automated Action equivalent and an estimate of the rebuild effort for each.

eTrigue Status field exports as numeric codes (1 = Active, 2 = Opt-Out, 3 = Bounced, etc.) rather than human-readable labels. We decode the numeric codes during the data transformation step and map to Odoo Contact.active = True for Active, Contact.active = False for Opt-Out or Bounced. Opt-out status is also recorded in a custom field etrigue_original_status to preserve the full audit trail.

eTrigue Prospect Owner (the marketing user responsible for the record) maps to Odoo CRM User by email match. We extract all distinct Owner email addresses from the Prospects export and match against the Odoo User table. Any Owner without a matching Odoo User is flagged in a reconciliation report for the customer's admin to provision before the final migration phase.