Migrate from Drivecentric to Odoo CRM

DriveCentric Contact individuals map to Odoo res.partner records with contact_type = 'contact'. Name, email, phone, address, job title, and custom fields migrate directly. DriveCentric contacts associated with a primary dealership carry the dealership name into the company_name field for Odoo's reporting model.

DriveCentric Dealership records (organizations) map to Odoo res.partner with contact_type = 'company'. A custom x_drivecentric_contact_type field distinguishes dealership records from individual contacts in Odoo. Multiple DriveCentric dealership branches map to parent/child res.partner hierarchies using Odoo's parent_id field where applicable. The hierarchy mapping preserves the dealership's geographic structure, allowing reports to filter by region or branch.

DriveCentric leads (unsold or early-stage opportunities) map to Odoo crm.lead records with type = 'lead'. Lead source, stage, priority, owner email, and create timestamp all migrate. Custom lead properties like lead_score or marketing_source map to x_ custom fields on crm.lead.

DriveCentric sold opportunities map to Odoo crm.lead records with type = 'opportunity'. The full opportunity name, amount, close date, stage name, probability, and owner email migrate. Automotive-specific fields like vehicle_id, VIN, and DMS_Opportunity_ID become custom fields on the crm.lead record.

DriveCentric pipeline stages (New Lead, Working, Demo Scheduled, Won, Lost) require a value-mapping table to Odoo's crm.stage names. Stage probability percentages map to Odoo's probability field per stage. We deliver the mapping table during scoping so stage assignment is intentional and not alphabetical.

DriveCentric logged calls migrate as Odoo mail.activity records with activity_type_id mapped to a custom 'Call' activity type we configure in Odoo before migration. Subject, date, notes, and owner email all transfer. Original timestamp preserved in activity_date_deadline or a custom x_original_date field.

DriveCentric logged emails migrate as Odoo mail.activity records with activity_type_id set to 'Email'. Subject, body content, direction (inbound/outbound), and owner email transfer. Email threads linked to contacts or opportunities via res_id and res_model foreign keys. Original email timestamps are stored in the activity_date_deadline field, ensuring activity history aligns with the original communication timeline.

DriveCentric notes migrate as Odoo ir.attachment records with res_model = 'crm.lead' or 'res.partner' depending on the parent record type. Note body content is stored as the attachment's description field. Rich-text formatting is preserved where possible, and inline images are downloaded and reattached as binary files.

DriveCentric file attachments re-upload to Odoo ir.attachment linked to the correct res_model and res_id (crm.lead or res.partner). File name, binary content, and create date migrate. Odoo's default 25MB per-file limit is enforced — files exceeding the limit are flagged and handled via alternative download links.

DriveCentric owner_id (a string identifier) resolves to Odoo res.users by email match. Unmatched owners are flagged before migration so Odoo accounts can be created first. Records for unmatched owners land with a fallback user_id assigned — your admin resolves ownership post-migration.

DriveCentric automotive custom fields (DMS_Customer_ID, vehicle_vin, vehicle_year, vehicle_make, vehicle_model, vehicle_trim, vehicle_color, stock_number, lot_id) have no native Odoo CRM equivalent. We create x_dms_customer_id, x_vehicle_vin, x_vehicle_year, x_vehicle_make, x_vehicle_model, x_stock_number, and x_lot_id as Char, Integer, or Selection fields on crm.lead before migration begins.

DriveCentric lifecycle_stage values (New, Active, At Risk, Churned) have no direct Odoo CRM equivalent. We create x_lifecycle_stage as a Selection field on crm.lead with the same pick-list values. Stage-changed timestamps migrate as x_lifecycle_stage_date custom datetime fields for reporting continuity. You can configure stage change alerts or automated actions based on the x_lifecycle_stage value in Odoo's workflow engine.