Migrate from Field Services Workflow and Logistics to HubSpot

HubSpot has no native work order object — FSM work orders must be modeled as deals with custom properties

HubSpot's CRM object model centers on contacts, companies, deals, tickets, and custom objects. There is no native work order, service appointment, or technician scheduling object. Every WorkOrder in Field Services Workflow and Logistics must translate to a HubSpot deal with FSM-specific metadata (priority, work order type, service address, SLA terms) stored as HubSpot custom deal properties. HubSpot custom objects (available on Enterprise) can host a separate work-order-like object if your team needs a formal service-records object, but the standard migration path maps to deals. We surface this decision early in the mapping plan so your HubSpot admin can pre-create the required custom properties before the migration runs.

FSM scheduling rules and dispatcher logic cannot be extracted from Salesforce — automations must be rebuilt in HubSpot

Field Services Workflow and Logistics stores scheduling constraints (skill matching, geographic routing, SLA thresholds) as FSM managed-package configurations that are not exposed via Salesforce REST or Bulk APIs. The logic governing how a work order routes to a specific technician cannot be exported as a data artifact. When migrating to HubSpot, dispatcher routing rules must be rebuilt using HubSpot workflows and, where available, HubSpot Operations Hub's data transformation capabilities. We export your FSM workflow definitions as a documented reference so your HubSpot admin has a rebuild blueprint, but the automation logic itself does not migrate.

Salesforce API rate limits on FSM objects require staged batch extraction for large work order volumes

Salesforce enforces daily API request limits by edition (100,000 daily API calls for Enterprise Edition plus 1,000 additional calls per user license). Field Services Workflow and Logistics FSM managed-package objects count against these limits during extraction. For migrations with 50,000+ work orders or dense ServiceAppointment histories, we stage the extraction in batches and throttle API calls to avoid hitting Salesforce's limit mid-migration. We agree on a batch schedule with your team and run extraction during off-peak hours to minimize impact on live FSM operations.

Skill requirements and pick-list values need manual recreation in HubSpot after migration

FSM SkillRequirement pick-list values (certification levels, trade categories, service specialties) are defined in Salesforce's setup and are not automatically available in HubSpot. When skill requirements migrate as a custom multi-checkbox property on the deal, the HubSpot admin must manually create each skill option in HubSpot's property settings after migration. If your FSM org has 20+ distinct skill types, plan for 30–45 minutes of HubSpot admin time to recreate the pick-list. We provide the full list of source values in the migration plan to make recreation straightforward.

Multi-level asset hierarchies flatten in HubSpot — parent-child relationships need custom field reconstruction

Field Services Workflow and Logistics supports parent-child asset hierarchies (a customer's HVAC system with nested components). HubSpot's company and contact model does not support native hierarchical asset trees. Parent-child relationships between assets must be flattened using a custom Parent_Asset_ID__c property that references the HubSpot company record ID of the parent asset. This allows your reporting to reconstruct the hierarchy by joining on the custom property, but the native HubSpot UI will not display a tree view of assets. We capture the full asset hierarchy from Salesforce during extraction and surface it in a custom HubSpot property for post-migration reconstruction.