Migrate from Field Harmony to Freshsales

Field Harmony contacts (technicians and end customers) map directly to Freshsales Contacts. Technician-specific fields (certification_type, technician_rating) migrate as custom fields on the Contact record. Customer contacts keep standard fields (name, email, phone, address) with direct equivalents in Freshsales. The original Field Harmony contact ID is preserved in a custom Source_System_ID__c field for delta-run deduplication and cross-reference.

Field Harmony companies map to Freshsales Accounts. The primary service address from Field Harmony maps to the standard Address field on the Account. Additional service locations are stored in a custom Service_Location object linked to the Account record to preserve multi-site job history.

Each Field Harmony job maps to a Freshsales Deal (called Opportunity in the API). Job name, description, scheduled date, and total value carry forward. Deal owner is resolved by email match against Freshsales users. The job's service location is stored in a custom Location_Custom__c field on the Deal for routing reference.

Field Harmony work orders have no native Freshsales equivalent because Freshsales lacks a field-service job-record object. We create a Work_Order__c custom object in Freshsales with fields for work order number, status, priority, technician assignment (lookup to Contact), service date, and notes. The Work_Order__c record is linked to the parent Deal via a lookup relationship.

Field Harmony supports multiple service locations per customer account — a critical feature for field service. Freshsales stores only a primary address on the Account. We create a Service_Location__c custom object with fields for location name, full address, location type (commercial/residential/industrial), and a lookup to the Account. Each job in Field Harmony is linked to one Service_Location__c record.

Field Harmony parts and inventory items map to Freshsales Products (name, SKU, unit price). When a work order specifies parts used, those map to Deal Product line items attached to the parent Deal. Stock quantity and reorder threshold from Field Harmony migrate as custom fields on the Freshsales Product record since Freshsales Products do not track inventory natively.

Field Harmony work order notes and job comments migrate as Freshsales Notes linked to the parent Work_Order__c or Deal. Original timestamps, author (technician name), and record-type context are preserved as custom fields on the Note for audit continuity. The Note's title field captures the note type (e.g., 'Work Order Comment', 'Job Note') while the body preserves the full original text from Field Harmony.

Field Harmony job owners and assigned technicians are resolved by email match against Freshsales users. Unmatched technicians are flagged before migration — your admin either creates a Freshsales Contact record for the technician or reassigns the work order to an existing user. Technician certifications and ratings migrate as Contact custom fields.

Field Harmony job status values (Scheduled, In Progress, On Hold, Completed, Cancelled) map to Freshsales Deal Stage pick-list values defined in your Freshsales pipeline. Completed jobs also set the parent Contact's Lifecycle Stage to 'Customer' to reflect a serviced relationship. Stage-entered timestamps are preserved as custom datetime fields on the Deal.

Field Harmony file attachments on jobs and work orders are downloaded and re-uploaded to Freshsales Files linked to the parent record. File size limits per Freshsales apply — files over 25MB are flagged for chunked upload. Inline images in notes are extracted and rehosted separately.

Field Harmony custom fields defined at the job level map to either custom fields on the Deal object or on the Work_Order__c custom object depending on whether the field applies to the job as a whole or to a specific work order. Custom field type mapping follows Freshsales field type equivalents (text, number, date, pick-list).

Field Harmony's scheduling rules, technician routing logic, and dispatch automations have no native Freshsales equivalent. These must be rebuilt as Freshsales workflow automations. FlitStack AI exports the rule definitions from Field Harmony as a structured reference document your admin can use to recreate the logic in Freshsales Automator or the Pro/Enterprise workflow builder.