Migrate from ActiveTrail to Odoo CRM

ActiveTrail Contact records route to Odoo Lead if the contact has never been associated with a sales opportunity or purchase interaction; they route to Odoo Contact if the contact has an ActiveTrail lifecycle stage of customer, evangelist, or has associated deal or purchase history. We compute the split using ActiveTrail's lifecycle_stage and has_purchased properties at migration time and preserve the original lifecycle stage in a custom field at_original_lifecycle_stage__c on both Lead and Contact for audit.

ActiveTrail contacts with an associated company name or website domain map to an Odoo crm.lead partner_id (Company) or res.partner record. We create the Company record first using the contact's company field or inferred domain, then link the Contact to it via the parent_id field. Contacts without a company association create standalone res.partner records of type individual.

ActiveTrail Segments are dynamic rule sets built on contact properties and behavioral triggers. We export segment definitions as rule-set documentation. Static segments (contacts explicitly added) migrate as Odoo tags on the target Lead or Contact record. Dynamic segments that rely on ActiveTrail behavioral properties (opens, clicks, last activity date) cannot be replicated natively in Odoo CRM without Odoo Marketing Automation; we document these as requiring a rebuild using Odoo Lead Filters or the Marketing Automation domain filters.

ActiveTrail custom contact fields (text, number, date, dropdown, checkbox) map to Odoo custom fields created in Odoo Studio on the res.partner model for Contacts and crm.lead for Leads. Dropdown fields in ActiveTrail require Odoo Selection fields with the same option values. All custom fields are provisioned in the destination Odoo database before record import begins.

ActiveTrail behavioral tags migrate as Odoo tags on the res.partner or crm.lead record. Tags are stored in the mail.message.mt model in Odoo and appear in the Tags smart button on contact and lead forms. Tag names pass through as lowercase with spaces replaced by underscores to comply with Odoo's tag slug format.

ActiveTrail email campaign metadata (campaign name, subject, send date, audience count, total sent) does not map to a native Odoo campaign object without the Odoo Marketing Automation app installed. We log campaign participation as a mail.message record attached to the Lead or Contact with a note body summarizing the campaign send and the contact's subscription status at time of send. Email template assets (HTML, images) migrate as Odoo email templates via the mail.template model.

ActiveTrail SMS campaign metadata migrates similarly to email campaigns as activity notes on the Lead or Contact record. Phone number format normalization (E.164) is applied during migration. The SMS content text is logged as a note; Odoo does not maintain SMS history natively without a third-party SMS gateway integration.

ActiveTrail automation journeys with triggers, conditions, delays, and multi-channel actions (email, SMS, WhatsApp) cannot be migrated as live-running workflows. We export the journey definition as a written document including trigger type, step-by-step logic tree, delay timers, channel actions, and entry/exit conditions. The customer's Odoo admin rebuilds these using Odoo CRM Automate actions (server actions, activity creation, email notifications) or the Odoo Marketing Automation app if licensed.

ActiveTrail landing pages built in the platform's page builder are exported as HTML files or documented as page structure descriptions. Odoo Website does not natively import ActiveTrail landing pages. We deliver the HTML assets and field-mapping notes for the customer's web team to reconstruct in Odoo Website or an external CMS. Form fields embedded in landing pages are documented for reconstruction in Odoo Form Builder or Website forms.

ActiveTrail signup form field definitions (field names, types, required flags, list association) are exported and documented. Form-to-list associations that trigger automation entry points are noted for reconstruction in Odoo Website forms or Odoo Marketing Automation as lead generation rules.

ActiveTrail survey structure (questions, answer options, conditional logic, embedded placement) is exported as a questionnaire document. Survey responses at the contact level migrate as notes on the Lead or Contact record. Odoo does not include a native survey builder in the base CRM module; reconstruction paths include Odoo Survey (separate app) or third-party integrations.

ActiveTrail campaign engagement events (opens, clicks, unsubscribes) are exported as contact-level activity notes appended to the Lead or Contact record in Odoo. These appear as internal notes in the contact's chatter, not as native Odoo engagement records. We preserve the original timestamp, engagement type, and campaign reference for historical audit but clarify that they do not appear in Odoo's native reporting dashboards.