Migrate from ServiceNow Customer Service Management to Zoho Desk

ServiceNow Cases map directly to Zoho Desk Tickets. The Case number becomes the ticket number, case_state maps to Ticket Status (Open, Pending, On Hold, Closed), and priority maps to Priority. We resolve the assigned_to fulfiller reference to a Zoho Desk agent email match. Parent Case to child Case Task relationships migrate as Ticket sub-tasks in Zoho Desk. The customer_sys_id is preserved as a custom field sn_original_id__c for audit and cross-reference during the post-migration reconciliation window.

Case Tasks are child records of Cases and inherit the parent ticket's customer context. They map 1:1 to Zoho Desk sub-tasks with assignment chain, status, and due-date preserved. We resolve the parent_case reference to the migrated ticket ID during the sub-task phase so that the parent-child hierarchy is intact on completion.

ServiceNow CSM Accounts (customer companies) map to Zoho Desk Accounts with name, address, and account hierarchy preserved. The account hierarchy in ServiceNow (parent Account with child Accounts) maps to Zoho Desk's organization hierarchy structure. ServiceNow account classification (customer, partner, competitor) migrates as a custom picklist field on the Zoho Desk Account.

ServiceNow CSM Contacts map to Zoho Desk Contacts with email, phone, title, and department preserved. We resolve the contact's account link to the migrated Account ID. Any custom Contact fields from the extended CSM schema are pre-created in Zoho Desk before import. Role (decision maker, economic buyer, champion) migrates as a custom picklist field.

ServiceNow CSM Consumers represent end customers in B2C scenarios. Zoho Desk does not have a separate Consumer object; Consumer records map to Zoho Desk Contacts with a custom field csm_consumer_type__c set to true. Any B2C-specific properties (date of birth, loyalty tier, household ID) migrate as custom fields on the Contact record. If the destination Zoho Desk org uses only Organizations for B2C records, we map Consumers to Account records with the is_company flag set to false.

ServiceNow Service Organizations (internal and external business locations that handle cases) map to Zoho Desk Teams. The IBL/EBL/OSP hierarchy maps to the team structure in Zoho Desk. Each Service Organization's assignment group members migrate as team member assignments in Zoho Desk. Custom fields on the Service Organization record are pre-created on the Team record.

ServiceNow CSM Install Base tracks products sold to customers including warranty status and contract associations. Zoho Desk does not have a native Install Base equivalent. We migrate Install Base records as a custom Zoho Desk module (named 'Installed Products') with product name, serial number, warranty expiry, and contract reference fields. Relationships between Install Base and Account, Contact, and Case records are preserved as lookups in the custom module.

ServiceNow Service Definitions link products and services to case types and define eligibility rules. This is a CSM-specific concept with no Zoho Desk equivalent. We export Service Definitions as structured metadata (JSON) and migrate the relevant service-offering and entitlement data into a custom Zoho Desk module named 'Service Offerings.' Eligibility rules and product-to-service associations are documented separately for the customer's admin to configure in Zoho Desk Blueprint if needed.

ServiceNow Knowledge Articles migrate to Zoho Desk Knowledge Base with article text, metadata, author, and approval status preserved. HTML content renders at the destination. Note that Zoho Desk's native KB import does not carry article attachments; we extract attachments separately via the ServiceNow Attachment API and re-associate them as Zoho Desk KB article attachments post-import, handling the document ID conversion manually per file.

Nearly every CSM instance carries custom fields on Case, Account, Contact, and Consumer tables added via the form configuration. We export the full extended schema using ServiceNow Table API queries that surface all columns, then pre-create equivalent custom fields in Zoho Desk before data import begins. Reference fields (lookups to other tables) are handled as multi-select picklists or lookup configurations in Zoho Desk depending on the destination field type available. Any fields without a matching Zoho Desk type are flagged for review during scoping.

File attachments on ServiceNow Cases and Case Tasks are extracted via the ServiceNow Attachment API using document IDs. We re-associate files at the destination using Zoho Desk's attachment API, mapping them to the corresponding migrated tickets and sub-tasks. Knowledge Base article attachments are handled separately as noted above because Zoho Desk's KB import does not include them by default.

ServiceNow CSM users with the fulfiller role map to Zoho Desk agents. We resolve by email match during import. Users with only the requester role in ServiceNow are not billable seats and map to Zoho Desk end-user contacts. Any ServiceNow user without a matching Zoho Desk agent account is held in the reconciliation queue for the customer's admin to provision before record import continues.

ServiceNow Assignment Sets define which groups or users receive assignments for specific case categories. Zoho Desk Blueprint and Assignment Rules provide comparable routing logic. We document each Assignment Set's conditions, assigned group, and escalation path as a written spec for the customer's Zoho Desk admin to rebuild in Blueprint. This is not migrated as code.

ServiceNow Case internal work notes and customer-visible comments migrate to Zoho Desk ticket comments. We preserve the is_public flag: internal notes map to private comments visible only to agents, and customer-facing comments map to public comments. The comment author resolves to the migrated agent or contact record.