Migrate from Field Services Workflow and Logistics to Zoho CRM

Salesforce Work Orders map directly to Zoho Deals. The Work Order number becomes the Deal name with original WO number preserved in a custom field. Status field maps via value mapping: 'New' → 'Presentation', 'In Progress' → 'Needs Analysis', 'Closed' → 'Closed Won/Lost'. Parent Work Orders without service appointments migrate as standalone Deals; child line items require subform or related list reconstruction.

Work Order Line Items represent service line entries (labor hours, parts installed, travel charges). These map to Zoho Products linked to the parent Deal via Deal-Product associations. Each line item quantity and unit price map to Zoho's Product quantity and list price on the deal. Material costs and service fees appear as separate Product line entries.

Service Appointments in Salesforce track scheduled visits, including start/end time, assigned technician, and location. These migrate as Zoho Events with the original start/end datetime preserved. The assigned Service Resource resolves by email to a Zoho user. Earliest start date and due date map to Event start/end. Status ('None', 'Scheduled', 'Completed', 'Cannot Complete') maps via value mapping.

Service Resources represent technicians, dispatchers, and field agents in Salesforce Field Service. Each resolves by email match to a Zoho CRM user. The resource type ('Technician', 'Dispatcher') maps to Zoho's role-based access. Active/Inactive status maps directly. Skills and certifications attached to the resource migrate to a custom module or picklist.

Salesforce Skill Requirements define which certifications or competencies a work order requires. There is no native Zoho equivalent—these migrate to a custom module ('Technician Skills') with lookup to the Contact/Users record, skill name, proficiency level, and expiration date. FlitStack creates the custom module and maps all skill records before the main migration run.

Salesforce Operating Hours define business hours and availability windows for dispatch. Zoho has no native operating hours object. Availability windows migrate as custom multi-select picklists on Zoho Users ('Available Days') and custom time-range fields. Recurring availability patterns are documented as a rebuild reference for Zoho Blueprint scheduling rules.

Service Territories define geographic coverage areas in Salesforce Field Service with associated operating hours and assigned resources. Zoho has no native territory management. Territories migrate to a custom module with territory name, postal code ranges, and linked Service Resource lookups. Geo-coordinates for map-based dispatch are preserved as reference fields pending Zoho FSM integration.

Work Order Location stores the service site address, including street, city, state, postal code, and latitude/longitude. The address maps directly to the Account's billing address fields in Zoho CRM. Latitude and longitude migrate to custom decimal fields for geo-reference. Multiple service locations per account are supported via Zoho's multi-address configuration or related Contact records.

Salesforce Products used in Field Service (parts, service fees, labor rates) map 1:1 to Zoho Products. Product name, code, unit price, and product family migrate directly. The Product2 object in Salesforce has a direct equivalent in Zoho's Product module. Active/inactive status maps from Salesforce's IsActive flag.

Completed Service Appointments with historical status migrate as Zoho Events with 'Completed' status flag set. The appointment outcome (parts used, notes, customer signature reference) migrates as linked Notes on the Event record. Original scheduled technician and actual technician are both preserved for audit continuity.

Salesforce Entitlements link work orders to service contracts and SLA terms. Zoho has no native entitlement object. Entitlement records (contract name, SLA tier, remaining incidents) migrate to a custom module linked to the Account. SLA breach flags and response-time tracking are preserved as custom datetime and checkbox fields for rebuild in Zoho.

Customer accounts in Salesforce Field Service map directly to Zoho Accounts. Account name, industry, phone, website, and billing address migrate directly. Salesforce's Account source (e.g., 'Customer Portal', 'Manual') maps to a custom picklist in Zoho for data provenance. Parent-child account hierarchies use Zoho's Parent Account lookup.

Contacts in Salesforce Field Service include both customer contacts and internal technician contacts. All contacts migrate to Zoho Contacts by email deduplication. Salesforce's 'IsTechnician' flag maps to a custom checkbox in Zoho. The technician's home address (for dispatch proximity) migrates as a custom address field on the Contact record.

Work Order and Service Appointment attachments (photos, signed forms, parts images) migrate as Zoho Attachments linked to the corresponding Deal or Event. Customer signature images stored in Salesforce migrate as file attachments in Zoho. Maximum file size per Zoho upload is 50MB; files exceeding this are split or linked via URL reference.

Salesforce Work Order Priority ('Low', 'Medium', 'High', 'Critical') maps to a custom picklist field (Priority) on Zoho Deals. Value mapping is 1:1. Priority-based SLA response times documented as a rebuild reference for Zoho Blueprint conditional rules. Historical priority timestamps are preserved as custom datetime fields on each Deal.