Migrate from Adaptix to Odoo CRM

Adaptix Contacts map 1:1 to Odoo res.partner records. We set company_type = 'person' on every record. The Adaptix email field becomes partner email; name fields combine or split per Adaptix structure. All standard contact fields (phone, address, job title) migrate directly. Custom properties on Contact become Odoo custom fields on the res.partner model, created before migration.

Adaptix Companies map to Odoo res.partner records with company_type = 'company'. The HubSpot-style domain field becomes the partner website. Individual Contacts within a Company link to their parent Company partner via the child_ids relationship in Odoo. We create Company partners before Contact partners so the parent link resolves at insert time.

Adaptix lifecycle stage is stored as a contact property, not a separate object. We create Odoo CRM Leads for all Adaptix contacts that have a lifecycle stage value of lead or marketing-qualified and no associated deal history. The original Adaptix lifecycle stage value migrates to a custom field x_adaptix_lifecycle_stage__c on the crm.lead for audit.

Adaptix Tags used for contact classification migrate to Odoo CRM Tags. We extract the full tag list and create them in Odoo via the CRM Tag interface before contact import. Each contact's tag assignments migrate as CRM Tag links. Odoo CRM Tags appear on both Lead and Opportunity records.

Every Adaptix custom property on Contact varies per account. We enumerate all custom properties during discovery, map each to an Odoo custom field with the matching data type (char, selection, boolean, date, etc.), and create the field definition via Odoo's Studio or XML before any partner records are imported.

Adaptix company-level custom properties (industry classifications, annual revenue if tracked, customer tier) map to Odoo custom fields on the res.partner model, scoped to company-type partners. We apply the same discovery, type-mapping, and schema-creation process as for contact custom properties.

Adaptix Audience Segments are filter-rule definitions applied to the contact list. We extract each segment's filter logic and recreate it as an Odoo CRM domain filter or saved filter. The member contact list also exports separately so the segment can be reviewed and rebuilt with the correct Odoo filter conditions.

Adaptix automation definitions do not export as executable code. We document each active automation in a step-by-step format: trigger event, conditions, actions, and delays. This document maps directly to Odoo Workflow Builder actions (server actions, automated actions, on-create rules). The customer's Odoo admin uses this as a rebuild checklist.

Adaptix email engagement records (sends, opens, clicks) migrate as Odoo CRM activities with activity_type = email or as mail.message records on the partner. The email subject and body migrate to the activity note or message body. Activity date preserves the original timestamp. Note that Odoo CRM does not natively track open and click events; we migrate them as informational activities rather than engagement metrics.

Adaptix SMS consent records migrate to Odoo res.partner custom fields tracking SMS opt-in status and opt-in timestamp. The SMS message history itself is not a discrete Odoo CRM object; we document it as a reference table and recommend Odoo's SMS module (in-app SMS in Odoo 17+) as the replacement sending tool.

Adaptix call engagements map to Odoo CRM activities with activity_type = Call. Duration, call notes, and disposition migrate to custom activity fields. Call recording URLs migrate as attachment links on the activity record. The activity is linked to the resolved Partner record.

Adaptix meeting engagements map to Odoo calendar.event records. Start datetime, end datetime, location, and attendee list migrate. The event links to the Partner record via the Odoo calendar/event partner relationship. Meeting notes migrate as event description or as an attached note.

Adaptix notes and tasks migrate to Odoo CRM notes (mail.message with subtype = comment) or tasks (crm.activity with type = Task). Status, priority, and due date from Adaptix task engagements map to the corresponding Odoo activity fields. Assignment resolves to the Partner owner via the Owner-to-User mapping table.

Adaptix Form definitions export as JSON schema (field names, types, consent checkboxes, and submission routing). There is no Odoo native form import equivalent; we deliver the form schema and recommend Odoo Website Form Builder or Survey module as the rebuild target. Each form's submission routing (automation trigger) is captured in the automation rebuild document.