Migrate from Tekion to Odoo CRM

Tekion Customers (vehicle owners) map to Odoo res.partner records. Tekion's customer type (individual vs. business) maps to Odoo's company_name and individual fields on res.partner. A Tekion customer linked to a dealership account requires Odoo's parent_id field on res.partner to represent the dealership relationship.

Tekion Contacts (dealership staff or customer contacts) map to Odoo res.partner as well. In Odoo, res.partner serves as both contact and company record — Tekion's separate Contact object lands as a res.partner with the 'is_company' flag set to False and a parent_id pointing to the related Customer/Company record.

Tekion's 90-day active lead export maps directly to Odoo crm.lead. Odoo uses crm.lead for both raw leads and qualified opportunities — Tekion leads that are in active stages become Odoo crm.lead records; leads converted to deals in Tekion become crm.lead records with type='opportunity' and a linked partner.

Tekion Deals map to Odoo crm.lead with type='opportunity'. The deal's amount, stage, expected close date, and linked customer map to Odoo's expected_revenue, stage_id, date_deadline, and partner_id respectively. Tekion deal name becomes crm.lead name field. If Tekion deals link to multiple customers, Odoo creates one crm.lead per deal-customer pair.

Tekion pipeline stages map to Odoo crm.stage records scoped to the relevant Odoo sales team. Stage sequence, name, and probability are mapped value-by-value. Tekion stage-entered timestamps are stored as custom datetime fields on the crm.lead record since Odoo's standard crm.lead model does not track historical stage-entry timestamps natively.

Tekion vehicle records (VIN, make, model, year, mileage) have no direct Odoo CRM equivalent. We create a custom Odoo addon that extends res.partner with vehicle-related fields (x_vin, x_make, x_model, x_year, x_last_mileage). Each vehicle record is linked to the res.partner representing the vehicle's owner.

Tekion service records (RO number, service type, date, advisor, status) migrate to a custom Odoo addon model linked to res.partner. Historical service activities are also surfaced as mail.message records on the partner for visibility in Odoo's chatter. Original RO numbers and advisor assignments are preserved in custom fields.

Tekion F&I product attachments (GAP, dent protection, service contracts) linked to deals or customers migrate to Odoo product.product records in a custom product category. The link to the Odoo crm.lead or res.partner is stored via a custom Many2one field in the custom addon since Odoo's standard models do not link F&I products to CRM records natively.

Tekion owner assignments on leads and deals are resolved by email match against Odoo res.users. Unmatched owners are flagged before migration — your team either creates the Odoo user first or assigns those records to a fallback user. Tekion's user permissions model does not map to Odoo's record rules and access groups automatically.

Tekion file attachments on customers, contacts, and deals migrate as Odoo ir.attachment records linked to the corresponding res.partner or crm.lead. Files are re-uploaded via Odoo's attachment storage (filestore). Tekion PDF documents are migrated within the standard 30-day conversion window referenced in Tekion's Implementation Terms.

Tekion logged calls, emails, and notes migrate as Odoo mail.message records with mail.activity subtypes on the relevant crm.lead or res.partner. Original timestamps, author assignments, and attachments are preserved. The mail.message body is stored in Odoo's html field, while subtype (call, email, note) maps to the mail.activity.type value. Odoo's activity kanban view displays these as scheduled and logged activities, and they appear in the partner's or lead's chatter for context.

Any Tekion custom fields on Customers, Contacts, Leads, or Deals require a custom Odoo addon defining the equivalent field on crm.lead or res.partner. The custom field name in Odoo follows the x_<internalname> convention or a named convention defined in your custom addon. Pick-list value mappings are applied value-by-value at migration time.