Migrate from Simplicity Enterprise CRM to Odoo CRM

Simplicity Contact records map directly to Odoo Contact records. Standard fields (name, email, phone, address) map to res.partner fields directly. The Simplicity contact_type (individual vs organisation) maps to Odoo's is_company flag. Custom fields on Contact are enumerated during schema discovery and mapped to Odoo custom char, selection, or relational fields on res.partner before import.

Simplicity Company records map to Odoo Contact records with is_company set to true. The company_name from Simplicity becomes the name field on the Odoo contact. Address, industry, and custom fields on the Company object map to equivalent fields on the res.partner record. Contact is imported first so that the Contact record exists before any Contact-to-Company relationship records are loaded.

Simplicity stores the Contact-to-Company relationship explicitly. In Odoo, we model this by setting parent_id on the Contact record to the is_company Contact record. We resolve the parent_id by matching on contact name or domain during the transform phase before import.

Simplicity Deal records map to Odoo CRM Opportunities. The deal name maps to opportunity name, deal value maps to expected_revenue, and Simplicity pipeline stages map to Odoo CRM stage IDs via explicit stage-name mapping. Closed-won and closed-lost reasons from Simplicity custom fields become Odoo CRM tag records or custom Char fields.

Simplicity pipeline stages are enumerated during schema discovery and mapped to Odoo CRM stage records in the correct sequence order. Stage probability values from Simplicity are set on the corresponding Odoo stage. If Simplicity has multiple pipelines, we create separate CRM teams or use tags to scope stages in Odoo.

Simplicity email activity records map to Odoo mail.message records linked via model=res.partner and res_id pointing to the Contact. Email body migrates as HTML content in message_body. We preserve the original timestamp in message_date. Emails without a parent Contact are attached to the nearest related Contact or Company record.

Simplicity call activity records are mapped to CRM phone calls in Odoo CRM. Call duration, disposition, and outcome are stored as custom fields on the crm.phonecall model if Odoo CRM phonecall is activated, or as tagged mail.message records with a call-type tag. The related Contact or Company is resolved via the Simplicity activity parent link.

Simplicity meeting records map to Odoo calendar.event records. Start and end datetime, location, and meeting title migrate directly. Attendees are resolved to Odoo partner records and added as calendar.attendee records. If Odoo Calendar app is not active, meetings are archived as mail.message records with event metadata preserved in message_body.

Simplicity note activity records map to Odoo mail.message records with subtype=note. The note body migrates as message_body in plain text. Notes are linked to the parent Contact, Company, or Deal record via res_model and res_id on the message.

Simplicity segment membership defines which contacts belong to which behavioural or demographic groups. Odoo does not have a native segment object in CRM. We map segments to CRM tags (res.partner.category) with the segment name as the tag label. Contact-segment associations are preserved as TagAssignment records. If the customer has more than 50 segments, we evaluate whether a separate Segment custom object in Odoo is warranted.

Simplicity campaign records (campaign name, type, status, start and end dates) map to Odoo CRM tags on related opportunities plus a reference record in the Odoo Marketing app's mail.mailing model if that app is active. Campaign-to-contact response history is preserved as tagged mail.message records because Odoo CRM does not have a native campaign-response object.

Simplicity stores which contacts responded to which campaigns through which channels. Odoo does not have a campaign-response object. We map these to tagged mail.message records on the Contact, with the tag containing the campaign name and response channel (email_open, email_click, sms_reply). This preserves the behavioural signal for reporting without forcing a non-native object structure into Odoo.

Simplicity loyalty module stores reward tiers, point balances, and program membership as separate relational records linked to Contacts. Odoo CRM does not have a native loyalty module. We map loyalty tier to a custom selection field on res.partner (loyalty_tier), point balance to a custom Float field (loyalty_points), and program membership dates to custom Date fields. If the customer needs full loyalty tracking, Odoo Loyalty app (separate from CRM) can be evaluated as a post-migration add-on.

Simplicity integrates social follower counts and interaction records with Contact profiles. Odoo CRM does not have a native social media integration field set. We map social profile URLs (LinkedIn, Twitter) to custom Char fields on res.partner and store aggregate follower counts as custom Integer fields. Raw interaction logs are archived as structured notes on the Contact for admin reference.

Simplicity's configurable data structure means nearly every object has client-specific custom fields. During schema discovery, we enumerate all active custom fields across all objects, determine their Odoo field type (char, selection, float, date, many2one, etc.), and pre-create the corresponding Odoo custom fields on the target model before data import. Custom picklist values are mapped to Odoo selection options or many2one relational records.

Simplicity file attachments linked to Contacts, Companies, or Deals are mapped to Odoo ir.attachment records. The attachment name, mimetype, and binary content migrate directly. The res_model and res_id on each attachment record are set to point to the migrated Contact or Opportunity so that attachments appear in the correct Odoo record's attachment list.