Migrate your Zoho Desk data

Tickets are the core object and support all standard fields plus custom fields. Status values vary between source and destination and require explicit mapping. We extract the full ticket record including priority, channel origin, and linked sub-forms, then normalize statuses at the destination.

Thread history including internal and public comments, email body, and inline attachments is stored as a linked sub-object to Tickets. We export threads in chronological order and reconstruct the conversation thread at the destination, noting that inline images may require re-hosting.

Contacts map 1:1 to standard CRM contact schemas across most platforms. Zoho Desk stores contact name, email, phone, address, and custom properties. We handle duplicate detection by email and map any custom Contact fields to destination equivalents.

Accounts represent the parent organization for a Contact and support hierarchical structures. We migrate Account name, industry, website, and linking relationships to Contacts. Multi-department account structures are preserved via the account-subaccount relationship.

Products are a lookup/reference object linking to Tickets for warranty and entitlement tracking. They carry name, SKU, description, and custom fields. We migrate Products as reference data and map the product-to-ticket association at the destination.

Tasks are sub-objects of Tickets used for action items and to-dos. We export task subject, due date, assignee, and status. Tasks without a parent ticket are flagged for manual placement during migration.

Knowledge Base Articles are versioned content published to Help Centers. We export title, body HTML, author, category, tags, and publication status. HTML content is transferred as-is; images embedded in article bodies require URL remapping if the source help center domain is not replicated.

Departments are organizational containers that route tickets and assign agents. They carry name, email, phone, and settings. We migrate department structures and agent assignments, noting that multi-department routing rules may need rebuild verification at the destination.

Agents are the billing unit in Zoho Desk and carry name, email, role, and department assignment. We migrate agent records and preserve comment ownership by matching email addresses. Inactive agents must be activated in the target account before migration or their comments will be attributed to a generic fallback user.

Teams are agent groupings used for ticket assignment and workload balancing. We migrate team membership and the team-ticket assignment rules. Teams without members are skipped to avoid orphaned routing configurations.

Tags are flat labels applied to Tickets and Contacts. We export tag names and apply them to the corresponding records at the destination. Tag-based automations in Zoho Desk will not transfer and must be rebuilt in the target system.

Ticket and article attachments are stored in Zoho WorkDrive or as direct file references. We extract file URLs and download attachments up to the Zoho-imposed 10GB upload limit. Files exceeding this limit are flagged for customer decision on compression or exclusion.

Custom fields on Tickets, Contacts, and Accounts are exported with their data types (text, picklist, date, number). We map custom field schemas between source and destination, handling picklist value translation and preserving the custom field relationship to the parent object.

Blueprints are Zoho Desk-specific workflow state machines that enforce ticket progression through defined stages. These are not portable objects and cannot be exported via API. We document the Blueprint stage definitions for manual reconstruction at the destination platform.

SLA Policies define response and resolution time thresholds linked to ticket priority or category. We export the SLA configuration and flag which tickets reference which policy, but SLA enforcement rules must be rebuilt in the destination system using that platform's own SLA engine.