Migrate from Zoho FSM to Zoho CRM

FSM Contact maps directly to CRM Contact, transferring standard fields such as name, email, phone, mobile, title, and mailing address via the Zoho Bulk API. Contact type pick‑list values are reconciled with CRM's options, and non‑matching values are added to the pick‑list before import. The FSM contact‑to‑company link is preserved as a Contact.Account_Name lookup, so each contact links to its correct CRM account.

FSM Company maps directly to CRM Account, converting Company_Name to Account_Name, phone to Phone, and website to Website via the Zoho Bulk API. Additional fields such as industry, account type, billing address, and parent‑company hierarchy are mapped to their CRM equivalents, with non‑matching pick‑list values created in CRM before the import. The parent‑company relationship is preserved using CRM's Parent Account lookup, maintaining multi‑level hierarchies in the target system.

FSM Assets migrate to CRM Assets with the Account lookup resolved first so each asset links to the correct customer account. Asset service history — past Work Orders and Service Appointments — is preserved as linked custom objects or Notes.

CRM has no native Request object. We create a custom module FSM_Requests__c in CRM, define fields matching FSM's Request schema (subject, status, priority, related Contact and Asset lookups), and import all historical Requests preserving the original create date and owner.

CRM has no native Work Order equivalent. We create FSM_Work_Orders__c as a custom module with Services, Parts, and Service Tasks stored as subforms. FSM work order status, scheduled times, assigned technician, and related Asset and Contact are mapped field-by-field. Service and Parts line-item limits are noted per FSM edition.

FSM Service Appointments map to CRM Events for scheduled time blocks and CRM Tasks for to-do items. Appointment start and end times become Event Start_Time and End_Time. Technician assignment resolves by email match to CRM users. FSM appointment notes migrate as CRM event descriptions.

FSM Estimates map to CRM Quotes, subject to field-level mapping. Estimate line items (services and parts) map to Quote Line Items. Status values (Draft, Sent, Accepted, Rejected) map to corresponding CRM Quote stage values. Currency handling follows Zoho CRM's multi-currency model.

CRM has no native Skill matching model. FSM technician skills are preserved as multi-select custom fields on the CRM User record and optionally on Contacts for customer-facing skill requirements. We surface this in the migration plan so your admin can configure the pick-list values before import.

FSM file attachments on Work Orders, Service Appointments, and Assets are uploaded to CRM using the Zoho Bulk API Attachments endpoint, preserving original filenames and MIME types. File size limits for the CRM edition are enforced, and oversized files are flagged for manual review. Inline images from FSM notes are extracted, downloaded, and re‑hosted in CRM's file storage, then linked to the corresponding record to retain visual context.

FSM technicians and dispatchers resolve by email match against CRM users. Unmatched FSM users are flagged before migration — you either invite them to CRM first or assign their records to a fallback CRM user owner. FSM profile permissions (Dispatcher, Field Agent) map to CRM roles.

Any FSM custom modules and associated custom fields are reproduced as CRM custom modules. Custom field data types are matched to CRM field types: text to single-line, pick-list to pick-list, multi-select to multi-select, date to date. FSM subform relationships become CRM subforms on the custom module.