EU, US and India data residency · a DPA you can sign

Trust Center →

Zoho Desk to FlowTux: the export, the field map, the cutover

Zoho Desk has two export features and they do different jobs. The module export gives you ticket rows. Threads, comments and attachments come from Data Backup or the API.

Getting your data out of Zoho Desk

Each line below was checked against Zoho Desk’s own documentation on 2026-11-16. Vendors change these pages; follow the source link before you rely on a number.

Module export
Select a department, then Setup > Data Administration > Export > New Export. CSV, one module at a time, and needs the Export Records permission. Source: help.zoho.com
Record limit
Zoho’s export article says up to 50,000 records per export; its Data Administration FAQ says a maximum of 3,000. Plan for the lower number until you see otherwise. Source: help.zoho.com
Threads
The FAQ: to export email threads in tickets, raise a data backup request with Zoho Desk support. Source: help.zoho.com
Data Backup
Setup > Data Administration > Data Backup, primary contact only. Includes tickets with threads, comments and attachments, plus KB articles, as a ZIP of CSVs. 30 days between full backups; kept for 7 days. Source: help.zoho.com
API
GET /api/v1/tickets (up to 100 per page), /tickets/{id}/threads and /tickets/{id}/comments. Comments carry isPublic. Source: desk.zoho.com
API credits
Daily credits per org: Standard 50,000 + 250 per agent, Professional 75,000 + 500, Enterprise 100,000 + 1,000. Concurrency 10 to 25 by edition. Source: help.zoho.com
Credit cost
A list call costs 3 credits for the first 2,000 records, rising to 10 credits past 10,000 and 100 past 100,000. Fetching one record by id costs 1. Source: desk.zoho.com
Knowledge base
GET /api/v1/articles lists articles; the body is in the answer field of GET /api/v1/articles/{id}. Source: desk.zoho.com

Not verified

We could not confirm these from Zoho Desk’s documentation. Check them in your own account.

  • Which export record limit is current (50,000 or 3,000).
  • Whether Data Backup is still in beta and support-gated in 2026.
  • Whether the CSV export includes the ticket number.

Field mapping

What each Zoho Desk field becomes in FlowTux. We confirm every row with you before loading.

Zoho DeskFlowTuxNotes
ticketNumberOriginal ticket number, kept on the imported ticket
subject, descriptionTicket title and first message
status, statusTypeStatus: Open, In Progress, Resolved, ClosedMap your status list on the call.
priorityPriority: Critical, High, Medium, Low
category, subCategory, classificationCategory, the starting taxonomy Tux AI triages against
departmentId, teamIdRouting inputExports are per department; repeat for each one that moves.
contactIdRequester, matched by email address
assigneeIdOwner: an Admin or Agent member
thread (direction in / out)Comment on the ticket thread
comment (isPublic: false)Internal note, never shown to the requester
cf (custom fields)Ticket body, or archiveFlowTux has no documented custom-field object. Values you need are written into the ticket during import; the rest stay in the archive. Agreed field by field on the scoping call.
KB articleKnowledge base article in the Support Portal (write it, import a page by URL, or upload a file)

What carries over

  • Tickets in the window you choose, with threads and private comments kept apart
  • Status, priority and category, mapped as in the table
  • Contacts and agents, matched by email
  • KB articles you choose to reload

What does not

  • Blueprints, workflows and assignment rules
  • SLA definitions and happiness ratings
  • Community forum content, which Zoho excludes from Data Backup
  • Attachments on closed tickets, unless you decide otherwise on the scoping call

The Zoho Desk plan, step by step

  1. Ask for Data Backup earlyOnly the primary contact can run it, it may need a request to Zoho support, and full backups are 30 days apart. Start this on day one.
  2. Or budget API creditsThread pulls cost 3 credits per ticket. A Standard org with 10 agents has 52,500 credits a day: roughly 17,000 tickets’ threads a day before buying more.
  3. Download within 7 daysBackups are removed from Backup History after 7 days, and attachments arrive as secure links you fetch through the API.
  4. Send the export; we map itPer department. We map statuses, priorities and categories with you, then check counts per status and per month.
  5. Repoint intake and run bothForward the department mailbox to FlowTux, connect Slack, and run both for two weeks while open Zoho tickets drain.

Run both. Decide with data.

The risk in switching helpdesks is not the import. It is committing before you know whether the AI actually closes your tickets. So keep Zoho Desk running, send new tickets to FlowTux, and compare the two queues on live traffic for two weeks. If the numbers do not justify the move, you have lost two weeks and no data.

How long it takes

The calendar risk is Data Backup: one full backup per 30 days, and possibly a support request first. Schedule around it. The parallel run is two weeks.

Migration help is included: we do the import and the field mapping with you on a call, at no extra cost and on every plan. There is no self-serve importer, so nothing loads until you have seen the mapping.

Zoho Desk migration FAQ

Does the Zoho Desk export include ticket threads?

Not the module export. Zoho’s FAQ says email threads need a Data Backup request. Data Backup includes threads, comments and attachments.

How many records can Zoho Desk export at once?

Zoho’s documentation conflicts: the export article says 50,000 per export, the FAQ says 3,000. Check in your own account before planning around either.

Will the API run out of credits?

It can. Credits are daily and depend on edition and agent count, and deep pagination costs more per call. Extra credits can be bought for a single day.

Who does the import?

We do, with you. You send the backup or API export; the FlowTux team maps and loads it on a call.

Start with two weeks in parallel

Keep Zoho Desk running. Point one channel at FlowTux, send us the export, and compare the two queues on live traffic before anything is switched off.