Migrate from karmaCRM to Odoo CRM

karmaCRM Contact records map to Odoo res.partner with is_company = False and company_type = 'person'. The karmaCRM company association becomes partner_id on the Odoo record. Address fields (street, city, state, zip, country) map directly. Email, phone, website, and job_title preserve. Custom field values attach as ir.config_parameter or custom res.partner fields created via Odoo Studio before migration. The partner_id lookup requires karmaCRM Company records to import first so the Odoo Partner ID is available at Contact import time.

karmaCRM Company records map to Odoo res.partner with is_company = True and company_type = 'company'. The domain from the company record becomes the website field on the Odoo Partner. Industry and size fields map to custom picklist fields if configured; otherwise they land in a notes field. This object must import before Contacts because Contact records carry a required company_id reference.

karmaCRM Deal records map to Odoo crm.lead with type = 'opportunity'. Deal name becomes name, deal value becomes planned_revenue, stage name maps to stage_id (which requires Odoo stage creation matching the source stage names), and owner maps to user_id via email resolution against res.users. Closed-Lost and Closed-Won states from karmaCRM set the Odoo probability field to 0 or 100 respectively.

karmaCRM Tasks map to Odoo mail.activity records linked to the migrated crm.lead via res_id and model = 'crm.lead'. Task title becomes activity summary, due date maps to date_deadline, and priority maps to priority. Assigned owner maps to user_id via email lookup. Completed status sets the activity as done; open tasks remain pending. Activities import after crm.lead records exist so the res_id reference resolves correctly.

karmaCRM Events map to Odoo calendar.event records. Start time, end time, duration, and location transfer directly. The linked contact and company associations map to calendar.event partner_ids via Odoo EventRelation resolution using the migrated res.partner records. Events import after partner resolution is complete so attendee lookups succeed.

karmaCRM tags applied to contacts and companies map to Odoo crm.tag records. We create matching tag names in Odoo during schema setup and attach them to crm.lead records via crm.tag.rel during the deal import phase. Tags that do not match an existing Odoo tag are created on the fly during migration.

karmaCRM custom field definitions and values are preserved as freeform name-value pairs. For standard-equivalent fields (text, number, date, picklist) we create matching custom fields on res.partner or crm.lead via Odoo Studio before migration. For non-standard fields without a clear Odoo type, we store values in a JSON blob field crm_lead_x_source_data on the target record for manual reconstruction. Odoo requires developer mode or Studio access to create custom fields — we document the full field list and types for the customer's admin to configure before the data phase runs.

karmaCRM email campaign records on Pro and Premium tiers include audience lists, subject lines, send dates, and open/click statistics. Campaign metadata migrates as a structured CSV attached to the related crm.lead records or stored as an Odoo document for admin reference. Email body content does not migrate because Odoo's mass mailing module is separate from its base CRM and requires module installation and template configuration that we handle as post-migration scope.

karmaCRM user records (name, email, role, API token) map to Odoo res.users by email match. Role names from karmaCRM map to Odoo access rights groups (Internal User, Portal User, custom groups) if the customer has configured group-based permissions. Any karmaCRM owner referenced on a Deal, Task, or Event without a matching Odoo user is held in a reconciliation queue for the customer's admin to provision before record import resumes.

karmaCRM attachments linked to contacts, companies, and deals have no documented export path via the API or UI. We flag attachments as out of scope during scoping, document which records have attachments so the customer can manually retrieve them from karmaCRM before account closure, and note that post-migration reattachment to the Odoo res.partner or crm.lead records is a manual step.

karmaCRM integrates with Google Calendar, Google Contacts, and MailChimp. OAuth tokens and integration configurations do not transfer between platforms. We document which integrations are active during discovery and provide a configuration guide for reconnecting them in Odoo (Google Calendar sync via Odoo's calendar module and MailChimp integration via an Odoo App store module).

karmaCRM's webhook definitions are not accessible via the standard API or export path. We document active webhook endpoints and payloads during discovery as a written inventory. The customer or their Odoo developer rebuilds equivalent outbound webhooks using Odoo's base automation rules or a custom module post-migration.