Migrate from Dispatch to Odoo CRM

Dispatch customer records map directly to Odoo res.partner. Email, phone, and address fields translate cleanly, while optional fields such as street2, latitude, and longitude are captured in matching or custom fields. Dispatch contacts without an assigned company land as individual res.partner records with partner_type='contact'. Multiple service locations per Dispatch customer require one res.partner per location, linked to the parent company via the partner relationship.

Dispatch business accounts map to res.partner records with partner_type='company'. Odoo's parent_id field handles company hierarchies, and standard fields such as website, industry_id, and employee_count transfer directly. Dispatch company hierarchies (parent/child relationships) map using Odoo's Parent Partner field. Multi-location Dispatch companies split into one parent res.partner plus child partners per location, each inheriting the company's contact information and storing location-specific details.

Dispatch jobs lack a native Odoo equivalent in base CRM. We map job records to crm.lead as opportunities — job name becomes lead name, job status maps to crm.lead stage_id values, and job description maps to crm.lead description. If Odoo Field Service is installed, jobs map to project.task instead.

Dispatch job stages (New, Scheduled, In Progress, Completed, Cancelled) map to Odoo CRM stage records via value-by-value mapping. Each Dispatch stage requires a corresponding Odoo stage created in Settings > CRM > Stages before migration. Stage probabilities and fold (won/lost) settings re-applied in Odoo CRM pipeline configuration.

Dispatch technicians and dispatchers map to Odoo res.users by email match. Dispatch user records carry scheduling and assignment data — Odoo user records carry security and workflow ownership. Unmatched Dispatch users flagged before migration; fallback owner assigned or new Odoo users created.

Dispatch stores multiple service addresses per customer (street, city, state, zip, GPS coordinates). Odoo res.partner holds one address per partner record. Multiple Dispatch locations split into separate res.partner records linked to the parent company via partner_type='contact' and address type (partner_address_type field). GPS coordinates stored as custom float fields on each location partner.

Dispatch job notes and uploaded files migrate as Odoo ir.attachment records linked to the corresponding crm.lead (job). File size limits from Odoo apply (default 25MB per file). Inline images in notes extracted and rehosted as attachment records with res_model='crm.lead' and res_id referencing the migrated job.

Dispatch custom properties on jobs require Odoo custom fields created via Settings > Technical > Models before migration. Field type mapping: text → char or text, numbers → float or integer, dates → date or datetime, dropdowns → selection. Custom field creation in Odoo requires Enterprise edition or manual database access for Community. We deliver a custom-field setup plan before data lands.

Dispatch contact-level custom properties map to custom fields on res.partner. Like job custom fields, these require pre-migration setup in Odoo's Technical Settings. Selection-type custom fields in Dispatch map to Odoo selection fields with exact option values preserved. We provide the field-definition JSON so your Odoo admin or consultant creates them before migration.

Dispatch call logs, email records, and notes map to Odoo mail.message records linked to the corresponding crm.lead or res.partner. Original timestamps preserved as mail.message.date. Dispatch activity owners map to Odoo res.users by email match. Odoo's messaging and activity tracking uses the 'mail' module — these migrate cleanly if Dispatch exposes activity history via API.

Dispatch automation rules (job-status triggers, scheduling logic, notification rules) have no Odoo equivalent in base CRM. We export your Dispatch workflow definitions as a structured JSON document for your Odoo consultant to rebuild using Odoo's automated actions and action server. This is not a data migration — it is a documentation deliverable to support your post-migration configuration.