Migrate from Zoho FSM to Salesforce Sales Cloud

Zoho FSM contacts migrate to Salesforce Contacts 1:1. Salesforce requires an AccountId for every Contact — contacts without a primary company in Zoho FSM attach to a default 'Unassigned Account' or the Account derived from the related Company. All contact fields including email, phone, address, and title map directly to their Salesforce equivalents.

Zoho FSM companies map to Salesforce Accounts. Company hierarchies (parent/child) preserved via Salesforce's Parent Account field. Multi-branch companies that use branch as a sub-company within Zoho FSM are split into separate Account records per branch in Salesforce to maintain accurate organizational representation.

Zoho FSM assets migrate to Salesforce Assets. The AccountId on Asset links to the migrated Company. Product2Id is resolved by matching Zoho FSM Services and Parts product names to Salesforce Products. Serial number and installation date map to Name, InstallDate, and Status fields.

Zoho FSM Requests become Salesforce Cases. Request status (Open, On Hold, Closed) maps to Case Status pick-list. Priority from Zoho FSM maps to Case Priority. The related Contact and Account links are preserved. Description and resolution notes migrate to Case Description and Resolution fields.

Zoho FSM work orders split across two Salesforce objects: the service record itself becomes a Case, while the billable value maps to an Opportunity with Products (line items). The split allows Salesforce to track both service history and post-service revenue. Work order number preserved as Case CaseNumber or custom field.

Zoho FSM service appointments map to Salesforce Events (scheduled technician time) and related Tasks (pre-visit and post-visit checklist items). Original start/end times, assigned technician (owner), and location coordinates (latitude/longitude) are preserved. Status from Zoho FSM (Scheduled, Dispatched, Completed, Cancelled) maps to Event Status.

Zoho FSM service line items and parts migrate as OpportunityLineItems on the associated Opportunity. Unit price, quantity, and product name map to Salesforce PricebookEntry. If Zoho FSM uses custom pricing per work order, the migration applies the same values to Salesforce's PricebookEntry pricing structure.

Zoho FSM estimates map to Salesforce Opportunities with Quote objects. The estimate total and line items become Opportunity Amount and OpportunityLineItems. If Salesforce CPQ is in use, estimates translate to CPQ Quote records. Approval status from Zoho FSM migrates as a custom pick-list field on Opportunity.

Zoho FSM skills attached to service resources have no native Salesforce equivalent. Skills are stored in custom fields (Technician_Skills__c) on the User object, and the required skill for a job becomes a custom pick-list on the Case. This enables Salesforce Flow routing rules to assign based on skill match.

Zoho FSM timesheet data migrates to a custom Time_Sheet_Entry__c object linked to the Case or Work Order. Fields include hours worked, technician (UserId), date, and billable flag. Salesforce does not have a native timesheet object — this custom object replicates Zoho FSM's labor tracking for payroll and invoicing.

Zoho FSM file attachments on work orders, assets, and service reports re-upload to Salesforce Files (ContentDocument). File size limits apply — Salesforce default 25MB per file. Photos attached to assets and service reports are downloaded and re-hosted in Salesforce's file storage linked to the parent record.

Zoho FSM blueprints and workflow rules do not migrate. They have to be rebuilt in Salesforce Flow. FlitStack AI exports the Zoho FSM blueprint definitions as a reference document for the Salesforce admin to use during Flow creation. Assignment rules and escalation logic require manual translation to Omni-Channel and Flow.