Migrate from HelpDesk to Zoho Desk

HelpDesk Tickets map directly to Zoho Desk Tickets with subject, description, status, priority, type, channel, and timestamps preserved. We resolve HelpDesk agent assignments by email match to Zoho Desk Agents during import. The primary complexity is that HelpDesk uses a flat inbox model while Zoho Desk scopes tickets to a Department; we map HelpDesk Inboxes to Zoho Desk Departments during scoping so that ticket assignment respects the department hierarchy. Custom ticket fields are enumerated from the HelpDesk API during discovery and pre-created in Zoho Desk before any ticket import begins.

HelpDesk Customer profiles (name, email, phone, company, and custom properties) map to Zoho Desk Contacts. We create the Contact in Zoho Desk with the HelpDesk customer ID stored as ContactExtId for cross-reference. If HelpDesk stores a company name on the customer record, we either link the Contact to a Zoho Desk Account using the AccountExtId or create the Account during import if one does not exist. Email is the primary deduplication key on import.

HelpDesk Agent accounts (name, email, role, and availability status) map to Zoho Desk Agents by email match. Agent roles (admin, agent) map to Zoho Desk role assignments during provisioning. Any HelpDesk Agent referenced on a ticket who does not have a corresponding Zoho Desk Agent account is held in a reconciliation queue; the customer's admin provisions the missing account before ticket import resumes to avoid orphaned agent assignments.

HelpDesk Conversation messages on a ticket map to Zoho Desk Thread entries within the corresponding Ticket. Author attribution (agent vs customer), message content, and timestamp are preserved in the Thread record. Thread direction (incoming from customer, outgoing from agent) is retained so that the ticket's full resolution history reads correctly in Zoho Desk. We import Threads in chronological order to maintain the conversation timeline.

HelpDesk stores attachments on CDN URLs that expire or become inaccessible after account closure. We download all HelpDesk attachment URLs to FlitStack-managed storage as the first migration step, then re-upload each file to Zoho Desk using the Zoho Desk Files API and attach it to the correct ticket record. This prevents orphaned attachments and ensures that all linked files remain accessible in Zoho Desk after cutover. If the HelpDesk account is closed before migration completes, unrecoverable attachments are flagged in the reconciliation report.

Tags applied to HelpDesk Tickets migrate as Tag strings in Zoho Desk. We preserve the full tag vocabulary and re-apply tag associations to the corresponding Zoho Desk tickets so that tag-based filtering and reporting work identically post-migration. Tag-based segmentation in Zoho Desk reports will reflect the same groupings as in HelpDesk without requiring manual relabeling.

HelpDesk exports custom field values but does not include the field schema definition in the export. We enumerate all HelpDesk custom field types (text, number, date, dropdown, checkbox, etc.) by querying the HelpDesk API during discovery, then create matching fields in Zoho Desk before importing ticket records. If a HelpDesk custom field type is not supported natively in Zoho Desk (for example, a complex multi-select with conditional logic), we flag the discrepancy during scoping and propose a transformation such as converting to a multi-select picklist or storing the value in a custom text field.

HelpDesk SLA policies (first response time and resolution time targets by priority) map to Zoho Desk SLA Policies. We document every HelpDesk SLA rule during discovery, map the response and resolution time thresholds to Zoho Desk's SLA Policy configuration fields, and flag any HelpDesk-specific SLA conditions (such as time-based triggers tied to HelpDesk's inbox model) that require rebuilding in Zoho Desk's SLA Rule builder. Complex multi-step SLA chains with conditional escalation paths are documented in the automation rebuild guide rather than migrated as executable code.

HelpDesk automated inbox rules for ticket routing and agent assignment map to Zoho Desk's Assignment Rules and Workflow Rules. We document every active HelpDesk inbox rule during discovery, including trigger conditions, routing criteria (by tag, channel, priority, inbox assignment), and action outcomes. The mapping matrix we deliver maps each HelpDesk rule to its recommended Zoho Desk equivalent, noting that routing based on HelpDesk Inboxes requires mapping to Zoho Desk Departments first. Complex rule chains with multiple nested conditions are documented in the rebuild guide for the customer's admin to recreate in Zoho Desk's visual workflow builder.

HelpDesk canned responses (reusable response templates) map to Zoho Desk Solutions as individual articles. If HelpDesk organizes canned responses into folders or categories, we replicate the folder structure as Zoho Desk Categories under the Solutions module. The response content migrates as-is; any dynamic variable placeholders (such as customer name or ticket number) are preserved as text and should be replaced with Zoho Desk's equivalent variable syntax post-migration if the customer uses Zoho Desk's variable system for templates.

HelpDesk ticket created_at and updated_at timestamps migrate to Zoho Desk's createdTime and modifiedTime fields via the Zoho Desk API. We set these timestamps directly on import so that the ticket's historical record reflects the original creation and modification dates rather than the migration date. Zoho Desk allows past timestamps on the API so historical ticket ages are preserved correctly in the timeline and SLA calculations apply from the original date.

HelpDesk's channel field (email, chat, phone, form, API) maps directly to Zoho Desk's channel field using the same enumerated values. If HelpDesk records a specific phone number or chat transcript reference on the ticket, we preserve this in Zoho Desk's channel-specific fields where supported or store it in a custom text field if the channel metadata type is not natively available in Zoho Desk's channel mapping.

Tickets submitted through HelpDesk's customer portal map to Zoho Desk Tickets with the channel field set to Portal. We preserve the portal user's contact information and link the ticket to the corresponding Zoho Desk Contact record by email lookup. Any portal-specific submission metadata (such as the portal page URL or form version) is stored in a custom text field for audit and reference.