Migrate from Connect Field Service to Zoho CRM

Work Orders are the primary work record in Connect Field Service and map to Zoho Deals. Status, priority, work type, and sub-stage fields migrate as custom fields on the Deal record since Zoho Deal records do not have native service-stage fields. Each Work Order retains its original Account and Contact links.

Connect Field Service Service Appointments carry scheduling data (scheduled start, scheduled end, travel time, actual duration) alongside the work outcome. Completed and in-progress appointments with a defined duration migrate as Zoho Events; administrative or pending-flagged appointments migrate as Tasks. Both carry the parent Work Order link.

Direct name-to-name mapping. Connect Field Service Accounts carry billing address, shipping address, and geographic territory linkage. Zoho Accounts store the equivalent address fields. Parent-account hierarchies in Connect map to the Zoho Parent Account lookup, preserving the organizational structure across systems. Billing and shipping addresses transfer as distinct field sets, maintaining separation between financial and operational address data. Geographic territory references in Connect Field Service attach to the Account record and must be reconciled against the Territories_C module after migration to ensure scheduling logic remains functional.

Connect Field Service Contact records (technicians, customer contacts) map directly to Zoho Contacts. Email, phone, title, mailing address, and account linkage all transfer. Contact roles on Work Orders surface as Deal Contact Roles in Zoho CRM, allowing users to track which contacts were involved in specific service engagements. Primary technician assignments from Connect Field Service map to the Deal Owner field, while secondary contacts appear in the Deal Contact Roles section. Customer contacts associated with Work Orders retain their account lookups, enabling full visibility into service history by account.

Assets are first-class objects in Connect Field Service — linked to Accounts with serial number, install date, warranty expiration, product name, and maintenance history. Zoho CRM has no native Asset equivalent, so a custom module (Assets_C) is created with lookups to Accounts and Products. Maintenance history and time entries attach as related Activities.

Connect Field Service product catalog (parts, service items, bundles) maps to Zoho CRM Products. Product name, SKU, unit price, and active status transfer. Quantity on hand, cost price, and product family require custom fields on the Zoho Product record since Zoho Products do not natively track inventory quantities.

Work Order line items track parts used and labor applied per Work Order. In Connect Field Service, each line item references a Product and carries quantity and cost. These migrate as line-item notes or attachments on the corresponding Zoho Deal record, with the part reference stored as a custom text field since Zoho Deals do not have a native line-item sub-object.

Technician absence records (vacation, sick leave, training) in Connect Field Service migrate as all-day Events in Zoho CRM attached to the technician's Contact record. Absence type and reason are stored as custom pick-list fields on the Event. The migration preserves the original absence duration, allowing administrators to view technician availability windows. Travel time or buffer periods that were linked to absences in Connect Field Service are captured as separate related records or attached notes, since Zoho Events do not natively support multi-segment time blocks. This ensures scheduling logic can be reconstructed in Zoho by reviewing absence data alongside Work Order assignments.

Field service activity logs, time entries, and status-change history that are tracked in Connect Field Service migrate as Zoho CRM Notes and Activities linked to the parent Deal (formerly Work Order). Original timestamps and owner IDs are preserved. Each migrated log entry retains its creation date, modification date, and the identity of the technician or dispatcher who made the change. This preservation enables full audit continuity in Zoho, supporting compliance requirements that depend on historical record integrity. Administrators can filter activity history by date range, technician, or status transition type to reconstruct the complete service lifecycle for any migrated Work Order.

Service contracts and entitlement records in Connect Field Service define which customers receive which services under warranty or SLA. These map to a custom module (ServiceContracts_C) with lookups to Accounts and Assets, carrying contract start/end dates, service type, and coverage level as custom fields.

Connect Field Service territories define geographic zones used for scheduling and dispatch. Zoho CRM has no native territory object. Territories migrate as a custom module (Territories_C) with zone name, region, postal code ranges, and assigned technician lookups — used by Zoho administrators as a reference when assigning Work Order records.