Migrate your Zoho FSM data

Contacts is a first-class module with a defined import (CSV) and export path. We map all standard fields and preserve the linked Address record associated with each Contact during migration.

Companies exports alongside Contacts and includes their related Addresses. We maintain the bi-directional link between Companies and Contacts when migrating to or from Zoho FSM.

Assets link to both Contacts and Companies, and the export includes that linkage. We preserve the asset-to-site relationship when moving Assets in or out of Zoho FSM.

Requests is the parent entity for Work Orders and Estimates. Zoho FSM exports Requests with related data, and we restore the parent-child chain when loading into a destination FSM platform.

Estimates include Standard Estimates with optional line items across all paid tiers. We carry forward the estimate-to-Work-Order linkage and preserve any approved/rejected status state during migration.

Work Orders are the core operational record. They export with their Services, Parts, Service Tasks, and Skills as a bundled related-data set. We chunk Work Orders by tier line-item limits (10/20/30/50 per work order) during import to avoid truncation.

Service Appointments export with their Time Sheets and assigned Service Resources. Multi-day appointments are only available on Professional and Premium tiers, so we flag destination plans that lack this capability before migration.

Time Sheets track hours per appointment and per task. Per-appointment limits vary by tier (10 on Free/Standard, 15 on Professional, 5 on Premium). We normalize the count and flag records that would exceed a lower-tier destination plan's limits.

Services and Parts are inventoried line items. Exports include Service Tasks as related data. We map part pricing and availability flags to match the destination platform's inventory structure.

Skills are used to match field agents to Work Orders and are exported as a related record of Work Orders. We treat Skills as a tagging/matching layer and map them to equivalent attributes in the destination CRM.

Crews group multiple field agents for collaborative dispatch. We export Crew membership alongside Service Appointments and map crew assignments to Teams or Grouping concepts in the destination platform.

Territories segment service areas by geography, department, or commerce type. We export territory definitions and the agent-to-territory assignments, mapping them to equivalent segmentation in the destination system.

Time Off records prevent double-booking of field agents. Export includes Time Off linked to Service Resources. We validate against the destination platform's scheduling constraints to prevent appointment conflicts post-migration.

Service Resources represent the field agents themselves with their profiles (Administrator, Dispatcher, Field Agent, Limited Field Agent). We map the user profile assignments and license type alongside the resource record.