Migrate from Connect Field Service to HubSpot

Dynamics 365 Accounts map directly to HubSpot Companies. Primary address, industry, and account manager fields migrate as Company properties. Parent-account hierarchies in Dynamics translate to HubSpot's parent-company association. Multi-site accounts collapse to one primary company with additional site addresses stored as custom properties.

Contacts migrate 1:1 to HubSpot Contacts. Email, phone, job title, and address fields use direct mapping. The primary contact role on a Work Order (Customer Account Contact) becomes the primary association on the corresponding HubSpot Ticket. Secondary contacts on service appointments are linked as additional ticket associations.

Work Orders are the core migration object. Each Work Order becomes a HubSpot Ticket, with operational fields (priority, city, incident type, service account) carried as custom properties. The original Work Order number is preserved in a custom property (Work_Order_Number__c) for traceability. Work Order status maps to HubSpot Ticket status using value mapping: In Progress, On Hold, and Completed map to HubSpot's open, pending, and closed states respectively.

Each Work Order Product line splits into two destinations: the product name and quantity migrate as HubSpot Line Items linked to the Ticket; pricing details (unit price, tax, discount) migrate as custom properties on the Line Item. Products not yet in HubSpot's product library are flagged so they can be created before the full migration runs.

Work Order Service Tasks capture the line-item labor tasks and durations. These migrate as custom properties on the HubSpot Ticket — task name, estimated duration, and task type are stored as a JSON-encoded custom property list for display in the ticket timeline. No native equivalent exists in HubSpot's data model.

Service Appointments attached to a Work Order are converted to HubSpot Ticket Comments with original start time, end time, travel duration, and booking status preserved in the comment body. For multi-booking scenarios where multiple technicians are assigned, the primary technician assignment becomes the ticket assignee; secondary bookings are recorded as ticket comments.

Field technicians in Dynamics 365 Bookable Resources map to HubSpot Contacts in a dedicated Technician contact list. Skill certifications, resource type, and working hours are stored as HubSpot custom properties on the Contact. Email match is used to link technicians to HubSpot users for ticket assignment.

Dynamics 365 Skills attached to Bookable Resources have no native HubSpot equivalent. We create a multi-select custom property (Technician_Skills__c) on the HubSpot Contact record and populate it with skill values from the source. Skill level and certification expiry dates are stored as additional custom properties on the same Contact.

Service territories in Dynamics 365 Field Service define which geographic regions a technician covers. These migrate as a custom pick-list property (Service_Territory__c) on the HubSpot Contact record. Multi-territory assignments use a semicolon-delimited custom property since HubSpot has no native many-to-many territory-to-contact model.

Connected Field Service IoT alerts and Customer Assets have no direct HubSpot equivalent. Alerts migrate as HubSpot Tickets with the originating device ID and alert type stored as custom properties. Customer Assets migrate as a HubSpot custom object (Asset__c) with a many-to-one relationship to the Company. IoT alert history is preserved as ticket comments on the Asset record.

Incident types in Dynamics 365 classify the type of service being performed. These map to a custom pick-list property (Incident_Type__c) on HubSpot Tickets. Each Dynamics 365 incident type value is mapped individually to ensure correct categorization in HubSpot's ticket reporting and pipeline filtering.

Work Order Notes and internal email communications migrate as HubSpot Ticket internal notes. Public-facing email threads on a Work Order become Ticket conversation comments. Original timestamps and author names are preserved on each comment. Rich-text formatting in Dynamics notes is converted to plain text for HubSpot compatibility.

Work Order and Service Appointment attachments (photos, signed forms, inspection reports) are downloaded and re-uploaded to HubSpot Files, then associated with the corresponding Ticket record. Inline images in notes are downloaded separately and re-hosted in HubSpot's file manager. File size limits per HubSpot's storage tier apply — large files are flagged before migration.