Migrate from Dispatch Pro to Odoo CRM

Dispatch Pro work orders map directly to Odoo crm.lead records. The job name becomes the lead name, job status maps to an Odoo pipeline stage, and the job amount maps to Odoo's expected_revenue field. Dispatch Pro job IDs are preserved in Odoo's id_name reference field for traceability.

Dispatch Pro job statuses (Scheduled, Dispatched, En Route, In Progress, On Hold, Completed, Cancelled) map value-by-value to Odoo CRM stage records. Each Dispatch Pro status value requires a matching stage created in Odoo before migration so stage_id references resolve correctly on import.

Dispatch Pro customer records (name, phone, email, address) migrate to Odoo res.partner. The contact_type field is set to 'contact' for individuals and 'company' for businesses identified as commercial entities in Dispatch Pro. Primary customer records are created first so job-to-customer foreign keys resolve during job import.

Dispatch Pro service address fields (street, city, state, zip) migrate to the partner address fields on the customer record. If the service location differs from the customer billing address, a separate partner record is created with type 'other' and linked to the primary customer partner.

Odoo has no native technician entity. Dispatch Pro technicians are matched to Odoo res.users by email for users who will work in the CRM. Unmatched technicians are stored as a custom Char field on the lead (x_technician_assigned) so the assignment data is preserved even when no Odoo user account exists for that technician.

Dispatch Pro custom fields on jobs (e.g., job_type, priority_level, custom_tag) require Odoo custom field creation before import. Each custom field definition is created as an x_ field on crm.lead using Odoo Studio or a data migration script. Field type matching is verified: text fields become char/text, numeric fields become float, date fields become date.

Dispatch Pro job activity log entries (status changes, technician notes, dispatcher actions) migrate as Odoo mail.message records linked to the crm.lead. The original timestamp and actor name are preserved in the message body. This preserves the job's chronological history inside Odoo's activity feed.

Files and photos attached to Dispatch Pro jobs are downloaded and re-uploaded to Odoo as ir.attachment records linked to the corresponding crm.lead. The original filename and content type are preserved. Inline images embedded in job notes are extracted and stored as separate attachments.

Dispatch Pro job type values (e.g., Repair, Installation, Warranty, Maintenance) map to Odoo crm.lead.tag_ids as a tag record per job type. Alternatively, if job type controls pipeline routing, a custom selection field is created on crm.lead and populated via value mapping. The mapping choice is confirmed during the sample migration review.

Dispatch Pro customer tags (e.g., VIP, Commercial, Residential) migrate as res.partner.category_id entries. Tags are created in Odoo first, then linked to partner records during the customer import phase. Multiple tags per customer are supported via the category_id many2many relationship, and they enable segmentation and filtering in Odoo reporting, preserving the original grouping logic from Dispatch Pro.

If Dispatch Pro records the origin of a customer or job (Phone, Web, Walk-in, Referral), those values map to Odoo's crm.lead.source_id selection field. Custom source values require Odoo configuration before migration or are stored in a custom Char field as a fallback.