Migrate from Connect Field Service to HighLevel

Connect Field Service Contact records (or Account-associated persons) migrate directly to HighLevel Contacts. Email, phone, address, and owner assignment transfer 1:1. Contacts without an email receive a generated placeholder identifier for HighLevel's import requirements. Primary company association migrates as a Company record lookup.

Connect Field Service Account (Salesforce) or Customer (Dynamics) maps to HighLevel Company. Company name, address, industry, and revenue fields translate directly. Multi-site accounts (parent-child hierarchies) collapse to individual Company records in HighLevel, with site-specific location data stored as custom fields.

WorkOrder has no HighLevel native equivalent. We create a WorkOrder custom object in HighLevel and map standard fields: WorkOrderNumber becomes Work_Order_Number__c; Subject maps to Name; Status translates through a value-mapping table (Scheduled → Open, In Progress → Working, Completed → Won, Cancelled → Lost); Priority, Description, and Street address transfer as custom fields. Original WorkOrderId preserved as Source_System_ID__c for delta-run de-duplication.

ServiceAppointment tracks individual job windows and technician assignments. Each appointment migrates as a custom object record linked to the parent WorkOrder. ScheduledStart and ScheduledEnd map to Appointment_Start__c and Appointment_End__c datetime fields. ActualStart and ActualEnd (if job completed) map to Completed_Start__c and Completed_End__c. Status maps via value mapping (Scheduled → Open, Dispatched → Working, Completed → Won).

Line items capture parts, labor, and service details per work order. Each line item migrates as a custom object with a lookup to its parent WorkOrder. Product2 reference becomes Product_Name__c text field (since HighLevel has no native product catalog linkage for FSM). Quantity and UnitAmount map to Quantity__c and Unit_Amount__c. The original line item ID migrates as Source_LineItem_ID__c.

ServiceResource models technicians and dispatch resources. Each active ServiceResource migrates as a HighLevel User record by matching email addresses. Skill certifications stored as custom fields (Skill_Certifications__c) as comma-separated values. Resource type (Technician vs. Dispatcher) maps to a Role custom field. Unmatched resources flagged for manual user creation before migration commits.

Skill definitions (Electrical, HVAC, Plumbing) and per-appointment skill requirements have no HighLevel equivalent. We create a Skill custom object in HighLevel and map skill names to Name fields. SkillRequirement records (which skill a specific job needs) link to WorkOrder custom objects via a junction relationship field. Skill taxonomy preserved for workflow-trigger reconstruction.

Service contracts and entitlement records (warranty coverage, SLA terms, contract start/end dates) require a custom ServiceContract object in HighLevel. ContractNumber, StartDate, EndDate, and Status map to custom fields. Coverage terms (hours included, response-time SLA) stored as text fields since HighLevel lacks native entitlement logic. Links to parent Account preserved as Company lookup.

Connect Field Service activity records (call logs, notes, field visit summaries) map to HighLevel Tasks. Subject transfers to Task Name; Description maps to Notes field; CreatedDate preserves as Original_Created_Date__c custom field since HighLevel Task CreatedDate reflects import time. Owner resolved by email match to HighLevel User. Activities without owners attach to a migration-service system user temporarily.

Work-order attachments (photos, signed forms, inspection reports) re-upload to HighLevel Files linked to the parent WorkOrder custom object record. File size limits per HighLevel's upload constraints apply. Inline images in notes are extracted and rehosted as individual file attachments. Original file names preserved in the display title.

Dispatch territories and operating-hour configurations have no HighLevel equivalent. We create a Territory custom object and map territory name, geographic boundaries (stored as text description), and operating-hours windows to custom fields. Scheduling-timezone alignment handled through a Timezone__c field on each Territory record. Territory links to WorkOrders via a lookup field for reporting continuity.

Post-service survey responses and CSAT scores migrate to a ServiceSurvey custom object. Survey score maps to NPS_Score__c or CSAT_Score__c numeric fields. Free-text responses stored as Long Text Area. Survey links to the parent WorkOrder via a lookup. HighLevel's native reputation management features can be connected post-migration for ongoing feedback capture.