---
title: "Zendesk to Zoho Desk Migration: Field Mapping & Rollback"
description: "Migrate Zendesk to Zoho Desk with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/helpdesk/zendesk/to/zoho-desk"
---

# Zendesk to Zoho Desk migration

We migrate Tickets, Contacts, Organizations, and Help Center articles from Zendesk into Zoho Desk, preserving thread integrity and timestamps through the API, resolving custom field types during import, and flagging every automation requiring rebuild in Zoho's Blueprint before cutover.

Short answer

FlitStack AI migrates tickets, contacts, agents, accounts and custom fields from Zendesk to Zoho Desk, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 2-4 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/helpdesk/zendesk/to/zoho-desk#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Zendesk ![](https://flitstack.ai/platforms-trim/zendesk.webp)

Destination Zoho Desk ![](https://flitstack.ai/platforms-trim/zoho-desk.webp)

Ticket Contact Agent Account Custom Fields

Mapped field by field · sample run · one-click rollback

## What moves from Zendesk to Zoho Desk?

Moving from Zendesk to Zoho Desk is a structural migration that trades Zendesk's enterprise-grade ecosystem depth for Zoho Desk's price predictability and native CRM integration.

Read the full summary

Zendesk's Tickets, Users, Organizations, Brands, Views, Triggers, Automations, SLA Policies, and Help Center content must all be evaluated against Zoho Desk's object model, which separates Business Rules, Workflow Rules, and Time-Based Rules rather than grouping them into Zendesk's Trigger and Automation primitives. We migrate Tickets with full comment threads, attachments, and custom field values; Contacts and Organizations as 1:1 mappings; Help Center articles with section hierarchy; and Tags as flat labels. We do not migrate Triggers, Automations, Macros, SLA Policies, Brands, Views, or Dynamic Content as code — we deliver a written inventory of every Zendesk automation with a recommended Blueprint equivalent for Zoho Desk, and the customer's admin rebuilds them post-migration.

1:1

### Ticket → Ticket

Zendesk Tickets map directly to Zoho Desk Tickets.

How it maps

Every ticket's status (New, Open, Pending, Hold, Solved, Closed), priority, type, and assignee transfers. We resolve Zendesk's assignee email against Zoho Desk agent records at migration time; if a Zoho Desk agent profile does not exist for the assignee, the ticket is assigned to the migration admin and flagged in the reconciliation report. Comments migrate as threaded replies in Zoho Desk's Conversations tab. Ticket channel (email, chat, voice, social) maps to Zoho Desk's channel field, though Zendesk's social channel types may map to a generic 'Social' or 'Other' channel depending on the Zoho Desk version.

1:1

### User (End-User / Requester) → Contact

Zendesk End-Users (requesters) map to Zoho Desk Contacts.

How it maps

We extract name, email, phone, role (end-user vs agent), organization membership, and all custom field values. Zoho Desk Contacts have a one-to-many relationship with Tickets; each Zendesk requester becomes a Contact with its full ticket history. Role distinctions between end-users and agents in Zendesk do not map directly to Zoho Desk's agent model — we flag agent-role users for manual configuration in Zoho Desk post-migration.

mapping

### Agent → Agent

Zendesk Agents map to Zoho Desk Agents.

How it maps

Agent email addresses must match between Zendesk and Zoho Desk for the migration to resolve assignments automatically. Zoho Desk's Zwitch documentation confirms that migrated agents are listed under the 'Imported' tab and do not need to accept invitations. We flag any Zendesk Light Agent records — these map to Zoho Desk Agents but receive no ticket assignments per Zoho's permission model. Department permissions must be configured manually in Zoho Desk after migration.

1:1

### Organization → Account

Zendesk Organizations map to Zoho Desk Accounts.

How it maps

Organization name, domain names, details fields, and user memberships transfer. The Account record is created before any Contact import so that the Account-Contact lookup relationship is satisfied at insert time. Cross-references between Zendesk Organizations and their member Users transfer as Zoho Desk Account-Contact relationships.

configuration

### Custom Fields (Ticket, User, Organization) → Custom Fields

Zendesk ticket custom fields, user custom fields, and organization custom fields migrate to Zoho Desk equivalent fields.

How it maps

Per Zoho's Zwitch documentation, Zoho Desk auto-creates fields that do not already exist and identifies field types from the data (e.g., picklist values become picklist fields). Nested custom fields (hierarchical structures) are not supported for migration. We run a type-resolution step during scoping to identify any Zendesk fields that may not map cleanly (e.g., complex conditional fields, lookup fields to external objects) and flag them for manual Zoho Desk field creation before migration begins.

1:1

### Attachment → Attachment

Ticket comment attachments and Help Center article attachments download from Zendesk via the API and re-upload to Zoho Desk preserving original filenames and MIME types.

How it maps

We store attachments against the parent ticket or article record using Zoho Desk's file upload API. Note: Zendesk inline images embedded in ticket comments are not migrated per Zoho Zwitch limitations; these images remain accessible only while the Zendesk account is active. We notify customers of this limitation during scoping and recommend downloading inline images before migration if they are critical.

******What moves 12 objects

Zendesk Zoho Desk

- Ticket Ticket 1:1
- User Contact 1:1
- Agent Agent transformed
- Organization Account 1:1
- Custom Fields Custom Fields transformed
- Attachment Attachment 1:1

\+ 6 more in the mapping below

## How Zendesk and Zoho Desk differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                       | Zendesk                                                                                      | Zoho Desk                                                                                                                                        |
| ------------------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Automation model                | Triggers (event-driven) + Automations (time-based) under a combined business-rules framework | Business Rules (filter/condition) + Workflow Rules (automated actions) + Time-Based Rules (resolution reminders) as three separate feature types |
| Pricing model                   | Per-agent at $19-$169/month with AI and advanced features as costly add-ons                  | Per-agent from Free (3 agents) to $40/agent/month with Zia AI built into mid and high tiers                                                      |
| Multi-brand vs multi-department | Up to 300 Brands each with own email, help center, and routing                               | Multi-department model with one help center, department-scoped permissions and SLAs                                                              |
| Custom Objects                  | Enterprise/Enterprise Plus only ($150-$169/agent/mo tier)                                    | Custom fields available across Standard tier; custom functions via Deluge scripting on Professional+                                             |
| AI assistant                    | Zendesk AI add-on at $50/agent/month or as a Usage-based add-on                              | Zia AI built-in at no additional cost on Professional and Enterprise tiers                                                                       |
| CRM integration                 | Native sync to Salesforce, HubSpot, and other CRMs via third-party integrations              | Native bidirectional sync with Zoho CRM at no added cost; Microsoft 365 integrations built-in                                                    |
| Knowledge Base                  | Separate Help Center with multi-brand, multi-locale, and Dynamic Content (Growth+)           | Integrated Help Center with self-service portal, forums, and multi-department article scoping                                                    |

## What to watch for in a Zendesk to Zoho Desk migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Tags and Groups cannot be migrated through Zoho's native Zwitch tool

Zoho's official Zwitch migration documentation explicitly states that Tags, Groups, Teams, and Collaborators cannot be migrated.

How we handle it

We handle Tags via direct API read/write by extracting tag assignments from Zendesk Tickets and writing them to Zoho Desk ticket tag fields during the ticket import phase. Groups require manual pre-creation in Zoho Desk before ticket migration begins so that assignment resolution can resolve the group membership during import. We flag this in the discovery report and provide a Group-to-Team mapping template for the customer's admin to complete before migration starts.

high

### Inline images in ticket comments do not transfer and become inaccessible after Zendesk deactivation

Zoho's Zwitch documentation confirms that inline images embedded in ticket comments are not migrated and remain visible only while the Zendesk account is active.

How we handle it

After the Zendesk account is deactivated, inline images will no longer be accessible at all. We notify customers of this limitation during scoping and recommend downloading inline images before the migration window if they contain critical information (screenshots, diagrams, embedded visuals). We cannot re-upload images that are not accessible in Zendesk at migration time.

medium

### Zendesk Triggers and Automations do not migrate to Zoho Blueprint or Workflow Rules

Zendesk's combined Trigger and Automation model (event-driven + time-based rules) maps to three separate concepts in Zoho Desk: Business Rules (ticket filtering on conditions), Workflow Rules (automated actions and notifications), and Time-Based Rules (resolution reminders).

How we handle it

These are not direct equivalents. We do not migrate Triggers and Automations as code. We deliver a written inventory of every active Zendesk Trigger and Automation with its conditions, actions, and recommended Zoho Desk equivalent (Business Rule, Workflow Rule, or Time-Based Rule). The customer's admin rebuilds them in Zoho Desk's Blueprint interface post-migration.

medium

### Zendesk multi-brand structure maps imperfectly to Zoho Desk's multi-department model

Zendesk Brands (up to 300 on Enterprise) each have their own email addresses, Help Centers, and routing.

How we handle it

Zoho Desk uses a multi-department model where a single Help Center serves all departments with article scoping by department. Accounts using Zendesk's multi-brand feature for distinct product-line or subsidiary support will need to re-evaluate whether Zoho Desk's department-scoped article visibility meets their requirements. We document the existing Brand structure and the recommended department configuration in Zoho Desk during scoping, noting any routing logic that cannot be replicated in Zoho's model.

medium

### Zendesk account must remain active with sufficient API rate limits throughout migration

Zoho's Zwitch documentation requires the Zendesk account to remain active and have sufficient API rate limits during the entire migration process to prevent interruptions or data loss.

How we handle it

We coordinate migration windows to minimize Zendesk account activity, run delta migrations for records created or modified during the cutover period, and recommend that customers do not deactivate their Zendesk account until the Zoho Desk migration is validated and accepted. If the Zendesk account is deactivated mid-migration, inline images and any API-accessible data will become inaccessible, potentially causing incomplete transfer.

## How the migration runs

1. ### Discovery and data audit

   We audit the source Zendesk account across plan tier (Team/Growth/Professional/Enterprise), active ticket volume, user count, organization count, custom field definitions (types, required vs optional, conditional dependencies), Help Center article count and section hierarchy, active Triggers and Automations, SLA Policy definitions, and attachment volume.

   What this step covers

   We pair this with a Zoho Desk account readiness check: verifying the target plan tier, confirming department structure, and identifying any Zoho Creator requirements for custom object modeling. The discovery output is a written migration scope with object-level counts, a custom field mapping table, and a decision on which Zendesk automations will migrate as inventory versus requiring rebuild.

2. ### Pre-migration Zoho Desk configuration

   Before any data moves, we configure Zoho Desk to accept the incoming records.

   What this step covers

   This includes creating custom fields that do not auto-resolve from the migration data, pre-creating Teams (mapped from Zendesk Groups) so that ticket assignment resolution can resolve group memberships, configuring SLA Policies (mapped from Zendesk SLA definitions), and setting up the Help Center section hierarchy to match Zendesk's Category and Section structure. We also temporarily disable any Zoho Desk validation rules or required field conditions that could reject migrating records during the bulk import phase.

3. ### Agent and contact provisioning

   We extract every distinct Zendesk agent and end-user email address referenced on tickets, organizations, and user records.

   What this step covers

   Agent profiles are matched by email against Zoho Desk's agent list; any Zendesk Agents without a matching Zoho Desk agent profile are flagged in the reconciliation report for the customer's admin to provision before ticket import begins. End-users (requesters) migrate as Zoho Desk Contacts and do not require pre-provisioning. Light Agent records from Zendesk migrate as Zoho Desk Agents with no ticket assignment capability per Zoho's permission model.

4. ### Ticket migration with attachment handling

   We migrate Tickets in dependency order: Accounts (from Zendesk Organizations), Contacts (from Zendesk Users), then Tickets with their comment threads, attachments, tags, and custom field values.

   What this step covers

   Attachments are downloaded from Zendesk via the API in parallel with ticket records and re-uploaded to Zoho Desk preserving filename and MIME type. Inline images are flagged as non-transferable and documented for the customer's admin. Tags are written to Zoho Desk tag fields during ticket import. Comment authorship is attributed to the matching Zoho Desk agent; comments from agents not yet provisioned in Zoho Desk are attributed to the migration admin and flagged.

5. ### Knowledge Base article migration

   We use Zendesk's Help Center API to iterate over Categories, Sections, and Articles, downloading HTML content, translations, and section hierarchy.

   What this step covers

   Articles are created in Zoho Desk's Help Center under the matching section structure. Dynamic Content items (Zendesk Growth+ multilingual placeholders) are mapped to Zoho Desk locale fields on the equivalent article. Internal links between Zendesk articles are documented in a cross-link audit report for the customer's admin to update post-migration. We do not update internal links automatically because each platform assigns different article IDs.

6. ### Cutover, validation, and automation rebuild handoff

   We freeze Zendesk write access during cutover and run a final delta migration for any records modified during the migration window.

   What this step covers

   Validation includes record count reconciliation (tickets in, contacts in, accounts in, articles in), spot-checking 25-50 random records against the Zendesk source, and confirming that attachments and timestamps are intact. We deliver the Trigger and Automation inventory document, the macro-to-template mapping, the SLA rebuild guide, and the internal link audit to the customer's admin team. We do not rebuild Zendesk Triggers and Automations as Zoho Desk Workflow Rules and Business Rules inside the migration scope; that work is a separate engagement. We support a one-week hypercare window for reconciliation issues raised during the customer's first week of live Zoho Desk operation.

![](https://flitstack.ai/platforms/zendesk.svg) Zendesk ![](https://flitstack.ai/platforms/zoho-desk.svg) Zoho Desk

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Zoho Desk Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**2-4 weeks** Typical, smaller accounts

**5-8 weeks** Large or heavily customised accounts

A quote scales with ticket volume, custom field complexity, and the number of Help Center articles requiring section hierarchy reconstruction. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Zendesk to Zoho Desk →](https://flitstack.ai/contact)

## Why teams move from Zendesk to Zoho Desk

- Per-agent costs scale beyond what small and mid-market teams can sustain. Zendesk's Suite Team starts at $49/agent/month and scales to $169/agent/month on Enterprise, with AI features as separate add-ons that push effective cost 30-50 percent above the base rate. Zoho Desk's Professional tier at roughly $23/agent/month includes Zia AI, SLAs, Blueprint automation, and multi-department support, delivering a lower total cost of ownership for teams under 50 agents without sacrificing core ticketing functionality.
- Zendesk's data export restrictions on Team and Essential plans force smaller teams into API scripting or migration services just to retrieve their own data. Reviewers on Reddit's r/msp and r/CRM cite this as a lock-in mechanism that punishes teams mid-contract. Zoho Desk offers a free plan for up to three agents and no export restrictions at any tier, giving smaller teams portability and visibility into their own data without additional tooling.
- Zendesk's AI capabilities require additional configuration and behave inconsistently across channels, frustrating teams that expect plug-and-play automation. Zia AI in Zoho Desk provides sentiment analysis, automatic ticket tagging, response suggestions, and anomaly detection as built-in features on Professional and Enterprise tiers without a separate AI subscription. Multiple reviewers cite this as a concrete feature parity win for Zoho Desk.
- Setup complexity and feature gating frustrate smaller Zendesk teams. An MSP admin on Reddit with six years of Zendesk experience noted that features are being locked behind pay walls and agent minimums, pushing them toward alternatives that better fit smaller shop budgets and use cases. Zoho Desk's Express plan at $7/agent/month and its self-service onboarding appeal to teams that find Zendesk's configuration overhead disproportionate to their scale.
- Native Zoho CRM integration delivers a unified customer view without third-party sync tools or additional cost. For teams already inside the Zoho ecosystem or evaluating a move to it, Zoho Desk's bidirectional CRM sync means every support ticket surfaces the full customer record including deals, activities, and account history with no integration setup required. This is a structural advantage over Zendesk, which requires third-party integrations or professional services to achieve equivalent CRM visibility.

Questions, answered

## Zendesk to Zoho Desk migration questions

How long does a Zendesk to Zoho Desk migration take?

Migrations under 10,000 tickets, 5,000 contacts, and 500 Help Center articles typically complete in two to four weeks. Migrations with large attachment volumes (over 50,000 files), complex multi-custom-field ticket schemas, multiple Help Centers, or extensive Brands requiring Zoho Desk multi-department restructuring move to five to eight weeks. The timeline includes discovery and scoping (one week), Zoho Desk pre-configuration (one week), ticket and contact migration (one to three weeks), KB article migration (three to five days), and cutover validation (two to three days). Automations and SLA rebuild work happens post-migration and is not included in the timeline.

Do Zendesk Triggers, Automations, Macros, and SLA Policies migrate to Zoho Desk?

No. Zendesk Triggers and Automations do not migrate as executable code because they are structurally different from Zoho Desk's Business Rules, Workflow Rules, and Time-Based Rules. Macros do not migrate as templates but we do map their content to Zoho Desk Ticket Templates. SLA Policy definitions migrate as structured records, but SLA assignment rules require manual configuration in Zoho Desk's SLA UI. We deliver a written inventory of every active Zendesk Trigger, Automation, Macro, and SLA Policy with its conditions, actions, and a recommended Zoho Desk equivalent, so the customer's admin can rebuild them in Blueprint post-migration.

Will we lose our Help Center articles and knowledge base content?

No. Help Center articles migrate with their full HTML content, section hierarchy, and translations intact. Dynamic Content items (multilingual placeholders from Zendesk Growth+) map to Zoho Desk locale fields on the equivalent articles. Internal links between articles will not auto-update after migration — we deliver a cross-link audit report listing every Zendesk internal URL for the customer's admin to update manually in Zoho Desk. We recommend completing this link audit before deactivating the Zendesk account.

What happens to Zendesk tags and groups during migration?

Tags migrate via direct API read/write. We extract Zendesk tag assignments and write them to Zoho Desk ticket tag fields during the ticket import phase. Groups do not migrate automatically through Zoho's native tool, but we handle this by reading Zendesk Groups via the API and creating equivalent Zoho Desk Teams before ticket migration begins, so that ticket assignment can resolve the group membership at import time. Zoho's Zwitch documentation explicitly lists Groups as non-migratable; our API-based approach fills this gap.

Can we keep Zendesk running alongside Zoho Desk during migration?

Yes. We recommend keeping Zendesk active throughout the migration window and running a delta migration for any records created or modified during the cutover period before switching Zoho Desk to production. The Zendesk account must remain active with sufficient API rate limits during migration to prevent data loss — this is a Zoho Zwitch requirement for all Zendesk-to-Zoho migrations. We do not recommend deactivating Zendesk until Zoho Desk validation is complete and the customer's admin has confirmed the migrated data is accurate.

Do attachments and inline images migrate completely?

File attachments on tickets and Help Center articles download from Zendesk via the API and re-upload to Zoho Desk preserving original filenames and MIME types. Inline images embedded in ticket comments are the exception: Zoho's migration tooling does not support inline image transfer, and these images remain accessible only while the Zendesk account is active. We flag this limitation during scoping and recommend downloading any critical inline images before migration begins. Once the Zendesk account is deactivated, inline images become inaccessible.

Does Zoho Desk integrate with our existing CRM if it is not Zoho CRM?

Zoho Desk's native bidirectional CRM sync is designed for Zoho CRM specifically. For teams using Salesforce, HubSpot, Microsoft Dynamics, or another CRM, Zoho Desk offers integration through Zapier, Make (Integromat), or its REST API. We do not configure cross-platform CRM integrations as part of the standard migration scope, but we can scope a Zoho Desk-to-Salesforce or Zoho Desk-to-HubSpot integration as a separate engagement if the customer's team uses a non-Zoho CRM. Zoho Desk's embedded analytics and Zoho Analytics integration are available regardless of which CRM is in use.

## Related migrations

[![](https://flitstack.ai/platforms-trim/zoho-desk.webp) Migrate to **Zoho Desk** Every source we move into Zoho Desk, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/helpdesk/zoho-desk) [**Zoho Desk to Zendesk** The same pair in reverse](https://flitstack.ai/migrations/helpdesk/zoho-desk/to/zendesk) [**Zendesk to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zendesk/to/freshdesk) [**Zendesk to HubSpot Service Hub** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zendesk/to/hubspot-service-hub) [**Zendesk to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zendesk/to/intercom)

## Sources: official documentation

1. [Managing Fields — Zoho Desk Online Help](https://help.zoho.com/portal/en/kb/desk/customization/layouts-and-fields/articles/understanding-fields-and-properties)
2. [Types of Custom Fields — Zoho Online Help](https://help.zoho.com/portal/en/kb/crm/customize-crm-account/customizing-fields/articles/types-of-fields)
3. [Migrate Data From Other Help Desk Servers to Zoho Desk (Zwitch) — Zoho Desk](https://help.zoho.com/portal/en/kb/desk/data-administration/data-migration/articles/migrate-data-from-other-help-desk-zwitch)
4. [Importing Data in Zoho Desk — Online Help](https://help.zoho.com/portal/en/kb/desk/data-administration/import-export/articles/importing-data-in-desk)
5. [About ticket import — Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408886248218-About-ticket-import)
6. [How can I bulk update users — Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408888554394-How-can-I-bulk-update-users)
7. [About custom objects — Zendesk help](https://support.zendesk.com/hc/en-us/articles/6034114094618-About-custom-objects)

Get a quote

## Moving from Zendesk to Zoho Desk?

Tell us roughly how many records and objects you have. We scope the mapping and the Zoho Desk setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
