Migrate from ServiceNow Field Service Management to Zoho CRM

ServiceNow Customer Accounts map directly to Zoho Accounts using the name field as the primary key. Parent Account relationships (using the u_parent_account reference field) migrate to Zoho's Parent Account lookup. Multi-site customers stored as separate ServiceNow Account records with location linking map to individual Zoho Account records, with site names appended to the Account Name.

ServiceNow Contact table (sn_customerservice_contact) maps to Zoho Contacts. The primary Contact for an Account is linked via the Account Name lookup in Zoho. ServiceNow contacts without a parent Account land as standalone Zoho Contacts. Email addresses serve as the deduplication key during migration.

ServiceNow system users migrate to Zoho Users via email address match. The migration flags any ServiceNow user without an email address for manual Zoho user creation before the migration run. User active/inactive status is preserved; inactive ServiceNow users create inactive Zoho users.

ServiceNow Work Orders (sn_fsm_work_order) map to Zoho Deals. The Work Order number becomes the Deal Name prefix. Work Order state (1–4: Pending to Closed Complete) maps to Zoho deal stage values via value_mapping. ServiceNow priority (1 Critical to 4 Low) migrates as a custom pick-list field on the Deal. Original Work Order opened_at timestamp is preserved in a custom field.

ServiceNow Work Order Tasks (sn_fsm_task) map directly to Zoho Tasks linked to the parent Deal. Task state and priority carry over as Zoho Task status and priority. Assignment in ServiceNow (assigned_to sys_user reference) resolves to Zoho User by email. The parent Work Order sys_id is stored in a custom field on each Task for traceability.

ServiceNow Incidents (incident table) migrate to Zoho Cases. The incident number becomes the Case number field. ServiceNow incident state (New → Closed) maps to Zoho Case status via value_mapping. Opened_by user resolves to Zoho User by email. The short_description field maps to Case Subject, and description maps to Case Content.

ServiceNow Problems (problem table) map to Zoho Solutions. Problem state maps to Solution status. The problem_short_description maps to Solution Title, and problem_state determines whether the Solution is marked Active or Obsolete. Problem Incidents linked via the problem_id reference are preserved as notes on the Zoho Solution record.

ServiceNow generic Tasks (task table not linked to Work Orders) migrate as standalone Zoho Tasks. Parent references are preserved as task description notes. Assigned-to user resolves by email match to Zoho Users. Short description becomes Zoho Task Subject. Due dates and priority levels transfer as Zoho Task fields, and sub‑tasks inherit those attributes. When a generic Task references an Account, the Account Name lookup is set to maintain the relationship.

ServiceNow Locations (cmn_location) with address data migrate into the Address fields on Zoho Accounts. Multi-location customers with separate Location records generate multiple Zoho Account records with the site name appended. Latitude/longitude from ServiceNow are stored as custom number fields on the Account for potential map integration.

ServiceNow Installed Products (alm_hardware) or Asset records map to Zoho Products or a custom Assets module depending on your Zoho plan. Serial number, model number, and install date migrate as custom fields. The link between an Asset and its parent Account is preserved via Account Name lookup. Products without serial numbers migrate to Zoho Products directly.

ServiceNow CMDB Configuration Items that do not map to Zoho Products become records in a Zoho Custom Module (Asset Registry). Class name from sn_cmdb_ci_class_map becomes a pick-list value. The CI's supporting CI relationships are exported as note attachments for manual re-creation in Zoho since Zoho lacks a native CMDB relationship model.

ServiceNow file attachments on Work Orders, Incidents, Problems, and Tasks are downloaded and re-uploaded to Zoho. Attachments on Zoho records attach directly to the migrated record (Deal, Case, Task). The original filename and content type are preserved. File size must fall within Zoho's 50MB per-file limit; larger files are flagged for manual handling.

ServiceNow Service Requests that represent request-only interactions (not work orders) merge into Zoho Tasks or Cases depending on whether the request involves ongoing work. Request item (sc_req_item) details are appended to the Zoho Task description. Approval state from ServiceNow is preserved as a custom pick-list on the Task.

ServiceNow Knowledge Articles cannot be directly migrated to Zoho Solutions because Zoho Solutions are customer-facing answer articles with a different schema. Knowledge article text is exported as a JSON blob and stored as a Zoho attachment. We recommend manually rebuilding high-value knowledge articles in Zoho using our exported content as source copy.