Migrate from ConSol to Odoo CRM

ConSol stores contacts and companies as separate objects with a linking table. Odoo uses a single res.partner model where contacts and companies share the same table — ConSol contacts migrate as partners with partner_type='contact' and a link to the parent company partner.

ConSol company records map to Odoo res.partner entries with partner_type='company'. The parent_id field on child contact partners references the company partner, preserving ConSol's N:N contact-company relationship in Odoo's hierarchical parent-child model. Since Odoo supports only a single parent per contact, the primary company association is migrated first, with secondary associations preserved in custom fields or partner relationship entries for complete data fidelity.

ConSol ticket records map directly to Odoo helpdesk.ticket. The ticket number becomes the ticket name, description maps to description, priority maps via value-mapping to Odoo's priority field, and the assigned support team maps to team_id. ConSol SLA identifiers are stored in a custom field for rebuild reference.

If your team does not deploy the Odoo helpdesk module and uses only CRM, ConSol tickets migrate to crm.lead with a custom field (cs_ticket_ref) preserving the original ConSol ticket number and a ticket_type='service' tag to distinguish service cases from sales leads.

ConSol work orders translate to Odoo project.task records linked to a project record. The work order status maps to task stage via value-mapping; assigned team maps to project_id; due date maps to date_deadline. For on-site service work orders, the Odoo field service module (project_task_template) is the closer equivalent.

ConSol communication logs (emails, call notes, internal messages) are merged into Odoo's mail.message records attached to the target ticket or partner. Email-type logs map to Odoo mail.message with subtype='comment'; logged calls with duration map as Odoo CRM activities of type 'call' on the related partner or ticket record.

ConSol file attachments and documents migrate to Odoo's ir.attachment table. The original file name, mime type, and binary content are preserved. Attachments are linked to the migrated record (helpdesk.ticket, res.partner, or project.task) via res_model and res_id fields. Files over Odoo's default 25MB limit are flagged before migration.

ConSol SLA policies tracking response and resolution time against priority tier have no direct Odoo CRM equivalent without the helpdesk module. We preserve SLA policy names, threshold values (in hours), and stage targets as custom fields on helpdesk.ticket (or crm.lead). Your Odoo admin uses these as a rebuild guide for helpdesk.sla.policy after go-live.

ConSol workflow definitions, automated routing rules, and escalation triggers do not migrate. FlitStack AI exports every ConSol automation as a structured JSON document describing the trigger conditions, rule logic, and assigned actions — this serves as the functional specification for rebuilding in Odoo Studio automated actions.

ConSol support agents and owners resolve to Odoo res.users by email address match. Unmatched ConSol users are flagged before migration; your team either creates Odoo user accounts first or assigns their records to a fallback Odoo user. The original ConSol user ID is preserved in a custom field (source_user_id) on migrated records.

ConSol custom fields and any custom objects extend the standard objects in Odoo. Custom Char, Integer, and Boolean fields map directly to Odoo Char, Integer, and Boolean fields. Selection fields require value-by-value mapping to Odoo Selection fields. Many-to-many relationship fields in ConSol map to Odoo Many2many fields on the relevant model.

ConSol change management records and approval history log into Odoo's mail.message audit trail on the relevant ticket or project.task. Approval status transitions map as comment messages with the actor and timestamp so Odoo displays the audit trail in the chatter without requiring a dedicated change-management module.