Migrate from Socrates to Odoo CRM

Socrates contacts with a populated company field map to Odoo crm.lead records with partner_id set to the corresponding res.partner record. Contacts without a company land as crm.lead with partner_id blank. The crm.lead type field ('lead' vs 'opportunity') is set based on the Socrates lifecycle_stage — prospects map as 'lead', customers as 'opportunity'.

Socrates company associations on a Contact create or update a corresponding Odoo res.partner record via the Odoo xmlrpc External API. The Socrates Contact firstname and lastname concatenate into res.partner.name, while email, phone, and address fields map directly to res.partner.email, res.partner.phone, and res.partner.street/city/state_id/zip/country_id respectively. If a res.partner with the same email already exists, FlitStack updates that record instead of creating a duplicate, preserving any additional Odoo-specific fields.

Socrates Company objects map to Odoo res.partner with partner_type='company'. The res.partner.vat field receives the Socrates company tax ID if present. Odoo res.partner records of type 'company' serve as the parent for all Socrates Contact records that list this company as their primary association.

Socrates Deals map to Odoo crm.lead records with type='opportunity'. The deal name becomes crm.lead.name; deal amount becomes crm.lead.planned_revenue. The Socrates pipeline stage name maps to an Odoo crm.stage record by name lookup, populating crm.lead.stage_id. Probability is read from the Odoo stage record rather than copied from Socrates to keep Odoo's probability model authoritative.

Each Socrates pipeline creates a set of crm.stage rows in Odoo. Stage names map by exact string match; stage sequence order preserves the Socrates kanban card order. If a Socrates pipeline name matches an existing Odoo stage, FlitStack uses the existing stage rather than duplicating it. New stages are created via xmlrpc before deal records load.

Socrates custom Contact properties that have no direct Odoo equivalent (numeric lead scores, multi-select flags, relationship-type pick-lists) are created as ir.model.fields on the crm.lead model before migration. Pick-list custom properties require explicit selection=[] tuples — FlitStack enumerates the distinct Socrates values from the export to build the tuple. The original Socrates property values load into the new custom field on each crm.lead record.

Socrates deal custom properties map to Odoo ir.model.fields on the crm.lead model. Date custom fields use odoo.fields.Date; numeric fields use odoo.fields.Float or Integer depending on the Socrates schema type. Value-mapping custom fields (e.g., a Deal custom pick-list like 'Region' or 'Product Line') require selection tuples built from Socrates distinct values.

Socrates engagement records (calls, emails, meetings) map to Odoo mail.activity rows with res_model='crm.lead' and res_id pointing to the migrated crm.lead record. Activity type maps via Socrates engagement_type to Odoo activity_type_id (call, email, meeting). Original timestamps are preserved as mail.activity.date_deadline for follow-up scheduling; creation date is stored in a custom Created_in_Source__c field for audit purposes.

Socrates notes map to Odoo note.note records. The note body maps to note.note.memo. The related Socrates record (Contact, Deal) is stored via note.note.res_model and note.note.res_id pointing to the corresponding Odoo record. If Odoo Note app is not installed, notes migrate as mail.message records on the crm.lead.

Socrates owner IDs are resolved by matching the owner email to Odoo res.users.login. If an Odoo res.users record with the matching email exists, the crm.lead.user_id is set to that user ID. If no match is found, FlitStack flags the unmapped owner before migration and assigns the record to a configurable fallback Odoo user — no record lands without an owner.

Socrates file attachments (documents, images) map to Odoo ir.attachment with name, datas (base64-encoded content), res_model='crm.lead', and res_id pointing to the target opportunity. Inline images in notes are extracted and saved as separate ir.attachment records. File size limits follow Odoo's 25MB per-file default; files exceeding this threshold are flagged for manual handling.

Socrates contact tags map to Odoo res.partner.category (tag) records. The Socrates tag name becomes the category name; if a matching category already exists, FlitStack reuses it rather than creating a duplicate. Tags are linked to the migrated res.partner via res.partner.category_id many2many relation. Deal-level tags map to crm.lead.tag_ids using the same pattern.