Migrate from Q Dispatch to Odoo CRM

Q Dispatch work orders map to Odoo crm.lead records as opportunities. The work order name becomes the crm.lead name field. Job description, address, and scheduled date map to crm.lead description, street/city fields, and planned_date_end respectively. Status is remapped from Q Dispatch statuses to Odoo pipeline stages.

Q Dispatch customer records map to Odoo res.partner. Company-type customers use contact_type='contact' and store the company name in name; individual customers use contact_type='person' with firstname and lastname split. Email, phone, mobile, and address fields map directly to Odoo partner fields.

Q Dispatch technicians map to Odoo res.users by email match. Active technicians become Odoo internal users with appropriate access rights. Inactive or archived technicians are optionally migrated as res.partner contacts. Skill tags from Q Dispatch require custom fields on res.users since Odoo has no native skill-tag model.

Q Dispatch service line items on work orders merge into Odoo sale.order.line records. If the destination Odoo instance includes the Sale app, service lines create sale.order.line entries linked to the crm.lead opportunity. Line descriptions, quantities, and unit prices transfer directly.

Q Dispatch scheduling data migrates to Odoo calendar.event records linked to the res.users technician. Start and end times preserve from the work order schedule. The dispatch board routing logic itself does not transfer — that workflow must be rebuilt using Odoo Project tasks or a field service module post-migration.

Q Dispatch sites (multiple service locations per customer) become address records under the parent res.partner. Site-specific notes and access instructions map to custom Char fields on the partner record since Odoo has no native multi-site-per-customer model in the base CRM.

File attachments from Q Dispatch work orders download and re-upload to Odoo as ir.attachment records linked to the corresponding crm.lead. Odoo's attachment storage uses the database filestore by default; large file migrations require sufficient disk allocation in the Odoo instance.

Q Dispatch work order notes and internal comments migrate as Odoo mail.message records attached to the crm.lead. Original timestamps and author information (resolved by email match to res.users) are preserved. Public-facing customer communications become mail.message with subtypes, while internal notes use the 'note' subtype to distinguish visibility within Odoo. Attachments on notes also migrate as ir.attachment records linked to the corresponding mail.message.

Q Dispatch custom fields on work orders require Odoo custom field creation via Settings > Technical > Models before data loads. We generate the field creation XML for each custom field, matching the source field type (Char, Integer, Selection, Date, etc.) and populate values during the migration run.

Q Dispatch billing and invoice records do not migrate as native Odoo accounting entries. If Odoo Accounting is in use, we export invoice data as CSV for manual import into account.move. Completed invoice metadata (amount, date, status) is preserved as custom fields on the linked crm.lead for historical reference.