Migrate from Salesforce Field Service to HubSpot

Direct map. Salesforce Account maps to HubSpot Company. Account address, industry, employee count, annual revenue, and parent hierarchy all transfer as standard Company properties. Parent Account relationships map via HubSpot's parent company association feature, with the parent Account requiring migration before the child to ensure proper linkage. This preserves the organizational hierarchy established in your Salesforce instance.

Direct map. Salesforce Contact maps to HubSpot Contact with all standard fields transferred including name, email, phone, title, and address. Owner resolution matches Salesforce OwnerId email to a corresponding HubSpot user before record insertion. Any unmatched owners are flagged for admin review and manual assignment in HubSpot after migration completes.

HubSpot has no native Asset object. FlitStack creates an FSL_Asset custom object in HubSpot with fields mirroring the Salesforce Asset schema including serial number, install date, status, product reference, and linked Account/Contact lookups stored as ID properties. This custom object preserves your complete asset registry and enables linking assets to service records in HubSpot.

WorkOrder does not map to a single HubSpot object. Core fields (name, amount, close date, owner) land as a HubSpot Deal. FSL-specific fields (status, priority, latitude, longitude, service type) become custom properties on a FSL_Work_Order custom object linked to the Deal.

ServiceAppointment has no HubSpot equivalent, so FlitStack creates an FSL_Service_Appointment custom object containing subject, description, scheduled start and end times, arrival window, status, and linked WorkOrder ID as properties. Appointment notes transfer as HubSpot engagement notes attached to the parent WorkOrder Deal record.

ServiceTerritory governs geographic coverage and which technicians serve which areas. HubSpot has no territory object. FlitStack exports the territory name and boundary data as a custom text property on each affected Deal so admins can rebuild territory logic in HubSpot Teams.

Technician time-off records stored in ResourceAbsence have no direct HubSpot equivalent. FlitStack maps absence dates, resource reference, and absence type to a FSL_Absence custom object that can be referenced when rebuilding the scheduling calendar in HubSpot, preserving technician availability data for operations planning.

Salesforce Product2 maps directly to HubSpot Product. Product name, code, family, description, and standard cost transfer as HubSpot Product properties. Pricing information requires separate mapping to HubSpot line-item pricing models, with pricing rules needing to be re-established in HubSpot's e-commerce or sales tooling.

WorkOrderLineItem details which product or service was performed on a work order. HubSpot Deals have line items natively, but FSL line items include service-type fields (quantity, work type, duration) that need a FSL_Line_Item custom object linked to the parent WorkOrder Deal.

Files attached to WorkOrder, ServiceAppointment, or Asset via Salesforce ContentDocumentLink are downloaded by FlitStack and re-uploaded to HubSpot Files. Each file is associated to its corresponding migrated record (Deal or custom FSL object) using HubSpot's file association API, with original file names and upload timestamps preserved.

FSL Resource records represent technicians and dispatchers with skill and geolocation data. FlitStack maps resource name and email to a HubSpot Contact record and stores skill tags, service territory assignments, and resource type as custom contact properties, preserving your technician roster within HubSpot's contact management system.

WorkOrder comments and Chatter feed items transfer as HubSpot engagement notes on the parent WorkOrder Deal record. Original timestamps, author names, and comment bodies are preserved in the note metadata, maintaining complete service history and communication threads within the migrated deal records.