Migrate from Creatio to Odoo CRM

Creatio Account maps directly to Odoo res.partner with company_type set to 'company'. Address fields (street, city, state, zip, country) map to Odoo's address fields (street, street2, city, state_id, zip, country_id). Industry lookup in Creatio maps to an Odoo custom selection field or a many2one to an industry master table that we create during schema setup. The Account name maps to partner_name on res.partner. We use the Account's unique Id as an external ID during import so that related records can reference it correctly.

Creatio Contact maps to Odoo res.partner with company_type set to 'person', linked to the parent Account (res.partner with company_type='company') via parent_id. The Contact's email, phone, job title, department, and mobile fields map to corresponding res.partner fields. We separate Contacts from Accounts by reading the Contact's company_type discriminator field. Owner assignment (the Creatio owner lookup) maps to Odoo's user_id field on crm.lead and crm.opportunity after the User reconciliation step. Lifecycle stage from Creatio migrates to a custom Char field lifecycle_stage__c for audit.

Creatio Opportunity maps to Odoo crm.lead with type = 'opportunity'. Stage name from Creatio maps to Odoo's stage_id lookup against the pipeline's stage sequence. Amount, probability, and expected close date map to expected_revenue, probability, and date_deadline on crm.lead. The Account (Company) lookup resolves to the res.partner parent_id on crm.lead at migration time using the external ID we set during Account migration. The Opportunity's linked Contact(s) attach as follower records on the Odoo opportunity.

Each Creatio pipeline maps to an Odoo crm.team (sales team) with its own ordered stage sequence defined in crm.stage. We extract the full stage list including order, name, probability percentage, and any stage automation triggers from Creatio's package schema before migration. Stage probability values map to Odoo's stage probability (rounded to integer). Odoo's stage sequence is ordered by sequence integer, not by name, so we preserve Creatio's stage ordering explicitly during configuration.

Creatio's unified Activity schema stores Call, Email, and Task records with a discriminative activity type field. We separate by type at migration time: Call records map to Odoo crm.activity with activity_type_id set to a type whose name contains 'Call'; Email records map to a type named 'Email'; Task records map to a type named 'Task'. Each activity's subject, body (description), date, and duration map to corresponding Odoo fields. The activity is linked to the parent Contact or Opportunity record via res_id and res_model references.

Creatio Lead maps to Odoo crm.lead with type = 'lead' (separate from Opportunity). Lead status maps to Odoo's stage_id within the lead's pipeline. Source attribution (Lead Source) migrates to Odoo's source_id lookup against the utm.source master table. Lead score migrates to a custom Float field lead_score__c if the customer uses lead scoring in Creatio. Lead owner resolves via the User mapping step.

Creatio Cases map to Odoo crm.helpdesk.ticket if the Helpdesk app is installed on the destination Odoo instance; otherwise Cases map to crm.lead with a custom type discriminator. Case status, priority, and resolution SLA fields map to ticket stage_id, priority, and tag fields. The Case's linked Contact and Account map to the ticket's partner_id and project_id references. If Odoo Helpdesk is not available in the destination subscription, we map Cases to a custom crm.case model we create during schema setup.

Creatio Products map to Odoo product.product records with the product's name, default_code (SKU), list_price, and standard_price migrated directly. Multi-currency pricing from Creatio (available on Business and Scale) requires creating Odoo product.pricelist items per currency rather than storing currency on the product record itself, since Odoo stores product price in the company currency and uses pricelists for currency-specific pricing.

Creatio Users map to Odoo res.users by email match. We extract every distinct owner referenced on Accounts, Contacts, Opportunities, Cases, and Activities during the extraction phase. Any Creatio user without a matching Odoo res.users record is placed in a reconciliation queue for the customer's Odoo admin to provision before record migration proceeds. OwnerId references on all standard objects are resolved at writeback time using this map.

Creatio file attachments migrate to Odoo ir.attachment records. We detect the storage mode during discovery: if UseEntityFileApi is enabled (S3 or Azure Blob), we download files from the external storage endpoint and upload them to Odoo's ir.attachment storage location (database or configured external storage). Files without a Creatio storage location are skipped and flagged in the reconciliation report. The ir.attachment's res_model and res_id link the file to the corresponding migrated Odoo record.

Creatio custom entity schemas (built in the Object designer, stored in user packages) require schema reverse-engineering before migration. We extract the package schema XML, parse the column definitions and lookup relationships, and create corresponding Odoo models via ir.model and ir.model.fields. Each custom field maps to an Odoo field type: Char/Text, Integer/Float, Date/Datetime, Many2one, One2many, Many2many, Selection. Lookup dependencies are resolved by ensuring parent models (Accounts, Contacts, Opportunities) migrate before custom objects.

Creatio custom fields on base schemas (Account, Contact, Opportunity, Case) map to Odoo custom fields on the corresponding model. Calculated fields in Creatio do not migrate as formulas because Odoo handles computed fields differently; we skip the calculated value and document the formula for Odoo Studio rebuild as a computed field or onchange method. Multicurrency fields in Creatio migrate as Odoo monetary fields with a Many2one to res.currency, and the currency lookup resolves from the Creatio currency record mapping.