Migrate from Marketing Creatio to Odoo CRM

Creatio Contacts map directly to Odoo res.partner records. The contact's name splits into firstname and lastname on res.partner; email, phone, and job title map as direct fields. The primary Account link becomes res.partner.parent_id (many companies on one partner handled via the commercial partner link). Multi-company association in Creatio collapses to one primary parent_id with others flagged for manual review.

Creatio Accounts also map to res.partner with partner_type='company'. The organization name populates partner.name, website maps to website, and industry maps as a selection field. Parent-child hierarchies in Creatio translate to res.partner.parent_id on the child company record, preserving the corporate structure. Employees and annual revenue migrate as custom float fields since Odoo base doesn't carry these on the partner by default.

Creatio Leads become Odoo crm.lead records with type='lead'. The lead's status maps to the crm_stage_id via value_mapping, and priority maps to Odoo's priority field (0–4 scale). Source information from Creatio's lead_source field migrates as crm.lead.source_id lookup. Unqualified leads retain their create date and assigned owner (resolved by email) so sales managers can trace pipeline entry history.

Creatio Opportunities map to Odoo crm.lead records with type='opportunity'. The deal amount populates expected_revenue, close date maps to date_deadline, and the pipeline stage resolves to the matching crm_stage_id. Lost opportunities carry their loss_reason in a custom text field since Odoo stores this on the stage rather than the record. Won/lost state is set via stage probability — stages above 90% probability are marked won.

Creatio pipeline definitions become Odoo crm.stage records organized under sales teams (crm.team). Each pipeline in Creatio creates a separate stage sequence in Odoo. Stage display order and probability values are preserved as sequence integers and probability percentages. Teams with multiple Creatio pipelines generate multiple stage sequences under a single team or split across teams depending on your Odoo configuration.

Creatio engagement records — calls, emails, meetings, and notes — all migrate to Odoo's crm.activity log attached to the corresponding crm.lead. The activity's subtype (call, email, meeting) maps to Odoo's activity_type_id via value_mapping. Original timestamps, duration, and body content are preserved. Attachments on activities migrate to ir.attachment linked by res_model='crm.activity' and res_id matching the activity record.

Creatio file attachments on any record re-upload to Odoo ir.attachment linked to the target record (res_model + res_id). File name, mimetype, and binary content are preserved. Odoo's 25MB per-file limit is enforced; files exceeding this are flagged for manual handling. Inline images in Creatio notes are downloaded and re-hosted as attachment records.

Creatio marketing campaign membership and campaign statistics have no native Odoo equivalent — Odoo Email Marketing handles active campaigns differently. We preserve campaign names as crm.tag records for reference and surface campaign membership as a custom many2many field on crm.lead. The campaign's automation logic (nurturing sequences, scoring rules) must be rebuilt in Odoo's Email Marketing or using automated actions.

Creatio custom objects (Enterprise tier) require Odoo-side schema decisions: either extend crm.lead with custom fields or create a new ir.model via Odoo Studio or Python module. We audit your Creatio custom object schema, map each custom field to an Odoo equivalent (selection, char, float, date, many2one), and deliver a schema setup plan before data loads. N:N custom object relationships become Odoo many2many fields or junction models.

Creatio's lead scoring model — whether using explicit numeric scores or grade/rating pick-lists — has no Odoo native equivalent. We migrate the score or rating value to a custom float field (lead_score__c) or selection field (lead_rating__c) on crm.lead. Automated re-scoring based on Odoo activities must be implemented via Odoo's automation rules post-migration.

Creatio owner IDs resolve to Odoo res.users by email address match before migration. Any Creatio owner without a corresponding Odoo user is flagged with a fallback assignment (usually the admin) and a custom partner_id__c field holding the original Creatio owner name. Teams should provision Odoo users before migration so the email match resolves automatically for all active sales reps.

Odoo's write_date and create_date are set at migration time, overwriting original Creatio timestamps. We preserve the original created_on and modified_on values from Creatio in custom datetime fields (original_create_date__c, original_write_date__c) so reporting on record age and modification history remains accurate after cutover.