Migrate from matrix to Odoo CRM

Matrix contacts map directly to Odoo res.partner records. Type is set to 'contact' (individual). Parent_id is left blank unless Matrix links the contact to a company—in that case parent_id points to the mapped company partner. Email, phone, address, and custom fields are transferred as direct fields or custom columns. Duplicate detection uses email address normalization to avoid creating multiple partner records for the same individual.

Matrix companies map to Odoo res.partner with type='company'. These must load before contacts so that child-partner records can reference the correct parent_id. Website, industry, and employee count all transfer as direct fields on the partner. Company address components are split into street, street2, city, state_id, zip, and country_id. If Matrix stores locations for a company, location is created as a child partner of type 'contact' linked to the parent company.

Matrix deals become Odoo crm.lead records. The type field is set to 'opportunity' so they appear in the Odoo pipeline view. Stage names are looked up in the target crm_team's stage set and mapped value-by-value. Planned revenue, probability, and close date transfer as fields. Any custom fields are mapped to x_studio columns on crm.lead. If the deal has attachments, they are linked via ir.attachment after the lead record is inserted.

Matrix leads that have not been converted to deals land in Odoo as crm.lead with type='lead'. They appear in the Leads menu rather than the Pipeline. Converting them in Odoo creates the partner record and links the opportunity. Lead source, tags, and fields transfer to the crm.lead record. Stage defaults to the team’s default stage. If the lead has an email, Odoo links it to the matching partner on conversion.

Matrix pipeline stage names map to Odoo crm.stage records. Each stage is scoped to a crm.team via team_id. If Matrix has multiple pipelines, we create multiple Odoo teams and assign their respective stages so stage pick-lists stay correct per team.

Matrix scheduled tasks (calls, follow-ups) map to Odoo crm.activity. Activity type_id links to the correct crm.activity.type (call, meeting, etc.) and res_model='crm.lead' attaches the activity to the target opportunity. The mapping also includes the activity's deadline (date_deadline), responsible user (user_id), and optional description. If the activity references a specific contact, the res_id points to the related crm.lead or res.partner record. Unmapped activity types are logged as generic 'Other' and can be reclassified after migration.

Logged emails and completed meetings become Odoo mail.message records with model='crm.lead'. The message body and subject transfer; original timestamps are preserved as write_date for audit continuity. Each message record stores the author, body, and creation timestamp. The model field is set to 'crm.lead' and res_id references the target opportunity. Attachments linked to the message are migrated as separate ir.attachment records. Any HTML content is converted to plain text for consistency.

Matrix notes migrate as Odoo mail.message records with subtype='mt_note'. They attach to the target crm.lead or res.partner via res_id/res_model. Plain-text formatting is preserved; HTML notes are stripped to plain text to match Odoo's note rendering. The note subtype is set to 'mt_note', ensuring it appears in the Odoo chatter as an internal note. If the original note contains any mention of a contact or deal, the res_id is linked accordingly. Rich-text formatting is simplified to plain text.

Matrix file attachments download from the source and re-upload to Odoo's ir.attachment table, linked to the migrated record via res_model and res_id. File name, mimetype, and create date are all preserved. During extraction, file metadata including name, mimetype, and create date are captured. Files are uploaded via Odoo's ir.attachment controller using base64 encoding. Theattachment is linked to the appropriate res_model and res_id. Duplicate files are detected by hash to avoid re-uploading.

Matrix owner IDs are resolved by email against Odoo res.users. Where no matching user exists, the record is assigned to the migration fallback user and the original owner ID is stored in x_matrix_owner_id for manual reassignment. If the email lookup fails, the record is assigned to a designated fallback user and a custom field x_matrix_owner_id stores the original Matrix owner identifier. The fallback user is configurable and can be changed post-migration. Owner resolution is logged for audit.

Matrix tags map to Odoo crm.lead.tag records. Tags are de-duplicated (case-insensitive) during migration and written to the crm_lead_tag_rel junction table. Tags shared across multiple record types are preserved per lead. Tag names are normalized to title case and stripped of leading/trailing spaces before insertion. The migration script checks for existing tags in the Odoo database; matching tags are reused rather than duplicated. Tags are associated with leads via the crm_lead_tag_rel junction table.

Matrix custom objects with their own schema require Odoo custom field creation before data loads. We document the full custom object schema from Matrix and deliver an Odoo field-creation script as part of the pre-migration plan. For each custom object, we generate a field-creation script that defines the necessary custom fields in Odoo, using x_studio prefixes for Community and Enterprise. The script is reviewed and executed before data loading. Custom object relationships are mapped to many-to-one or one-to-many fields on the target model.

Matrix lead source values map to Odoo utm.source records and link via source_id on crm.lead. Where Matrix uses campaign names not present in Odoo's default utm configuration, we pre-create the source records during the schema-setup phase. If a Matrix campaign does not exist in Odoo's utm.source list, the migration script pre-creates the record during the schema-setup phase. Source IDs are stored on crm.lead via source_id. The mapping also preserves medium and campaign tags when present. and ensures proper attribution reporting in Odoo's analytics.