Migrate from Krayin CRM to Odoo CRM

Krayin Leads map directly to Odoo CRM Lead. The Krayin lead_id migrates as a custom reference field (x_krayin_lead_id) for audit traceability. Lead status values map to Odoo stage names, with Krayin pipeline stages configured as Odoo stages under the Lead's Kanban view. Any Krayin lead score values migrate to a custom float field in Odoo since Odoo's native lead scoring is AI-driven and requires Odoo Enterprise or a third-party module.

Krayin Persons map to Odoo Contacts. We map name, email, phone, and address fields directly, and resolve the Krayin company_id (Persons linked to Companies) by matching on company name to an Odoo Account created first in the load order. Krayin tags on Persons migrate to Odoo Tags (x_tags or the native tag_ids if the customer enables Tags in Odoo Settings). Custom attribute values on Persons migrate to Odoo custom fields created during schema design.

Krayin Company records map to Odoo CRM Account. The company name becomes the Account name, website migrates to the Account website field, and any custom address fields map to the Account's contact address. Account is created before Person import so that the parent account lookup on Contact is satisfied at the moment of insert. Krayin company phone and industry values map to Odoo Account custom fields when no direct field exists.

Krayin Deals map to Odoo CRM Opportunity. The Krayin deal amount, probability (stored as a percentage), expected close date, and stage name map to Odoo's expected_revenue, probability, date_deadline, and stage_id. The Krayin lead_id or person_id attached to the Deal resolves to the corresponding Odoo Lead or Contact via the reference fields preserved during import. Closed-Lost and Closed-Won reason values from Krayin custom fields map to Odoo Opportunity custom fields.

Krayin Quotes map to Odoo Sale Orders in the Quotation state. Line items map to Sale Order Lines with product, quantity, unit price, and discount preserved. The Krayin Person or Company on the Quote resolves to an Odoo Partner (Contact or Account) and a Contact (for bill-to/ship-to). Custom quote templates, approval workflows, and e-signature status from Krayin do not migrate; we document them in the scope deliverable for manual rebuild in Odoo Sales.

Krayin Products map to Odoo Product Templates. SKU maps to the Odoo product.default_code field, name maps to the template name, price maps to the Odoo list_price, and cost maps to the standard_price if populated in Krayin. Product type (goods vs. services) maps to the Odoo product type field (storable vs. consumable vs. service). Inventory quantities migrate if Odoo inventory is activated; otherwise products import as service or consumable type.

Krayin call activities map to Odoo CRM Next Activities on the Lead or Opportunity, represented as Task records with activity_type set to Call. Duration, disposition, and notes from Krayin migrate to custom fields on the Odoo activity. The original Krayin activity timestamp migrates as the Odoo activity's create_date for timeline ordering.

Krayin meeting activities map to Odoo Calendar Event records. Start datetime, end datetime, location, and description migrate directly. Attendee resolution links the meeting to the Krayin-linked Person or Deal by resolving the Krayin person_id to the Odoo Contact and lead_id to the Odoo Lead via the preserved reference fields.

Krayin task activities map to Odoo CRM Task records on the related Lead or Opportunity. Task title, description, due date, and status (open/closed) migrate. Krayin task assignments migrate by matching the Krayin user_id to an Odoo User record by email.

Krayin note activities map to Odoo Mail Message records with message_type = notification (displayed as a note in the chatter). Note body migrates as plain text with the original Krayin timestamp preserved. Notes linked to Deals map to the Odoo Opportunity chatter; notes linked to Persons map to the Contact chatter.

Krayin pipeline definitions and their custom stages migrate as Odoo CRM Stage configurations under the Leads and Opportunities Kanban views. Each Krayin pipeline becomes a separate Kanban column set in Odoo. Stage probabilities migrate from Krayin to Odoo stage probability values, and stage order is preserved. Automation rules per stage in Krayin (which cannot be exported) are documented in the scope deliverable for rebuild in Odoo Workflow Builder or Automated Actions.

Krayin Users map to Odoo Users. We match by email address and import name, email, and role. Krayin role and permission sets require manual reconfiguration in Odoo's Access Rights settings (Settings > Users > Access Rights) because Krayin and Odoo use different permission models. Active/inactive status migrates as-is; the customer's Odoo admin activates new users post-migration.

Krayin tag assignments on Leads, Persons, and Deals migrate as tag string arrays stored in a custom multi-value field x_krayin_tags on the corresponding Odoo record. If the customer has activated Odoo's native Tags (available in CRM Settings), we map to the native tag_ids field instead. Tags with no equivalent in Odoo are preserved as string values for post-migration cleanup.

Krayin custom attributes on Leads, Persons, Companies, Deals, and Products migrate to Odoo custom fields. We probe the Krayin custom_attributes database table during discovery since not all custom attribute types are exposed via the REST API. Dropdown and multi-select attributes in Krayin map to Odoo selection fields or many2many tags depending on cardinality. Date and datetime attributes migrate as Odoo date/datetime fields. The Odoo custom fields are created before migration in a staging environment for validation.