Migrate from Concord CRM to Odoo CRM

Concord CRM Contacts map to Odoo res.partner records with the customer_rank set to indicate commercial contact status. The Concord contact's company_id foreign key references the migrated Concord Company, which maps to the Odoo res.partner with supplier_rank = 0. Email, phone, job title, address, and custom fields migrate directly. Any Concord Contact without an assigned company_id becomes a standalone res.partner; we flag these for manual review during scoping to determine whether they should receive a parent company record.

Concord CRM Companies map to Odoo res.partner records with supplier_rank = 1 and customer_rank = 0, designating them as commercial entities rather than individual contacts. The company name, domain, address, phone, and all standard and custom fields migrate. Companies must be imported before Contacts in the migration sequence because the res.partner.id generated during the Company import is required as the parent_id on the Contact import to satisfy the many2one relationship.

Concord CRM Deals map to Odoo crm.lead records with type = 'opportunity', attached to the parent res.partner Account via partner_id. Deal value maps to Odoo's planned_revenue field. Concord's deal stage names map to Odoo crm.stage names via the stage mapping matrix defined during scoping; we create Odoo stages with matching names and probability percentages before migration begins. Assigned user maps via email resolution to Odoo user_id. Expected close date migrates to date_deadline. Concord's pipeline concept maps to Odoo's crm.team; we assign the migrated deal to the relevant team based on Concord's pipeline assignment or owner territory.

Concord CRM Products map to Odoo product.product records with name, default_code (SKU), list_price, and standard_price preserved. The Concord product's description field migrates to Odoo's description field. Products are independent records with no foreign-key dependencies, so migration order is flexible. We recommend migrating Products before any Deal records that reference them if the customer plans to attach line items, though Concord Deals do not natively support line items without a custom extension.

Concord CRM Activity records with type = 'call' or 'meeting' map to Odoo calendar.event. We reconstruct the parent association using Concord's linked_resource_type and linked_resource_id: if linked to a Contact, we set res_model = 'res.partner' and res_id = the migrated partner.id; if linked to a Deal, we set res_model = 'crm.lead' and res_id = the migrated opportunity.id. Start and stop times migrate to start and stop fields; duration recalculates from the time delta. Notes from Concord's activity body migrate as a calendar.event.description entry.

Concord CRM Activity records with type = 'task' map to Odoo project.task records linked to the CRM project (project with use_tasks = True). The Concord task's title maps to Odoo's name field, description to the notes field, and due date to the date_deadline. Owner assignment resolves via email match to Odoo user_id. If the customer does not have the Project app enabled in Odoo, tasks are stored in crm.lead as mail.message records with a task flag, and we document this decision during scoping.

Concord CRM Activity records with type = 'note' map to Odoo note.note records. We link the note to the parent record (Contact or Deal) using Concord's linked_resource_type and linked_resource_id with res_model and res_id. The note body migrates as the note.note content field. Activity timestamps are preserved in the note's create_date for audit ordering.

Concord CRM Activity records representing emails map to Odoo mail.message records with message_type = 'email'. Email body migrates as the message body; sender and recipient addresses map to mail.message's author_id and partner_ids. Parent resolution uses Concord's linked_resource_id to set res_model and res_id on the mail.message, linking the email to the correct Contact or Deal. Email attachments from Concord migrate as mail.message attachments, stored as ir.attachment records linked to the message.

Concord CRM custom fields are fully supported via API using the field UUID as the key. Before migration, we pre-create all matching Odoo custom fields using ir.model.fields with the appropriate field type (char, selection, integer, float, date, datetime, boolean, text) and assign them to the correct model (res.partner, crm.lead) and field group. Concord Boolean fields map to Odoo boolean fields; Concord select fields map to Odoo selection fields with the same options. We flag any Concord field types that have no Odoo equivalent (such as Concord-specific multi-select formats) during scoping for manual handling.

Concord CRM Users are resolved by email address against Odoo's res.users table. The migration user must have a matching Odoo user record to populate the owner_id (user_id) on migrated Deals and Activities. Any Concord user without a matching Odoo user goes to a reconciliation queue for the customer's Odoo admin to provision before record import resumes. Role and permission sets from Concord do not map directly to Odoo access rights; we document the Concord role assignments as a separate configuration step for the customer's Odoo admin.

Concord CRM pipeline stages are stored as deal properties and export as stage names or IDs. We create Odoo crm.stage records with matching names and probability percentages before Deals are migrated. Concord's pipeline concept maps to Odoo's crm.team: each Concord pipeline becomes a separate crm.team in Odoo with its own stage sequence. Stage order and visual grouping in Concord map to Odoo's stage sequence within the team's pipeline.

Concord CRM tag values stored as comma-separated or multi-select fields map to Odoo crm.tag records. We extract unique tag values during the data audit, create matching crm.tag records in Odoo before the main migration, and populate tag_ids on crm.lead during import using the tag ID lookup. Tags used for contact classification versus deal classification require separate tagging strategies; we document this decision during scoping.

Concord CRM workflow configurations (trigger: Company/Contact/Deal created, Deal stage changed; action: Create Activity, Send Email, Trigger Webhook) are explicitly not executed during data import. We audit all active workflows during scoping, document their trigger conditions and actions in a written inventory, and provide a recommended Odoo Automated Actions or Studio equivalent for each. The customer's Odoo admin rebuilds these post-migration; we do not convert Concord workflow logic to Odoo server actions as part of the migration scope.

Concord CRM stores file attachments in storage/app with no standard export tool. We extract attachments via direct file system access scoped to the Concord installation, organize them by parent record type (Contact, Company, Deal) using the Concord attachment metadata export, zip by record, and upload to Odoo as ir.attachment records with res_model = 'res.partner' or 'crm.lead' and res_id pointing to the migrated record. This step adds a manual coordination requirement with the customer's server access and is scoped separately if file volume exceeds 5,000 attachments.