Migrate from Attio to Odoo CRM

Attio People records map to Odoo res.partner with type='contact'. The Attio person name fields (first_name, last_name) concatenate to res.partner.name. Email, phone, job title, and all custom attributes migrate as fields on res.partner. We preserve the Attio record ID as a custom field attio_id__mc for dedupe and reconciliation. The partner must be created after its parent company if the Attio Person is linked to a Company via a Relationship Attribute.

Attio Company records map to Odoo res.partner with type='company' and is_company=True. The Attio company domain becomes res.partner.website. All custom attributes (industry, employee count, revenue tier) migrate as fields. This record is created first because Attio Person-to-Company relationships require a parent res.partner before child contact records can be written.

Attio Deal records map to Odoo crm.lead with type='opportunity'. Attio pipeline stages map to Odoo crm.stage values in the destination stage sequence. Deal amount migrates to crm.lead.expected_revenue; close date migrates to date_deadline. We resolve the Company link via Relationship Attributes to crm.lead.partner_id and Contact links to crm.lead.contact_id at migration time before writing.

Attio custom objects (gated by plan: 3 on Free, 5 on Plus, 12 on Pro, unlimited on Enterprise) require a destination validation step before migration. Odoo Studio custom fields on res.partner or crm.lead handle most custom attributes. For Attio custom objects with complex relationships (nested custom object with lookups to other custom objects), we may recommend a separate Odoo custom module. We audit the custom object count during scoping and flag when the destination plan (CRM app only vs full Odoo Online) has field count limits that constrain the mapping.

Attio Lists are workflow-context record collections, not standalone records. Attio explicitly documents that objects cannot be mapped to Lists during migration (they map to objects only). We extract all List memberships per record, translate each List name to an Odoo Tag (crm.tag), and attach the corresponding tag_ids to the migrated crm.lead or res.partner. Lists used for segmentation logic (dynamic membership based on conditions) do not have an Odoo equivalent and are documented as rebuild items for Odoo Studio filters or domain-based search defaults.

Attio Notes as threads attached to records map to Odoo mail.message records linked to the crm.lead or res.partner via mail.thread relations. Note body, timestamp, and author attribution preserve. For short notes without threaded replies, we may inline the note body into crm.lead.description as a historical summary for rep context. The migration approach is chosen per-note length during scoping.

Attio Tasks with assignee, due date, and status map to Odoo project.task records. We create a dedicated CRM project in Odoo (type='project') to hold migrated tasks so they appear under the CRM module without requiring a full Project Management module license. Task status, priority, and due date migrate. Owner assignments resolve by email match to Odoo res.users.

Attio Relationship Attributes (foreign-key chains between People, Companies, Deals, and custom objects) require reconstruction via API before writing because CSV exports flatten these chains. We query Attio's relationship endpoints to build parent-child maps, then write child records with their parent reference satisfied. Odoo's partner contact model handles Person-to-Company links; Deal-to-Company links use crm.lead.partner_id; multi-contact Deal links use the crm.lead.contact_id with EventContactHistory tracked via mail.message.

Attio Owner references on Deals and other records map to Odoo res.users. We resolve by email match. Owners without a matching Odoo user go to a reconciliation queue for admin provisioning before the record import phase. Active vs inactive status migrates as a flag so that the admin can activate or deactivate users in the destination org post-migration.

Attio email and calendar sync attaches to People and Company records only. Migrated activities land as mail.message records on the corresponding res.partner or crm.lead. Meeting details (start time, end time, location, attendees) preserve as structured mail.message fields. Email content preserves as body HTML. We do not migrate email headers or MIME structure; only the rendered body for rep visibility.

Attio Sequences (sales engagement cadences available on Pro and Enterprise plans) do not have a direct Odoo equivalent. Odoo does not ship a native cadence or sequence feature; teams typically rebuild this logic in a sales engagement tool (Mailchimp, Lemlist, or a dedicated sales engagement platform) or via Odoo Studio automations with manual tracking. We deliver a written inventory of every Attio Sequence with its step logic, timing, and body templates so the customer's admin can evaluate Odoo Studio automation rebuild or a third-party sales engagement tool.

Attio Workflows are credit-consuming automation objects with trigger, condition, and action block architecture that has no Odoo equivalent. Odoo Studio server actions, base.automation rules, and ir.actions handle record-triggered automation differently. We do not migrate Workflows as code. We deliver a written inventory of every active Attio Workflow with its trigger type, condition logic, action sequence, and credit consumption estimate, with a recommendation for Odoo Studio rebuild scope or a no-code automation layer (n8n, Make) if the logic requires cross-module triggers.