Migrate from Fieldproxy to Odoo CRM

Fieldproxy Customer maps directly to Odoo res.partner. Individual contacts and company records both use the same model — set is_company=True for organizations and False for persons. Email, phone, address, and website fields transfer directly. Multi-site customers require one res.partner per site address or a parent-child partner hierarchy.

Fieldproxy Job is the primary work-order record and maps to Odoo crm.lead. Open jobs with a status of 'scheduled' or 'in_progress' become Odoo Opportunities. Completed or closed jobs can become historical Leads or be merged into the associated res.partner record as a note. Job name maps to crm.lead name; job description maps to crm.lead description.

Fieldproxy job line items (parts used, labor hours, materials) have no direct Odoo CRM equivalent. Odoo separates estimating (crm.lead) from fulfillment (sale.order). We store line-item summaries as custom text fields on crm.lead for reference and recommend creating Odoo Sale Orders from the migrated jobs post-migration for full order management.

Fieldproxy Technician records represent field employees who log into the mobile app. They map to Odoo res.users by email address — technicians with an Odoo user account get their jobs attributed to their user_id in crm.lead. Technicians without Odoo user accounts become res.partner records flagged with a custom 'Technician_in_Source__c' field for reference.

Fieldproxy stores service-site addresses separate from customer records. We merge site address into the associated res.partner address fields. For multi-site customers, we create a separate res.partner record per site with the site address as the partner address and the parent_id set to the primary customer partner.

Fieldproxy job statuses (New, Scheduled, In Progress, On Hold, Completed, Cancelled) map to Odoo CRM pipeline stages. We create a dedicated Odoo pipeline and stage values that mirror Fieldproxy statuses. Stage-to-stage mapping is configured value-by-value in the migration plan before data lands.

Fieldproxy records job activities — status change logs, technician notes, customer签核 — as activity entries. These migrate as Odoo mail.message records linked to the crm.lead via res_id and model fields. Original timestamps and technician author are preserved. Rich-text formatting in notes is converted to Odoo's HTML note format.

Fieldproxy attachments (job photos, signed forms, parts images) re-upload to Odoo as ir.attachment records linked to the corresponding crm.lead. Files are downloaded from Fieldproxy storage and uploaded to Odoo's filestore. Odoo Community edition has a 25MB per-file limit — large files are flagged for splitting before migration.

Any custom fields defined on Fieldproxy Job objects (e.g., job_priority, job_type, parts_catalog_id) are read from the Fieldproxy API and created as custom fields on Odoo's crm.lead model using the ir.model.fields API. Field types are mapped: text to char, number to float, picklist to selection. The migration plan lists each custom field and its Odoo equivalent before the run.

Custom fields on Fieldproxy Customer objects — such as tax_id, credit_limit, or service_tier — migrate as custom fields on Odoo res.partner. We apply the same field-type mapping rules as for job custom fields: text to char, numbers to float, picklists to selection fields. Odoo naming conventions require snake_case — Fieldproxy camelCase names are automatically converted to follow this standard.

Fieldproxy workflow rules (job assignment logic, notification triggers, status-based routing) have no Odoo equivalent and cannot be migrated. We export the Fieldproxy workflow definitions as a structured JSON document so your Odoo administrator can rebuild them using Odoo's base.automation, server actions, and activity scheduled actions.

Fieldproxy stores technician GPS tracks and geofence data tied to job visits. Odoo CRM has no geolocation or route-tracking model. We preserve GPS coordinates from the most recent job visit as custom coordinate fields on the res.partner record, but live tracking data is not migrated as it has no operational equivalent in Odoo.