Zoho Desk CSV exports drop threads. Use the API or Data Backup, plan 2–4 weeks, handle Freshdesk's 400–700 req/min limits, and request a migration API key for timestamps.
There is no native migration path from Zoho Desk to Freshdesk; all data movement requires API-based extraction or Zoho's on-request Data Backup feature, since standard Zoho Desk CSV exports omit ticket threads and comments entirely. The two platforms differ fundamentally in their data models—Zoho Desk's Departments, Blueprints, Products, and Activities have no direct Freshdesk equivalents, and ticket threading models (Threads/Comments vs. Conversations) require field-level transformation of direction and visibility metadata. Custom work is required to handle object remapping, deep-pagination credit optimization on extraction, Freshdesk's plan-based rate limits on loading (400–700 req/min), and obtaining a special migration API key from Freshdesk to preserve historical timestamps on imported tickets.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
TL;DR — Zoho Desk to Freshdesk Migration
Zoho Desk's standard ticket export drops all conversation threads and comments. A complete migration requires API-based extraction or Zoho's Data Backup feature. Plan 2–4 weeks end-to-end, including discovery, sandbox testing, UAT, and delta sync. The load side is bounded by Freshdesk's plan-based rate limits (400 req/min on Pro, 700 on Enterprise). Zoho Desk Blueprints, Products, and Activities have no Freshdesk equivalent — archive or rebuild those. Contact Freshdesk support for a special migration API key before starting, or all imported tickets will show today's date instead of historical timestamps.
Data Backup constraints
Only the Zoho Desk primary contact can create or download backups. Zoho documents a 10 million record backup ceiling, 31-day limits for custom backup windows, and a 30-day wait between full backups. Attachment entries arrive as secure download links rather than already-expanded files — plan around these rules before announcing a cutover date. (help.zoho.com)
Freshdesk timestamp limitation
The standard Freshdesk ticket creation API (POST /api/v2/tickets) does not allow you to set created_at or updated_at timestamps. All imported tickets will show today's date unless you contact Freshdesk support for a special migration API key that permits setting historical timestamps. This is a well-documented limitation that catches many DIY migrations. Request the key before you start scripting — approval can take 2–5 business days and there is no additional cost, but it requires explaining your migration use case to Freshdesk support.
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 Freshdesk can hold your support model
Walk your current workflow through Freshdesk: 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 → Freshdesk 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.
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 → Freshdesk specifics
- Zoho Desk REST API
- The GET /api/v1/tickets/{ticket_id}/threads endpoint returns full thread content including HTML body, attachments, and direction. This is the only path that gives you programmatic, reliable, targeted access to full conversation data. Note: Zoho Desk has been introducing v2 API endpoints alongside v1. Verify current endpoint availability against Zoho's API changelog before locking your script to a specific version, as v1 endpoints may be deprecated on a rolling basis.
- Data Backup feature
- Available on request from Zoho Desk support (contact support@zohodesk.com). Provides a bulk export including tickets, threads, comments, and attachment download links. Attachments arrive as secure download links that must be fetched separately before they expire.
- Bulk Export API
- The /api/v1/bulkExport endpoint supports exporting up to 100,000 records per request with callback URLs, but thread content still requires individual API calls per ticket.
- Deep-pagination tax
- If you're extracting tickets at high offsets (beyond the 10,000th record), credit costs per call escalate from ~3 to ~50 credits. Extract in modifiedTime-sorted batches with date windowing to minimize deep pagination.
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 → Freshdesk 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 → Freshdesk 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 Freshdesk 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.
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 Freshdesk sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Freshdesk 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 Freshdesk'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 → Freshdesk specifics
- Field-level spot checks
- Sample 50 random tickets and verify every field (status, priority, custom dropdowns, assignee, tags) matches the source.
- Thread completeness
- For sampled tickets, verify that every thread in Zoho Desk has a corresponding note in Freshdesk with correct content and chronological ordering.
- Automation smoke test
- Create a new test ticket in Freshdesk post-migration (after re-enabling automations) to verify Dispatch'r, Supervisor, SLA policies, and email notifications fire correctly on new tickets. Migrated tickets will not have accurate SLA history.
- Portal visibility check
- Log in as a customer to the Freshdesk portal and verify that public notes on migrated tickets are visible and readable.
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 Freshdesk, 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 Freshdesk'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.
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 Freshdesk 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 Freshdesk, 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.
-
Record-count reconciliation
Compare total tickets, contacts, and companies between source and target. A mismatch greater than 0.1% requires investigation.
Zoho Desk → Freshdesk specifics
- Attachment verification
- Open 20 tickets with attachments and confirm files are downloadable without 404 errors. Verify file sizes match the source.
- Inline image verification
- Open 10 tickets with inline images and confirm images render correctly in the Freshdesk agent view and customer portal.
- Timestamp verification
- Confirm that migrated tickets display their original Zoho Desk creation dates, not the import date. If timestamps show today's date, the migration API key is not working correctly.
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.
Object Object
| Zoho Desk field | Freshdesk field | Notes |
|---|---|---|
| Departments | Groups | Departments control layouts, SLAs, and agent access in Zoho Desk. Groups in Freshdesk are simpler. If you use Zoho Departments for distinct brands, map them to Freshdesk Products instead. |
| Accounts | Companies | Freshdesk requires Company names to be unique — deduplicate Zoho Accounts before loading. Custom fields require manual re-creation. |
| Contacts | Contacts | Freshdesk uses email as the primary identifier. Zoho Desk supports multi-account contact mapping; Freshdesk links one company per contact. Contacts without emails require dummy emails or phone number mapping. |
| Tickets | Tickets | Status values, picklists, and custom fields need explicit mapping. Zoho custom fields must be pre-created in Freshdesk with matching data types. |
| Threads | Conversations (replies/notes) | Zoho Desk separates public threads, private threads, and comments. Freshdesk uses reply, note, and forward. Direction (in/out) and visibility (public/private) must be transformed. |
| Tags | Tags | Direct mapping. |
| Agents | Agents | Agent roles and profiles differ structurally. Agents must be created in Freshdesk first to retain ticket assignment history. |
| KB Articles | Solution Articles | Freshdesk structures KB articles under Categories and Folders. Zoho Desk hierarchies must be rebuilt to match this structure. |
| Blueprints | ❌ No equivalent | Freshdesk has no Blueprint feature. Workflow rules can partially replicate this. |
| Products | ❌ No native equivalent | Freshdesk does not have a Products module. Products can be stored as tags or custom dropdown values. |
| Activities (Tasks/Calls/Events) | ❌ No equivalent | Freshdesk does not support activities. Archive these separately. |
| SLAs | SLA Policies | Must be manually recreated. SLA history does not migrate. |
| Custom Fields | Custom Fields | Field types must match exactly. A Zoho Picklist maps to a Freshdesk custom_dropdown. A Zoho Multiselect maps to a Freshdesk custom_checkbox (array). Mismatched types cause silent data truncation. |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets | medium | Ticket metadata maps well, but custom statuses must be explicitly remapped to Freshdesk's strict predefined status IDs, and historical timestamps require a special migration API key. |
| Conversations (Threads/Comments) | high | Zoho Desk's separate public threads, private threads, and comments must be transformed into Freshdesk's reply/note/forward model with correct direction and visibility, and standard exports omit this data entirely. |
| Contacts | medium | Freshdesk uses email as the primary identifier and links only one company per contact, while Zoho Desk supports multi-account contact mapping; contacts without emails require dummy values or phone-based workarounds. |
| Companies (Accounts) | medium | Freshdesk requires unique company names, so Zoho Desk Accounts must be deduplicated before loading, and custom fields require manual re-creation in the destination. |
| Custom Fields | high | Field types must match exactly between systems, API names differ (Freshdesk auto-generates cf_ prefixed names), and mismatched types such as Picklist-to-dropdown cause silent data truncation. |
| Agents | low | Agents can be created in Freshdesk ahead of migration, but role and profile structures differ between the platforms, requiring manual role re-creation. |
| Knowledge Base Articles | medium | Zoho Desk KB hierarchies must be rebuilt to match Freshdesk's Category-and-Folder structure, and embedded media or internal links need to be re-mapped. |
| Tags | low | Tags map directly between the two platforms with minimal transformation required. |
| Attachments | medium | Freshdesk caps attachments at 20 MB per file and 15 per ticket/conversation; oversized files must be hosted externally, and Data Backup attachment links expire and must be fetched promptly. |
| SLA Policies | medium | SLA policies must be manually recreated in Freshdesk and historical SLA compliance data does not migrate, impacting post-migration reporting continuity. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Thread and Comment Loss
Zoho Desk's standard CSV export omits all ticket threads and comments, requiring API-based extraction or a Data Backup request to preserve conversation history.
Department-to-Group Mismatch
Zoho Desk Departments control layouts, SLAs, and agent access as top-level organizational units, but Freshdesk Groups are simpler agent-grouping constructs with no 1:1 mapping.
Historical Timestamp Preservation
Freshdesk's standard ticket creation API does not allow setting created_at or updated_at, so without a special migration API key from Freshdesk support, all imported tickets show today's date.
API Rate Limit Bottlenecks
Zoho Desk's credit-based daily limits with deep-pagination cost escalation and Freshdesk's per-minute account-wide rate caps (200–700 req/min depending on plan) create compounding throughput constraints during extraction and loading.
No Equivalent for Blueprints/Products
Zoho Desk Blueprints, Products, and Activities have no native Freshdesk counterparts, requiring data to be archived or partially reconstructed using workflow rules, tags, or custom fields.
Custom Field Type Mapping
Zoho Desk and Freshdesk use different custom field type systems—such as Picklist vs. custom_dropdown and Multiselect vs. custom_checkbox—and mismatched types cause silent data truncation during import.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate Zoho Desk to Freshdesk without losing data?
Yes, but only through API-based extraction or Zoho's Data Backup feature. The standard CSV export omits all ticket threads and comments. Use the REST API to extract tickets, threads, and attachments, then load them into Freshdesk as notes to avoid triggering outbound emails.
How long does a Zoho Desk to Freshdesk migration take?
Typical end-to-end timelines are 10–18 days including discovery, script development, test migration, production load, and validation. The actual data transfer for 50,000 tickets takes about 1 day on Freshdesk Pro (400 calls/min). Most elapsed time goes to field mapping, UAT, and stakeholder review.
What data cannot be migrated from Zoho Desk to Freshdesk?
Zoho Desk Blueprints, Products, Activities (Tasks/Calls/Events), SLA history, workflow rules, and satisfaction ratings have no native Freshdesk equivalent. These must be archived or manually recreated using Freshdesk automations and tagging.
Does Freshdesk preserve timestamps during ticket import?
Not with the standard API. The POST /api/v2/tickets endpoint ignores created_at and updated_at fields. You must contact Freshdesk support for a special migration API key that allows setting historical timestamps.
Will Freshdesk send emails to customers during import?
Yes, if you use the reply endpoint. Import historical conversations as private or public notes instead of replies to avoid triggering outbound notifications. Disable all email notification rules in Freshdesk Admin before starting.