Migrate from Field service software to Zoho CRM

FSM Customers map directly to Zoho Accounts. FSM location data (service address, GPS coordinates, access instructions) becomes a set of custom fields on the Account — Street, City, State, Postal Code plus Access_Notes__c for key-entry codes and special instructions. Parent-child customer hierarchies in the FSM map to Zoho Parent Account relationships.

The primary contact on an FSM customer record maps to a Zoho Contact linked to the Account via AccountId lookup. The Contact carries name, email, phone, and job title directly. If the FSM stores multiple contacts per customer (site manager, billing contact, field supervisor), secondary contacts are also migrated and linked to the same Account.

FSM Locations merge into either the Account address block (for single-location customers) or a custom Zoho module named Service Locations. This custom module has a lookup to Account and stores location-specific fields: Site_Name__c, GPS_Latitude__c, GPS_Longitude__c, Access_Instructions__c, and Preferred_Technician__c. Multi-location customers end up with one Account and multiple Service Location records.

FSM Work Orders do not have a native Zoho equivalent — they map into a custom Zoho module named Work Orders created via the _C suffix convention (Work_Orders_C). The module stores: Work_Order_Number__c, Description__c, Status__c (value-mapped from FSM statuses to Zoho pick-list), Priority__c, Job_Type__c, Scheduled_Start__c, Scheduled_End__c, Actual_Start__c, Actual_End__c, Assigned_Technician__c (lookup to Zoho Users), Location__c (lookup to Service Locations), and Original_Work_Order_ID__c for traceability.

FSM work orders often contain multiple line items (parts used, labor hours, travel charges). Each line item type splits into a separate subform row within the Zoho Work Orders custom module: Parts_Line_Items subform (Part_Name__c, Part_Number__c, Quantity__c, Unit_Price__c) and Labor_Line_Items subform (Technician__c lookup, Hours__c, Rate__c). This preserves the line-item granularity without forcing one-to-one field mapping.

FSM technician records map to Zoho Users resolved by email address match. Unmatched FSM technicians are flagged as users-to-be-invited before migration. Additional technician fields from the FSM (Certification_Level__c, Service_Area__c, Max_Jobs_Per_Day__c) migrate as custom fields on the Zoho User record, enabling Zoho admin to build routing rules from these attributes post-migration.

FSM service catalog items and parts inventory map to Zoho Products. Fields Name, Code, Unit_Price, and Category map directly. The FSM product type (part vs. service) maps to Zoho Product_Category pick-list (Inventory Item or Service). Products are linked to Work Order line items via Product_Id lookup in the subform.

FSM scheduling data migrates as Zoho Events (for scheduled job windows with start/end datetime, technician assignment, and location) linked to the Work Order record. Real-time dispatch notes that do not have a fixed time window migrate as Zoho Tasks with Subject, Status, and Assigned_To fields. The original scheduling rule (e.g., 'assign to available technician in zone A') does not migrate — it must be rebuilt in Zoho Blueprint.

FSM job completion notes, status-change history, and technician check-in records migrate as Zoho Notes attached to the Work Order. Phone calls and emails logged against a work order migrate as Zoho Tasks with Type='Call' or Type='Email'. Original timestamps and technician names are preserved. Attachments (job photos, signed forms) re-upload as Zoho Files.

FSM platforms with custom objects (equipment registers, warranty records, preventive maintenance schedules) map 1:1 to Zoho custom modules created via the _C naming convention. Relationships between custom objects and standard objects (Work Orders, Accounts) are recreated as Zoho Lookup fields. Many-to-many relationships require a Zoho junction module.