Migrate from Field Harmony to Salesforce Sales Cloud

Field Harmony Customer maps to Salesforce Account (company data) and a related Contact (primary contact on the account). Phone, email, and address fields migrate to the Account record; the named contact migrates to the Contact object linked by AccountId. If a customer has multiple service locations, each location may result in a separate Account with its own Contact, depending on whether you want consolidated or per-site billing and service records.

Work Order is the primary record in Field Harmony. It maps to Salesforce Case with status value-by-value translation, priority mapping, and original resolution notes preserved in the Case Description or custom fields. Case.AccountId links to the migrated Account. The Work Order number becomes CaseNumber, and any custom fields on the Work Order are created as custom __c fields on the Case object.

Field Harmony Service Appointments (scheduled visits) map to Salesforce Tasks with ActivityDate matching the scheduled date, and the technician mapped to Task.OwnerId via email-to-Salesforce-User lookup. Original appointment duration migrates as Task.DurationInMinutes or as StartDateTime/EndDateTime on Event. Recurring appointments create a series of Tasks or Events depending on your reporting needs.

Completed work orders with status 'completed' create closed Tasks in Salesforce to preserve service history. Each state change in Field Harmony (status transitions, reassignments) is captured as a separate Task record with the original timestamp and owner preserved. This creates an audit trail showing the complete lifecycle of each work order from creation through resolution.

Field Harmony technicians map to Salesforce Users for ownership resolution. Email is the match key — if a Salesforce User exists with the technician's email, their UserId becomes the OwnerId on migrated Cases and Tasks. If no match exists, the record is flagged before migration with a fallback owner assigned.

Field Harmony dispatch rules and scheduling automations have no direct Salesforce equivalent — they are procedural logic that cannot be carried as data. We export the rule definitions as a reference document; your Salesforce admin rebuilds them as Salesforce Flow criteria or Apex triggers post-migration.

Parts and inventory items in Field Harmony map to Salesforce Product2 records. The SKU migrates to Product2.ProductCode, name to Product2.Name, and unit price to a custom Product2.UnitCost__c field. On-hand quantity is a custom field on Product2 — Salesforce does not natively track inventory on Products.

Parts consumed on a Work Order are represented as line items in Field Harmony. Migrated as custom fields on the Case record (Part_1__c, Part_2__c, etc.) or as a related custom object with junction to Case — the structure depends on whether parts usage needs to drive revenue reporting in Salesforce.

Field Harmony service addresses stored on Work Order relocate to the Account record in Salesforce as BillingAddress and ShippingAddress. If the customer Account does not yet exist, it is created first so the Case can reference AccountId. Multi-site customers may result in multiple Accounts in Salesforce.

Photos, signed forms, and documents attached to Field Harmony Work Orders are downloaded and re-uploaded to Salesforce Files (ContentDocument). Each file is linked to the migrated Case record via ContentDocumentLink. Files exceeding Salesforce's 25MB per-file limit are flagged for manual handling.

Any custom field created in Field Harmony via their builder migrates as a Salesforce custom field with the __c suffix. Field data type determines Salesforce type: text becomes Text(255), numbers become Number, dates become Date, pick-lists become Picklist with value-by-value translation configured in Salesforce Setup.