Migrate from Field service software to HighLevel

Direct map. Each field service customer record migrates as a HighLevel contact with full name, phone, email, and address preserved. Original customer create date is stored in a custom datetime field because HighLevel's CreatedDate reflects migration time, not source-system date.

Direct map. Field service software company or business-account records map to HighLevel companies with direct field-to-field correspondence for name, address, phone, and website. Service-site locations attached to a company in the source can be represented as additional address fields on the company record or as separate company records with a parent-child relationship. The original company create date is preserved in a custom datetime field since HighLevel's built-in timestamp reflects the migration execution time rather than the source record creation date.

Work orders map to HighLevel opportunities using a configured pipeline stage that mirrors the job lifecycle (e.g., Scheduled → In Progress → Completed → Invoiced). Status, priority, scheduled date, and completion date migrate as custom fields on the opportunity. If the source tracks multi-step job checklists, those map to opportunity notes or a linked custom object.

Service tickets and support requests migrate as HighLevel tasks with subject, description, due date, status, and owner preserved. Original ticket number is stored as a custom field (Source_Ticket_ID__c) for traceability. Completed-at timestamp migrates as a custom datetime field on the task.

Field service technicians resolve against HighLevel users by email match. If a technician record has no matching HighLevel user email, FlitStack flags the record for your team to create the user account before migration — no record lands without an assigned HighLevel user. Role and certification data from the source migrates as custom fields on the user.

Field service software asset records (equipment, warranty info, serial numbers, maintenance schedules) have no direct HighLevel equivalent. FlitStack creates a custom object named 'Asset' in HighLevel with fields for name, serial number, warranty expiration, linked contact, and maintenance schedule. A custom relationship field links each asset to its customer contact.

Parts and inventory items used in field service work orders map to a custom object in HighLevel with fields for name, SKU, quantity on hand, and unit cost. Work-order line items that reference specific parts are stored as custom fields on the work-order opportunity linking to the part custom object.

Photos, signed forms, and documents attached to work orders in the field service software are downloaded and re-uploaded to HighLevel's file storage linked to the corresponding opportunity or contact record. HighLevel's file size limits apply (25MB per file); larger files are flagged for chunking or alternative storage.

Multiple service locations associated with a single customer map to additional address fields on the HighLevel contact or company record. If the source tracks separate site names and addresses per location, each site becomes a separate address record with a custom 'Site Name' field and a lookup to the primary contact.

Job completion notes, technician comments, and status-change history migrate as HighLevel notes linked to the opportunity record. Timestamps and technician names are preserved in the note body for audit continuity. Automated activity logging from the source system migrates as a series of completed tasks with the original activity type preserved.

Invoicing and payment records from field service software have no native HighLevel equivalent — HighLevel does not generate per-job invoices. We preserve invoice number, amount, and payment status as custom fields on the opportunity record for reference. Full invoicing must be rebuilt in HighLevel Payments or connected to an external accounting tool.