Migrate from Zoho Desk to Zendesk

Zoho Desk Tickets map directly to Zendesk Tickets. The ticket_subject, ticket_status, ticket_priority, ticket_dueDate, ticket_description, and ticket_channel fields map to their Zendesk equivalents (subject, status, priority, due_at, description, via). Custom fields on Zoho Tickets migrate to Zendesk custom ticket fields, which must be pre-created in Zendesk with matching field types. Zoho ticket classification (Incident, Request, Problem, Question) does not have a direct Zendesk equivalent and is preserved in a custom field for reference.

Zoho Desk thread history (public comments, internal notes, email body) exports as a chronological list linked to the parent Ticket. We reconstruct the conversation in Zendesk as a sequence of Comment records on the Ticket. Note: Zoho distinguishes outbound (agent-to-customer) replies from inbound (customer-to-agent) responses. Zendesk marks all migrated comments as Incoming by default. We preserve the original direction flag in a custom field so reporting on agent response time remains auditable, but the native Zendesk UI will display all comments as inbound.

Zoho Desk Contacts map 1:1 to Zendesk End Users. Name, email, phone, address, and custom fields migrate directly. We run duplicate detection on email address before import; if a Zendesk End User with the same email already exists, we merge records or flag for admin resolution. Zoho contact_type (customer, partner, vendor) does not have a Zendesk equivalent and is stored in a custom field.

Zoho Desk Accounts map to Zendesk Organizations. The account name, industry, website, phone, and address fields migrate directly. Accounts with multiple contacts in Zoho create the Organization first, then link End Users to it during import via the organization_id reference. We preserve the hierarchical parent-account relationship if the Zoho account has a parent structure by mapping it to Zendesk's parent_organization_id where available on the Zendesk plan.

Zoho Desk Products (used for warranty and entitlement tracking on Tickets) map to Zendesk Products. We extract the product name, description, and status and create Zendesk Products before importing Tickets so that the ticket_product reference is satisfied at insert time. Products without linked tickets are imported as a reference data set only.

Zoho Desk Tasks linked to Tickets migrate to Zendesk Tasks attached to the corresponding Ticket. Standalone Tasks without a parent Ticket are flagged during scoping and held for admin placement since Zendesk supports standalone Tasks but they are not linked to Tickets natively. Task subject, due date, assignee (via email match to Zendesk agent), and status transfer directly.

Zoho Desk Knowledge Base articles migrate to Zendesk Guide articles. We export title, body HTML, author, section, tags, and publication status. HTML content transfers as-is; embedded images are downloaded and re-uploaded to Zendesk's file hosting. Zoho's Root Category and Section hierarchy maps to Zendesk's Section and Label taxonomy, which must be pre-created in Zendesk Guide before the article import. Article translations are not supported for transfer to Zendesk Guide without a Guide Premium plan.

Zoho Desk Agents map to Zendesk Agents (Users with agent role). Agent name, email, role (administrator, agent, supervisor), and department assignment migrate. We resolve agents by email match to Zendesk. If a Zoho Desk agent email does not correspond to a Zendesk agent account, their comment authorship defaults to the importing admin account in Zendesk. We pre-reconcile this list during scoping so the customer can provision missing agent accounts before migration begins.

Zoho Desk Departments map to Zendesk Groups. Department name, email, and agent membership transfer. Multi-department configurations in Zoho Desk that span ticket routing and SLA assignment require pre-configuration of corresponding Groups in Zendesk before migration so that ticket assignment and routing rules can reference them. Department email routing (for split-ticket email addresses) maps to Zendesk brand-specific email configurations.

Zoho Desk Teams (agent groupings for ticket assignment and workload balancing) map to Zendesk Teams. Team membership and the team-ticket assignment rules transfer. Teams without members are skipped to avoid orphaned routing rules. Zendesk Teams are used for agent routing and viewing permissions.

Tags from Zoho Desk migrate as Zendesk Tags applied to the corresponding Tickets and End Users. Tag names transfer directly. However, tag-based automations in Zoho Desk are not migratable; these are documented in the excluded-objects inventory for the admin to rebuild using Zendesk triggers and automations post-migration.

Ticket and article attachments are extracted from Zoho Desk, downloaded to temporary storage, and re-uploaded to Zendesk's file hosting at import time. We audit total attachment volume during scoping against Zoho Desk's file transfer limits. Files exceeding the transfer limit are flagged for selective exclusion or chunked transfers. Inline images embedded in thread content are not migratable via the native Zoho tool and are flagged for manual re-insertion post-migration.

Custom fields on Tickets, Contacts, and Accounts in Zoho Desk are exported with their data types (text, picklist, date, number, checkbox, multi-select). We pre-create equivalent custom fields in Zendesk with matching types before any data import begins. Picklist values from Zoho migrate as option labels in Zendesk picklists; multi-select picklists map to Zendesk tagger fields. Any Zoho custom fields without a Zendesk equivalent are documented for admin decision on whether to create a custom field or store the data as a private note.