Migrate from Field Services Workflow and Logistics to HighLevel

Direct map. HighLevel Contact stores name, email, phone, address, and custom fields. FSM operator assignments that appear as contact-level fields in the FSM system migrate as custom Contact fields in HighLevel. Multi-contact accounts (multiple technicians per customer) collapse to individual Contact records; the FSM relationship to the parent account is preserved via custom field.

Direct map. HighLevel Company stores business name, domain, industry, employee count, and address. FSM company-level custom properties migrate as custom fields on the HighLevel Company object. Parent-child company hierarchies in the FSM system map to HighLevel's Company relationships where supported.

FSM Work Orders map to HighLevel Opportunities. The FSM work order name becomes the Opportunity name, amount maps to the Opportunity amount field, and the FSM work order stage maps to the HighLevel Opportunity Stage value. FSM-specific fields — technician assigned, service address, parts used, custom properties — are preserved as custom fields on the HighLevel Opportunity record. HighLevel has no native work-order object, so this transformation carries the full FSM job context.

FSM work order status values (Scheduled, In Progress, On Hold, Completed, Cancelled) map value-by-value to HighLevel Opportunity Stage names. Each FSM stage maps to one HighLevel stage; stage order and probabilities are re-applied based on the destination pipeline's stage configuration. Custom FSM stage values that do not match a pre-existing HighLevel stage are created as new Opportunity Stages during schema setup.

HighLevel has no native asset or equipment management object. FSL assets — with serial number, model, location, GPS coordinates, and service history — are migrated to a custom object (Asset__c) in HighLevel. Asset-to-customer relationships are preserved via custom relationship fields on the custom object. Each asset record's linked work order history is preserved as a custom text field on the Asset__c record.

HighLevel does not have a technician/operator object separate from its User model. FSM technician records are resolved by email match against existing HighLevel Users; matched technicians appear as HighLevel Users and their FSM assignment data is preserved as a custom field on the Opportunity record for traceability. Unmatched technician names are stored in a custom field on the relevant Opportunities.

FSM service addresses associated with work orders do not map to a standard HighLevel address field. We create custom address fields (Service_Street__c, Service_City__c, Service_State__c, Service_Zip__c, Service_Country__c) on the HighLevel Opportunity record and populate them from the FSM work order's service location data.

Any custom FSM properties on Work Order, Asset, Contact, or Company objects that have no direct HighLevel equivalent are created as custom fields on the corresponding HighLevel object. Field type is matched (text → text, number → number, pick-list → pick-list) and FSM pick-list values are mapped to HighLevel pick-list options. Custom fields are created in HighLevel's Settings → Custom Fields before the migration load runs.

FSM file attachments on work orders and assets are downloaded and re-uploaded to HighLevel's Files section, linked to the corresponding migrated record (Contact, Company, or Opportunity). HighLevel's file storage limits apply; inline images in FSM notes are extracted, rehosted, and the note body is updated with the new file references.

FSM work order notes and technician log entries map directly to HighLevel Notes on the corresponding Opportunity record. Original timestamps and author attribution are preserved. Rich-text formatting from the FSM system is simplified to plain text for HighLevel compatibility. Notes are linked to the Opportunity record created from the parent work order.