Migrate from QuickDesk to Odoo CRM

QuickDesk Contacts map to Odoo res.partner records. We extract all standard fields (name, email, phone, company name as text) plus any custom contact properties via the QuickDesk API. The company name field triggers a lookup against the dedupe queue to link the Contact to an existing Partner record; if no match exists, the Contact becomes a standalone Partner. A custom field qd_original_type__c is set to 'contact' to preserve the original record type for audit.

QuickDesk Leads with personalized form data map to Odoo crm.lead (opportunity) records. Lead source, creation date, status, and any custom form fields migrate to crm_lead fields. If the destination Odoo instance uses the Lead object before conversion to Opportunity, we preserve the is_lead flag by setting type = 'lead' on the crm.lead record. Personalized lead form fields that have no Odoo standard equivalent are created as custom fields on crm.lead before import.

QuickDesk stores company names as text on Contact records, not as a separate object. We extract every distinct company name value during the Contact audit, run a similarity dedupe pass (normalizing case, legal suffixes like Ltd/LLC, and common abbreviations) to produce a set of deduplicated company names, then create a res.partner record for each unique company with partner_type = 'company'. Contacts are linked to their resolved Company Partner via partner_id. Any contact sharing a company-name variant is flagged for the customer's admin to review before final merge.

QuickDesk's single Customer Pipeline maps to an Odoo crm.team. The team is provisioned in Odoo with the same name as the QuickDesk pipeline. If the customer has multiple QuickDesk pipelines (rare), each maps to a separate crm.team in Odoo, with stage scoping managed via team-specific stage assignments.

Each QuickDesk pipeline stage maps to an Odoo crm.stage record on the corresponding team. Stage name, sequence order, and probability percentage migrate from QuickDesk stage configuration to Odoo stage probability field. QuickDesk stages like prospecting, qualification, proposal, negotiation, and close transfer directly; custom-named stages are preserved as-is and the customer's admin can rename them post-migration to match Odoo conventions.

QuickDesk Deals map to Odoo crm.lead with type = 'opportunity'. The deal name becomes the opportunity name, deal value maps to planned_revenue, expected close date maps to date_deadline, and QuickDesk stage assignment maps to stage_id via the resolved crm.stage record. Deal owner from QuickDesk resolves to the Odoo user via email match. If QuickDesk stores product line items on a deal, these migrate to Opportunity Line Items in Odoo Sale Orders linked via the opportunity.

QuickDesk call logs with duration and outcome migrate to Odoo calendar.event records with meeting_type = 'call'. Duration in minutes from QuickDesk sets stop on the calendar event. Attendees link to the Odoo partner record. Call disposition and outcome text migrate to a custom field call_disposition__c on the event. If QuickDesk stores a recording URL, it is preserved in a custom field recording_url__c.

QuickDesk tasks with due dates and assignee information map to Odoo mail.activity records linked to the parent crm.lead or res.partner. Task status (pending, completed) maps to Odoo activity state. Priority migrates to activity_priority. The activity_type_id references the standard Odoo To Do type unless the customer has configured custom activity types.

QuickDesk meetings migrate to Odoo calendar.event records with full start and end time preserved. Location maps to Odoo location. Attendee list migrates to calendar.event attendee records linked to the resolved res.partner contacts. Any meeting notes from QuickDesk become a mail.message on the event record.

QuickDesk custom fields on Leads and Contacts are extracted with their definitions during scoping. We pre-create matching custom fields in Odoo on crm.lead (for lead-specific fields) and res.partner (for contact fields) using Odoo's custom field inheritance approach before data import begins. Personalized lead form field definitions are mapped to crm.lead custom fields with the same label and data type. Any field type that has no Odoo equivalent (e.g., multi-checkbox from a QuickDesk form) is stored as a Char or Text field with the original value serialized as JSON.

QuickDesk's custom object model uses custom fields on Leads and Contacts rather than separate database tables. We map each QuickDesk custom object definition to a named group of custom fields on the appropriate Odoo model. If the customer has a true custom object (non-standard entity type), we create an Odoo ir.model definition and a corresponding database table before migration. Odoo custom models follow the __custom__ naming pattern and support all standard Odoo field types.

QuickDesk tags associated with Leads and Contacts migrate to Odoo res.partner.category records (the same tags model used across contacts and companies in Odoo). Tags are created by name in Odoo before import, then assigned via res_partner_category_rel during the contact and company insert phase. If QuickDesk stores per-object tag sets (separate tags for Leads vs Contacts), they share the same Odoo category model and the customer's admin can filter by model in Odoo Reporting.