Migrate from Mobile Worker to Odoo CRM

Mobile Worker worker/employee records map to Odoo res.partner with type=contact. Name, email, phone, and address fields migrate directly. The employee ID from the source is stored as x_source_employee_id for traceability and delta-run matching. This custom field ensures proper record linkage during incremental syncs and provides a reliable reference point for audit trails and reconciliation reports.

Customer contacts stored in Mobile Worker — typically site addresses with a contact name and phone — map directly to Odoo res.partner. Company-level customers may require a separate res.partner (company) with individual contacts linked via child_ids. This hierarchical structure preserves the relationship between organizational units and their designated representatives, enabling proper sales territory assignment and communication routing in Odoo.

Work orders are the primary migrated record type. Work order title becomes crm.lead name. Original work order status (e.g., Pending, Scheduled, Completed) maps to a stage value via value_mapping. Priority, create date, and close date migrate as standard lead fields or custom fields depending on the Odoo field schema.

Mobile Worker assignment records link a worker to a work order. When one worker is assigned, the worker's partner ID writes to crm.lead.user_id (owner). For multi-technician assignments, we store all assigned partner IDs as a custom x_assigned_worker_ids multi-value field on the lead.

Mobile Worker location records contain site address and GPS coordinates. Site address migrates as address fields on res.partner. Latitude, longitude, geofence_radius, and route_sequence store as x_latitude, x_longitude, x_geofence_radius, and x_route_sequence custom fields on crm.lead since Odoo CRM has no native geolocation model.

Any Mobile Worker custom fields on work orders that don't map to a standard Odoo crm.lead field create new x_* custom fields during the planning phase. These include Odoo-native fields (char, selection, integer, float, date, datetime) selected based on the source field type analysis.

Work order status values (e.g., New, In Progress, On Hold, Completed, Cancelled) map via a value-by-value lookup to Odoo CRM stage names. The source status is preserved in x_original_status custom field for reporting continuity. Priority (Low, Medium, High, Urgent) maps directly to crm.lead priority if the field exists in the target Odoo schema.

Photos, signed forms, inspection documents, and other attachments linked to Mobile Worker work orders are downloaded from source storage, re-uploaded to Odoo ir_attachment, and linked to the corresponding crm.lead record via res_model and res_id. The original filename and MIME type are preserved.

Mobile Worker call logs, site visit notes, and work-order notes migrate as Odoo mail.message records attached to crm.lead. Original timestamps, note body content, and author/worker name are preserved. These surface in the lead chatter history, allowing sales reps to review complete interaction timelines and maintain context across customer touchpoints. The migration preserves all metadata for audit compliance and customer relationship management.

Mobile Worker team or department names map to Odoo crm.team records. Team member assignment rules do not migrate — those scheduling and dispatch rules must be rebuilt using Odoo team member configuration and Odoo Studio automations. This includes reassigning team leads, configuring territory-based routing, and setting up automated assignment workflows based on skill sets and workload distribution.