Migrate from Field Harmony to HubSpot

Field Harmony work orders map directly to HubSpot Tickets. The work order name becomes the ticket subject, priority and service type map as custom pick-lists, and the original Field Harmony work order ID is preserved in a custom text field for traceability and delta-run de-duplication.

Field Harmony customer accounts map 1:1 to HubSpot Company records. Company name, billing address, and industry classification transfer directly. Primary contact links are preserved as HubSpot company-to-contact associations. If industry classification values differ, they are mapped to the nearest HubSpot standard picklist option to maintain reporting consistency.

Field Harmony contact records — customer name, phone, email, and role — migrate to HubSpot Contacts. Mobile phone and role fields transfer as HubSpot custom properties since HubSpot's standard Contact object does not include a role field. These custom properties are created during the provisioning step and are flagged for review.

When a Field Harmony customer has multiple service locations, the primary location maps to the HubSpot Company address. Secondary and tertiary addresses are stored as a custom multi-line text property (Service_Locations__c) to preserve full location data. This approach keeps all service locations accessible within the CRM.

Field Harmony line items (parts used, labor hours, service fees) are aggregated and stored as a custom long-text property on the HubSpot Ticket. Each line item becomes a separate line in the text block with part name, quantity, and cost. Full itemised invoicing requires a separate billing integration.

Field Harmony asset records migrate to a HubSpot custom object named Asset. Asset name, serial number, model, manufacturer, location, and installation date map to custom properties on the Asset custom object. Parent-child location hierarchies are flattened into a single location string and preserved as a reference property.

Field Harmony locations (facilities, floors, zones) are mapped to the HubSpot Company address for the primary location. For multi-floor or multi-zone tracking, location details are stored as a custom text property on the linked Asset record. This ensures asset-level location data is available for reporting and future scheduling.

Field Harmony technician profiles do not map to HubSpot native objects. We preserve technician name, certifications, and service categories as custom properties on a designated HubSpot User reference record, and list assigned technicians per work order as a custom multi-contact property on the Ticket.

Appointment windows and scheduled date-time data from Field Harmony are stored as custom datetime properties on the HubSpot Ticket (Scheduled_Date__c, Appointment_Window__c). Route-sequence data is stored as a text reference property. HubSpot's native Meetings object can capture one scheduled event per ticket. Ongoing scheduling requires a third-party scheduling integration.

Field Harmony custom fields on any object are mapped to HubSpot custom properties on the equivalent HubSpot object. Field service-specific fields like Service_Category__c, Work_Order_Type__c, and Technician_Region__c are created as HubSpot custom properties before migration. Multi-select pick-lists in Field Harmony are mapped to HubSpot multi-checkbox or single-select properties depending on the source value structure.