Switching from Freshdesk to Zoho Desk: A Complete Migration Guide

When you decide to switch Freshdesk to Zoho Desk, the biggest risk is not the software itself but losing ticket history, misconfiguring automations, or leaving agents confused during the first week of live operations. This guide covers every stage of the migration: what to export from Freshdesk, how to configure Zoho Desk from scratch, what actually transfers during a ticket migration, and what you have to rebuild manually. Whether you are running a 5-person support team or a 50-agent department, the sequence is the same. Follow it in order and you avoid the common failure modes that turn a one-weekend cutover into a three-week cleanup project.

What to Export from Freshdesk Before You Start

A migration that skips the export audit almost always results in missing contacts or broken ticket references on the Zoho Desk side. Before you touch Zoho Desk settings, extract everything from Freshdesk and store it locally.

Contacts and companies

Go to Freshdesk Admin > Export Contacts. Select all fields including custom contact fields. Export as CSV. Do the same for Companies (accounts). These become your contacts and accounts in Zoho Desk. Custom fields will need to be manually recreated in Zoho Desk before import, so note every custom field name, type (text, dropdown, date), and whether it is required.

Ticket history

Freshdesk allows a full ticket export from the Reports section. Download tickets with all fields: ticket ID, subject, description, requester, agent, group, priority, status, creation date, resolution date, first response time, tags, and custom fields. Export in CSV format. For attachments, Freshdesk does not bulk-export them natively; you need a third-party migration tool such as Help Desk Migration or Trello-based export scripts if attachments are business-critical.

Knowledge base articles

Export all solution categories and articles from Freshdesk via Admin > Solutions. The native export gives you HTML files per article. Record the folder structure (category name, section name, article title, SEO metadata) because Zoho Desk has an equivalent category/section/article hierarchy and you will rebuild it manually or via API.

Agents and groups

List all agents with their email addresses, roles, and group assignments. In Freshdesk these are under Admin > Agents and Admin > Groups. You will invite agents to Zoho Desk using the same email addresses, which preserves the requester history mapping when tickets are imported.

Automations, SLA policies, and canned responses

There is no direct import path for these. Export or screenshot every automation rule, SLA policy, and canned response in Freshdesk. Record the trigger conditions and actions in a spreadsheet. You will rebuild them manually in Zoho Desk, and the logic is close enough that a 1:1 rebuild is straightforward for most standard rules.

Setting Up Zoho Desk: Workspace, Departments, Agents, and Channels

Zoho Desk organises work differently from Freshdesk. Freshdesk uses Groups; Zoho Desk uses Departments. A department in Zoho Desk is a self-contained support unit with its own email channel, SLA policies, automations, and knowledge base. If you run one support team, create one department. If you run separate product support and billing support queues, create two departments.

Initial workspace configuration

Log in to Zoho Desk and go to Setup. Set your business hours, time zone, and default language first. These settings affect SLA calculations from the moment tickets are created. Set them before importing any ticket data.

Creating departments

Under Setup > Departments, create a department for each logical team. Assign a department email address. If your Freshdesk groups map directly to teams, use those same names so agents recognise the structure immediately.

Inviting agents and assigning roles

Under Setup > Agents, invite agents using the same email addresses they used in Freshdesk. Zoho Desk has four standard roles: Administrator, Supervisor, Agent, and Light Agent. Map your Freshdesk roles to the closest equivalent. Assign each agent to their department and any relevant teams within that department.

Custom contact fields

Under Setup > Contacts > Fields, recreate every custom field you noted during the Freshdesk export. Match the field type exactly. Fields that exist in Zoho Desk before you import contacts will populate correctly; fields created after import will be empty for existing records.

Migrating Ticket History and Closed Tickets

This is the section most teams underestimate. Not all ticket data transfers cleanly, and knowing what transfers versus what does not helps you decide whether to do a full historical migration or a clean-start cutover with a historical archive.

What transfers via a migration tool

Using a dedicated migration service (Help Desk Migration is the most commonly used for Freshdesk to Zoho Desk), the following data transfers reliably: ticket subject and description, requester and CC contacts, status, priority, creation and resolution dates, public replies and private notes, tags, and attachments (subject to file size limits). Custom ticket fields transfer if you map them to equivalent fields in Zoho Desk during the migration setup.

What does not transfer or requires manual work

Closed ticket import strategy

For most teams, a two-year rolling import is sufficient. Import open tickets and tickets from the past 24 months as active records in Zoho Desk. Archive older Freshdesk data by keeping the Freshdesk account in read-only mode for 90 days post-cutover, then exporting it as a final CSV archive for compliance. This avoids importing tens of thousands of old closed tickets that agents will rarely reference.

Recreating Automations, SLA Policies, and Escalation Rules

Zoho Desk’s automation engine is called Workflow Rules. It uses the same trigger/condition/action model as Freshdesk, with slightly different terminology.

SLA policies

In Zoho Desk, go to Setup > SLA Policies. Create policies per department. Zoho Desk allows response time and resolution time targets by ticket priority, with business-hours vs. calendar-hours configuration. The escalation rules (what happens if an SLA is breached) are set within each SLA policy, not as separate rules.

Workflow rules

Under Setup > Automation > Workflow Rules, recreate your Freshdesk automation rules. Zoho Desk triggers include: ticket creation, ticket update, field value change, and scheduled rules (time-based). If your Freshdesk rule ran on ticket creation when priority was high, you create a Workflow Rule with trigger “Ticket is created”, condition “Priority equals High”, and the equivalent action (assign to group, send email, change status).

Macros for canned responses

Freshdesk canned responses map to Macros in Zoho Desk. Go to Setup > Productivity > Macros. Each macro can update fields, add tags, send a reply template, and change ticket status in one click. Import your canned response text and wrap each one in a macro definition. Agents will find macros in the ticket view under the macro dropdown, which is the same muscle memory as using canned responses in Freshdesk.

Round-robin and auto-assignment

Freshdesk’s Automatic Ticket Assignment maps to Zoho Desk’s Assignment Rules under Setup > Automation. You can assign by round-robin within a department, by skill, or by availability. Recreate your Freshdesk group routing logic using Zoho Desk department-based assignment rules.

Migrating the Knowledge Base: Articles, Categories, and SEO Settings

Zoho Desk’s Help Center uses a three-level hierarchy: Categories > Sections > Articles. Freshdesk uses Categories > Folders > Articles. The naming differs but the structure is equivalent.

Recreating the category structure

Under the Help Center module in Zoho Desk, create your top-level categories first, then sections under each. Once the folder structure exists, you can create articles manually or via the Zoho Desk API if you have HTML exports from Freshdesk.

Article content import via API

Zoho Desk has a Knowledge Base API endpoint: POST /api/v1/articles. Send the article title, HTML body, category ID, section ID, and SEO metadata (meta title, meta description, permalink). This is the most efficient path if you have 50 or more articles. A simple Python script can loop through your Freshdesk HTML exports and post them to Zoho Desk in under an hour.

SEO settings per article

Each article in Zoho Desk has a dedicated SEO tab where you set the meta title, meta description, and custom URL. Freshdesk exports do not include this data in the CSV; you need to retrieve it via the Freshdesk API (GET /api/v2/solutions/articles/{id}) if you want to preserve existing meta tags. For most teams, it is faster to rewrite SEO metadata for the top 20 highest-traffic articles rather than attempting a full programmatic migration.

Channel Setup: Email, Phone, Chat, and Social in Zoho Desk

Every support channel you used in Freshdesk has a direct equivalent in Zoho Desk. The key difference is that Zoho Desk channels are configured per department, not globally.

Email channels

Under Setup > Channels > Email, add your support email addresses. Zoho Desk provides a forwarding address for each channel. Set up email forwarding from your existing support address (support@yourcompany.com) to the Zoho Desk forwarding address. Replies from Zoho Desk will come from your original support address via SMTP relay. Do not shut down the Freshdesk email channel until you have confirmed Zoho Desk is receiving and replying correctly, which typically takes 24 hours to validate end-to-end.

Phone and chat

If you use Freshdesk’s built-in phone (powered by Freshcaller), the equivalent in Zoho Desk is Zoho Telephony via the Zoho Voice integration or a third-party telephony provider. Chat migrates similarly: Freshdesk’s Freshchat maps to Zoho Desk’s built-in chat widget or a Zoho SalesIQ integration if you are already on Zoho One.

Social and portal

Twitter and Facebook social channel connections are available under Setup > Social in Zoho Desk. Reconnect your social accounts there. The customer portal URL changes from your Freshdesk subdomain to a Zoho Desk subdomain (or your custom domain). Update the portal link in your website footer and email signatures on cutover day.

Training Your Support Team on Key Zoho Desk UI Differences

Agents who are accustomed to Freshdesk will find Zoho Desk familiar at the concept level but different in the UI layout. Focus training on the five areas where the differences create the most friction in the first week.

Ticket list view and filters

Freshdesk uses a left-panel filter approach. Zoho Desk uses a view-based system where agents switch between pre-defined views (My Open Tickets, All Open Tickets, Overdue, etc.) and can create custom views. Train agents to create their personal custom views first, because this replaces the filtering habits they built in Freshdesk.

Reply and note interface

Zoho Desk’s reply editor is at the bottom of the ticket timeline, toggled between Reply, Forward, and Private Note using a tab interface. In Freshdesk, public reply and private note are separate buttons. Agents need to know the tab toggle or they accidentally send private notes as public replies in the first few days.

Macros versus canned responses

Macros in Zoho Desk do more than canned responses in Freshdesk. A macro can change the ticket status, assign to an agent, and send a pre-written reply in one action. Teach agents to use macros rather than just the text templates they relied on in Freshdesk.

Time tracking

Zoho Desk’s time tracking is a manual log per ticket under the Time Entry tab. If your team used Freshdesk’s time tracking, agents need to log time explicitly in Zoho Desk. It is not automatic. Configure a reminder or workflow rule to prompt agents to add time entries before closing tickets if time tracking is business-critical for billing.

Reports and analytics

Freshdesk’s reports are ticket-centric. Zoho Desk has a comparable Reports module plus a deeper Analytics section (available in higher plans). The built-in Zoho Desk report builder uses a drag-and-drop interface. The core metrics (FRT, resolution time, ticket volume, CSAT) are all available. Agents and supervisors who relied on custom Freshdesk reports will need 1 to 2 hours to rebuild their dashboards, but the capability gap is minimal. If you are on Zoho One, the Zoho Analytics integration unlocks cross-department reporting that Freshdesk does not offer at an equivalent price point.

Go-Live Checklist and What to Monitor in the First Two Weeks

A structured go-live reduces the chaos that accompanies any platform cutover. Run through this checklist on cutover day and review the monitoring items daily for two weeks.

Go-live day checklist

• Email forwarding from old support address to Zoho Desk confirmed working
• Customer portal URL updated in website and email signatures
• All agents invited, added to correct departments and teams
• SLA policies active with correct business hours
• Workflow rules live and tested with at least one test ticket per rule
• Macros available in agent view and tested
• Knowledge base published and accessible at Help Center URL
• Social channel connections verified
• Freshdesk set to read-only mode (do not deactivate until 90 days post-cutover)

First two weeks: what to watch

Monitor the following metrics daily using Zoho Desk’s built-in Reports dashboard:

• Unassigned ticket count: spikes indicate assignment rule gaps. Fix workflow rules immediately when you see tickets piling up in the unassigned queue.
• First response time: compare to your Freshdesk baseline. An increase of more than 20% sustained beyond day 3 means agents are navigating unfamiliar UI. Schedule a focused training session rather than waiting for it to self-correct.
• SLA breach rate: if breaches jump above normal, check that SLA policies have business hours set correctly. The most common cause is time zone mismatch in the SLA settings.
• Reopened ticket rate: if agents are accidentally closing tickets by misusing status dropdowns, this surfaces in the first week. Adjust your workflow rules to require a resolution comment before closure if the rate is unusually high.

By day 14, most teams are operating at or above their Freshdesk efficiency levels. The initial dip in speed is normal and recoverable within the first week for experienced support teams.

Migrating support platforms is a process that rewards careful preparation over speed. Get the export audit right, configure Zoho Desk systematically before importing data, and give your agents one week of structured training before cutover. Most teams that follow this sequence are fully operational in Zoho Desk within three weeks and report no meaningful service degradation during the transition.