Migrate from SysAid to Zoho Desk

SysAid Service Records map directly to Zoho Desk Tickets as the primary ticket entity. We map subject to Ticket Subject, preserve status, priority, assignee (resolved by email to Zoho Desk Agent), requester (mapped to Zoho Desk Contact), impact, urgency, and all category levels. Attachments are re-linked post-import using file references extracted from SysAid. Historical timestamps are preserved where the destination API permits; Zoho Desk's native API does not allow setting createdAt on tickets, so the original SysAid creation date is stored in a custom field for audit. The SysAid Service Record ID is preserved in an external ID field for reconciliation.

SysAid Assets span three categories requiring separate mapping. Catalog items map to Zoho Desk Products (ProductName, Total Stock, Unit Price, SKU). Configuration Item records map to a custom Zoho Desk object zds_CI__c to replicate SysAid's CI tracking including relationship data. Agent-based inventory records map to custom fields on the Product or CI object depending on data type. The split is designed during discovery and confirmed with the customer before migration. Zoho Desk's Inventory module (part of Zoho Inventory) is an option if the customer licenses it, but is not part of standard Zoho Desk and requires separate setup.

SysAid Users (end users, agents, and administrators) map to Zoho Desk Agents. We match by email address as the reconciliation key. The SysAid role assignment maps to Zoho Desk permission profiles, and department membership maps to Zoho Desk Teams. SysAid permission logic tied to roles must be rebuilt as Zoho Desk permission profiles and department-level access controls after migration. Agents without a matching email in Zoho Desk are held in a reconciliation queue for the customer's admin to provision before record import resumes.

SysAid Company records map to Zoho Desk Accounts with company name as the primary match key. We extract company contact information, address data, and multi-company segmentation rules. If the customer's SysAid instance uses multi-company segmentation to track subsidiaries or business units, we preserve those relationships as Zoho Desk Account hierarchies (parent Account with child Accounts). The Account must be created before any Contact or Ticket import so that the lookup relationship is satisfied at insert time.

SysAid Tasks map directly to Zoho Desk Tasks with title, status, assignee, due dates, and parent entity references preserved. Task dependencies (SysAid supports parent-child task relationships) cannot map natively in Zoho Desk because Zoho Desk does not have a native task dependency field. We store the dependency reference in a custom text field (ParentTaskReference__c) and document the dependency chain for the customer's admin to implement using Zoho Desk Tasks or a project management integration.

SysAid Projects map to Zoho Desk Projects with project name, status, start and end dates, assigned users, and contained task records. Project-level custom fields migrate as custom fields on the Zoho Desk Project object. Milestone data maps to Zoho Desk task records with milestone-specific custom field flags. Projects containing many task records may require batched import to stay within Zoho Desk API time limits.

SysAid Knowledge Base articles require HTML cleaning and media remediation before becoming Zoho Desk Help Center articles. SysAid KB article formatting (tables, code blocks, embedded images) frequently contains inline styles and proprietary media references that do not render correctly in Zoho Desk's article editor. We extract article body content, strip incompatible inline styles, re-upload media as Zoho Desk attachments, and publish to the appropriate Help Center category. Formatting fidelity is a best-effort assessment; post-migration manual cleanup of article layout is common and should be budgeted separately.

SysAid custom fields (up to 200 per entity across Service Record, Asset, Task, Project, CI, User, Company, and Action Item) require type-validated mapping to Zoho Desk custom field types: string, decimal, integer, currency, checkbox, date, datetime, phone, URL, picklist, and multi-select picklist. A significant architectural difference: Zoho Desk custom fields are scoped per department, meaning a custom field created in one department is not automatically available in another. If SysAid custom fields are used across all agents regardless of department, we must create equivalent fields in every Zoho Desk department that will receive migrated records. Field-type mismatches (e.g., SysAid supports data types that Zoho Desk does not) are flagged during scoping and resolved as a configuration decision with the customer.

SysAid Action Items map to Zoho Desk Tasks if they function as lightweight checklist items attached to Service Records. If the customer's Action Items have custom fields, custom triggers, or a more complex schema, they may require a dedicated Zoho Desk custom object (zds_ActionItem__c) with custom fields created to match. Custom triggers defined on SysAid Action Items do not transfer; the automation logic is platform-specific and must be rebuilt as Zoho Desk Blueprint steps or Macros.

SysAid Time Logs (billable and non-billable hours logged against Service Records) map to Zoho Desk Time Entries with hours, dates, billable flag, and agent association preserved. SysAid time log categories map to Zoho Desk time entry categories or custom fields. Time log data volume is typically low relative to ticket volume, but we include it in the migration scope to preserve historical billing and capacity reporting data.

SysAid attachments are stored at the service record level and include files from comments and notes. We extract file references and re-link them post-migration to the corresponding Zoho Desk Ticket using Zoho Desk's attachment API. Attachment storage size limits and the destination plan's storage quota must be confirmed before migration begins. For accounts with large attachment volumes, we may stage the attachment migration after ticket data is confirmed to avoid timeouts during the primary import phase.

SysAid CI (Configuration Item) relationship data (which CI is related to which other CI, to which Service Record, and to which User or Asset) maps to a custom Zoho Desk object zds_CIRelationship__c with lookup fields to the related CI, Service Record, and Asset records. This preserves the relationship graph that IT teams use for impact analysis and root-cause investigation. If the customer uses SysAid's CI relationship fields heavily, we recommend licensing Zoho Desk's CMDB capabilities or a third-party CMDB integration as a longer-term replacement.