Zoho Desk to Freshdesk migration
We migrate Tickets, Contacts, Accounts, Products, KB Articles, and historical timestamps from Zoho Desk into Freshdesk with thread chronology preserved, custom field schemas mapped between platforms, and every tag and attachment transferred to the correct destination record — while flagging Blueprints and SLA policies as non-transferable workflow objects that require rebuild in Freshdesk's Scenario builder.
FlitStack AI migrates tickets, ticket conversations, customers, organizations and products from Zoho Desk to Freshdesk, 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: 3-5 weeks.

What moves from Zoho Desk to Freshdesk?
Moving from Zoho Desk to Freshdesk is a structural migration that requires careful object mapping because the two platforms model tickets, organizations, and workflows differently.
Read the full summary
Zoho Desk uses a Tickets-centric model with linked Contacts, optional Account hierarchies, and Blueprints as proprietary workflow state machines. Freshdesk uses a Tickets model with Customers and Organizations, and replaces Zoho's Blueprints with Scenarios (an automation framework with different trigger-action architecture). We extract ticket fields, thread history, contact records, account relationships, product references, and KB article content through the Zoho Desk API, then write them into Freshdesk's REST API with field-type matching and picklist translation. We do not migrate Blueprints or SLA policies as automation code — these are documented for the customer's admin to rebuild in Freshdesk's Scenario builder. Tag-based routing rules in Zoho do not transfer and require reconstruction in Freshdesk's automation layer. The migration typically completes in three to seven weeks depending on record volume and custom field complexity.
Ticket → Ticket
Zoho Desk Tickets map directly to Freshdesk Tickets with standard fields (subject, description, status, priority, type, source channel, assignee, group) transferred 1:1.
How it maps
Custom fields on tickets migrate with type mapping: Zoho picklist values translate to Freshdesk dropdown options, date fields preserve ISO timestamps, and number fields use the same numeric type. Zoho ticket display IDs are preserved in a custom field zoho_display_id for audit reference. Status values (Open, Pending, On-Hold, Closed, etc.) are explicitly mapped to Freshdesk status equivalents during the transform phase.
Thread (Conversations) → Ticket Conversations
Thread history including public replies, internal notes, and email body is stored as sub-objects linked to the parent Ticket in Zoho Desk.
How it maps
We export threads in chronological order and reconstruct the conversation timeline in Freshdesk's ticket conversation feed. Inline attachments referenced in threads migrate as ticket attachments with URLs preserved. Internal notes in Zoho map to Freshdesk's private notes. The created_at timestamp on each thread entry is preserved as the Freshdesk conversation timestamp to maintain historical timeline integrity.
Contact → Customer
Zoho Desk Contacts map to Freshdesk Customers.
How it maps
Name, email, phone, mobile, address, and social profile fields transfer directly. Custom fields on contacts migrate with the same type-mapping logic used for ticket custom fields. Duplicate detection runs on email address before insert. If a Zoho Contact has no email, we use the contact name as the Freshdesk unique identifier. The original Zoho contact ID is preserved in a custom field zoho_contact_id.
Account (Organization) → Organization
Zoho Desk Accounts map to Freshdesk Organizations.
How it maps
Name, industry, website, phone, address, and annual revenue transfer directly. Multi-department accounts in Zoho (where sub-departments share one Account parent) flatten to a single Freshdesk Organization since Freshdesk does not support hierarchical account structures. We create an Organization record first, then link all associated Customer records via the Organization ID resolved at migration time.
Product → Product
Zoho Desk Products (SKU, name, description, custom fields) map to Freshdesk Products.
How it maps
Products are a reference object used in ticket warranty and entitlement tracking. We migrate product records as reference data before ticket import so that ticket-product lookups are resolved at insert time. If the Zoho Product has custom fields, we create matching custom fields in Freshdesk before the product migration phase.
KB Articles → Solutions
Zoho Desk KB Articles (titled content published to help centers) map to Freshdesk Solutions.
How it maps
We export title, body HTML, author, category, tags, and publication status. HTML content transfers as-is with embedded images re-hosted to Freshdesk's attachment storage. Zoho article category hierarchies (KBRootCategories and KBSections) translate to Freshdesk's folder and section structure. Publication status (Published, Draft, Archived) maps to Freshdesk's visibility settings. Note: Knowledge base attachments do not migrate via Zoho API and must be re-hosted separately.
- TicketTicket1:1
- ThreadTicket Conversations1:1
- ContactCustomer1:1
- AccountOrganization1:1
- ProductProduct1:1
- KB ArticlesSolutions1:1
+ 2 more in the mapping below
How Zoho Desk and Freshdesk 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 | Zoho Desk | Freshdesk |
|---|---|---|
| Workflow automation | Blueprints (state-machine workflow enforcement), gated at Professional and above | Scenarios (event-triggered automation builder) available from Pro plan with different trigger-action model |
| Ticket hierarchy | Parent-child ticket relationships natively supported | No native parent-child hierarchy; uses separate tickets or threaded replies |
| Free tier agents | 3 agents on the free plan | 10 agents on the free plan, significantly more generous for small teams |
| Organization model | Accounts as hierarchical organizational containers linked to Contacts | Organizations and Contacts as separate flat structures with a link field |
| AI integration | Zia AI on Professional and Enterprise plans with basic ticket routing | Freddy AI with mature chatbot, ticket triage, and self-service capabilities on Pro and above |
| Ecosystem integration | Deep Zoho ecosystem integration (CRM, Books, Creator) but shallow outside it | 500+ third-party integrations including Slack, Shopify, Salesforce, and Jira with less ecosystem lock-in |
| Customization depth | Basic customization, complex customization requires Deluge scripting | Custom fields, workflows, and automation tools that adapt the platform to unique needs without scripting |
What to watch for in a Zoho Desk to Freshdesk migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Blueprints and SLA policies have no export endpoint
Zoho Desk Blueprints are proprietary state-machine workflows that enforce ticket progression through defined stages with conditional escalation paths.
How we handle it
SLA Policies define response and resolution time thresholds linked to ticket priority or category. Neither object has a public API export endpoint. When migrating away from Zoho Desk to Freshdesk, these workflow objects cannot transfer as code. We document the Blueprint stage definitions, transition rules, and SLA threshold configurations in a written inventory delivered alongside the migration. The customer's admin rebuilds them in Freshdesk's Scenario builder using the documented parameters. Tag-based routing rules that rely on Zoho-specific tag behavior are similarly non-transferable and require Freshdesk Scenario reconstruction.
Parent-child ticket relationships have no Freshdesk equivalent
Zoho Desk supports parent-child ticket hierarchies for decomposing complex issues into sub-tasks linked to a parent ticket.
How we handle it
Freshdesk does not natively support this structure. We handle this during scoping by identifying all Zoho parent-child relationships. Child tickets migrate as standalone Freshdesk tickets with the original parent ticket ID stored in a custom field zoho_parent_ticket_id for reference. Agents can manually link related tickets in Freshdesk via the tickets tab, but there is no automated parent-child enforcement after migration.
Created_at timestamps on tickets are not preserved during API export
When exporting tickets from Zoho Desk via API, the original ticket creation timestamp is not included in the standard export response.
How we handle it
The export returns the modified timestamp but defaults the created_at date to the day of migration execution. We flag this limitation during scoping and document it in the migration plan. For compliance or audit use cases requiring original creation timestamps, we attempt extraction from Zoho's audit log API where available, and fall back to documenting the discrepancy in the migration report so the customer's admin can set expectations with stakeholders.
Agent email identity determines comment attribution after migration
During migration, comment and thread authorship in Zoho Desk is attributed by matching agent email addresses.
How we handle it
If a Zoho agent email does not correspond to an active Freshdesk agent account, all comments from that agent are assigned to the closest matching Freshdesk user or flagged as unattributed. We verify agent email correspondence between the source and destination before migration begins and flag any mismatches during the scoping call. Customers must provision missing Freshdesk agents or confirm a mapping before the migration window opens.
File attachment batch size may exceed Zoho's 10GB upload ceiling
Large help desk instances with extensive attachment archives may exceed the 10GB batch transfer ceiling that Zoho's export process imposes.
How we handle it
We audit total attachment volume during scoping and propose a file-splitting strategy or selective attachment exclusion if the threshold is breached. Attachments are downloaded to temporary storage and re-uploaded to Freshdesk in sequence. Priority is given to recent ticket attachments; older archived attachments can be excluded or migrated in a secondary batch if the primary batch exceeds the limit.
How the migration runs
Discovery and scoping
We audit the source Zoho Desk instance: plan tier (Free, Express, Standard, Professional, Enterprise), ticket volume, attachment size, custom field count, active Blueprint definitions, SLA policy configurations, and department structure.
What this step covers
We extract a full object inventory via the Zoho Desk API including all linked sub-objects (threads, comments, products). We pair this with a Freshdesk target plan review to confirm which automation features (Freddy AI, collision detection, custom reports) are available on the customer's chosen tier. The discovery output is a written migration scope document covering every object, its volume, and its mapping type.
Schema design and Freshdesk target setup
We design the Freshdesk destination schema before any data moves.
What this step covers
This includes creating custom fields on Tickets, Customers, and Organizations to match the Zoho custom field schema (with picklist value translation where Zoho and Freshdesk use different enumerated options). We configure Freshdesk groups based on Zoho department assignments, set up agent profiles and roles, and configure the Freshdesk product catalog. We create a zoho_display_id custom field on tickets and zoho_contact_id on customers to preserve original Zoho record identifiers for audit and reconciliation.
Attachment audit and file preparation
We run a full attachment audit to calculate total file size against Zoho's 10GB batch ceiling.
What this step covers
If the total exceeds the limit, we propose a selective attachment strategy: prioritize attachments from open tickets and tickets modified within the past 12 months, and defer older archived attachments to a secondary migration batch. We download all in-scope attachments to temporary storage, re-host images embedded in KB articles to Freshdesk's attachment storage, and prepare a file manifest for the Freshdesk upload phase.
Blueprint and SLA documentation
We extract and document every Zoho Blueprint definition including stage names, transition conditions, required fields per stage, and escalation triggers.
What this step covers
We document every SLA policy including name, response time threshold, resolution time threshold, applicable ticket priorities, and business hours configuration. This documentation is delivered as a written inventory that the customer's admin uses to rebuild equivalent automation in Freshdesk's Scenario builder post-migration. We explicitly scope Blueprints and SLA policies as excluded from data migration.
Parallel migration in dependency order
We run the migration in dependency order: Products (reference data first), Organizations (from Zoho Accounts), Customers (from Zoho Contacts, with OrganizationId resolved), Agents (with email-to-agent mapping validated), Tickets (with assignees, groups, and product links resolved), Ticket Conversations (chronologically ordered), KB Articles (with folder structure created first), and Tags (applied to records post-insert).
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. We use Freshdesk's REST API with batch chunking and rate-limit handling to avoid throttling on high-volume accounts.
Validation and cutover
We run reconciliation checks comparing source and destination record counts across all object types.
What this step covers
We spot-check 25-50 random tickets against the Zoho source to verify field mapping accuracy, attachment presence, and conversation chronology. The customer's support team lead validates a sample of ticket histories and approves the migration before we open Freshdesk as the system of record. We deliver the Blueprint and SLA documentation alongside the migration report. We do not rebuild Zoho automations in Freshdesk as part of the migration scope; that is a separate engagement handled by the customer's admin or a Freshdesk implementation partner.
- Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, custom field count, and the complexity of resolving Zoho Blueprints to Freshdesk Scenarios. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Zoho Desk to Freshdesk →Why teams move from Zoho Desk to Freshdesk
- Teams report Zoho Desk's interface as dated and inconsistent across modules compared to modern SaaS competitors. Long-term users on G2 and Reddit cite clunky navigation, slow ticket handling workflows, and a steep learning curve for new agents as ongoing friction that accumulates as team size grows. Freshdesk's interface consistently earns higher usability ratings for daily ticket handling tasks, with agents able to ramp faster without dedicated training investment.
- While both platforms offer free tiers, Freshdesk's free plan accommodates 10 agents versus Zoho Desk's 3-agent limit. For small to mid-size teams evaluating a platform before committing, Freshdesk's free tier provides a more realistic preview of multi-agent workflows and team collaboration, reducing the financial risk of evaluation.
- Outside the Zoho ecosystem, connecting Zoho Desk to non-Zoho CRMs, calendars, or analytics tools requires custom Deluge scripts or third-party middleware. Freshdesk offers over 500 marketplace integrations including native connections to Slack, Shopify, Salesforce, Jira, and HubSpot without scripting. Teams running heterogeneous tech stacks find Freshdesk's integration ecosystem reduces middleware overhead and operational complexity.
- Zoho Desk's Blueprints and SLA policies are proprietary constructs with no export endpoint. Teams that have invested significant time building ticket routing workflows in Blueprints find they cannot move those workflows when switching platforms. Freshdesk's Scenario builder is a different automation model, requiring a documented rebuild. While both are excluded from migration scope, the documentation and rebuild work is smaller when both systems share a more conventional trigger-action automation paradigm.
- Freshdesk's collision detection feature prevents two agents from working on the same ticket simultaneously — a workflow safeguard that Zoho Desk lacks as a native feature. Teams with high ticket volume and multiple agents handling the same customer queue cite collision detection as a meaningful daily efficiency improvement that reduces duplicate responses and customer confusion.
Questions, answered
Zoho Desk to Freshdesk migration questions
How long does a Zoho Desk to Freshdesk migration take?
Straightforward migrations under 10,000 tickets, 5,000 contacts, and 5,000 organizations with standard custom fields and no large attachment archives complete in three to five weeks. Migrations with extensive attachment volumes approaching the 10GB ceiling, complex multi-department structures, custom field divergence requiring manual picklist translation, or large KB article archives move to seven to twelve weeks because of the file re-hosting and schema reconciliation work.
Do Zoho Desk Blueprints and SLA policies migrate to Freshdesk?
No. Zoho Desk Blueprints are proprietary workflow state machines with no export endpoint. Freshdesk's Scenario builder uses a different trigger-action automation model that does not accept Blueprint data directly. We document every Blueprint definition (stage names, transitions, required fields, escalation rules) and every SLA policy configuration (thresholds, priorities, business hours) in a written inventory delivered alongside the migration. The customer's admin uses this documentation to rebuild equivalent automation in Freshdesk's Scenario builder. This is manual reconstruction work outside standard migration scope.
Can we migrate our Zoho Desk knowledge base articles to Freshdesk?
Yes, we migrate KB articles as Freshdesk Solutions. We transfer title, body HTML, author, category folder structure, tags, and publication status. HTML content and embedded images transfer as-is. Note that Zoho knowledge base attachments are not accessible via the standard Zoho Desk API and must be re-hosted separately; we flag these during scoping and handle them as a secondary step if the customer requires them.
Will ticket creation timestamps be preserved after migration?
The original ticket creation timestamp in Zoho Desk is not included in the standard API export response. We flag this as a known limitation during scoping. For compliance or audit use cases requiring original timestamps, we attempt extraction from Zoho's audit log API where available and document the discrepancy in the migration report. Customers with strict timestamp requirements should validate whether this limitation affects their reporting and service-level auditing before migration begins.
What happens to parent-child ticket relationships during migration?
Zoho Desk supports parent-child ticket hierarchies that have no native Freshdesk equivalent. We handle this by migrating child tickets as standalone Freshdesk tickets with the original parent ticket ID stored in a custom field zoho_parent_ticket_id for reference. Agents can manually link related tickets in Freshdesk via the tickets tab, but there is no automated parent-child enforcement. We identify all parent-child relationships during scoping so the customer can plan their post-migration linking strategy.
Do Zoho Desk tags and tag-based routing rules migrate to Freshdesk?
Tag names themselves migrate as flat labels applied to the corresponding tickets and contacts in Freshdesk. However, tag-based automation rules in Zoho Desk — routing rules triggered by specific tag assignments — do not transfer because Freshdesk's Scenario automation uses a different trigger model. We document every tag-based automation during the Blueprint documentation phase and include it in the automation inventory delivered alongside the migration.
Can we run a trial migration before committing to the full cutover?
Yes. We run a demo migration with a subset of production data (typically 50-200 records per object type) into a Freshdesk sandbox or trial account before the production migration. The customer reviews the imported records for field mapping accuracy, attachment presence, conversation chronology, and tag application. Any mapping corrections are applied to the migration scripts before the full production migration begins. Demo migrations are scoped and quoted separately from full migrations.
Related migrations
Sources: official documentation
- Import to Freshdesk — Freshworks Marketplace
- Import and export customers and company information — Freshdesk
- Throughput and plan-tier limits — Freshdesk
- Associating different object types in Freshdesk
- Managing Fields — Zoho Desk Online Help
- Types of Custom Fields — Zoho Online Help
- Migrate Data From Other Help Desk Servers to Zoho Desk (Zwitch) — Zoho Desk
Get a quote
Moving from Zoho Desk to Freshdesk?
Tell us roughly how many records and objects you have. We scope the mapping and the Freshdesk setup with you, then send a quote.
Get a quote