Migrate from Serviceaide Intelligent Service Management to Zoho Desk

Serviceaide ISM CCTIs map directly to Zoho Desk Tickets. Standard fields—title, description, status, priority, assignee, requester—map cleanly. Custom ticket fields require field-level mapping against Zoho Desk's custom fields API. ISM's SLA-driven group reassignments (which silently drop via webhook per ISM-13232) are re-applied explicitly after ticket insert by resolving the group name to a Zoho Desk department or agent group ID. We validate and strip special characters from any CI-linked fields before insert to prevent workflow deadlocks.

ISM user records with analyst or agent roles map to Zoho Desk Agents. Role assignments, department, and location from ISM map to Zoho Desk's role, department, and profile fields. ISM end-user accounts map to Zoho Desk Contacts. We resolve owners by email match against the destination org's user table. Any ISM user without a matching Zoho Desk agent is held in a reconciliation queue for the customer's admin to provision before ticket import begins.

ISM's organization-level configuration for multi-tenant MSP and BPO environments maps to Zoho Desk Accounts. Organization-level branding and SLA templates require separate per-tenant mapping when migrating multi-tenant ISM deployments. Account names and domain fields migrate directly. We scope extraction to the specific ISM organization ID and validate tenant boundaries before staging any migration payload to prevent cross-tenant data bleed.

ISM Configuration Items with CI Approval Phases and relationships require a split during migration. Because Zoho Desk does not have a native CMDB module, CIs map to the Products module, with relationship metadata preserved in a custom text field ci_relationships__c as a structured JSON block. CI Approval Phase approval chain (approver name, date, comments) is extracted from ISM's separate metadata fields and appended as a comment thread on the migrated Product record. The ISM-13238 special character defect is scrubbed from all approval phase fields before insert.

ISM Knowledge Manager articles map to Zoho Desk Articles. Article content, tags, and ticket associations migrate directly. The approver metadata (approver names and comments stored separately from the article body per ISM architecture) is preserved as a structured header block at the top of the article body so the approval chain is reconstructable in Zoho Desk. Luma Knowledge artifact associations are mapped to article references and appended as internal notes. Articles are assigned to the correct Zoho Desk category and section during import.

ISM's Service Catalog and Service Manager records map to Zoho Desk Products, as they represent service offerings rather than physical assets. Service-to-ticket associations are preserved by mapping the ISM service identifier to a custom field on the Zoho Desk Ticket. Custom service-level fields map to custom fields on the Product object. SLA thresholds associated with services are documented in the migration inventory for rebuild in Zoho Desk SLA policies.

ISM Asset Center records map to Zoho Desk Assets. Hardware and software inventory fields migrate with type preservation. Asset Center filter bugs in ISM mean some asset records may have incomplete or duplicate fields; we validate field completeness post-extraction and flag records requiring manual review before Zoho Desk insert. Asset-to-CI associations from ISM migrate as structured metadata on the corresponding Zoho Desk Asset record.

ISM Change Manager records with risk assessment, approval phases, and associated CIs map to Zoho Desk Tasks with custom fields for change type, risk level, and approval status. Risk scoring from ISM is preserved in a custom field. Because Zoho Desk has no native Change Management module, the change record schema is extended via custom fields at migration time. The approval chain and phase transitions are appended as task comments with timestamp and approver attribution.

Files attached to ISM tickets, knowledge articles, and change records are extracted with the parent record and re-associated to the migrated Zoho Desk object using Zoho Desk's attachment API endpoints. Inline images in KB article bodies are downloaded and re-uploaded to Zoho Desk's media library to preserve rendering after migration. Attachments larger than 25 MB are flagged for the customer to handle via alternative file storage since Zoho Desk's API enforces a 25 MB attachment limit.

ISM tags used for ticket categorization map to Zoho Desk Tags. Custom fields on ISM tickets and other objects require field-level mapping against the Zoho Desk custom fields API. We pre-create the Zoho Desk custom field schema before migration begins so that the field IDs are available at insert time. Custom field data type mapping is validated against Zoho Desk's supported field types; unsupported types are documented for manual intervention.

For MSP and BPO customers migrating from ISM's multi-tenant architecture, each ISM tenant maps to a Zoho Desk department within a single Zoho organization. If the customer requires full portal isolation (separate help centers per client), we document the portal configuration steps required post-migration. Tenant isolation boundaries from ISM are validated against Zoho Desk's department and portal scoping model during schema design.

ISM Luma AI knowledge artifacts associated with resolved tickets are extracted and re-linked to the corresponding Zoho Desk Ticket as internal notes with a Luma-prefixed header. The Luma knowledge entry content is migrated as an Article if the artifact represents a reusable knowledge piece, or as an internal note on the ticket if it is a ticket-specific resolution artifact. Zia suggestions from Zoho Desk can partially replace Luma's functionality post-migration but require separate configuration.