Migrate from Field Harmony to Odoo CRM

Field Harmony contacts map directly to Odoo res.partner records. Set is_company=False for individual contacts to distinguish them from companies. Company association preserved via parent_id linking to the res.partner record where is_company=True. Email, phone, street address, city, state, zip, and country fields migrate as direct field mappings with value mapping for state and country to Odoo state_id and country_id records.

Field Harmony companies map to res.partner where is_company=True to designate them as organization records. Parent-child company hierarchies in Field Harmony translate directly to parent_id relationships on the Odoo res.partner model. Multi-location companies may require multiple res.partner address records with each location linked via child_ids to the primary company record.

Field Harmony work orders are the primary job entity containing all service information. These map to Odoo crm.lead as opportunities with type='opportunity'. Service type, job status, scheduled date, and assigned technician migrate as custom fields since Odoo crm.lead has no native work-order model. Original work-order IDs preserved as Source_System_ID__c for audit traceability and delta-run matching.

Parts and line items from Field Harmony work orders require a two-step approach: migrate the crm.lead first, then create linked sale.order records if Odoo Sales app is active. If only CRM app is active, parts data migrates as custom fields on crm.lead. The Odoo Sales module provides native line-item tracking for parts, labor, and pricing.

Field Harmony technicians map to Odoo res.users. Email-based matching links technicians to existing Odoo user accounts. Unmatched technicians flagged before migration — either create Odoo users first or assign to a fallback user during the migration run. Technician schedule, territory, and service area data preserved as custom char fields on res.users.

Field Harmony stores service locations separately from customer contacts. These map to res.partner records with type='delivery' or type='other' linked via parent_id to the primary customer res.partner record. GPS coordinates and location-specific data preserved as custom latitude and longitude fields on the address res.partner.

Field Harmony scheduling data — including appointment slots, route assignments, technician dispatch status, and GPS route data — has no Odoo CRM equivalent. Migrate as custom fields on crm.lead: Scheduled_Date__c, Assigned_Technician__c, Dispatch_Status__c, and Route_Data__c. Scheduling logic must be rebuilt using Odoo Studio, server actions, or third-party field-service applications.

Field Harmony attachments including job photos, signature captures, parts images, and document uploads migrate to Odoo ir.attachment records linked to the corresponding crm.lead or res.partner via res_model and res_id fields. File size limits apply: Odoo default maximum is 25MB per file, with larger files requiring chunked upload configuration.

Field Harmony custom fields added per object via settings UI require Odoo custom field creation via Settings > Technical > Custom Fields or via developer mode. Custom fields on contacts, companies, work orders, and technicians each need separate Odoo field definitions with matching data types before migration data can populate them.

Field Harmony service history including completed jobs, status changes, technician notes, and customer communications migrates to Odoo crm.lead as internal notes using mail.message records with message_type='notification'. Original timestamps and technician attribution preserved in the message record. Note that Odoo activity model (crm.lead activities) is separate from historical log entries.

Field Harmony custom reports and dashboards do not migrate to Odoo as they are platform-specific implementations. Odoo CRM native reports, custom reports via Odoo Studio, and PostgreSQL-based analytics provide replacement functionality. The underlying migrated data is fully available for reporting in Odoo once migration completes and dashboards can be rebuilt in Odoo Studio.

Field Harmony drag-and-drop workflows and automation rules do not migrate as they use proprietary workflow definitions. These must be rebuilt in Odoo using Studio for simple automations, server actions for complex logic, or the Odoo Workflow Editor application available in the Odoo Apps store. FlitStack can export workflow definitions as a reference document to guide the Odoo rebuild process.