Migrate from Sales Creatio to Odoo CRM

Creatio Accounts (companies) map directly to Odoo res.partner records with partner_type set to 'company'. Standard address fields (street, city, state, country, zip), industry, phone, and website migrate as-is. The primary contact within the Account maps to a separate res.partner record linked via parent_id. We preserve the Account owner (user_id) from Creatio as the Salesperson on the Odoo partner record.

Creatio Contacts map to Odoo res.partner records with partner_type set to 'individual' and a parent_id reference to the Account partner. Email, phone, mobile, job title, and department fields migrate directly. Lifecycle stage from Creatio becomes a custom selection field (x_creatio_lifecycle) on the partner for reporting continuity.

Creatio Leads map to Odoo crm.lead records. The Lead source, status, rating, and conversion date from Creatio map to Odoo's source_id, stage_id, priority, and date_closed fields respectively. Unconverted Leads in Creatio become Odoo Leads; converted Leads are represented as the linked Opportunity record in Odoo. We preserve the original Lead creation date as x_creatio_lead_create_date on the Odoo record.

Creatio Opportunities map to Odoo crm.lead records of type 'opportunity'. Deal amount maps to Odoo's expected_revenue field. The Creatio pipeline stage maps to Odoo crm.stage (stage sequence). Close date migrates as date_deadline. Probability is preserved as a custom float field (x_creatio_probability) since Odoo's stage-based probability calculation differs from Creatio's custom probabilities per deal.

Creatio's multiple named pipelines require Odoo Record Type or crm.team configuration to represent. Each Creatio pipeline becomes either a separate crm.team (for territory-based segmentation) or stage names within the single Odoo pipeline. Stage order, probability percentages, and stage type (all stages or closed stages only) are configured in Odoo Settings > CRM > Stages before opportunity migration.

Creatio Cases map to Odoo Helpdesk tickets (helpdesk.ticket) if the Helpdesk app is installed in the Odoo instance. Case priority maps to Odoo ticket priority (0-5). Case status (New, In Progress, Pending, Resolved, Closed) maps to ticket stage_id. Account and Contact lookups map to partner_id and partner_asset_id on the ticket. If Helpdesk is not installed, Cases map to crm.lead as a separate object type, which increases timeline and cost.

Creatio Activities are heterogeneous: calls and tasks map to Odoo mail.activity (with activity_type_id set to 'call' or 'to_do'); meetings map to calendar.event with attendee links to the res.partner record via calendar.event.res_partner_rel; emails map to mail.message records linked to the crm.lead or res.partner. The Regarding (lookup) from Creatio resolves to the Odoo record_id and res_model fields. Activity timestamps (created_on) are preserved as activity_date_deadline offset to the original date.

Creatio Orders map to Odoo sale.order records. Order header fields (order number, date, Account, Contact) migrate directly. The Order-to-Product lookup resolves to the Odoo product.product reference at migration time. Order status maps to Odoo state (draft, sent, sale, done, cancel). Historical Orders are migrated as confirmed records to preserve the full sales record.

Creatio Products map to Odoo product.product records. Standard price, cost, unit of measure (uom_id), and product category map directly. The product type (goods vs service) maps to Odoo's type field (product vs service). Product images stored in Creatio migrate as Odoo product image attachments via ir.attachment.

Creatio custom objects created in Studio map to Odoo custom models via Developer mode (Settings > Technical > Database Structure > Models). We extract the Creatio custom object schema (field name, type, required flag) and create the equivalent Odoo model before data migration. Custom field types including lookups, dropdowns, checkboxes, and date fields are mapped to their Odoo field type equivalents. Any lookup fields referencing standard Creatio objects require a pre-migration lookup table to resolve the foreign key at migration time.

Creatio custom fields added to standard objects (Account, Contact, Opportunity) map to Odoo ir.model.fields records with name prefixed x_creatio_ to follow Odoo's custom field convention. We extract field type, required constraints, and default values from Creatio and create matching fields on the Odoo res.partner or crm.lead model before migration. Lookup-type custom fields require a separate resolution step to map the Creatio lookup value to the Odoo record ID.

Creatio Users and Owners map to Odoo res.users records matched by email address. Active status, name, and login (email) transfer directly. The Creatio organizational unit maps to Odoo's property_stock_formal entity if the warehouse or inventory modules are active. Any Creatio Owner without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before record migration proceeds.