Migrate from Dynamics 365 Field Service to HubSpot

Dynamics 365 account records map 1:1 to HubSpot company records. Primary address fields (city, country, line1) transfer to HubSpot's address properties. The HubSpot company domain property derives from the Dynamics account website field. This direct mapping preserves all standard account fields in HubSpot company properties with no transformation required. Unresolved lookups are flagged before migration commits.

Dynamics 365 contact records migrate to HubSpot contacts. The mobilephone field maps directly to HubSpot mobilephone. The contact's parentcustomerid lookup (account reference) resolves to an association with the target HubSpot company — any unresolved lookups are flagged before migration commits. This ensures account-contact relationships are preserved in HubSpot associations. All standard contact fields transfer as HubSpot contact properties.

Dynamics 365 work orders map to HubSpot tickets. The msdyn_name becomes the ticket subject; msdyn_description becomes the ticket body. Work order status codes (Active, Scheduled, Completed) map via value_mapping to HubSpot ticket_status values (open, pending, closed). The msdyn_serviceaccount lookup resolves to the primary HubSpot company association. Work order priority and incident type fields migrate as custom properties on the ticket.

Work order line items migrate as HubSpot line items associated with the migrated ticket. The msdyn_product lookup resolves to a HubSpot product ID — the product must exist in HubSpot first or is created during the migration. Quantity and unit amount transfer as line item properties. Line item tax and discount fields from Dynamics become custom properties on the HubSpot line item.

Dynamics 365 field service products map to HubSpot product records. Product name, product number, and pricedescription transfer directly. The product's default unit map resolves to HubSpot's unit cost property. All standard product fields (stock keeping unit, vendor name) migrate as HubSpot product properties. The product must exist in HubSpot before line item migration references it.

Dynamics 365 bookable resources represent field technicians and equipment. These map to HubSpot users by email match — unmatched bookable resources without email addresses are flagged for manual user creation or exclusion from the migration. Resource type (technician, facility, equipment) becomes a custom property on the HubSpot user or ticket depending on whether the resource maps to a user record or a custom property.

Dynamics 365 booking status codes (e.g., In Progress, Completed, Canceled) have no native HubSpot equivalent. These migrate as a custom pick-list property (Booking_Status__c) on HubSpot tickets, with value_mapping applied to translate Dynamics status codes to HubSpot-compatible pick-list values. Status reason codes from Dynamics map to corresponding pick-list labels in HubSpot. The custom property is created during migration setup if not already present in HubSpot.

HubSpot has no native facility or equipment entity. Field service equipment records migrate as HubSpot custom properties (facility name, location, capacity) on the ticket if your HubSpot plan supports custom objects, or are flagged for manual rebuild as a custom HubSpot object. Equipment type and operational status fields become additional custom properties on the associated ticket or custom object.

Dynamics 365 custom entities (entities with names prefixed msdyn_ or custom_* in your Dataverse instance) that lack HubSpot native equivalents migrate as HubSpot custom properties — or as HubSpot custom objects on Enterprise plans. We surface the full list during the schema discovery phase so your team decides the mapping strategy. Custom entity relationships to standard entities (account, contact, work order) are resolved via value_mapping on the corresponding HubSpot custom property or object.

Notes attached to Dynamics 365 accounts, contacts, and work orders migrate as HubSpot engagement notes. Original timestamps, owners, and parent-record links are preserved. Rich-text formatting in Dynamics notes converts to HubSpot's note formatting model. Note attachments (files) require separate handling — they migrate to HubSpot file storage with links embedded in the engagement note record. Any formatting not supported by HubSpot converts to plain text.

Work order incidents (the problem type or incident category linked to a work order) migrate as a custom pick-list property on the HubSpot ticket. Incident type name becomes the custom property value — no native HubSpot equivalent exists, so this is recreated as Incident_Type__c. The incident's primary customer and product lookups resolve to HubSpot company and product associations where applicable.

Purchase order and inventory management records in Dynamics 365 Field Service (used for parts tracking) have no HubSpot equivalent. These records are excluded from the CRM migration scope — your team rebuilds inventory tracking in HubSpot or a separate operations tool. Purchase order history can be exported as a CSV reference file for manual entry into your replacement inventory system.