Migrate from Zoho FSM to Pipedrive

Zoho FSM contacts map 1:1 to Pipedrive People. Name, email, phone, address, and owner assignment transfer directly. Contacts linked to multiple companies in Zoho FSM require a primary organization assignment in Pipedrive — the most recently modified company becomes the primary Organization link.

Zoho FSM companies map to Pipedrive Organizations. Company name, domain, industry, employee count, and annual revenue fields transfer directly. Zoho parent-child company hierarchies map to Pipedrive's parent organization field — the parent must exist before the child organization is created.

Zoho FSM work orders carry job details, service tasks, parts, line items, and status — none of which have native Pipedrive equivalents. FlitStack splits the work order: header details (subject, description, status, priority) become Pipedrive Deal fields and custom fields; line items (parts and services) become Deal Product entries or custom fields depending on your Pipedrive plan.

Zoho FSM service appointments store scheduling windows, technician assignments, trip data, and time slots that Pipedrive does not model natively. Appointment date, time, and duration become Pipedrive Activity records (type=Meeting or Task) linked to the corresponding Deal. Technician assignments and trip data migrate as custom fields on the Activity record.

Zoho FSM customer requests represent incoming service inquiries before a work order is created. Multiple requests from the same contact can be consolidated into a single Pipedrive Deal representing the opportunity, or each request can become a separate Deal with a custom Request_ID field for traceability.

Zoho FSM assets track equipment, serial numbers, installation dates, and customer-site locations. Pipedrive has no native asset module. Assets are migrated as a custom object (Pipedrive Enterprise plan) or as custom fields on the linked Organization record — serial number, product name, and warranty status transfer as text fields.

Zoho FSM estimates with line items map to Pipedrive Deals with Products attached. Estimate status (Draft, Sent, Accepted, Rejected) maps to a custom pick-list field on the Deal. Total amount, tax, and discount fields become custom number fields or Product pricing on the Deal.

Zoho FSM users and field agents resolve to Pipedrive users by email match. Active/inactive status, profile (Administrator, Dispatcher, Field Agent), and territory assignments transfer as custom fields on the Pipedrive user record since Pipedrive does not have a native territory model for user assignment.

Zoho FSM notes attached to any record (contact, company, work order, appointment) migrate as Pipedrive Activity records with type=Note. Original create date, author, and linked entity are preserved. Rich-text formatting in Zoho notes is simplified to plain text in Pipedrive.

Zoho FSM territories group field agents and service areas by geography or department. Pipedrive has no native territory concept for user or organization grouping. Territory data is preserved as a custom text field on both the User record and the Organization record for filtering and reporting — your admin configures territory-based visibility rules manually in Pipedrive.

Zoho FSM service and parts catalog items map to Pipedrive Products. Product name, unit price, unit, tax, and description transfer directly. Bundle and variant relationships in Zoho FSM collapse to a flat product list in Pipedrive — your admin reassembles bundles post-migration if needed.

Zoho FSM skills assign technician capabilities (HVAC certification, electrical license, etc.) to field agents for dispatch routing. Pipedrive has no native skills model. Skills migrate as a multi-select custom field on the Pipedrive User record — your dispatcher uses this field manually for routing decisions or workflow filters.

Zoho FSM time sheets track technician hours per service appointment or work order. Each time sheet entry becomes a Pipedrive Activity record (type=Task) linked to the corresponding Deal, with start time, end time, and total hours stored as custom number fields. Original technician user assignment is preserved.