Zoho Desk to Zendesk requires API-based extraction (CSV omits threads). Plan 2–4 weeks, handle attachments via download links, and use Zendesk's Ticket Import API to preserve timestamps without triggering automations.
There is no native migration path from Zoho Desk to Zendesk; all data must be extracted via API, data backup, or CSV export and transformed before import. The core complexity stems from fundamental architectural differences: Zoho Desk uses typed thread objects (Reply, Forward, Comment) under a department-centric model, while Zendesk flattens all conversation history into Comments with a public boolean on a ticket-centric architecture. Custom development is required to flatten contact-account hierarchies, deduplicate users across departments, handle attachment re-uploading via Zendesk's Uploads API, and rebuild automation logic (Blueprints, Workflows, SLAs) manually since no migration path exists for business rules.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
TL;DR — Zoho Desk to Zendesk Migration
A Zoho Desk to Zendesk migration is moderately complex due to structural differences in how each platform handles ticket threading, contact hierarchies, and API throttling. Realistic timeline: 2–4 weeks for most teams, potentially longer for enterprise volumes above 500K tickets. The single biggest risk is losing ticket thread history and inline images — Zoho Desk's CSV export does not include threads or comments, and its Data Backup provides only secure download links for attachments that must be fetched via API before import. Zoho Desk objects with no clean Zendesk equivalent include Products, Blueprints, and Activities (Tasks, Calls, Events). In-house is viable if you have a developer who can commit 2–4 weeks and you have fewer than 50K tickets. For anything larger, or when preserving full conversation fidelity matters, a managed migration service eliminates the re-migration risk that catches most DIY teams.
Zoho Desk does not document a Retry-After header
When you hit a 429, implement exponential backoff starting at 2 seconds, doubling up to a 64-second cap. Access tokens expire every 60 minutes — build automatic refresh using your refresh token into long-running extraction jobs or they will fail silently with 401 errors that look like data issues.
Imported Zendesk tickets do not carry reliable native SLA and metric history
Zendesk explicitly states that metrics and SLAs are not supported for imported tickets. Tag imported records (e.g., migrated_from_zoho) and exclude them from live SLA dashboards using view and reporting filters. (developer.zendesk.com)
Avoid naive page=501+ ticket list walks during validation
Zendesk rate-limits list-tickets requests beyond page 500 to 50 requests per minute. Use the Incremental Exports API (GET /api/v2/incremental/tickets) or cursor-based pagination (page [after] parameter) for large-scale validation. (developer.zendesk.com)
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of Zoho Desk
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm Zendesk can hold your support model
Walk your current workflow through Zendesk: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated Zoho Desk → Zendesk timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
Zoho Desk → Zendesk specifics
- Zendesk's app ecosystem
- Zendesk Marketplace offers 1,500+ integrations compared to Zoho Desk's smaller marketplace. Teams running Salesforce, Jira, or Slack as core tools find Zendesk's native connectors reduce integration maintenance.
- AI and automation maturity
- Zendesk's AI agents, Answer Bot, and intelligent triage require articles in Zendesk Guide — a standalone knowledge base in Zoho Desk can't power those features.
- Reporting consolidation
- Organizations already using Zendesk for other brands or business units need a single reporting layer. Running Zoho Desk alongside Zendesk creates data silos that make cross-brand SLA reporting impossible.
- Multi-brand support
- Zendesk natively supports multiple brands under one account. Zoho Desk's department model doesn't map cleanly to brand-level separation.
- < 10K tickets, standard fields, no attachments?
- A third-party tool probably works. Verify it preserves thread direction and agent attribution before committing.
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full Zoho Desk export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the Zoho Desk export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in Zoho Desk where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
Zoho Desk → Zendesk specifics
- Accounts
- → GET /api/v1/accounts?from=1&limit=100 (paginate)
- Contacts
- → GET /api/v1/contacts?from=1&limit=100 (paginate)
- Attachments per ticket
- → GET /api/v1/tickets/{id}/attachments → download each file via the attachment URL
- KB Articles
- → GET /api/v1/articles (if migrating knowledge base)
- User cleanup
- Imported end-users can be deleted via DELETE /api/v2/users/{id} only if they have no tickets. If tickets were created, delete tickets first.
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass Zoho Desk → Zendesk field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the Zoho Desk → Zendesk field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where Zendesk has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
Zoho Desk → Zendesk specifics
- 10K–100K tickets, some custom fields?
- Custom scripts if you have engineering bandwidth. Budget 3–4 weeks including testing.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a Zendesk sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Zendesk sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under Zendesk's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
Zoho Desk → Zendesk specifics
- Sandbox restore
- If you have a Zendesk sandbox, the faster path is to wipe the production import and re-run from staging. Zendesk does not offer a native "restore to pre-migration state" — there is no snapshot/rollback feature.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in Zendesk, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while Zoho Desk stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from Zendesk's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze Zoho Desk and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep Zoho Desk read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
-
Configure webhooks
in Zoho Desk under Settings → Automation → Webhooks for these events:
Zoho Desk → Zendesk specifics
- Point webhooks
- to a lightweight endpoint (e.g., AWS Lambda, Cloud Function) that writes events to a queue (SQS, Pub/Sub, or a database table).
- Final cutover
- When the queue is empty and no new events arrive for 15+ minutes, switch channels (email routing, chat widget, phone) to Zendesk. Re-enable the live automation set. Keep Zoho Desk in read-only mode until support leadership signs off.
- Big-bang
- Migrate everything over a weekend. Works for < 50K tickets. Risk: if validation fails, rollback is manual (see rollback procedure below).
- Incremental with delta sync
- Run the initial migration, keep both systems live, then do a final delta sync of tickets created/updated since the initial run. Best for zero-downtime requirements.
- Zendesk bulk delete
- Use DELETE /api/v2/tickets/destroy_many?ids={ids} (up to 100 IDs per request) to remove imported tickets. This is rate-limited — budget significant time for large volumes.
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile Zoho Desk and Zendesk record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in Zendesk, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep Zoho Desk read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
Zoho Desk → Zendesk specifics
- Reconciliation
- After the initial load completes, process the queued webhook events. For each event:
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
Zoho Desk Zendesk
| Zoho Desk field | Zendesk field | Notes |
|---|---|---|
| Ticket | Ticket | Status values differ; Zoho's custom statuses need mapping to Zendesk custom ticket statuses. Zendesk requires subject and requester_id on every ticket. |
| Thread (Reply/Forward/Comment) | Comment | Zoho thread types collapse to public: true/false; forward metadata is lost. Empty thread bodies must receive placeholder text — Zendesk's Import API rejects empty comment bodies. |
| Contact | User (end-user) | Zendesk identifies users by email globally. Duplicate emails across Zoho departments must be deduplicated pre-import. |
| Account | Organization | 1:1 mapping, but Zoho's multi-department account associations don't carry over. Zoho's parent-child Account hierarchies are flat in Zendesk unless you use Enterprise features. |
| Agent | User (agent role) | Agents must exist in Zendesk before ticket import to preserve author attribution. Former agents should be created as suspended users. |
| Department | Group, Brand, or both | Zoho departments are broader (channel routing, layouts); Zendesk groups are agent containers. See the multi-brand mapping section below for deciding whether a department becomes a Group, a Brand, or both. |
| Team | Group, tag, or custom field | No clean 1:1 default. |
| Product | Custom ticket field or tag | Zendesk Support has no native Product object. |
| KB Article | Article (Help Center) | Zoho's Category→Section→Article maps to Zendesk's Category→Section→Article, but folder structures rarely align. See the KB migration section below. |
| Task / Call / Event | — | No native equivalent. Store as internal notes on related tickets or export to a CRM. |
| Time Entry | Time tracking (marketplace app) | Requires Zendesk Time Tracking app; values must be re-entered or imported via API. |
| Attachment | Attachment | Must upload to Zendesk via Uploads API first, then reference by token in the ticket import payload. |
| Tag | Tag | Direct mapping. Zendesk tags are lowercase with no spaces; normalize Zoho tags before import. |
| Custom Field | Custom Field | Types may differ (Zoho picklist → Zendesk dropdown). IDs are platform-specific. |
| Blueprint | — | No equivalent. Rebuild as Zendesk ticket statuses + triggers. |
| Workflow Rule / Automation | Trigger / Automation | Must be manually rebuilt. No migration path for logic. |
| SLA | SLA Policy | Must be manually rebuilt in Zendesk Admin Center. |
| Satisfaction Rating | — (partial) | Zoho Desk happiness ratings don't map to Zendesk CSAT. Historical ratings can be stored as tags or custom fields but won't populate Zendesk's satisfaction reporting. |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets | medium | Ticket metadata maps reasonably well, but Zendesk requires subject and requester_id on every ticket—Zoho tickets created via chat or phone may lack subjects—and all ticket IDs are reassigned on import, requiring external_id preservation. |
| Ticket Threads / Comments | high | Zoho Desk's CSV export excludes threads entirely, the API is required for full conversation history, and thread type metadata (reply vs. forward) is lost when collapsing into Zendesk's flat Comment model with empty bodies rejected by the Import API. |
| Contacts | medium | Zendesk identifies users globally by email, so duplicate emails across Zoho departments must be deduplicated pre-import, and the Account→Contact parent-child relationship is flattened. |
| Organizations (Accounts) | low | Zoho Accounts map 1:1 to Zendesk Organizations, though multi-department account associations and parent-child account hierarchies are not preserved unless using Zendesk Enterprise features. |
| Agents | medium | Agents must exist in Zendesk before ticket import to preserve author attribution, and former agents should be created as suspended users to maintain historical conversation accuracy. |
| Attachments | high | Attachments from Zoho's Data Backup are provided as expiring secure download links that must be individually fetched and re-uploaded to Zendesk's Uploads API before import, creating a complex multi-step pipeline with time-sensitive dependencies. |
| Custom Fields | medium | Field type mismatches (picklist to dropdown, multi-select semicolons to arrays), value normalization requirements (case, spaces, special characters), and Zendesk's 2,000-option cap on dropdowns all require careful pre-processing. |
| Knowledge Base Articles | medium | Zoho's Category→Section→Article structure maps conceptually to Zendesk Guide's hierarchy, but folder structures rarely align cleanly and inline media references must be re-hosted. |
| Tags | low | Tags map directly between platforms, but Zendesk enforces lowercase with no spaces, requiring normalization of Zoho tag values before import. |
| Workflows / Automations / Blueprints | high | No migration path exists for business logic; all Zoho Desk Workflow Rules, Blueprints, and SLA policies must be manually rebuilt as Zendesk Triggers, Automations, and SLA Policies from scratch. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Thread Model Structural Mismatch
Zoho Desk's typed threads (Reply, Forward, Comment) must be collapsed into Zendesk's single Comment object with a public boolean, losing forward-vs-reply directional metadata unless explicitly preserved in comment body text or tags.
Contact Hierarchy Flattening
Zoho Desk's parent-child Account→Contact→Ticket chain across departments must be flattened into Zendesk's single User object optionally linked to Organizations, requiring deduplication of contacts that share emails across departments.
Attachment Extraction Complexity
Zoho Desk's Data Backup provides only secure download links for attachments that expire after 7 days, requiring each file to be individually fetched via API and then re-uploaded to Zendesk's Uploads API before being referenced by token in the ticket import payload.
Incompatible API Throttling Models
Zoho Desk uses a daily credit-based system with concurrency limits while Zendesk uses per-minute rate limits tied to plan tier, requiring completely different retry logic and batching strategies for extraction and import pipelines.
Department-to-Brand/Group Mapping
Zoho Desk departments serve combined purposes of channel routing, agent assignment, and layout customization, which must be decomposed into separate Zendesk concepts of Brands, Groups, and Triggers based on whether each department is customer-facing or an internal routing concept.
No-Equivalent Object Gaps
Zoho Desk objects including Products, Blueprints, Activities (Tasks, Calls, Events), and satisfaction ratings have no native Zendesk equivalents and must be either discarded, stored as tags/custom fields, or rebuilt using marketplace apps and trigger-based workarounds.
What breaks
Known failure modes. Have a recovery plan for each before you cut over.
Picklist / Enum values
Zoho Desk allows spaces, special characters, and mixed case in picklist values. Zendesk dropdown custom fields require exact string matches. A Zoho value of "In Progress" won't match a Zendesk tag of in_progress. Pre-normalize values before import.
Multi-select fields
Zoho Desk supports multi-select picklists using semicolon-delimited values. Zendesk multi-select custom fields expect an array in the API. Format conversion is required.
Date/Time formats
Zoho Desk exports dates in GMT. Zendesk's Ticket Import API accepts ISO 8601. No conversion is typically needed, but validate timezone consistency in your transform layer. (help.zoho.com)
Required fields
Zendesk requires subject and requester_id on every ticket. Zoho Desk tickets created via chat or phone may lack a subject — insert a placeholder value.
Legacy IDs
Zendesk assigns new ticket IDs during import. Store the original Zoho ticket ID in external_id and, if agents search by old ticket number, in a visible custom ticket field. (developer.zendesk.com)
Large dropdowns
Zendesk caps a custom ticket field at 2,000 options. If a Zoho picklist is really a lookup table, redesign it as a lookup relationship field or a separate organization/user field before cutover. (developer.zendesk.com)
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate Zoho Desk to Zendesk without losing data?
Yes, but only if you use the Zoho Desk API for extraction — not the CSV export, which omits threads and comments. API-based migration preserves full conversation history, attachments (when downloaded and re-uploaded), tags, and custom fields. The data most at risk is inline images embedded in HTML thread bodies, which reference Zoho-hosted URLs that break when you decommission the Zoho account.
How long does a Zoho Desk to Zendesk migration take?
Typical end-to-end timelines are 2–4 weeks including discovery, development, test migration, production migration, and validation. The actual data transfer for 100K tickets takes 1–2 days on a Zendesk Professional plan. Elapsed time is dominated by field mapping decisions, UAT, and stakeholder review.
What data cannot be migrated from Zoho Desk to Zendesk?
Zoho Desk Blueprints, Products, Activities (Tasks/Calls/Events), Forum topics, satisfaction ratings, and workflow rules have no native Zendesk equivalent. These must be rebuilt manually or stored as custom fields and tags. Zendesk also does not calculate SLA metrics for imported tickets, so historical SLA data is not portable.
Will Zendesk automations trigger on imported tickets?
No, if you use the Ticket Import API endpoint (/api/v2/imports/tickets). This endpoint bypasses triggers and automations by design. If you accidentally use the standard Tickets API (/api/v2/tickets) instead, every trigger will fire — potentially sending thousands of emails to customers.
Does Zoho Desk have a native migration tool for Zendesk?
No. Zoho offers Zwitch for importing into Zoho Desk from other platforms, but there is no native Zoho tool for exporting to Zendesk. Extraction must be done via CSV export, Data Backup, or the Zoho Desk REST API.