Migrate from Kordeva to Odoo CRM

Kordeva Contacts with a defined lifecycle or status property split into Odoo CRM Lead (unqualified prospects) and Contact (qualified buyers attached to a Company). We apply the split rule during scoping using Kordeva's contact status or custom lifecycle field as the criterion, and store the original Kordeva lifecycle value in a custom field on the Odoo Lead or Contact for historical audit. If no lifecycle property exists, all Contacts migrate to Odoo Lead by default and the customer decides which records to convert to Contact post-migration.

Kordeva Company records map directly to Odoo CRM Company. The company name becomes the Odoo Company name field, and any Kordeva custom company-level fields migrate to Odoo custom fields on the res.partner model. Company-contact associations preserve as Odoo's child-partner relationships under the parent Company.

Kordeva Deals map to Odoo CRM Opportunity. The deal name maps to opportunity name, deal amount maps to Odoo's expected_revenue and planned_revenue fields, and Kordeva pipeline stage names map to Odoo stage values. We create Odoo stages matching Kordeva's pipeline stages before migration and configure probability percentages per stage.

Each Kordeva deal pipeline maps to an Odoo CRM team with its own stage sequence. Stage names migrate verbatim or are renamed during scoping if the customer wants a cleaner Odoo stage label set. Stage probabilities transfer as integer percentages on each Odoo stage record.

Kordeva Custom Fields API exposes extended attributes on Contacts, Companies, Deals, and Activities. We enumerate every custom field definition during discovery, preserve field type (text, number, date, picklist, checkbox), and recreate each as an Odoo custom field on the matching model before data import. Multi-select picklists in Kordeva map to Odoo selection fields or many2many tags depending on the field cardinality.

Kordeva Owners (the assigned user on Contact, Company, Deal, and Activity) map to Odoo CRM User by email match. We extract every distinct owner referenced on migrating records and match against Odoo user records. Any Kordeva Owner without a matching Odoo User enters a reconciliation queue for the customer's admin to provision before record import resumes.

Kordeva email engagements (email logs against a Contact or Deal) migrate to Odoo mail.message records linked via the mail.thread model to the corresponding Odoo Lead, Contact, Company, or Opportunity. Email body, subject, sender, and timestamp transfer. Odoo's mail.tracking.value model preserves tracking status if Kordeva provides it.

Kordeva call engagements map to Odoo Note records with a call subtype tag. Call duration, disposition, and recording URL (if stored as a URL reference in Kordeva) migrate to Odoo note body fields. Odoo's phone module fields (x_phone_call_duration__c) are created during schema setup if structured call data is present.

Kordeva meeting engagements map to Odoo Calendar.Event records. Meeting title, start and end datetime, location, and attendee list transfer. Odoo Calendar attendee links (res.partner records) are resolved by email match against the migrated Contact or Lead records.

Kordeva task engagements map to Odoo CRM project tasks within the default CRM project. Task name, description, due date, priority, and assigned user transfer. Status mapping aligns Kordeva task states to Odoo stage values on the CRM task project. If Kordeva task hierarchy (subtasks) exists, we flatten to top-level tasks in Odoo with a parent task reference in the notes field.

Kordeva free-text notes logged against Contacts, Companies, or Deals migrate to Odoo Note records. Notes attach to the Odoo record via Odoo's res_id/res_model referencing the migrated Lead, Contact, Company, or Opportunity. Rich text content transfers as-is; attachments migrate as Odoo IrAttachment records linked to the Note.

Kordeva invoice records, line items, and payment status transfer to Odoo as res.partner records with an accounting flag indicating billing relationship. Odoo's full Accounting module (Invoicing) is a separate module from CRM; invoice records requiring full invoice schema (invoice number, date, amount, tax, payment terms) are migrated separately as Odoo account.move records only if the customer activates the Odoo Accounting module. Without Accounting active, invoice metadata migrates as structured note fields on the Contact for accounts receivable context.