Migrate from Salesforce Field Service to HighLevel

Salesforce Work Orders map to HighLevel Opportunities. The Work Order subject/name becomes the Opportunity name. Status maps to a custom Opportunity stage pick-list (New, In Progress, On Hold, Completed, Cancelled). Amount and expected revenue transfer to the Opportunity amount field.

Service Appointments map to HighLevel Tasks linked to the corresponding Work-Order-as-Opportunity. The appointment subject becomes the task name, scheduled date maps to due date, and actual duration in minutes is stored as a custom number field. Original Service Appointment ID is preserved as a reference field for traceability.

Work Order Line Items representing parts or sub-tasks become custom fields on the HighLevel Opportunity, capturing line-item description, quantity, and unit price. If HighLevel's Products feature is enabled, line items map as opportunity products with name, quantity, and price, allowing revenue calculations and inventory tracking to be preserved within the migrated records.

Assets in Salesforce (installed products, equipment) have no direct HighLevel equivalent. Asset name, product reference, serial number, and install date migrate as custom fields on the related HighLevel Contact or Company record. Status (Active, Shipped, Retired) maps to a custom pick-list field.

Salesforce Skill records (Electrical, HVAC, Plumbing) become HighLevel tags on the Contact/User record. Skill proficiency levels (1–5) map to a custom numeric field on the contact. Skill requirements from Service Appointments are preserved as tags on the linked task for technician matching reference.

Skill Requirements linking Service Appointments to required Skills migrate as a custom multi-select pick-list field on the HighLevel Task, listing the required skill names. This preserves which skills a job requires without a native requirement object. The multi-select format allows multiple required skills to be tracked on a single task for technician assignment and job qualification purposes.

Entitlements define service terms and covered SLAs per customer. Entitlement name, status (Active, Expired), start date, and end date migrate as custom fields on the HighLevel Contact or Company. The covered assets relationship is noted as a text reference field.

Service Contracts with contract line items and covered products have no HighLevel equivalent. Contract terms (annual value, renewal date) migrate as custom fields on the Company record. We recommend storing contract documents in HighLevel's file storage and linking via a custom URL field.

Salesforce field technicians and dispatchers (FSL Resources) map to HighLevel Users or Contacts depending on whether they are internal staff or external contractors. Email-based owner matching links the Resource's email to the HighLevel user account. This ensures that task assignments and opportunity ownership reflect the correct personnel after migration.

Salesforce Scheduling Policies with work rules and priority objectives have no HighLevel equivalent. FlitStack exports the policy configuration as a reference document for rebuilding in HighLevel's Workflow Builder and Calendar settings. Scheduling logic must be manually rebuilt post-migration. This includes any travel time assumptions, break buffers, or skill-based routing rules originally configured in Salesforce.

Optimization requests and their results, including route efficiency metrics and travel time savings calculations, are Salesforce-specific constructs with no HighLevel equivalent. These records are exported as a reference CSV for your operations team to review and manually incorporate into HighLevel workflows where applicable. The optimization logic itself cannot be directly migrated and requires manual process design.

Custom fields on Work Order objects (e.g., job type, priority, PO number) are read from the Salesforce API and recreated as custom fields on the HighLevel Opportunity. Field types are preserved: text stays text, pick-lists become pick-lists, dates stay dates.

Appointment Booking records capturing customer-confirmed service slots map to HighLevel Calendar events linked to the contact. Booking reference numbers are stored in a custom text field for cross-reference with the original Salesforce record. This preserves the appointment confirmation workflow while transitioning to HighLevel's native calendar functionality.

Customer Accounts in Salesforce Field Service map directly to HighLevel Companies. Company name, address, industry classification, and phone number transfer field-for-field. Parent-child Account hierarchies present in Salesforce map to HighLevel Company hierarchies where supported, preserving organizational structure across the migration.

Customer and technician Contacts migrate directly to HighLevel. Names, email addresses, phone numbers, titles, and mailing addresses map field-for-field between systems. Contacts associated with multiple Accounts in Salesforce are linked to the primary Company in HighLevel, with secondary associations preserved as tags on the contact record.