Migrate from Chakra Sales CRM to Odoo CRM

Chakra Sales CRM Leads map directly to Odoo crm.lead records. The customer chooses whether Odoo treats incoming leads as Odoo Leads (stage-based qualification) or converts them directly to Opportunities at import time. Chakra lead source, status, and qualification fields map to Odoo's lead_name, country_id, and medium_id fields. Any Chakra lead scoring custom fields require a corresponding Decimal or Integer custom field created in Odoo Studio before migration.

Chakra Deals map to Odoo crm.lead records with type=opportunity. The Chakra deal amount maps to Odoo's planned_revenue field, expected close date maps to date_deadline, and owner maps to Odoo user_id resolved by email match against Odoo Users. Stage names are captured from Chakra and mapped to Odoo's stage_id, which requires a pre-migration audit of the destination Odoo pipeline stage sequence.

Chakra Accounts (Companies) map to Odoo res.partner records where is_company=True. The Chakra company name becomes partner name; domain becomes website. Parent-child account hierarchies in Chakra map to Odoo's parent_id on res.partner. We create Company partners before Contact partners so that the parent_id relationship is satisfied at Contact import time.

Chakra Contacts map to Odoo res.partner records where is_company=False, with parent_id pointing to the corresponding company partner. Name, email, phone, and job title migrate directly. Chakra custom contact properties require a corresponding field created in Odoo Studio before migration, and we flag any field type mismatches (Chakra text vs Odoo selection, for example) during the discovery audit.

Chakra's pipeline stages are defined per-account via no-code setup and do not export with a schema file. We document the stage sequence (names, order, probabilities) during the discovery call, then configure matching crm.stage records in Odoo before migration. Stage probabilities from Chakra map to Odoo stage probability percentages. If Chakra has more stages than the Odoo database, we consolidate into the closest Odoo-native stage set.

Chakra Tasks map to Odoo mail.activity records linked to the target crm.lead or res.partner. Activity type (call, meeting, email, to-do) maps to Odoo's activity_type_id. Due date, assignee, and status preserve. If Chakra stores richer task metadata (priority, sub-task hierarchy), we map priority to Odoo's priority field and flag sub-task hierarchy for the customer admin to restructure in Odoo.

Chakra Notes attached to Contacts, Leads, or Deals migrate as Odoo mail.message records with message_type=comment on the parent crm.lead or res.partner. Note body migrates as HTML content. Author is set to the migrating user's Odoo User record resolved by email. Note creation timestamps preserve for activity timeline ordering.

Chakra custom fields on Contacts, Leads, Deals, and Accounts require pre-migration Odoo Studio configuration to create matching fields. We perform a field-level inventory during discovery, comparing Chakra custom fields against Odoo's standard field list, then instruct which fields to create as Char, Integer, Float, Date, or Selection types in Odoo before the load phase begins. Custom fields without a logical Odoo equivalent are flagged as requiring admin decision.

Chakra Owners map to Odoo res.users records resolved by email match. Any Chakra Owner without a matching Odoo User is held in a reconciliation queue; the customer's Odoo admin provisions the missing User before record import resumes. Inactive Chakra owners map to inactive Odoo Users if the customer wants to preserve historical assignment.

File attachments linked to Chakra CRM records may not export cleanly via the Cloud API. We audit attachment coverage during the pre-migration data audit. For records with critical attachments, we request a manual file export from the source account or perform a supplementary file transfer step, then link the resulting files to Odoo ir.attachment records tied to the correct res.partner or crm.lead via res_model and res_id.

Chakra workflow automation rules do not export via the Cloud API. We document each automation during the discovery phase: trigger event, conditions, and action sequence. We deliver a written inventory mapping each Chakra automation to a recommended Odoo Action Rule or Server Action configuration. The customer's admin rebuilds automations in Odoo Studio post-migration.

Chakra call logs migrate as Odoo mail.activity records with activity_type_id corresponding to a call type. Call duration, disposition, and any recording URL stored in Chakra custom fields map to Odoo custom fields on the activity. ActivityDate is set to the original Chakra timestamp for timeline ordering.

Chakra email engagement history migrates as Odoo mail.message records linked to the parent crm.lead or res.partner. Email subject and body preserve; attachments migrate as ir.attachment records. The message_type is set to email. We use Odoo's mail.message creation via XML-RPC rather than the mail.compose.message route to preserve the original timestamp.

Chakra meeting records migrate as Odoo calendar.event entries. Start and end datetime, location, and attendee list preserve. Attendees map to Odoo res.partner or res.users records via the calendar.attendee model. If Chakra stores meeting notes as separate records, those migrate as mail.message linked to the calendar.event.