Migrate from FieldFX to HubSpot

Salesforce Account maps directly to HubSpot Company in a one-to-one relationship. Since HubSpot stores domain as a separate property rather than embedding it in the company name, we extract the domain value from Account.Website and populate it into the Company domain field. For organizations with multiple addresses on an Account, we select the primary billing address and use it to populate the corresponding address fields on the Company record to maintain data consistency.

Salesforce Contact maps one-to-one to HubSpot Contact with all standard fields transferring directly. Name, email address, phone number, mobile phone, and job title migrate as direct field mappings without transformation. When a Contact record does not have an associated Account link in Salesforce, we assign it a default placeholder Company in HubSpot to prevent orphaned contact records. This placeholder can be replaced with the correct Company association once your team completes the account mapping review.

Salesforce Opportunity maps to HubSpot Deal — both represent a sales pipeline stage. We map Opportunity Stage values to HubSpot deal pipeline stage names via a value-mapping table. Forecast category and probability are stored as custom deal properties in HubSpot.

FieldFX WorkOrder has no native HubSpot equivalent. We re-model it as a HubSpot Custom Object (Work_Order__c) on Enterprise plans, with Work Order fields (status, type, priority, technician) as custom properties. Service-type Work Orders that represent customer support cases map to HubSpot Tickets instead.

FieldFX WorkDetails map to a custom WorkOrderLineItem object linked to the HubSpot Work_Order__c. Each line item's description, quantity, unit price, and service type become custom properties. If a Work Order maps to a HubSpot Ticket, line items flatten into a custom line-item property on the Ticket.

FieldFX Assets (serial number, install date, warranty expiration, maintenance history) have no HubSpot native equivalent. We create a HubSpot custom object Asset__c and link it to the associated Company or Contact record via the HubSpot association API. Serial numbers and warranty data become custom properties on the Asset__c object.

FieldFX Schedule & Dispatch stores ServiceAppointment records, technician availability windows, and resource assignments that have no native equivalent in HubSpot's data model. Appointment dates and assigned technician information are extracted and migrated as custom date properties and contact-type properties on the Work_Order__c record. However, the actual scheduling logic — including appointment slots, technician routes, and availability constraints — cannot be meaningfully represented in HubSpot and must be rebuilt using a dedicated third-party field service management or dispatch scheduling tool after the migration completes.

Salesforce Tasks representing calls and emails are mapped to HubSpot engagement timeline entries on the Contact record, preserving the original timestamp and activity type. Salesforce Events representing meetings map to HubSpot Meetings with original start and end times preserved along with the meeting owner. The parent record link to either the Contact or WorkOrder is maintained in HubSpot to preserve the relationship context and ensure activity history is accessible from the relevant record in the destination system.

FieldFX file attachments (stored as Salesforce Files/ContentVersion) are downloaded and re-uploaded to HubSpot Files. Each file re-attaches to the corresponding HubSpot record (Contact, Company, Work_Order__c, or Asset__c). Salesforce inline images in notes are extracted and re-hosted in HubSpot's file storage.

Every custom field on FieldFX objects (technician_id__c, service_type__c, coverage_type__c, warranty_status__c) requires a corresponding HubSpot custom property. We auto-create these in HubSpot before migration and flag any that exceed HubSpot's property type limits (e.g., currency fields with too many decimal places).

FieldFX technicians and dispatchers are Salesforce Users. We match them to HubSpot Users by email. If a Salesforce User has no corresponding HubSpot User, their records are assigned to a fallback HubSpot owner and the unresolved-user count is surfaced before the migration runs.

Salesforce Flow automations and FieldFX status workflows do not migrate. These are tied to Salesforce's execution engine. FlitStack exports every Flow definition as a structured YAML specification that your HubSpot admin can use as a rebuild reference for HubSpot workflows and workflow enrollment criteria.