Migrate from Ontraport to Odoo CRM

Ontraport Contacts map to Odoo CRM Partners (res.partner model). All standard fields (First Name, Last Name, Email, Phone) map 1:1. Custom fields migrate to Odoo custom fields on res.partner with appropriate field types (char, text, selection, date, etc.). Lifecycle stage from Ontraport migrates as a selection field or tag on the Partner record. We use Partner email as the dedupe key during import to avoid duplicate records.

Ontraport Company records map to Odoo Companies (res.company). The Company-to-Contact relationship (one-to-many) is preserved in Odoo using the Partner parent-child structure. We recommend deduping Company names in Ontraport before export because Ontraport does not enforce Company deduping, and Odoo's import deduping relies on exact name matching which can leave duplicates unresolved.

Ontraport Deals map to Odoo CRM Opportunities (crm.lead with type=pipeline). Deal pipeline becomes an Odoo Sales Team or Pipeline stage configuration. Deal stage maps to Odoo stage_id with probability mapping preserved from Ontraport. Deal amount, expected close date, and owner assignment migrate directly. The Contact or Company association from Ontraport maps to the Partner relation on the Odoo Opportunity.

Each Ontraport Deal pipeline becomes an Odoo Sales Team (crm.team) with its own stage pipeline. Ontraport stage names map to Odoo stages in order. Stage probability percentages transfer to the stage probability field. If multiple pipelines exist in Ontraport, each maps to a separate Odoo Sales Team so that pipeline visibility is preserved at the destination.

Ontraport Contact and Company tags migrate to Odoo CRM Tags. Tags are plain-text label values without hierarchy in Ontraport, so they map directly to Odoo tag strings. Tags attached to Deals migrate as Opportunity tags. We export the full tag assignment matrix per record and reapply all tags at the destination, preserving the relationship between tag and record.

Ontraport Notes linked to Contacts export as CSV rows that repeat the full Contact data per Note (a known Ontraport export behavior). We deduplicate these rows after export by Contact ID and re-link each Note to its single Odoo Partner record using Odoo's internal Notes model (mail.message with subtype=note). The original Note body, author, and creation date are preserved.

Ontraport Campaign assignments (which Contacts are enrolled in which campaigns) are exported as tag assignments or as a dedicated mapping table. Campaign names and enrollment status migrate as tags on the Partner record or as a custom field. Campaign-level configuration (email templates, send schedules, UTM parameters) does not migrate; we document the campaign list as a written inventory for the admin to rebuild in Odoo email marketing or a third-party tool.

Ontraport invoice and payment records map to Odoo Accounting (account.move model). Each Ontraport invoice becomes an Odoo Invoice (account.move with type=out_invoice). Payment records become Odoo Payment records (account.payment) linked to the corresponding invoice. The Contact-to-Partner link is preserved during import. Odoo Accounting must be activated in the Odoo instance before invoice migration; this is a separate module configuration step outside the CRM migration scope.

Ontraport custom objects (Pets, Courses, Projects, etc.) map to Odoo custom models (ir.model and ir.model.fields) created before migration. Each custom object record migrates as a row in the corresponding Odoo model. Lookup relationships between custom objects and Contacts or Companies in Ontraport map to Odoo Many2one or Many2many fields on the custom model. We pre-create the destination schema in Odoo during the configuration phase so that relationship IDs can be resolved during import.

Ontraport Tasks map to Odoo Project Tasks (project.task) or CRM Tasks depending on Odoo configuration. Task title, description, due date, assigned owner, and completion status migrate directly. Tasks linked to Deals migrate as Odoo Tasks under the corresponding Opportunity. Task priority and category map to Odoo's priority and project assignment fields.

Ontraport engagement data (email opens, clicks, form submissions, landing page visits) does not have a native Odoo equivalent as time-series activity records. We migrate engagement data as log notes (mail.message with subtype=note) attached to the related Partner record, preserving the engagement type, timestamp, and subject. The customer's admin may choose to aggregate this into a custom dashboard rather than rely on the activity timeline for this data type.

Ontraport Automation Rules and Sequences cannot be exported. We extract the list of active automations with trigger definitions and enrolled Contact counts as a written inventory document. The automation names, trigger events, conditions, and enrolled Contact list are documented so the customer's admin can rebuild each automation in Odoo Studio using server actions and automated actions. This is the highest-impact gap in any Ontraport migration and requires the most post-migration admin effort.