Migrate from Field Force Tracker to HighLevel

Field Force Tracker Client is a merged destination: company name and address become a HighLevel Company record; primary contact name, phone, and email become the primary Contact linked to that Company. Clients with multiple contacts in Field Force Tracker map to one Company with multiple Contact records.

Each Field Force Tracker work order becomes a HighLevel Opportunity. The pipeline name in HighLevel represents your service operation (e.g., 'Field Service Jobs'). Job status values map to custom pipeline stages — Open, Scheduled, In Progress, Completed, Invoiced — matching Field Force Tracker's job lifecycle.

Field Force Tracker technician profiles (name, phone, email, certification type) become HighLevel Contact records tagged with a 'Technician' tag. Email match resolves them to HighLevel users for Opportunity owner assignment. Multiple technicians per job stored as comma-separated tags on the Opportunity.

HighLevel has no native inventory module. Parts used per job are merged into Opportunity-level custom fields: one text field listing part names, one number field for total parts cost. Part quantities and unit prices stored in custom fields named Parts_List__c and Parts_Total_Cost__c.

Field Force Tracker client site address migrates to both the HighLevel Company Address field and the Contact Address field. Multi-location clients with separate billing and service addresses map to two Contact records with distinct address custom fields. For clients operating across multiple facilities, each distinct location receives its own Company-Contact pair in HighLevel to preserve geographic context for dispatch routing.

Field Force Tracker job statuses (New, Assigned, En Route, On Site, Completed, Invoiced) map to HighLevel pipeline stages via value-by-value mapping. Stage order, probability, and forecast category are set per stage in HighLevel's pipeline settings before migration loads begin. Each status transition in Field Force Tracker corresponds directly to a named stage in HighLevel with configured win probabilities.

Field Force Tracker service contracts (SLA terms, renewal date, contract value) have no native HighLevel equivalent. We create a ServiceContract Custom Object with fields for Contract_Value__c, Renewal_Date__c, and SLA_Terms__c, linked to the associated Company record. This structure preserves the contract's monetary value, expiration timeline, and service-level commitments in a queryable format.

Field Force Tracker's dedicated Assets module (equipment name, serial number, maintenance schedule) migrates as a Custom Object in HighLevel named Asset. Fields include Serial_Number__c, Equipment_Type__c, and Last_Maintenance_Date__c, linked to the Customer Company record. Each asset retains its equipment identity, maintenance history, and site association for future service scheduling and warranty tracking.

Field Force Tracker job notes and attached files (photos, signatures, PDF invoices) migrate as HighLevel Notes on the associated Opportunity record. Files re-upload to HighLevel's file storage. Original timestamps and any technician-attributed notes are preserved in the Note body. Attachments carry forward as HighLevel file uploads linked to the parent Opportunity for complete job documentation.

Field Force Tracker industry-specific properties — HVAC refrigerant type, elevator certificate tier, copier contract scope — require custom fields in HighLevel. We audit all active custom properties during scoping, deliver a custom-field creation plan, and then map values during the load phase. Inactive or deprecated properties are flagged for exclusion.