Migrate from FieldFX to HighLevel

FieldFX stores customer account data on the Salesforce Account object. FlitStack AI maps Account.Name, Account.BillingAddress, and Account.Industry to HighLevel Company records. Multi-location accounts with child locations become HighLevel Company records with address-level custom fields — no native parent-child hierarchy in HighLevel, so flat organization is the default.

FieldFX Contact records (linked to Account via AccountId) migrate as HighLevel Contacts. Owner resolution maps the Contact.OwnerId (Salesforce user email) to the HighLevel user assigned by email-match during the migration run. Unmatched owners are flagged for assignment before the full migration commits.

FieldFX Ticket records do not have a native HighLevel equivalent. For teams using tickets primarily as pipeline tracking records, FlitStack maps FX5__Ticket__c to HighLevel Opportunities using ticket name as opportunity name and ticket status as pipeline stage. For field-service-heavy setups, a custom Ticket custom object is created in HighLevel and records are loaded via the custom-objects API — your team chooses the strategy before the migration plan is finalized.

FieldFX Work Order records (EAM module) have no HighLevel equivalent. FlitStack creates a HighLevel custom object named 'Work Order' with custom fields mirroring the FX5__Work_Order__c schema. Work Order is linked to the Contact and Company custom objects via relationship fields in HighLevel's custom-object schema editor.

Ticket Item records attach to a Ticket and store service line details (item type, quantity, rate, extended amount). If the ticket maps to a HighLevel Opportunity, Ticket Items are stored in a related 'Ticket Item' custom object linked by a lookup to the parent ticket opportunity. This preserves the service-line structure without flattening it into a text field.

FieldFX Status Workflows define which status transitions are valid per record type. Each status value (e.g., Unassigned, Dispatched, In Progress, Completed, On Hold) is mapped value-by-value to a HighLevel pipeline stage or a custom pick-list field on the ticket opportunity. Stage transition history is preserved in a custom audit datetime field if tracked in FieldFX.

Priority field values from FX5__Ticket__c (e.g., Low, Medium, High, Critical) are mapped one-to-one to a custom Priority pick-list on the ticket opportunity in HighLevel. If the pick-list values differ between record types in FieldFX, each record type's value set is mapped independently.

FieldFX dispatch status (e.g., Not Dispatched, Dispatched, En Route, On Site) has no HighLevel equivalent. FlitStack creates a custom pick-list field 'Dispatch Status' on the ticket opportunity and maps values directly. This field is visible in HighLevel opportunity detail views and can trigger workflow automations.

FieldFX EAM module links Salesforce Asset records to tickets and work orders. HighLevel has no native Asset object, so FlitStack creates a custom Asset custom object with fields for asset name, serial number, location, status, and a lookup to the customer Company. Asset-to-ticket relationships are stored as relationship records on the custom Asset object.

FieldFX Price Books store service item pricing used in ticket items. HighLevel Products feature is limited for service pricing. FlitStack migrates Price Book entries as a custom 'Price Book' custom object with fields for item name, unit price, cost, and product category — linked to ticket items by item reference.

FieldFX notes and file attachments on ticket and work order records migrate to HighLevel's notes and file attachments on the corresponding contact, company, or opportunity record. Files are re-uploaded to HighLevel's file storage. Salesforce Files (ContentDocument/ContentVersion model) are downloaded and re-uploaded as HighLevel file attachments.

Salesforce users assigned as ticket owners or dispatch technicians are matched to HighLevel users by email address. Unmatched users are flagged before migration so the team can create HighLevel user accounts or reassign records to a fallback owner. This applies to both active and inactive Salesforce users with historical record ownership.