Migrate from Zoho FSM to HubSpot

Direct 1:1 map. Zoho FSM contact fields (first name, last name, email, phone, mobile, job title, address components) map to HubSpot contact properties with matching field names where available. The Zoho FSM contact's internal ID is preserved as Source_System_ID__c on the HubSpot Contact record for delta-run de-duplication, association resolution across related Work Orders and Service Appointments, and full audit traceability throughout the migration lifecycle.

Direct 1:1 map. Zoho FSM company fields (name, domain/website, industry, employee count, annual revenue, address) map to HubSpot company properties. Parent-child company hierarchies in Zoho FSM map to HubSpot's parent company association field. Multiple contacts per company handled via HubSpot's primary-company association plus secondary associations.

Zoho FSM Assets — which represent equipment, product units, or sites assigned to a customer location — map to HubSpot's Assets custom object (Enterprise) or are stored as a custom property on the associated Company record. Asset.Serial_Number, Asset.Product, and Asset.Site_Location map to matching custom properties in HubSpot.

HubSpot has no native Work Order equivalent. Zoho FSM Work Order fields (work order number, status, priority, assigned technician/crew, associated contact, associated company, associated assets, work order address, description, total amount) map to a HubSpot custom object (Work_Order__c) created under your Enterprise license. Work Order line items (service line items, part line items) become sub-records via HubSpot custom-line-item associations or custom object child records.

Zoho FSM Service Appointments carry scheduling details (start/end time, technician, service location, associated work order) with timestamps and status. These map to HubSpot Events for calendar display, with additional fields stored on a custom Service_Appointment__c object if your HubSpot plan includes custom objects. Service appointment status, duration, and service resource fields become custom properties on the HubSpot equivalent record.

Zoho FSM Requests represent initial service requests that may or may not convert to a Work Order. In HubSpot, Requests map either to a Ticket (for customer-facing service requests) or a Deal (for pre-sale or opportunity-linked requests). The mapping decision is made per your specification during the migration planning phase, and the Zoho FSM Request-to-Work-Order module mapping is preserved as a custom field on the resulting HubSpot record.

Zoho FSM Estimates (quotes with line items, pricing, discounts, and status) have no native HubSpot equivalent. Estimates map to a HubSpot Deal with line items, or to a custom Estimate__c custom object storing Estimate fields as custom properties. Estimate line items become HubSpot product associations or line-item custom fields, since HubSpot's product catalog does not natively support multiple price lists — multi-currency estimates require custom currency fields.

Zoho FSM Skills (used to match technicians to work orders by expertise) have no HubSpot CRM equivalent. Skills associated with a Zoho FSM contact or work order are migrated as a multi-select custom property (e.g., Technician_Skills__c) on the Contact or Work_Order__c record. Rebuilding skill-based routing in HubSpot requires workflow-based assignment rules.

Zoho FSM Territory management (geographic zones assigned to teams) has no HubSpot CRM native equivalent. Territory names associated with Zoho FSM service resources or work orders are migrated as custom properties on the relevant Contact or Work_Order__c record. Geographic routing must be rebuilt in HubSpot using workflow conditions or a third-party scheduling integration.

Zoho FSM Crews group multiple service resources for joint assignments. HubSpot has no native crew or team-grouping object. Crew membership is preserved as a multi-select custom property on the relevant Contact records (Technician_1, Technician_2, etc.) or as a custom junction object if your HubSpot plan supports custom objects.

Zoho FSM Time Sheets record hours worked per service appointment. HubSpot has no native time-tracking object. Time sheet entries migrate as Tasks with time-logging properties, or as a custom Time_Sheet__c object storing hours, date, technician, and associated service appointment reference. Labor-payment calculations based on time sheets must be rebuilt in HubSpot.

Zoho FSM allows multiple price lists per product, each with its own unit pricing. HubSpot supports a single product catalog with one unit price per product. If Zoho FSM uses multiple price lists, each list's pricing is migrated as a separate custom property on the HubSpot product (e.g., Price_List_A__c, Price_List_B__c), or a custom Price_List__c object is created to associate price values with list names.

Zoho FSM service resources (technicians, dispatchers) who are also CRM users map to HubSpot Users by email address resolution. Dispatchers who are not HubSpot Users are mapped to Contact records with a Role__c custom property set to 'Dispatcher'. Unmatched users are flagged before migration for team invitations or fallback assignment.

Zoho FSM file attachments on Work Orders, Estimates, or Service Appointments are downloaded and re-uploaded to HubSpot Files, linked to the corresponding HubSpot record (Work_Order__c, Estimate__c, or Event). File size limits (HubSpot default 25MB per file) are handled in the migration plan, with oversized files flagged for manual upload.

Zoho FSM heavily uses lookup fields creating N:1 and N:N relationships (e.g., Work Order to Asset, Work Order to Contact, Service Appointment to Technician). HubSpot associations are resolved by matching on the source system IDs stored in Source_System_ID__c custom fields. N:N relationships that cannot be expressed as a primary association become HubSpot association labels or a custom junction object (Work_Order_Asset__c, etc.).