Zendesk to Zoho Desk migration: what Zwitch moves, what it skips, and a cutover plan
Short answer
Zwitch, Zoho Desk's built-in migration service, moves the records of a Zendesk account well: tickets with comments, threads and attachments, agents, end users (as contacts), organizations (as accounts), most custom fields, and knowledge base sections, categories and translations. According to Zoho's own help pages it does not move ticket tags, groups, teams or collaborators, nested custom fields, agent custom fields, or inline images in tickets, and all data lands in a single Zoho Desk department. Nothing in Zoho's documented module list covers Zendesk triggers, automations, macros, SLA policies or views, so plan to rebuild your workflow layer by hand. The cutover itself runs in two phases: a bulk Phase 1 migration, then a Phase 2 delta about two weeks later that picks up new tickets and failed records. Keep Zendesk active, with API access and the migrating admin's credentials unchanged, until Zoho confirms it is safe to close it. Run a sample migration first, invite and confirm every agent in Zoho Desk with the same email address before you start, and budget time to check the error log, because Zoho says 3% to 5% of data can fail and must be followed up within two weeks.
Contents
- Why teams move from Zendesk to Zoho Desk
- What Zwitch moves from Zendesk
- What Zwitch skips or changes
- How the Zwitch process works
- A cutover plan that works
- Rebuilding the workflow layer: Zendesk concepts mapped to Zoho Desk
- Reconciliation: proving nothing was lost
- Who should, and who should not, move to Zoho Desk
- Frequently asked questions
Why teams move from Zendesk to Zoho Desk
The teams we see making this move are usually customer support teams, not internal IT, and the reasons are consistent: cost per agent, the pull of the wider Zoho suite (CRM, Books, Analytics) when the company already runs on Zoho, and a preference for one vendor relationship. Zoho Desk also publishes regional pricing; on Nov 1, 2026 its Zoho Desk pricing page, viewed from India, listed Standard at ₹800, Professional at ₹1,400 and Enterprise at ₹2,400 per user per month billed annually, plus a free edition for three users. Zoho localises the page by region, so check it from your own location. For comparison, Zendesk's Zendesk pricing page listed Support Team at $19, Suite Team at $55 and Suite Professional at $115 per agent per month billed annually, with Suite Enterprise through sales.
If you are moving an internal IT desk off Zendesk, Zoho Desk is a customer service tool too, so you would be swapping one customer support product for another. Read our Zendesk vs Freshservice for internal IT before committing; an ITSM tool may be the better destination.
Whatever the reason, be clear about what you are buying with the move. A Zendesk to Zoho Desk migration is two projects running in parallel: a data migration that Zoho largely runs for you, and a configuration rebuild that nobody runs for you. Teams that treat it as only the first project tend to go live with the right history and the wrong behaviour: tickets routed to the wrong team, SLAs that never fire, and agents re-creating macros from memory. For a mid-sized account we plan for four to six weeks of elapsed time when both projects are staffed, much of it set by the Zwitch queue and the two-week gap before Phase 2.
This guide relies only on Zoho's own help documentation for what Zwitch does and does not do: the Zwitch: Export from Zendesk article, the general Migrate Data from Other Help Desk Services (Zwitch) article, and the Zwitch FAQ. All were checked on Nov 1, 2026. Where those pages are silent, we say so and give our practitioner view separately.
What Zwitch moves from Zendesk
Zoho's Zendesk article says the tool extracts data from three Zendesk export modules (tickets, users and organizations) and uses Zendesk's API to bring across custom fields and parts of the knowledge base.
| Zendesk data | Lands in Zoho Desk as | Notes from Zoho's help pages |
|---|---|---|
| Tickets | Tickets, ticket comments, threads, attachments | Can be filtered by Zendesk group and brand; Zendesk ticket ID stored in a Zendesk-ID custom field |
| Users (agents) | Agents | Email addresses must match; agents listed under an Imported tab; department permissions set manually |
| Users (end users) | Contacts | A contact must exist for its tickets to import |
| Organizations | Accounts | Migrated contacts and accounts get an Is Migrated checkbox |
| Custom fields | Matching custom fields, created automatically if missing | All except nested custom fields; added to the Unused Fields section of the default department |
| Knowledge base | KB root categories, sections and article translations | Migrated articles carry the tag ZohoDesk Migrated |
| Ticket status, classification, category | Same values in Zoho Desk | Only these system fields are migrated; previously closed tickets get a Mig Closed status |
Zoho's FAQ also says records keep their original created and modified dates and the user who created them, which matters for reporting continuity.
What Zwitch skips or changes
This is the list that should drive your project plan. Every item below is stated in Zoho's own help pages.
| Gap | What Zoho's help pages say | What to do about it |
|---|---|---|
| Tags | Tags cannot be migrated | Export tags you report on and map them to a custom field before migration, or accept the loss |
| Groups and teams | Groups and teams cannot be migrated | Design Zoho Desk departments and teams first; reassign by rules after import |
| Collaborators (CCs) | Collaborators cannot be migrated | Accept for history; communicate the change to agents |
| Inline images in tickets and comments | Not migrated; visible only while the Zendesk account stays active | Decide whether any ticket history depends on inline images; if yes, archive those tickets separately before closing Zendesk |
| Nested custom fields | Not migrated | Flatten them into separate fields in Zendesk, or rebuild as dependent fields in Zoho Desk |
| Agent custom fields | Not supported for agent migration | Recreate manually |
| Missing agents | Tickets assigned to, and comments by, agents not in Zoho Desk are attributed to the admin who ran the migration | Invite and confirm every agent, including former staff whose history matters, before Phase 1 |
| Thread direction | All thread replies from Zendesk tickets are marked as Incoming | Train agents and adjust reports that rely on direction |
| Threads with no from/to address | Assigned to the organization admin and mapped to the Help Center channel | Expect some channel reporting noise on history |
| Departments | All data moves to one department; tickets cannot go to a custom department | Migrate into one department, then move tickets with rules or bulk actions |
| Light agents | Light agents will not be assigned any tickets | Map who needs full agent seats in Zoho Desk |
| Custom field labels | Labels limited to 50 characters and a set of allowed characters; others replaced by underscores | Clean labels in Zendesk first |
What Zoho's pages do not mention
Zoho's documented module list covers tickets, users, organizations, custom fields and knowledge base content. It does not list Zendesk triggers, automations, macros, SLA policies, views, ticket forms, business hours, satisfaction surveys, Help Center themes, or apps and integrations. We read that as: these are not migrated, and in every Zendesk migration we have scoped, they are rebuilt by hand. Treat them as a configuration workstream, not a data workstream.
Edition limits can block your custom fields
Zoho's FAQ says the total number of custom fields depends on edition: up to 230 in Enterprise, 150 in Professional and 50 in Standard, and none in the Free edition. If your Zendesk account has more custom fields than your target edition allows, prune before migration or buy the right edition.
How the Zwitch process works
Zwitch is not a self-service ETL tool you run on your own; you submit a request and Zoho's migration team performs it. From Zoho's documentation:
- Who can start it: the primary contact or a user with Support administrator permission.
- What you submit: the three Zendesk export ZIP files (organizations, users, tickets), plus your Zendesk service URL, an admin email and an API token. You upload in Setup, Data Administration, Zwitch.
- Editions: migration is supported on all paid editions; a trial account can migrate up to 2 GB.
- Size: uploads up to 10 GB, with larger volumes handled through Zoho support.
- Timing: requests are queue-based; Zoho gives an estimate after analysing your data.
- Cancellation: only while the request status is Submitted in Queue.
- Failure rate: Zoho states that 3% to 5% of data can fail due to data limitations or schema mismatches, with failed records returned as CSV.
- Retention: Zoho says migrated records are permanently removed 30 days after import completes, for data security.
Phase 1 and Phase 2
Zoho recommends a sample migration with a small slice of data first. Phase 1 moves all data in bulk; Zoho emails a report and per-module error logs, and you must respond to the error log within two weeks. Phase 2 begins about two weeks after Phase 1 and moves anything created in Zendesk since, plus re-migration of the failed records. Zoho says requests made after Phase 2 will not be accepted, so Phase 2 is your last chance.
Zoho's FAQ is explicit that you should not close Zendesk after exporting: the backup files lack some data (inline images, attachments, some custom field values) that the engine fetches through the API, and Zoho will tell you when it is safe to close. You can reduce Zendesk seats during the project, except for the admin whose credentials Zwitch is using.
A cutover plan that works
The Zwitch phases define the data timeline. Wrap them in a project plan that also covers configuration, people and channels. This is the plan we use; adjust the durations to your volume.
Weeks 1 to 2: prepare
Inventory Zendesk: ticket volume, brands, groups, custom fields (and which are nested), tags used in reporting, triggers, automations, macros, SLA policies, views, Help Center structure, integrations. Decide what history you need live. Choose your Zoho Desk edition based on field limits and features. Design departments, teams, roles and layouts.
Weeks 2 to 4: build and sample
Invite and confirm all agents in Zoho Desk with the same emails as Zendesk. Create the Mig Closed status. Rebuild workflows, assignment rules, SLAs and macros (as reply templates) in Zoho Desk. Run a Zwitch sample migration and check tickets, threads, attachments, custom fields and KB articles against Zendesk.
Week 4 to 5: Phase 1
Submit the full Zwitch request. While it runs, prepare channels: support email forwarding, web forms, chat, social and phone. When Phase 1 completes, review the error log with the team and respond inside the two-week window.
Cutover day
Switch email forwarding and web forms to Zoho Desk, publish the new Help Center, and update links in your product and website. Freeze new work in Zendesk; agents finish in-flight conversations in Zoho Desk. Keep Zendesk running and API access intact.
About two weeks later: Phase 2 and close-out
Zoho runs Phase 2 to pick up the delta and failed records. Reconcile counts by status and month. Archive anything that depends on inline images. Only close Zendesk after Zoho confirms it is safe, and after your own reconciliation.
Cutover readiness checklist
- Every agent, including leavers whose history matters, exists in Zoho Desk with a matching email
- Nested custom fields flattened; labels cleaned to Zoho's allowed characters
- Tags you report on mapped to a custom field
- Departments and routing rules ready to redistribute tickets from the single migration department
- Triggers, automations, macros and SLAs rebuilt and tested
- Email, forms and widgets switched and tested end to end
- Error log owner named and two-week response deadline in the calendar
- Zendesk admin credentials and API token unchanged until Zoho confirms close-out
Rebuilding the workflow layer: Zendesk concepts mapped to Zoho Desk
Because the configuration layer does not migrate, the real design work is deciding how each Zendesk concept should look in Zoho Desk. The mapping below is our practitioner mapping; the edition notes come from Zoho's pricing page, checked on Nov 1, 2026.
| Zendesk concept | Closest Zoho Desk equivalent | Edition note (Zoho pricing page) |
|---|---|---|
| Groups | Departments and teams | Multi-department is listed from Professional |
| Triggers and automations | Workflows, escalation rules and assignment rules | Workflows and multi-level escalations from Express; round-robin from Professional; skill-based assignment in Enterprise |
| Multi-step processes in triggers and apps | Blueprints | Listed from Professional |
| Brands with separate help centers | Multi-brand help center | Listed in Enterprise |
| Help Center | Knowledge base and community | Knowledge base and community forum listed from Standard; multilingual help center from Professional |
| Custom objects | Custom modules | Listed in Enterprise |
| Sandbox | Sandbox | Listed in Enterprise |
| Light agents | Light users | Available on Professional and Enterprise; Enterprise includes 50 free light users |
Two design choices save the most rework. First, decide the department structure before Phase 1, because all migrated tickets arrive in one department and you will redistribute them with rules. Second, rebuild automation from the process, not from the trigger list. Most mature Zendesk accounts carry triggers nobody can explain; the migration is the cheapest moment to drop them.
Common mistakes we see
- Starting Zwitch before agents have accepted their Zoho Desk invitations, so history is attributed to the migration admin.
- Missing the two-week window to respond to the Phase 1 error log, so failed records are never retried.
- Downgrading the Zendesk plan or rotating the admin's API token mid-project, which breaks the API calls Zwitch depends on.
- Cancelling Zendesk the day after cutover, losing inline images that only render while the account is active.
- Choosing Zoho Desk Standard and then discovering the account has more custom fields than Standard allows.
Reconciliation: proving nothing was lost
A migration report saying completed is not proof. Reconcile it yourself before you close Zendesk.
| Check | How |
|---|---|
| Ticket counts | Compare counts by status and created month between Zendesk and Zoho Desk (use the Old Ticket ID / Zendesk-ID field) |
| Attachments | Open a sample of tickets with attachments from different years |
| Assignment | Count tickets attributed to the migration admin; a large number means agents were missing |
| Custom fields | Check that fields moved from Unused Fields into layouts and show values |
| Knowledge base | Compare article counts per category and spot-check translations |
| Contacts and accounts | Compare counts; check that tickets are linked to the right account |
Record what failed, what you re-ran in Phase 2, and what you consciously accepted as lost (for example tags or inline images on old tickets). That record is what you show auditors and leadership later.
Who should, and who should not, move to Zoho Desk
Good fit
Customer support teams already invested in the Zoho ecosystem; teams that want lower per-agent cost and can live with rebuilding their workflow layer; organisations comfortable with a vendor-run migration that follows Zoho's two-phase process.
Wrong choice when
You depend heavily on Zendesk apps, Sunshine custom objects or complex trigger chains you cannot easily rebuild; you need tags and collaborators preserved on history; or the team being migrated is internal IT that really needs an ITSM tool.
If you are still weighing destinations, compare Zoho Desk with an open-source option in our Frappe Helpdesk vs Zendesk vs Freshdesk guide, or, for internal IT, our Zendesk to Freshservice migration guide.
Frequently asked questions
Does Zoho Desk charge for migrating from Zendesk?
Zoho's pricing page promotes switching from other help desks for free with expert guidance through the data migration. Migration through Zwitch is supported on all paid editions; trial accounts are limited to 2 GB. Rebuilding workflows, testing and reconciliation are your own effort or a partner's.
Does Zwitch migrate Zendesk tags?
No. Zoho's Zendesk migration article says tags, groups, teams and collaborators cannot be migrated. If you rely on tags for reporting, copy them into a custom field in Zendesk before you export.
Are Zendesk macros and triggers migrated to Zoho Desk?
Zoho's help pages do not list macros, triggers, automations, SLA policies or views among the modules Zwitch migrates. Plan to rebuild them in Zoho Desk.
How long does a Zendesk to Zoho Desk migration take?
Zoho says timing depends on data volume and its migration queue, and gives an estimate after analysing your data. Phase 2 starts about two weeks after Phase 1, so allow at least a month end to end for the data alone, plus preparation time.
When can I close my Zendesk account?
Only after Zoho confirms it is safe. Zoho's FAQ says the export files lack some data the migration fetches through Zendesk's API, and inline images in tickets stay visible only while Zendesk remains active.
Can I migrate tickets into different Zoho Desk departments?
Not directly. Zoho's FAQ says the migration engine moves all data into one department. Move tickets to other departments after import with rules or bulk updates.