Migrate from MobileWorker to Odoo CRM

MobileWorker worker record maps directly to Odoo res.partner. The partner is created as type 'contact'. Employment status and worker type are preserved as custom selection fields on the partner record. Partner email, phone, and mobile map to standard res.partner fields. The original MobileWorker worker ID is stored in a custom char field for reference and delta-run matching during subsequent migration batches.

MobileWorker certifications and skill tags merge into Odoo res.partner_tags for broad categorization (HVAC, Electrical, Licensed) plus x_certification_date custom date fields per certification name stored as separate custom_char fields on the partner record. Certification expiry dates use separate custom date fields named x_<certification>_expiry on the res.partner.

MobileWorker assignments with estimated revenue map to Odoo crm.lead opportunities. The assignment status (Pending, In Progress, Completed) maps to crm.lead stage values via pre-agreed value mapping. Assignment description becomes crm.lead name. The associated customer site links via partner_id lookup against migrated location partners. Expected revenue from the assignment populates the opportunity expected_revenue field.

MobileWorker assignments representing time-and-materials work orders without a fixed deal value map to project.task in Odoo's Project app. The task inherits the partner_id from the associated customer location so timesheets, material expenses, and notes route back to the correct customer partner. This prevents zero-value items from cluttering the CRM pipeline.

MobileWorker location records map to Odoo res.partner addresses on the customer partner. Site name becomes partner name. Street, city, state, zip map to standard address fields. GPS latitude and longitude migrate to x_gps_latitude and x_gps_longitude custom float fields on the partner for map integration and route optimization capabilities.

MobileWorker customer accounts map to Odoo res.partner with company_type = 'company'. Child location partners are created as contacts under the parent company partner using the partner_id / child_ids relationship in Odoo. This preserves the customer-to-site hierarchy from MobileWorker in the Odoo partner structure.

MobileWorker weekly availability patterns have no direct Odoo equivalent. We preserve the schedule as x_availability_json custom char fields on res.partner containing a JSON structure with day-of-week availability windows. This JSON format allows post-migration custom modules to parse and act on availability data using Odoo's Python model hooks.

Files attached to MobileWorker assignments (photos, signed forms, permits) migrate as Odoo ir.attachment records linked to the corresponding crm.lead or project.task via res_model and res_id. Attachment size limits and file type restrictions are respected per Odoo configuration during the migration upload process.

MobileWorker log entries for completed tasks, notes, and status changes map to Odoo mail.message records on the parent crm.lead or project.task. Original timestamps, author information, and activity types are preserved from MobileWorker during the message creation in Odoo.

MobileWorker custom properties unique to a location (meter numbers, site codes, contract tiers) require Odoo custom fields created as x_<property_name> on res.partner. We generate the complete field creation plan before migration so the Odoo schema is ready before data lands in the system.