Switching from Zendesk to Zoho Desk is one of the most common helpdesk migrations for growing support teams, and the biggest fear is always the same: losing ticket history. Years of customer conversations, resolution notes, SLA records, and satisfaction ratings sit inside Zendesk, and a botched migration means starting from scratch. This guide walks through the complete zendesk to zoho desk migration process, from pre-migration audit to agent retraining, so you move every ticket, contact, and custom field without gaps. Whether you run a 5-agent team or a 200-agent operation, the steps here apply. You will learn how to export data from Zendesk, use Zoho’s Zwitch tool for the core import, handle custom fields and SLAs through API mapping, validate the transferred data, run a parallel system for safety, and retrain your agents on the new platform.
A clean migration starts weeks before you touch any export button. The audit phase maps everything in your current Zendesk instance that needs to transfer, and equally important, identifies what you can leave behind.
Log into Zendesk Admin and document the following counts: total tickets (open, pending, solved, closed), total end users and organizations, agents and their group assignments, custom ticket fields and their types, macros, triggers, automations, SLA policies, satisfaction rating history, and knowledge base articles. Export these numbers to a spreadsheet. They become your validation benchmark after migration.
Most Zendesk instances carry dead weight: test tickets from initial setup, spam tickets, suspended accounts, and obsolete macros nobody has used in a year. Delete or archive these before migration. Migrating clean data cuts transfer time and reduces the chance of field-mapping errors. If your Zendesk has over 500,000 tickets, purging resolved tickets older than your retention policy (commonly 3 or 5 years) can reduce migration time from days to hours.
Zoho Desk uses Departments where Zendesk uses Groups. A single Zendesk group maps to one Zoho Desk department, but the Zwitch tool currently migrates all tickets into one department. If you run multiple Zendesk groups, plan for a post-migration reorganization within Zoho Desk. Document agent email addresses, since Zwitch requires that agent emails in Zoho Desk match their Zendesk emails for correct ticket assignment. If you are also planning a broader data migration to Zoho, this audit becomes even more critical because field mappings must align across CRM, Desk, and other Zoho apps.
Zendesk provides multiple export methods depending on your plan and data volume. Choosing the right one affects migration speed and completeness.
Go to Zendesk Admin > Account > Reports > Export. Select the JSON export option. This produces a complete dump of tickets, users, organizations, and comments. JSON preserves nested data structures (like conversation threads within tickets) better than CSV. The export file size limit is 2 GB per file. For large instances, Zendesk splits the export across multiple files automatically. Download all parts and keep them together in a single folder.
For instances with more than 1 million tickets, the full export can time out. Use Zendesk’s Incremental Export API to pull records in batches. Set a start_time parameter to pull tickets created after a specific date if you only need recent history. This method gives you finer control over what transfers and lets you run delta syncs during the parallel-run phase.
Zendesk exports do not include macros, triggers, automations, SLA policies, or satisfaction survey configurations. These are configuration objects, not data records. You will need to screenshot or document each one manually and rebuild them in Zoho Desk. Knowledge base articles export separately through the Help Center API or Guide admin interface.
Zoho’s built-in migration tool, Zwitch, handles the core data transfer. It supports direct migration from Zendesk, Freshdesk, Salesforce Desk, and several other platforms.
Before starting Zwitch, complete these steps in Zoho Desk: create the department where tickets will land, invite all agents using their Zendesk email addresses and confirm their accounts, and verify your Zoho Desk subscription tier supports the features you need (workflow rules, SLA management, and custom fields require the Professional plan or higher). Access Zwitch from Zoho Desk Setup > Data Administration > Import/Zwitch. Select Zendesk as the source platform.
Upload your Zendesk JSON export files. Zwitch reads the data and presents a field mapping screen. Standard fields (subject, description, status, priority, assignee) map automatically. Custom fields get dynamically created in Zoho Desk based on the data types Zwitch detects from a sample of your records. Review every mapping carefully. Common issues include:
Fix any mismatches before submitting. Once the migration starts, you cannot change field mappings mid-process. If you are also setting up Zoho Desk for the first time, configure your departments, roles, and email channels before running Zwitch so tickets land in the right queues immediately.
Submit the migration request. Zoho sends a confirmation email, and you must click the acknowledgment link to start the process. Track progress in the Zwitch dashboard, which shows status for each module: contacts, organizations, tickets, and comments. Migration duration depends on volume: under 100,000 tickets with moderate attachments typically completes within 24 hours. Instances with 500,000+ tickets may take 3 to 5 business days.
Zwitch handles the bulk migration, but certain data requires the Zoho Desk API for precise control. Custom field values that Zwitch misinterprets, ticket relationships (parent-child), and metadata like time-tracking entries need API-based imports.
After Zwitch completes, audit the custom fields it created. Pull a sample of 50 to 100 tickets via API and compare field values against the original Zendesk data. Where values differ (truncated text, wrong dropdown selections, missing multi-select values), use the Update Ticket API endpoint to correct them in bulk. Write a script that reads your Zendesk JSON export, matches each ticket by subject and creation date, and pushes corrected custom field values to the Zoho Desk API. Rate limits on the Zoho Desk API allow 15 requests per minute on the Free plan and up to 200 per minute on Enterprise.
Zendesk’s ticket relationships (linked tickets, side conversations) do not have a direct equivalent in Zwitch exports. Zoho Desk supports ticket threading and related tickets, but you need to re-establish these links via API after the primary migration. Export relationship data from Zendesk using the Relationships API, then create corresponding links in Zoho Desk.
SLAs and automations are the backbone of any helpdesk. Since Zwitch does not transfer these configurations, you need to rebuild them in Zoho Desk from your pre-migration documentation.
Zendesk SLAs are defined by conditions (priority, channel, form) and targets (first reply time, next reply time, resolution time). Zoho Desk SLAs follow a similar structure but use different terminology: Service Level Agreements in Zoho Desk tie to departments and are triggered by ticket properties. For each Zendesk SLA policy, create a matching Zoho Desk SLA with equivalent conditions and time targets. Zoho Desk supports business hours and calendar hours, same as Zendesk, so transfer those schedules first.
Zendesk macros (agent-triggered bulk actions) map to Zoho Desk Macros. Zendesk triggers (event-based rules) map to Zoho Desk Workflow Rules. Zendesk automations (time-based rules) map to Zoho Desk Time-Based Rules. Rebuild each one using your pre-migration documentation. Zoho Desk also offers Blueprint, a visual process editor that can replace complex multi-step Zendesk triggers. If your team relies on Zoho Flow automation, you can connect Zoho Desk to other tools in your stack without custom code.
Zendesk CSAT survey results export as part of the ticket data, but the actual survey configuration does not migrate. Set up Zoho Desk’s Customer Happiness Ratings in Setup > General > Happiness Ratings. Configure the rating scale, survey trigger timing, and email template. Historical satisfaction data from Zendesk tickets is preserved in the migrated ticket records, so your reporting baseline remains intact.
Post-migration validation is where most teams cut corners, and it is exactly where migrations fail. A systematic check catches issues before they reach your customers.
Compare total record counts across every module: tickets, contacts, organizations, comments, and attachments. A mismatch of even 1% on a 100,000-ticket migration means 1,000 tickets are missing or duplicated. Run count queries in both Zendesk (before deactivation) and Zoho Desk. Check by status (open, closed, pending) to identify if specific ticket types failed to transfer.
Pull 20 to 30 random tickets from different time periods and ticket types. For each one, verify: the conversation thread is complete (all agent and customer replies present), attachments open correctly, custom field values match the Zendesk original, agent assignment is correct, and creation/modification timestamps are preserved. Document any discrepancies and fix them via API before going live.
If your Zendesk connected to Slack, Shopify, Jira, or other tools, test the equivalent integrations in Zoho Desk. Zoho Desk offers native integrations with many platforms. For example, the Zoho Desk Slack integration lets agents receive and respond to tickets directly from Slack channels, similar to the Zendesk Slack app. Verify each integration endpoint works with the migrated data.
Running both systems simultaneously for 1 to 2 weeks protects against migration failures and gives agents time to adapt.
During the parallel phase, keep Zendesk active for incoming tickets. Route a copy of incoming emails to Zoho Desk using email forwarding rules. Agents work primarily in Zendesk but check Zoho Desk daily to verify that tickets appear correctly and test workflows. This is not a full dual-operation: the goal is verification, not equal usage. At the end of the parallel period, run a final delta sync to capture any tickets created in Zendesk after the initial Zwitch migration.
On cutover day, execute these steps in order:
A well-executed cutover during a low-volume period (early morning or weekend) minimizes customer-facing disruptions. Teams that are serious about reducing customer churn plan their migration during off-peak hours to prevent any tickets from slipping through the cracks.
The technical migration might be flawless, but if agents cannot navigate Zoho Desk on day one, customer experience suffers. Retraining should start during the parallel-run phase, not after cutover.
Break training into three sessions spaced across the parallel-run period:
Create a one-page cheat sheet mapping Zendesk terms to Zoho Desk equivalents. Key translations include: Views become Custom Views, Macros stay as Macros, Triggers become Workflow Rules, Automations become Time-Based Rules, Groups become Teams and Departments, Organizations become Accounts, and Satisfaction Ratings become Happiness Ratings. Pin this document in your team’s communication channel so agents can reference it during the first few weeks.
How long does a Zendesk to Zoho Desk migration take?
Most migrations complete within 1 to 5 business days depending on ticket volume. A helpdesk with under 100,000 tickets and minimal attachments typically finishes in 24 hours through Zoho’s Zwitch tool. Larger datasets with complex custom fields or heavy attachments may need 3 to 5 days plus additional time for validation.
Will I lose ticket history when migrating from Zendesk to Zoho Desk?
No. Zoho’s Zwitch migration tool transfers tickets with their full conversation threads, timestamps, agent assignments, and attachments. Creation and modification dates are preserved. Run a post-migration audit comparing ticket counts and spot-checking random records to confirm completeness.
Can I migrate Zendesk macros and automations to Zoho Desk?
Zwitch does not migrate macros or automations automatically. You need to manually recreate them in Zoho Desk using its workflow rules, macros, and Blueprint features. Export your Zendesk macros list beforehand and rebuild each one in Zoho Desk’s automation module during the parallel-run phase.
Does Zoho Desk support Zendesk custom fields after migration?
Yes. Zwitch dynamically creates custom fields in Zoho Desk based on sampled data from your Zendesk export. Review the field mapping after migration to confirm field types (text, dropdown, date) transferred correctly. Fields with complex validation rules may need manual adjustment in Zoho Desk’s field settings.
What is the cost of migrating from Zendesk to Zoho Desk?
Zoho’s Zwitch tool is free and included with every Zoho Desk plan. The main cost is the Zoho Desk subscription itself, which starts at USD 14 per agent per month for the Standard plan. If you hire a certified partner for migration planning, field mapping, and agent training, expect consulting fees ranging from USD 2,000 to USD 10,000 depending on complexity.
Aaxonix handles end-to-end Zendesk to Zoho Desk migrations for support teams of all sizes, including ticket export, custom field mapping, SLA rebuilding, and agent training. Book a free consultation to get a migration plan scoped to your ticket volume and timeline.
Book a free consultationA Zendesk to Zoho Desk migration does not need to be a high-risk project. With a thorough pre-migration audit, clean data export, careful field mapping in Zwitch, API-based corrections for edge cases, and a structured parallel-run period, you preserve every ticket thread and customer interaction. Start the process by documenting your current Zendesk setup and inviting your agents to Zoho Desk, then follow the steps in this guide from export through cutover. The result is a fully operational Zoho Desk instance with your complete support history intact and a team that knows how to use it.
How Indian business groups and holding companies use NetSuite OneWorld for multi-entity management: intercompany transactions,…
Automate business workflows with Zoho Flow: CRM to Books, Razorpay to CRM, WhatsApp notifications, and…
Configure NetSuite roles and permissions: standard roles for Indian teams, custom role creation, record-level restrictions,…
Our team builds systems that actually work. No fluff, just honest architecture and clean implementation.
