Migrate from Intrix CRM to Odoo CRM

Intrix Clients map to Odoo res.partner records in company mode. We extract the Client name, industry, contact information, and the 360-degree overview fields as custom char and text fields on res.partner. The res.partner record is created first so that its ID is available for Contact lookups during the child record import. Intrix's Client-level custom fields map to res.partner custom fields in the Odoo database.

Intrix Contacts map to Odoo res.partner records in individual mode, linked to the parent Client via the parent_id field on res.partner. We match Contacts to their parent Client by Client name or ID during import and set parent_id to the Odoo Partner ID. Salutation, first name, last name, phone, email, job title, and department transfer to the corresponding Odoo partner fields. Any Contact-level custom fields from Intrix map to res.partner custom fields.

Intrix Opportunities map to Odoo crm.lead records. The Opportunity name becomes crm.lead name, deal value maps to expected_revenue, expected close date maps to date_deadline, and owner assignment maps to user_id by email matching. Custom stage names from Intrix require a stage-name mapping to Odoo's crm.stage values, which we configure before import by querying the destination Odoo instance's active stage pipeline.

Intrix's configurable pipeline stages are customer-specific and must be mapped to Odoo crm.stage records within the appropriate pipeline ID. We extract the customer's active stage configuration from Intrix, create matching crm.stage records in Odoo, and map the stage probability percentages. If Intrix used multiple pipelines, we configure Odoo crm.team records and assign leads to teams via the team_id field.

Intrix Activities (calls, emails, meetings, tasks) logged against Clients or Opportunities map to Odoo mail.message records linked to the crm.lead via res_id and model fields. Call and meeting metadata (duration, disposition, attendees) transfer to custom fields on mail.message. Task-type activities map to project.task records with stage and user assignment resolved at import time. Activity timestamps are preserved on mail.message date to maintain the timeline order in the CRM record.

Intrix Projects map to Odoo project.project records. Project name, description, deadline, and owner assignment transfer to the Odoo equivalent fields. Project-level custom fields from Intrix map to project.project custom fields in Odoo. We create the project.project record before any task import to ensure the project_id lookup is satisfied at task insertion time.

Intrix Tasks map to Odoo project.task records linked to their parent project.project via project_id. The task dependency graph is the primary complexity: Intrix enforces predecessor-completion before child-task closure. We extract the dependency graph from Intrix, sort tasks by dependency level, and import parent tasks before child tasks. Odoo's project.task allows setting dependent tasks via the dependency_ids field once the parent task has an Odoo ID.

WHR is available only on Intrix Advanced and Unlimited tiers. Odoo does not have a direct WHR equivalent; time tracking lives in the project.timesheet or hr.attendance app. We map WHR records to project.timesheet entries linked to the relevant project.task or project.project, with hours, date, and employee mapping. If the destination Odoo instance does not have the Timesheet app installed, we document the custom field placement and advise on activation before migration begins.

Intrix Support is an add-on module (€2/user/month) on Advanced and Unlimited tiers. Odoo requires the helpdesk app to be installed for ticket migration. If the destination Odoo instance has helpdesk installed, tickets migrate to helpdesk.ticket with status mapping to ticket stage, assignee mapping to user_id by email, and email thread history flattened into the ticket description or chatter. If helpdesk is not installed, we document the ticket data for manual re-creation and advise on app activation.

Intrix allows custom fields on most objects. We extract the full custom field schema per object during scoping, then pre-create matching custom fields on the corresponding Odoo model (res.partner, crm.lead, project.project, project.task) before any data import. Field types are mapped: Intrix text to char or text, date to date, number to float or integer, checkbox to boolean, dropdown to selection. Unsupported field types are flagged with a schema gap note for the customer to resolve in Odoo Studio.

Intrix stores attachments per Client, Contact, or Project. We download files individually from the UI, then re-upload them to the corresponding Odoo record (res.partner, project.project, project.task) via Odoo's ir.attachment API. The original filename and any inline content type are preserved. File-per-record structure creates bulk import overhead for records with multiple attachments; we batch uploads in groups of 20 with rate-limit handling on the Odoo XML-RPC endpoint.

Intrix Users (Owners) referenced on Opportunities, Projects, and Tasks are mapped to Odoo res.users records by email matching. We extract every distinct owner email from the source data, query the destination Odoo instance for matching users, and hold any unmatched owners in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on Opportunities and Tasks resolve to user_id at migration time.

Intrix integrations (MailChimp, Google Calendar, accounting connectors) store connection credentials and sync state that cannot be migrated. We document all active integrations during scoping and deliver a written configuration guide for manual re-setup in Odoo: which Odoo apps provide equivalent connectivity (discuss for email, calendar integrations via Odoo apps or connector modules), the credentials to re-enter, and any sync configuration to rebuild.