Migrate from Cordis CRM to Odoo CRM

Cordis CRM Contacts map to Odoo res.partner records with partner_type set to 'contact'. The Cordis contact profile fields (name, email, phone, address) map to Odoo's standard partner fields. Interaction history and custom contact properties transfer to Odoo partner fields or custom res.partner fields created during schema setup. We resolve the company linkage using Cordis's company relationship graph and assign partner_id (the company contact record) in Odoo.

Cordis CRM Company records map to Odoo res.partner with is_company=True. The company name maps to name, website from Cordis's domain field, and any industry or revenue data to custom fields. Company is created before contact import so that the partner_id lookup is satisfied at the moment of contact insert.

Cordis CRM pipeline stages map to Odoo crm.lead stage_id values within the appropriate sales team (crm.team). Each Cordis pipeline becomes a separate Odoo sales team or a stage category, with stage order and probability percentages preserved. We create the Odoo stage configuration before migration and assign stage_ids during lead import.

Cordis stage names and probabilities migrate to Odoo crm.stage records within the relevant crm.team. Stage probability percentages map to Odoo's probability field on crm.lead. Stage order is preserved using Odoo's sequence field on stage.

Cordis CRM Deals map to Odoo crm.lead records with type='opportunity'. The Cordis deal amount, close date, and stage map to Odoo's expected_revenue, date_closed, and stage_id. The associated contact and company resolve to Odoo res.partner records via the ID mapping table created during earlier import phases.

Cordis CRM Tasks map to Odoo project.task records (for project-tied tasks) or calendar.event records (for scheduled activities). Task status, due date, and assigned owner migrate. Recurrence rules from Cordis do not transfer automatically; we document recurrence patterns in the handoff inventory for manual reconfiguration in Odoo's activity plan scheduling.

Cordis CRM documents linked to contact or company records migrate as Odoo ir.attachment records attached to the corresponding res.partner. We export the latest version of each document, preserve the filename, and re-associate via the record ID mapping table. Document version history (lineage) is not guaranteed to migrate; we flag multi-version documents in the scope document for customer review.

Cordis CRM Campaign records and membership data map to Odoo utm.mixin tracking fields on crm.lead (source_id, campaign_id, medium_id) plus crm.tag records for campaign categorization. Campaign engagement metrics are noted in the handoff inventory for Odoo reporting configuration.

Cordis CRM custom contact and company fields are surveyed during scoping and created as custom ir.model.field records on res.partner in Odoo before import. Field data types are mapped: text to char, numeric to float or integer, date to date, dropdown to selection. Custom field values on records migrate with field-to-field mapping per the scoping survey output.

File attachments linked to Cordis CRM records export individually with filename preservation. We re-associate them to Odoo records (res.partner, crm.lead) using the ID mapping table generated during import. Attachments without a resolvable parent record are placed in an attachments queue for customer admin resolution.

Cordis CRM Owners resolve by email match against Odoo res.users in the destination database. Owners without a matching Odoo user go to a reconciliation queue for the customer's admin to provision or map before record import resumes. Owner mapping must complete before opportunity and task import to satisfy assignment fields.

Cordis CRM interaction history (emails, call logs, meeting records) migrates to Odoo mail.message records linked to the parent res.partner or crm.lead via the ID mapping table. Email content attaches as mail.message body text; call duration and disposition become custom fields. Note that Cordis Google Workspace email history is not auto-exported; we extract from Gmail directly where the customer authorizes access rather than relying on the CRM export.