Migrate from Zoho FSM to Twenty CRM

Zoho FSM Contact maps 1:1 to Twenty People. Full name is reconstructed from First_Name_Last_Name or Full_Name fields. Email, phone, and job title carry over directly. The primary linked Company in Zoho FSM becomes the People.companyId relation in Twenty. Secondary contacts are imported as additional People records, and any duplicate email entries are flagged for manual review to preserve data integrity.

Zoho FSM Company maps to Twenty Company directly. Company name, domain, industry, and address fields carry over. Zoho's parent‑company hierarchy translates to Twenty's linked Company records via the parentCompanyId relation, with circular references flagged during the migration plan phase. Multi‑location subsidiaries are imported as separate Company rows, and billing versus service addresses are distinguished using Zoho’s address type tags.

Zoho FSM Asset stores equipment and service locations — Twenty has no native asset module, so we create a custom Asset object in Twenty and map asset name, serial number, installation date, and linked contact/company as custom fields. Asset status is preserved as a select field.

Zoho FSM Requests (service requests) have no direct Twenty CRM equivalent. We create a ServiceRequest custom object capturing request number, priority, status, description, and linked contact/company/asset as relation fields. Request history migrates as related Task records, and any attached files are stored in Twenty’s file repository with references on the ServiceRequest.

Zoho FSM Work Orders map to Twenty Opportunities but require enrichment — work order status, priority, and technician assignment migrate as custom fields on the Opportunity record. The work order total (service + parts) becomes the Opportunity amount. Service type and dispatch status are preserved for reporting continuity.

Service task line items and part line items from Zoho FSM work orders are too granular for Twenty's Opportunity model. These migrate to a custom WorkOrderLine custom object linked to the parent Opportunity, preserving line item description, quantity, unit cost, and total.

Zoho FSM Service Appointments (scheduled field visits) translate to Twenty Tasks. Appointment start/end datetime, assigned service resource, and status (Scheduled, In Progress, Completed, Cancelled) are captured as Task fields. Linked work order is preserved via the OpportunityId relation. Additionally, the service location address is stored as a custom Task field, and any appointment notes are migrated as linked Note records for completeness.

Zoho FSM Estimates are proposals tied to service requests or work orders. We create a custom Estimate object in Twenty, mapping estimate number, date, total amount, status, and linked contact/company/work order. Line items are stored as JSON or custom fields for reference.

Zoho FSM service resources (technicians, dispatchers) map to Twenty Workspace Members by email. Zoho FSM profile roles (Field Agent, Dispatcher) have no direct Twenty equivalent — we flag these for manual reassignment in Twenty's settings and preserve role names as a custom text field for reference.

Zoho FSM Skills assigned to service resources have no Twenty CRM equivalent. We create a Skill custom object linked to the service resource (WorkspaceMember), capturing skill name, certification level, and validity dates. This supports rebuilding skill‑based assignment logic manually. Multiple skills per resource are represented as separate Skill records, and skill categories can be added as custom pick‑list fields for easier filtering in Twenty’s list views.

Zoho FSM Territory management (geography‑based service area assignment) has no Twenty equivalent. A Territory custom object is created with name, region, postal codes, and assigned technician, allowing manual rebuild of routing rules in Twenty. Hierarchical territories (regions subdivided into zones) are supported by adding a parentTerritoryId relation, and multiple technicians can be linked to a single Territory record for team‑based coverage.

Notes on Zoho FSM records (contacts, companies, work orders) migrate directly to Twenty Notes. The note body, author, and timestamp carry over. Notes attached to a specific record link via Twenty's relation fields (e.g., noteableId on People or Opportunities). Embedded attachments are stored in Twenty’s file section and referenced by the note record, and any HTML formatting in the original note is simplified to plain text for compatibility.

Zoho FSM time sheets record hours worked per service appointment or task. We map start time, end time, and hours to Twenty Task records as custom duration fields, linked to the service appointment Task and the assigned technician (WorkspaceMember). Overtime entries are captured as additional duration fields, and time‑sheet totals can be aggregated in Twenty’s reporting views for labor cost analysis and future integration with invoicing modules.