Skip to content
Get a quote

Migrate to Zoho Desk

Zoho Desk is a Department-centric, edition-tiered helpdesk whose import success depends on pre-creating Departments, agents and Layouts, packaging CSVs in a single zipped bundle, and respecting the 10,000-row / 30 MB ceiling on each batch.

Short answer

FlitStack AI migrates tickets, threads, and customer histories into Zoho Desk from 250+ helpdesks, including Zendesk. Every field is mapped to Zoho Desk's objects, history and associations come across, the Zoho Desk setup is configured alongside, and the whole migration stays reversible in one click.

By

From Zendesk
DestinationZoho Desk
Zendesk
250+ sources mapped into Zoho Desk

Systems we move into Zoho Desk

The helpdesks teams most often move from. Each page shows what moves, the field mapping and what to watch for.

What Zoho Desk supports, and where its import tools stop

  • Deep Zoho ecosystem integration lets support data tie directly to CRM contacts, invoice records in Zoho Books, and custom apps built in Zoho Creator, providing a unified customer view without third-party middleware.
  • Pricing undercuts comparable platforms significantly: Enterprise at roughly $40 per agent per month versus Zendesk at comparable tiers, making it attractive for cost-sensitive teams scaling past 10 agents.
  • Blueprints and multi-level escalations allow teams to codify support workflows and enforce SLA routing automatically, reducing manual triage for mid-size support operations.
  • Multi-channel ticket ingestion unifies email, social media, live chat, and phone into a single queue view, giving agents one inbox without context-switching across channels.
Bulk APIOAuth 2.0 with access tokens; each API request must include an OAuthToken scoped to Desk APIs
Rate limitsTied to plan tier; Zoho documents 4,000 to 25,000 requests per day per organization (or 500 per user license, whichever is lower). No published per-minute ceiling; 429 responses have no Retry-After header, so we apply exponential backoff
ObjectSupportNote
TicketsmappedTickets are the core object and support all standard fields plus custom fields. Status values vary between source and destination and require explicit mapping. We extract the full ticket record including priority, channel origin, and linked sub-forms, then normalize statuses at the destination.
Threads (Conversations)mappedThread history including internal and public comments, email body, and inline attachments is stored as a linked sub-object to Tickets. We export threads in chronological order and reconstruct the conversation thread at the destination, noting that inline images may require re-hosting.
ContactsfullContacts map 1:1 to standard CRM contact schemas across most platforms. Zoho Desk stores contact name, email, phone, address, and custom properties. We handle duplicate detection by email and map any custom Contact fields to destination equivalents.
Accounts (Organizations)fullAccounts represent the parent organization for a Contact and support hierarchical structures. We migrate Account name, industry, website, and linking relationships to Contacts. Multi-department account structures are preserved via the account-subaccount relationship.
ProductsmappedProducts are a lookup/reference object linking to Tickets for warranty and entitlement tracking. They carry name, SKU, description, and custom fields. We migrate Products as reference data and map the product-to-ticket association at the destination.
TasksmappedTasks are sub-objects of Tickets used for action items and to-dos. We export task subject, due date, assignee, and status. Tasks without a parent ticket are flagged for manual placement during migration.
KB ArticlesmappedKnowledge Base Articles are versioned content published to Help Centers. We export title, body HTML, author, category, tags, and publication status. HTML content is transferred as-is; images embedded in article bodies require URL remapping if the source help center domain is not replicated.
DepartmentsmappedDepartments are organizational containers that route tickets and assign agents. They carry name, email, phone, and settings. We migrate department structures and agent assignments, noting that multi-department routing rules may need rebuild verification at the destination.
AgentsmappedAgents are the billing unit in Zoho Desk and carry name, email, role, and department assignment. We migrate agent records and preserve comment ownership by matching email addresses. Inactive agents must be activated in the target account before migration or their comments will be attributed to a generic fallback user.
TeamsfullTeams are agent groupings used for ticket assignment and workload balancing. We migrate team membership and the team-ticket assignment rules. Teams without members are skipped to avoid orphaned routing configurations.
TagsmappedTags are flat labels applied to Tickets and Contacts. We export tag names and apply them to the corresponding records at the destination. Tag-based automations in Zoho Desk will not transfer and must be rebuilt in the target system.
AttachmentsmappedTicket and article attachments are stored in Zoho WorkDrive or as direct file references. We extract file URLs and download attachments up to the Zoho-imposed 10GB upload limit. Files exceeding this limit are flagged for customer decision on compression or exclusion.
Custom FieldsmappedCustom fields on Tickets, Contacts, and Accounts are exported with their data types (text, picklist, date, number). We map custom field schemas between source and destination, handling picklist value translation and preserving the custom field relationship to the parent object.
BlueprintsnoneBlueprints are Zoho Desk-specific workflow state machines that enforce ticket progression through defined stages. These are not portable objects and cannot be exported via API. We document the Blueprint stage definitions for manual reconstruction at the destination platform.
SLA PoliciesmappedSLA Policies define response and resolution time thresholds linked to ticket priority or category. We export the SLA configuration and flag which tickets reference which policy, but SLA enforcement rules must be rebuilt in the destination system using that platform's own SLA engine.

The Zoho Desk migration guide

Why teams migrate to Zoho Desk

The four shapes a Zoho Desk migration takes, and what makes the platform easier — or harder — than the category average.

Zoho Desk is the customer-support product inside Zoho Corporation's broader suite. Zoho was founded in 1996 by Sridhar Vembu and Tony Thomas and is headquartered in Chennai, India1. Desk sits alongside Zoho CRM, Books, Projects, Campaigns and forty-plus sibling apps inside the Zoho One bundle, and it is the destination most often reached for by teams already invested in the Zoho ecosystem.

The typical Zoho Desk customer is a 10-to-200-agent support team buying on bundle economics and per-agent price. The Enterprise tier maxes out around €40 per agent per month — roughly a third of Zendesk's equivalent tier and meaningfully below Freshdesk's top plans. Teams already running Zoho CRM, Zoho Books or Zoho Projects get tight native integration that removes one of the larger setup-tax line items.

The shapes of migration that land on Zoho Desk tend to fall into four patterns. First, Zendesk exits, driven by per-agent pricing — Zendesk's mid-and-upper tiers sit at roughly $55 to $150+ per agent per month, and teams cite total-cost-of-ownership savings as the headline trigger. Second, Freshdesk consolidations, where teams already on other Zoho products fold support into the same suite10.

Third, suite consolidation inside Zoho One — replacing a Zendesk-plus-Intercom-plus-knowledge-base stack with Desk plus SalesIQ plus the built-in Knowledge Base. Fourth, legacy ManageEngine / ServiceDesk Plus or shared-inbox replacements, where the source is an on-prem or email-only system and the project is really a re-architecture. Zoho's Zwitch service explicitly names Zendesk, Freshdesk, Salesforce Service Cloud, HappyFox and Help Scout as common source platforms10.

What makes migrating to Zoho Desk easier than the category average is the dual import path. The native Import wizard accepts a single zipped CSV bundle covering Tickets, Contacts, Accounts, Agents, Tasks, Events, Calls, Custom Modules and Knowledge Base articles in one upload11. On top of that, Zwitch — Zoho's free assisted-migration service at [email protected] — handles transfers from Zendesk, Freshdesk and a dozen other sources, with uploads up to 10 GB10.

What makes it harder than the average is the Department-centric model, which forces every Ticket, every Layout, every Workflow Rule and every SLA to belong to a specific Department before import; the 30 MB / 10,000-row ceiling per CSV file in the native wizard; and a Created Time field that is system-managed on most modules and cannot be overwritten through the standard import path1124.

Workflow Rules, Assignment Rules, Macros, Blueprint state machines and SLA escalations do not import — they are rebuilt from documentation. CSAT history via Happiness Ratings is similarly not migratable as historical scores. Teams that scope the rebuild work up front finish on time; teams that assume parity do not.

Zoho Desk's import is fast when the CSV bundle is clean and the Department/Layout/Agent scaffolding is built first — every shortcut on that scaffolding costs you in skipped rows.

The Zoho Desk data model you need to map into

Departments, Layouts, Threads, Custom Modules, and the duplicate-check fields you'll wire on every record — the destination schema decoded.

Zoho Desk is organised around the Department — the platform's primary organising unit, equivalent to what other helpdesks call a Brand or Workspace. A Department owns its own Layouts, Workflow Rules, Assignment Rules, SLAs, Macros, Blueprint processes and Knowledge Base sections. A Ticket belongs to exactly one Department; a Contact and Account can be shared across all Departments11.

Before mapping any source field, you need to know which destination module the row belongs in, which Department + Layout it inherits, and which value will serve as its match key. The table below summarises the modules a Zoho Desk migration will touch1137.

ObjectWhat it storesRequiredTier
TicketsCustomer support requests across all channelsSubject, Contact, DepartmentAll paid editions
ThreadsEmail replies and inbound channel messages on a TicketTicket reference, Author, Direction, ContentAll paid editions
Ticket CommentsPrivate notes and public comments by agentsTicket reference, Author, ContentAll paid editions
ContactsEnd-customer records (the requester on Tickets)Last Name, EmailAll editions
AccountsCustomer organisations (parent of Contacts)Account NameAll editions
Agents / TeamsInternal support users and team groupingsEmail, Last Name, Department membershipAll editions; light users on lower tiers
Knowledge Base ArticlesHelp Center content (categories, sections, articles, translations)Title, Section, Status (draft / publish / review)All paid editions
Products / Tasks / Events / CallsCatalogue and activity records on TicketsPer-module — see field requirementsAll paid editions
Custom ModulesCustomer-defined record types tied to a DepartmentSchema defined first; per-field requirementsEnterprise only

Records get matched on import by what Zoho Desk calls duplicate-check fields. The default is Email on Contacts and Agents and Account Name on Accounts. Ticket matching is more nuanced — the wizard treats every ticket row as new unless you provide an explicit external identifier mapped against the Ticket Number custom field or a Ticket External ID you have created and marked unique11.

Tickets, Knowledge Base Articles and Custom Modules do not carry a natural foreign-key — create a custom single-line field (commonly external_id), mark Do not allow duplicate values, and populate from the source platform's primary key. This becomes your reconciliation anchor and lets re-imports be idempotent rather than additive70.

Custom field types determine validation, storage and edition availability. The wizard accepts string, decimal, integer, currency, checkbox, picklist, multi-line and date / date-time fields on Contracts, Time Entry, Agents, Tickets, Contacts, Accounts, Products, Calls, Tasks and Events79. Custom fields are scoped to a Department — a custom field created on Tickets in the Sales Department is not available on Tickets in the Support Department unless explicitly added there7.

Field typeLimitNotes
Single-line text255 charactersPlain string; can be marked unique70
Multi-line (small / large / rich)2,000 / 32,000 / 50,000 charsEncryption supported on small only; large not filterable71
Number / Decimal / Currency / PercentUp to 16 digitsCurrency respects org base currency setup
Date / Date-TimeOrg timezoneDate format must match org locale or row rejects43
Picklist (single-select)Per-edition value count limitReference value can differ from display label
Multi-Select PicklistPer-edition value count limitArray format on import, e.g. [tag1,tag2,tag3]149
Checkbox / BooleanTrue / false onlyStored as 1 / 0
LookupOne target module per fieldPopulated by parent ID or unique field value
Custom field scopePer Department, per moduleAdding to second Department requires explicit re-creation7

Relationships in Zoho Desk are modelled mostly as Lookups. A Ticket has Lookups to one Contact, one Account, one Product, one Department and one Layout. The platform also ships a Parent-Child Ticketing extension that links a parent Ticket to one or more child Tickets — useful for incident grouping but not the same as a generic many-to-many relation50. Cascade delete is not native: deleting a parent record nulls the child Lookup rather than removing the child51.

Custom Modules participate in Lookups the same way standard modules do, with identical match semantics. They are Enterprise only, and their schema, Layouts and unique-ID fields must exist on the destination Department before any record can be imported737. There is no global cross-Department custom module — a Custom Module created in one Department is invisible to records in another.

Pre-migration prep — the work before you touch Zoho Desk

What must be true on the source, the destination, and across the team before the first row hits the Import wizard or Zwitch queue.

The single best predictor of a clean Zoho Desk migration is how much work happens on the source side before the first import button is pressed. Zoho's Assisted Migration Guide devotes most of its prep checklist to source-side hygiene — file naming, mandatory-field coverage, agent provisioning, picklist value alignment — because the wizard rejects rows quietly on any mismatch and surfaces the reasons only in Import History45.

Build the Departments, Agents and Layouts first. The data lands cleanly when the destination scaffolding already exists; it lands in the default Department and reassigns to the import user when it doesn't.

Treat the source export as raw material that must be shaped to Zoho Desk's expected formats — agent assignments resolved to a Zoho Desk email or Agent ID, ticket-status values converted to the Department's status picklist, tags formatted as array-bracketed lists, dates rewritten in the org locale format, and CSV files saved as UTF-8.

Source-side prep

  • Audit and dedup the source database before export. Zoho Desk's wizard offers Skip / Overwrite / Clone behaviour for duplicates48, but catching case-only email duplicates and trailing-whitespace duplicates in the source is faster than reconciling them inside Desk.
  • Convert source ticket-status values to the destination's status picklist in every Department. Article Status, for example, only accepts draft, publish or review — anything else rejects the row149. Status, Priority, Classification and any Custom Picklist on Tickets all need the same alignment.
  • Save every CSV as UTF-8 before zipping. Excel saves CSVs as Windows-1252 by default on Western locales; non-UTF-8 produces mojibake on accented characters and full row rejection on Asian-language records47.
  • Stamp a stable external ID on every Ticket, Article and Custom Module record in the source export — a UUID or the source platform's primary key. This is the value you populate into the destination's external-ID custom field and use as your reconciliation anchor70.
  • Format tags in array brackets — [urgent,high priority,refund] — separated by commas inside square brackets, on every Ticket row that carries tags149. The wizard rejects unbracketed comma-separated tag values.

Destination-side prep

  • Create a Sandbox from Setup → Data Administration → Sandbox on Enterprise. Sandbox supports change-set deployment back to production for Layouts, Layout Rules, Validation Rules, Fields, Assignment Rules, Workflow Rules, Macros, Skills, Blueprint and Supervise rules4041.
  • Build every Department that will own imported Tickets — Departments are the top-level container, and Tickets land in the default Department if the Department column on the import file is missing or unmappable149.
  • Provision Agents with the same email addresses they used in the source system. The wizard maps imported Agent rows to existing users when the email matches; unmatched agents need the Add New Agent dialog under Setup → Agents before import to avoid Ticket Owner falling back to the import user45152.
  • Pre-create every custom field per Department per module with the right type — Field Type cannot be changed after creation, so a Text field created when an Integer was needed has to be deleted and recreated9.
  • Build Layouts, Layout Rules and Validation Rules before importing Tickets — Validation Rules trigger on all fields during an update, even untouched ones42, which can cascade rejections across rows that should otherwise be valid.

People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — 24 to 72 hours, longer for live chat and phone — and communicate it to every team. Train agents on Zoho Desk's daily-workflow patterns, Blueprint transitions and Help Center publishing flow before go-live. A clean Zendesk-to-Desk move under 25,000 Tickets often lands inside two business days via Zwitch; a Salesforce Service Cloud migration with Custom Modules and KB translations runs two to four weeks10.

Import mechanisms: native wizard and Zwitch

Two paths in, each with different limits and shapes. Picking the wrong one is how mid-migrations stall at the ZIP-size ceiling.

Zoho Desk exposes two load paths and the right one depends on dataset size, channel mix, and whether the load must be re-run idempotently. The native Import wizard handles most loads under 10,000 rows per file. Zwitch, Zoho's assisted Bulk Data Migration service, handles large source-helpdesk transfers end-to-end.

Native Import wizard

The native Import lives at Setup → Data Administration → Import11. It accepts a single ZIP file containing one CSV per module — Tickets, Contacts, Accounts, Agents, Products, Tasks, Events, Calls, Custom Modules and Knowledge Base Articles all in one upload1145. Naming matters: the CSV name must match the destination module (e.g. Tickets.csv, Contacts.csv) for auto-mapping to fire; mismatched names land in the Unmapped Files bucket and need manual drag-to-mapped.

Hard limits: the ZIP upload caps at 30 MB total, each CSV inside caps at 10,000 rows, and only the .csv format is supported inside the bundle11. Domain-mapped portals additionally need third-party cookies enabled in the agent's browser, or the upload throws a session error. The wizard runs a sample of the first few rows for field-mapping review before committing, and surfaces an Error Log per file under Completed with error in Import History.

Duplicate handling is per-record: the wizard offers Skip (existing row wins, new row dropped), Overwrite (new row replaces existing values; new fields added if mapped) and Clone (a duplicate is created alongside the existing record)48. The right call: the native Import for one-shot loads under 10,000 records per module, or any time the Departments and Layouts are fully built and the dataset fits the ZIP ceiling.

Zwitch — assisted Bulk Data Migration

Zwitch sits under Setup → Data Administration → Data Migration and is the larger-scope tool. It is operated by Zoho's in-house migration team, not self-serve: you submit a request describing source platform and dataset, the team queues the job, and the migration runs in two phases — Initial Migration (Phase 1, all data in bulk) and a follow-up Delta phase that captures changes from your test-import window10.

Zwitch accepts file uploads up to 10 GB, with larger volumes routed through [email protected]10. The service explicitly supports Zendesk, Freshdesk, Salesforce Service Cloud, HappyFox, Help Scout and many other source platforms10. Migration cancellation is only allowed while the request status is Submitted in Queue; once the team has started, the run completes before changes are accepted.

Third-party staging tools

Tools like Help Desk Migration (the Migration Wizard SaaS at help-desk-migration.com), ClonePartner and KingswaySoft's SSIS components sit between source and Zoho Desk. They handle file generation, mapping and submission against the destination, and are often used where a customer warehouse holds the cleaned data and the tool feeds Desk. Pricing typically scales by record count.

Mapping your data into Zoho Desk

The longest section — because field mapping is where almost every Zoho Desk migration that fails actually breaks.

Mapping is where every helpdesk migration earns its scars. The decisions in your mapping spreadsheet determine whether agents trust ticket history on day two, whether SLA reports work on day five, and whether the Help Center has the right articles on day thirty.

Work module by module in import order: Agents first (so Ticket Owner resolves), then Accounts (so Contacts can associate), then Contacts (so Tickets can reference), then Tickets, then Threads and Ticket Comments, then Tasks and Calls, then Knowledge Base Articles, then Custom Modules. The Zoho assisted-migration checklist enforces this order through its file-pattern naming (Agents_XX.csv, Accounts_XX.csv, Contacts_XX.csv, Tickets_XX.csv, Threads_XX.csv, TicketComments_XX.csv)45.

Contacts and Accounts

Common source → Zoho Desk Contact mapping
SourceDestinationNote
emailEmail (duplicate check field)Lowercased pre-import; primary match key on upsert
first_name / last_nameFirst Name / Last NameLast Name is mandatory on Contacts and Agents45
phone / mobilePhone / MobileNormalise to E.164; no enforced format
company / organisationAccount Name (Lookup)Import Accounts first; populate Lookup by Account Name or ID
created_atCustom Date-Time field (Legacy Created Date)Created Time on Contacts is system-managed24
external system primary keyExternal ID (custom single-line, marked unique)Reconciliation anchor for re-runs70

Ticket history — threads, comments, status, priority, channel

Tickets are the centre of any helpdesk migration, and Zoho Desk splits a Ticket's conversation into three related records: the Description (set at ticket creation), one or more Threads (email replies, chat messages, social inbound — the customer-facing conversation), and Ticket Comments (private notes between agents, plus public comments)121. A faithful migration moves all three.

The assisted-migration file pattern reflects this: Threads_XX.csv carries threadExtId, ticketExtId, author, direction (Inbound / Outbound), content (HTML supported), and createdTime; TicketComments_XX.csv carries commentExtId, ticketExtId, author, content, isPublic (true / false), createdTime45. Threads accept the original timestamp in the createdTime field — this is one of the few places where backdating works natively rather than via a Legacy custom field.

Common source → Zoho Desk Ticket mapping
SourceDestinationNote
ticket_id / case_numberTicket Number / External IDBuilt-in Ticket Number is auto-assigned; carry the source ID in a custom External ID149
subjectSubjectRequired; truncated to 255 chars
statusStatus (picklist per Department)Must exist on Department's Status picklist — Open, On Hold, Closed, etc.42
priorityPriorityPicklist; map Low / Medium / High to destination values
channel / sourceChannelEmail, Web, Phone, Chat, Twitter, Facebook, Forum, Forms
assigned_to / ownerTicket Owner (Assignee)Must be agent email or Agent ID, not agent name149152
requesterContact Name (Lookup)Import Contacts first; populate by email or Contact ID
department / brandDepartmentMandatory; falls back to default Department if unmapped149
tagsTagsArray bracket format on import: [urgent,refund,billing]149
created_atCustom Date-Time (Legacy Created Date)Created Time is system-managed; original date import requires support ticket158

Knowledge Base — articles, categories, translations

Zoho Desk's Knowledge Base is structured as Categories → Sections → Articles, with each article carrying a Status of draft, publish or review149. The native Import path is under Setup → Data Administration → Import → Import Articles, where you select the target Section and upload a CSV; Zwitch imports articles, sections and categories together when migrating from a supported source10.

Translations are the trap: each translated article is a separate record linked to its master article via a language field. The Migration Wizard SaaS at help-desk-migration.com explicitly lists language versions of knowledge base articles as a paid add-on for Zendesk, Salesforce Service Cloud, Intercom and Freshdesk source platforms — the native wizard handles primary-language articles, but multilingual stacks need either Zwitch or a third-party tool.

Article body is HTML — preserve formatting on export from the source. Inline images need to migrate as either external links or as Zoho-hosted media uploaded and then referenced in the article body. The migrate-inline-images-as-attachments option is available on Zwitch and on Migration Wizard for sources like Jira Service Management, HelpScout, Freshservice, Gorgias and HubSpot Service Hub.

Macros, Workflow Rules, Assignment Rules, Blueprint — rebuild, not migrate

Macros (one-click ticket updates such as Send Acknowledgement + Set Priority = High), Workflow Rules (time-based or event-based automations), Assignment Rules (routing to agents, teams, or skills), and Blueprint (visual state machines that enforce ticket-status transitions) do not import120. Every one of them must be rebuilt from documentation in the destination Department under Setup → Automation and Setup → Process Management.

Sandbox helps here: build Macros, Workflows, Assignment Rules and Blueprint flows in a Sandbox copy of the destination, validate against the imported sample data, then deploy via change-sets to production41. Zoho's pre-built Gallery Functions ship ready-to-use Deluge scripts for common patterns (Create CRM Contact for New Ticket, Auto-Merge Tickets with Identical Subject + Contact, Send Auto-Replies Outside Business Hours), which removes some rebuild surface38.

SLAs, escalations, and CSAT history

SLAs in Zoho Desk are configured per Department under Setup → Service Level Agreements, with rule criteria (priority, channel, contact tier), response-time targets and escalation actions tier-gated to Professional and Enterprise editions124. SLA timer values on existing tickets do not migrate — Desk recomputes SLA targets at the moment a ticket is created or reopened against the rules in force at that moment.

CSAT history via Happiness Ratings is similarly not migratable as historical scores. If you need historical CSAT for reporting continuity, the pattern is to create custom number and text fields on the Ticket (Legacy CSAT Score, Legacy CSAT Comment) and populate from the source export. Going forward, Desk's native Happiness Ratings collects new responses through the Help Center and email-signature widget.

Multi-channel inbox — email, web forms, chat, phone, social, ASAP

Zoho Desk handles inbound channels through Setup → Channels, configured per Department: Email (forwarding or SMTP/IMAP); Web Forms generated under Setup → Channels → Web Forms and embedded on customer sites; Chat through Zoho SalesIQ; Phone through Zoho Voice or third-party telephony (JustCall, Twilio, RingCentral); Social through Twitter, Facebook, Instagram; and the ASAP embeddable customer self-service widget that exposes Knowledge Base + ticket submission directly inside a product or website97.

Channel configuration does not migrate — the inboxes, forwarding rules, web-form code snippets, chat-widget keys and phone numbers are all re-provisioned in the destination Department after the data load. Critically, do not switch DNS or email forwarding to Desk until the import is validated, or you will get new tickets landing in an unvalidated environment alongside the migrated history.

Files and attachments

Attachments do not import in the CSV flow. The supported paths are: (a) Zwitch, which transfers attachments with their parent Ticket as part of the assisted migration; or (b) external storage links in a custom URL field. Maximum file upload size is 1 GB per attachment99, with external file sharing supported via Zoho WorkDrive. Email-template attachments cap at 3 MB across files.

Attachment Control under Setup → Security and Compliance lets admins restrict file types101 — apply these rules after the import, not during, or ingestion may fail on blocked types. For large attachment estates (hundreds of GB of call recordings or signed PDFs), the pattern most teams adopt is: migrate the most-referenced subset inline via Zwitch, and store the rest in S3 or WorkDrive with deep links in a custom URL field.

Audit trail, ownership and original timestamps

Zoho Desk's standard Created Time and Modified Time fields are system-managed on most modules and cannot be overwritten on import — they stamp to the moment the row was processed156. The historical Created Time and Closed Time can be imported, but only via the assisted route by emailing [email protected] and requesting the system override — it is not a self-serve option in the wizard158.

Ticket Owner during import requires the agent's email address or Agent ID, not the agent's name. Rows that name a non-existent agent silently fall back to the import-running user as Ticket Owner152. The same fallback applies to Created By and Modified By on records — without a pre-existing matching agent, every imported row credits its work to whoever ran the import152.

Audit Log under Setup → Privacy and Security → Audit Log captures Add, Update, Delete, Export, Download and channel-availability actions per user, with date, IP address, Department and Entity131. Audit log export is available as CSV for up to 30 days at a time, capped at 50 exports per day per admin150. There is no native bulk export of three years of audit history — long-horizon compliance archives need to be built incrementally.

The pitfalls that derail Zoho Desk migrations

Eight specific failure modes — ranked by impact, each tied to the exact Zoho Desk mechanism that breaks.

Validation and cutover

What to verify after the import job, in what order — and how to fail safely when something is wrong.

Validation is the bridge between the import finishing and agents being allowed in. The pattern that works on Zoho Desk is three stages: a Sandbox or Sample Migration dry-run on 5–10 percent of tickets with stakeholder spot-checks; a production load with real-time monitoring of Import History per module; and a 30-day post-migration data-quality audit. Department leads verifying their own tickets is the most reliable signal — they know what right looks like.

Build a reconciliation queries spreadsheet that compares source and destination counts. Anything outside a 0.5 percent variance gets investigated before agents get login access.

  • Total Tickets per Department per Status imported vs source — the wizard's Import History under Setup → Data Administration → Import History lists added, updated and skipped counts per file, retained for 60 days136.
  • Total Threads and Ticket Comments per Ticket vs source — a major gap signals that thread/comment association via ticketExtId broke during import.
  • Total Contacts and Accounts vs source, minus deliberately excluded rows (role-based emails, archived accounts, opt-outs).
  • Knowledge Base Article count per Category per Section vs source — and Status (draft / publish / review) distribution to confirm publication state round-tripped.
  • Agent ownership distribution — group by Ticket Owner and confirm no Department landed with the import-running user owning the majority of tickets (the silent fallback signature152).
  • Tag coverage — count distinct tags imported vs source, and inspect tickets where tag values look truncated (the array-bracket transform failed).
  • Attachment count per Ticket vs source — Zwitch reports this in its migration report; native-wizard migrations must reconcile by spot-checking the Attachments tab on a sample.

On top of reconciliation, run a manual spot-check protocol: pick 30 random Tickets across Departments and verify every field plus the full Thread + Comment graph against the source UI. Trace five high-priority Tickets end-to-end, including attachments and Contact / Account associations. If a discrepancy shows up in three or more of the 30, halt the load, fix the root cause, and re-import the affected rows by external ID.

Zoho Desk ships an Undo / Revert option in Import History — successful or completed-with-error imports can be reverted within two weeks130. The catch is that only created records can be undone; updated records cannot, because original values are not retained. Mixed Create / Update imports support partial revert only on the Create side130. Beyond two weeks, stamp every imported row with a custom Import Batch ID field and bulk-delete by that ID if catastrophe strikes.

Audit Log under Setup → Privacy and Security → Audit Log tracks every Add, Update, Delete and Export action per user with timestamp and IP, retained on a rolling window131. Export to CSV is capped at 30 days per export and 50 exports per day per admin150. For long-horizon compliance, build a scheduled export to your own storage rather than relying on in-product retention.

Cutover sequencing: (1) source goes read-only; (2) final delta export captures changes from the test-import window; (3) delta is imported via Zwitch Phase 2 or the same wizard flow; (4) reconciliation runs against the delta; (5) channel cutover — email forwarding, web-form snippets, ASAP widget keys and chat / phone routing are switched to Desk; (6) agents get login access with a 48-hour hyper-care window; (7) source decommission is scheduled 30 to 90 days out, never same-day.

Migration partners and tools

Authorized Zoho Partners, Zwitch, specialist migration SaaS — what each is good for and how to choose.

The Zoho Partner Program credentials Authorized, Advanced and Premium Partners through certifications, customer count and revenue tiers, and exposes them through Find a Zoho Partner at zoho.com/partners116. For Zoho Desk migrations specifically, partners with explicit Zendesk-to-Desk, Freshdesk-to-Desk or Salesforce Service Cloud-to-Desk practices tend to ship cleaner than generalist implementation shops.

Zoho also runs Zwitch, the in-house Bulk Data Migration service at [email protected]10. Zwitch is typically included at no incremental fee on Enterprise contracts and handles end-to-end transfers from Zendesk, Freshdesk, Salesforce Service Cloud, HappyFox, Help Scout and other sources, with uploads up to 10 GB. The trade-off is throughput — the in-house team is best for clean schemas; deeper Custom Module work, multi-language KB and CSAT preservation tend to land with certified partners.

On the specialist-SaaS side, Help Desk Migration (the Migration Wizard at help-desk-migration.com) and ClonePartner both expose self-serve and assisted Zoho Desk migration flows with paid add-ons for KB translations, inline-images-as-attachments, and migration of side conversations and call recordings. They are commonly used where the source platform is supported but the dataset has shape constraints (multilingual articles, very large attachment estates) that the native wizard cannot handle.

For ongoing post-migration sync — keeping Zoho Desk in step with Zoho CRM, Books, Projects or external systems — Zoho's own integrations and the Deluge custom-function layer cover most patterns, with Workato, Make and Zapier filling the gap on third-party tools.

Managed-migration cost ranges vary widely. A clean Freshdesk-to-Desk or HappyFox-to-Desk move under 25,000 Tickets with standard modules and no KB translations often lands in the $2,500–$8,000 range with setup fee plus per-module pricing on a specialist SaaS, or runs through Zwitch at no incremental fee on Enterprise. A Zendesk-to-Desk project with Custom Modules, multilingual KB and integration re-pointing typically runs $15,000–$80,000, driven by ticket volume, attachment depth, language count and source-automation rebuild scope.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Zoho Desk migrations and handles the Department + Layout + Agent scaffolding, picklist alignment, External ID match-key wiring, Threads-and-Comments association, the Created-Time-to-Legacy-Date pattern, Macro / Workflow / Blueprint rebuild scoping, and the validation work described in Sections 5 and 7. Pricing is fixed-fee by ticket count and source platform, with separate line items for KB translations, Custom Modules and CSAT depth.

This is one of several legitimate paths — the right choice depends on whether the team wants a Premium Partner, Zoho's in-house Zwitch service, a specialist migration SaaS, or a fixed-fee vendor. [Explore FlitStack →](/contact)

Zoho Desk migration checklist

Sequenced punch list for moving helpdesk data into Zoho Desk across Departments, Layouts, Blueprints, Macros, Workflow Rules, SLAs, and Help Center — covering export, transform, sandbox test, cutover, and validation. Typical timeline: 4–12 weeks.

0. Decide & Plan10 tasks
  • Document the in-scope Zoho Desk modules. List every standard module you will load (Tickets, Threads, Ticket Comments, Contacts, Accounts, Agents, Teams, Products, Tasks, Events, Calls, Time Entry, Contracts, Articles, Custom Modules). Anything not on this list is out of scope.If skipped: Late-discovered modules force schema changes mid-migration and trigger re-runs of upstream transform jobs.
  • Pick the Zoho Desk edition before any provisioning. Edition gates Sandbox availability (Enterprise), Blueprint state machines (Standard and above), per-Department Layouts (Professional and above), Multi-Department support, Zia AI (Enterprise), and Zoho Voice integration (Professional and Enterprise).If skipped: Choosing a lower edition than the data requires blocks Sandbox testing, per-Department customization, and Blueprint-driven state machines.
  • Define the historical-ticket scope window. Decide how many years of closed Tickets, Threads, Ticket Comments, Calls, and Knowledge Base Articles are in scope. Decide whether attachments are in scope or stay in the legacy archive.
  • Decide the historical-timestamp strategy for Tickets. Zoho Desk's Zwitch can preserve original Created Time and Closed Time on imported tickets; the standard UI Import cannot. Pick a path now: Zwitch with timestamp preservation, UI Import with Source Created Date custom field, or accept that Created Time equals migration date.If skipped: Without a written strategy, ticket-aging reports and SLA-historical analysis will reset on cutover day.
  • Document data-residency and compliance requirements. Zoho operates regional data centers (US, EU, IN, AU, JP, CN, CA, SA). Confirm which DC the org must live in, GDPR enablement for Contacts, SOC 2 + HIPAA scope (annual audit window Dec–Nov), and retention policies.If skipped: Provisioning in the wrong DC cannot be reversed by moving data later — it requires a fresh org and a second migration.
  • Decide the Department topology. Zoho Desk uses Departments as the primary organizing unit (replacing the Brand/Workspace model in other helpdesks). Decide whether to migrate to one Department or split by business line, product line, or region. Custom fields are Department-scoped.If skipped: Loading all tickets into one Department when the business needs multiple Departments later forces a second migration to re-distribute records.
  • Name a single accountable migration owner (DRI). One person signs off on Phase 0, Phase 4 sandbox results, and Phase 6 reconciliation. No committee.
  • Set the cutover date, time, and source-system freeze window. Pick a low-volume window. Confirm with support, customer success, and ops leads that no campaigns or product launches overlap.
  • Write the success criteria. Concrete pass/fail statements: total ticket count matches source within 0.1 percent, every open ticket is assigned to an agent, SLA clock on open tickets reflects the migrated due date, every active agent can log in and see their assigned tickets.If skipped: Without written criteria, the migration drags on indefinitely because nobody can declare it done.
  • List explicitly out-of-scope items. Examples: source-system custom dashboards (rebuild manually post-cutover), source-system trigger rules (rebuild as Zoho Workflow Rules and Macros), deleted tickets in the legacy recycle bin, CSAT historical scores (Zoho Desk Happiness Ratings cannot be backfilled).
1. Pre-Migration Prep27 tasks
  • Export current record counts per source object as a baseline. Capture exact counts for Tickets, Threads, Comments, Contacts, Accounts, Agents, KB Articles, Tasks, Calls, Events. This is the reference number for Phase 6 reconciliation.If skipped: Without a baseline, you cannot prove what was lost in transit.
  • Run deduplication on source Contacts using email as the match key. Zoho Desk identifies Contact duplicates by email on import. Resolving duplicates upstream is faster than untangling them after load.If skipped: Duplicate Contacts split ticket history across two records and break Contact-level reporting.
  • Run deduplication on source Accounts using domain as the match key. Pick one canonical Account per company; merge child Contacts and Tickets onto it.
  • Standardize email casing and trim whitespace across all email fields. Convert to lowercase. Strip leading and trailing spaces. Email is the matching key for Contact-to-existing-record resolution in Zoho Desk.
  • Identify and fix records missing required Zoho Desk fields. Required on Ticket import: Subject, Department, Contact Name (mapped via email or agentExtId), Status. Required on Contact: email. Required on Agent: agentExtId, Last Name, Email.If skipped: Rows with empty required fields are dropped to the error log and do not appear in the destination.
  • Inventory source custom fields per ticket type. Export field name, type, picklist values, validation rules, and required flag. This becomes the source side of the Phase 3 mapping spreadsheet. Note that Zoho Desk custom fields are Department-scoped.
  • Document source ticket status values and lifecycle transitions. Capture every distinct status value the source uses, plus which transitions are allowed. This becomes the input for the destination Blueprint and Status picklist.If skipped: Missing source statuses cause ticket rows to be skipped with a picklist-validation error during import.
  • Document SLA policies, business hours, and holiday calendars on the source. Zoho Desk SLAs are per-Department. Capture per-policy response time, resolution time, escalation tiers, and operational hours so they can be rebuilt in Phase 7.
  • Inventory source Macros, Trigger Rules, and Automations. Capture the rule name, trigger conditions, and actions. These do not migrate and must be rebuilt as Zoho Desk Macros, Workflow Rules, Assignment Rules, or Blueprints.
  • Provision the production Zoho Desk org in the chosen data center. Confirm the DC URL (.com, .eu, .in, .com.au, .jp, .com.cn, .ca, .sa) matches the Phase 0 residency decision.
  • Provision a Sandbox org from production. Sandbox is available on Enterprise. Use Setup > Data Administration > Sandbox to clone Layouts, Layout Rules, Validation Rules, Fields, Assignment Rules, Workflow Rules, Macros, Blueprints, and Skills.If skipped: Skipping Sandbox forces every test to happen in production where errors are visible to end users.
  • Create every Department that Phase 0 identified. Each Department gets its own Layouts, custom fields, Workflow Rules, Assignment Rules, SLAs, and Channels. Build them all before any import.If skipped: Loading tickets into a Department that does not exist places them in the default Department and forces a manual move at volume.
  • Create all destination Agents with email matching source-system agent emails. Matching emails lets the importer resolve Ticket Owner during load. Use Setup > Agents > New Agent or upload the agentExtId-keyed CSV described in the Zwitch guide.If skipped: Mismatched agent emails leave Ticket Owner blank and force a second pass to reassign at volume.
  • Build Teams and assign Agents to them. Teams cannot be re-imported by every migration path. Create them now via Setup > Teams > New Team and turn on the Team Assignment setting before any ticket load.
  • Set Roles and Profiles before any import. Roles control record sharing; Profiles control field-level permissions including the Import Records permission required to run the import itself.
  • Set org-level Time Zone, Date Format, Business Hours, and Holiday Lists. These affect parsed timestamps and SLA clock calculation. Lock them before any sandbox test.If skipped: Changing time zone after import does not retroactively re-stamp records and creates an off-by-N-hours bug on every datetime field.
  • Create every Ticket Layout per Department before any import. Tickets can only be imported into the default Layout per Department during the UI Import path. Decide naming and field placement now; field placement cannot easily be changed mid-load.
  • Create every custom field on every module before any import. Zoho Desk cannot create destination fields on the fly during import. Importing into a field that does not exist drops the column silently.If skipped: Silent column drops are the single most common cause of Phase 6 reconciliation gaps.
  • Create every picklist value, Status value, and Resolution code used by any record. Use Setup > Customization > Layouts and Fields. Status values must include every source status plus any new ones Phase 0 added.If skipped: Unknown picklist values are rejected row by row and the row is skipped to the error log.
  • Disable Blueprints, Workflow Rules, Assignment Rules, and Validation Rules before bulk import. Inserts during bulk load otherwise trigger workflows that send auto-acknowledgements, fire SLA timers, and move tickets into the wrong Blueprint state.If skipped: An active auto-acknowledgement workflow during a 50,000-ticket load emails every contact at cutover.
  • Pause Validation Rules specifically. Zoho Desk's Validation Rules fire on every field during an update, including fields the import did not touch. Disable them during load and re-enable in Phase 5.If skipped: Active validation rules can reject otherwise-valid imported records on unrelated field-state conditions.
  • Create a Source ID custom field on every module you will import. Populate it with the source-system primary key so reruns are idempotent and post-migration audits can trace back to the legacy record.If skipped: Without a Source ID, re-running a failed import duplicates every record.
  • Build Help Center Categories and Sections before importing Articles. Zoho Desk KB hierarchy is Categories > Sections > Articles. Articles cannot be imported into a Section that does not exist. Enable language locales now if multilingual KB is in scope.If skipped: Articles imported without a Section land in an unsorted area and require manual re-filing per article.
  • Decide and configure the Assignment Rule strategy. Three load-time options exist: assign Ticket Owner by agentExtId or email in the CSV, route via Assignment Rule conditions, or load with no owner and use Round Robin post-load.
  • Announce the source-system freeze window to all agents and end users. Pin the announcement in chat and email it at T-7 days, T-1 day, and T-1 hour.
  • Schedule Zoho Desk training sessions segmented by role. Agents, supervisors, and admins each need a focused 30 to 60 minute session within 5 business days of cutover.
  • Designate first-responder support contacts for the 48 hours post-cutover. At least one Zoho Desk admin on call. Name them publicly.
2. Source Export16 tasks
  • Export Tickets as CSV with all standard and custom fields. Include source primary key (becomes Source ID), Subject, Description, Status, Priority, Channel, Department, Contact email, Account, Ticket Owner email, Created Time, Closed Time, Due Date, Resolution.If skipped: Missing Channel or Department columns force every ticket into the default Department and a single channel.
  • Export Threads as a CSV linked to parent Ticket Source ID. Threads are the chronological email or chat exchanges on a ticket. Include sender, recipient, content, content type (HTML or plain), direction, and timestamp.If skipped: Importing tickets without Threads loses the entire conversation history and leaves agents with only the original Description.
  • Export Ticket Comments as a separate CSV linked to parent Ticket Source ID. Comments are the internal-note layer (distinct from Threads). Include author email, body, isPublic flag, and timestamp.
  • Export Contacts as CSV with all fields plus the Account ID lookup. If skipped: Exporting Contacts without the Account foreign key forces a manual re-association later, which is error-prone at volume.
  • Export Accounts (Companies) as CSV with all fields. Include phone, website, billing/shipping address, industry, and any custom Account fields.
  • Export Agents with email, Role, Profile, Department associations, Team, and active flag. Use the Zwitch-prescribed format if Zwitch is the planned path: agentExtId, Last Name, First Name, Full Name, Email.
  • Export Knowledge Base Articles, Categories, and Sections as three CSVs. Articles must reference Section ID and Category ID. Article Status field accepts only [draft, publish, review].If skipped: Articles with a Status value outside the allowed three values are rejected at import.
  • Export Article translations as a child CSV linked by Article Source ID. Each translation has its own title, body, and locale. Required only if multi-language KB is in scope.
  • Export Tasks, Events, and Calls as three separate CSVs. Each has a different schema in Zoho Desk. Include the parent record ID (Ticket Source ID or Contact email).
  • Export Products and Contracts if in scope. Both are standard Zoho Desk modules with their own field set.
  • Export ticket Tags as a parallel CSV. Tags must be supplied in array format like [urgent,high-priority,refund] on the Ticket CSV row. A parallel export simplifies dedup and normalization.
  • Export attachment metadata: file name, size, MIME type, parent record ID. Separate file from metadata; both are required at re-upload time.
  • Download attachment binaries to a staging bucket. Per-record attachment size cap varies by edition. Flag any oversize file for the Phase 3 decision.If skipped: Files larger than the per-file cap will not load and silently leave records unlinked.
  • Export source SLA policies, Business Hours, Holiday Lists, and Trigger Rules as a reference document. These do not migrate. They will be rebuilt manually as Zoho Desk SLAs, Workflow Rules, Macros, and Assignment Rules in Phase 7.
  • Capture screenshots of source dashboards, reports, Macros, Trigger Rules, and Automations. Reports and Automations do not migrate. The screenshots become the rebuild spec for Phase 7.
  • Record the exact UTC timestamp of each export. This is the baseline for the Phase 5 delta export.
3. Transform & Map28 tasks
  • Build a master mapping spreadsheet covering every source field. Columns: Source Module, Source Field, Source Type, Destination Module, Destination Field, Destination Type, Destination Department, Transformation Rule, Required (Y/N), Upsert Key (Y/N), Notes.If skipped: Without a single mapping document, transform logic drifts between engineers and reconciliation finger-pointing becomes unavoidable.
  • Confirm field-type compatibility row by row. Zoho Desk does not let you change field type after creation. A source Text field cannot be loaded into a destination Integer field; either change the destination field type now or transform the source value.
  • Decide the dedup behavior per module: Skip, Overwrite, or Clone. Zoho Desk import offers all three. Skip leaves the destination record untouched, Overwrite replaces fields with import values, Clone creates a duplicate. Document the choice per module.If skipped: Choosing Clone by accident on a re-run creates duplicate Contacts, Accounts, and Tickets.
  • Decide what to do with source fields that have no destination equivalent. Three options per field: drop, create a custom field, or concatenate into the Description.
  • Resolve every picklist value mismatch. Source 'New' to Destination 'Open'. Build a value-translation lookup that maps every distinct source value to a valid destination value before export. Article Status only accepts [draft, publish, review].If skipped: Mismatched picklist values cause row-level skips at insert time, with the row reported in the import error log but not loaded.
  • Map Profiles and Roles between source and destination. Source 'Agent' to Destination 'Support Agent' Profile, for example. This drives the Owner assignment.
  • Convert all dates and datetimes to ISO-8601. Zoho Desk import rejects ambiguous formats like DD/MM/YYYY. Use yyyy-MM-dd for Date and yyyy-MM-ddTHH:mm:ss+/-hh:mm for DateTime.If skipped: Date-format mismatches cause the entire CSV column to be rejected with no clear row-level diagnostic.
  • Re-encode every CSV as UTF-8. Zoho importer requires UTF-8. Files exported from older systems often land as Windows-1252 or UTF-16; verify with a hex check on the byte-order mark.If skipped: Non-UTF-8 files convert accented characters to mojibake or ASCII escape codes.
  • Truncate text fields that exceed Zoho Desk character limits. Plain Text small caps at 2,000 characters. Plain Text large caps at 32,000. Rich Text caps at 50,000. Single-line picklist caps at 120 characters. Decide whether to truncate or split oversize values.If skipped: Rows exceeding field width are rejected at import time.
  • Escape commas, quotes, and newlines in long-text fields. RFC 4180 quoting: wrap any field containing a comma or newline in double quotes and double any embedded double quotes.
  • Format Tags as a bracketed comma-separated array per Ticket row. Zoho Desk expects tags in the form [urgent,high-priority,refund] inside a single CSV cell.If skipped: Tags passed as plain comma-separated strings without brackets are rejected and the ticket row imports without tags.
  • Compress all CSV files for one module into a single ZIP per Zwitch / UI Import rules. Only ZIP-of-CSVs is accepted via the UI Import. ZIP file ceiling is 30 MB; per-CSV-file ceiling is 10,000 rows or 30 MB. Split larger datasets into multiple ZIPs and run sequential imports.If skipped: Oversize ZIPs are rejected by the UI Import with no row-level diagnostic.
  • Stage attachment archives by parent Ticket Source ID. Bulk attachment loads walk per-ticket; staging by parent ID lets the load run deterministically.
  • Implement the historical-timestamp strategy chosen in Phase 0. Zwitch can preserve original Created Time and Closed Time. UI Import cannot — populate a Source Created Date custom field per module and use it for reporting.If skipped: Reporting on Created Time when UI Import was used will show every ticket dated to migration day, destroying time-series trend analysis.
  • Set Ticket Owner via agent email or agentExtId on every Ticket row. Per the Zoho Desk Import documentation: Ticket Owner must be specified using the agent's email address or Agent ID, not the agent's name. Agent name is rejected.If skipped: Loading Ticket Owner as the agent's display name leaves every ticket unassigned and forces a second pass.
  • Decide the attachment strategy. Option A: re-upload binaries into each ticket. Option B: store binaries in Zoho WorkDrive and link via a URL custom field. Option B preserves storage quota.If skipped: Re-uploading 100 GB of attachments into a Standard org saturates storage and blocks new records.
  • Resolve Ticket-to-Contact relationships via Contact email. Zoho Desk auto-links Tickets to existing Contacts on email match. Load Contacts first so the link resolves.If skipped: Loading Tickets before Contacts creates orphan Tickets with a placeholder Contact that must be merged later.
  • Resolve Ticket-to-Account relationships via the Contact's Account. Zoho Desk infers the Account from the Contact in most cases. Load Accounts first, then Contacts (with Account email-domain match), then Tickets.
  • Plan Parent-Child Ticket linking for related tickets. Zoho Desk supports a Parent-Child relationship via the official extension. Linking is not supported in the UI Import — plan to perform the link step programmatically after the main load.If skipped: Skipping the parent-child link step leaves duplicate-ticket clusters that the support team has been manually merging.
  • Reassemble Ticket Threads and Comments per parent Ticket. Threads carry the email/chat conversation; Ticket Comments carry agent notes. Both are child objects keyed off Ticket Source ID and must load after the parent Ticket. Preserve thread sequence and sender direction (inbound vs outbound).If skipped: Threads loaded out of sequence display in the wrong order in the agent UI; comments loaded as Threads break public/private visibility.
  • Build the Help Center hierarchy: Categories, then Sections, then Articles, then translations. Each layer references IDs from the previous layer. Articles must reference an existing Section. Translations must reference an existing Article and a supported locale.If skipped: Loading Articles before Sections leaves orphan Articles in an unsorted area that has to be re-filed manually.
  • Rebuild Macros, Workflow Rules, Assignment Rules, and Blueprints as Zoho-native objects. Source-system trigger rules and macros do not migrate. Use the Phase 2 screenshots as the spec. Macros run on demand; Workflow Rules fire on create/edit/time; Assignment Rules route Tickets; Blueprints enforce state transitions.If skipped: Skipping this transform leaves the helpdesk with no automation on cutover day and forces agents to do everything manually.
  • Plan Blueprint state placement for imported Tickets. If a Blueprint governs Tickets in production, every imported Ticket must land in the state matching its Status. Disable the Blueprint during import, then run a state-correction pass post-load to transition tickets into the correct state.If skipped: An active Blueprint rejects Status values that violate transition rules, causing partial imports.
  • Rebuild SLA policies per Department, with response and resolution targets plus escalation tiers. Zoho Desk SLAs are Department-scoped. Rebuild Business Hours and Holiday Lists first; SLAs reference them.If skipped: Loading open tickets before SLA policies are active means their SLA clock starts from migration day rather than original Created Time.
  • Recognize that CSAT / Happiness Ratings cannot be backfilled. Zoho Desk Happiness Ratings are captured via survey response and cannot be inserted historically. Decide whether to load source CSAT scores into a custom 'Migrated CSAT' field for historical reference or accept that CSAT history lives only in archived exports.If skipped: Customer-success reports that depend on Happiness Ratings will show zero for the pre-cutover window.
  • Plan the multi-channel inbox configuration: email, web forms, SalesIQ chat, Zoho Voice, social, and the ASAP widget. Each channel needs its own setup: email forwarding addresses or IMAP, embedded web form on the customer site, SalesIQ brand and tracking code, Zoho Voice number assignments, connected social profiles, and the ASAP widget snippet for in-app self-service.If skipped: Cutting over before channels are wired means inbound tickets via the old channels stop arriving the moment the source freeze starts.
  • Recompute SLA clocks for open Tickets at cutover. For each open Ticket, compute the elapsed time since source Created Time and seed the new SLA Due Date so the clock resumes correctly rather than restarting.If skipped: Restarting the SLA clock on cutover hides every breached ticket and makes the team look better than they are.
  • Map source Department / Brand / Workspace concept onto Zoho Desk Departments. Zoho Desk Departments replace what other helpdesks call Brands or Workspaces. Apply the topology from Phase 0 uniformly on every Ticket row before export.
4. Sandbox Test Migration15 tasks
  • Load a 1–5 percent representative sample of every in-scope module into Sandbox. Match the production method exactly (UI Import or Zwitch). Sandbox results only predict production if the load path is identical.
  • Validate field-by-field on 10 random Sandbox Tickets per Department. Open each Ticket in the agent UI and compare every field, every Thread, and every Comment to the source export. Document any discrepancy.If skipped: Sampling fewer than 10 records misses field-level drops that only surface on certain ticket subtypes.
  • Test Thread ordering and Comment visibility on at least 5 Sandbox Tickets. Confirm threads display in chronological order, sender direction is correct, and public/private comment flags landed as intended.If skipped: Misordered threads make the entire ticket history unreadable for agents.
  • Test KB Article import end to end: Category, Section, Article, Translation. Confirm each layer references the previous correctly and articles render with formatting intact.
  • Test the Channel picklist for every source channel value. Confirm every translated Channel value lands on a Ticket and the channel-volume report counts it.
  • Test datetime timezone handling on Tickets with near-midnight Created Time. Pick records near a day boundary to surface off-by-one-day errors.
  • Test special-character handling: emoji, accents, quotes, newlines. Pick at least 5 source records containing each.If skipped: Character-encoding bugs are invisible until a customer sees mojibake in a reply.
  • Test Attachment upload on at least 25 records. Verify file integrity (size matches source) and that the attachment appears on the ticket's Attachments related list.
  • Test a Zwitch sample migration if Zwitch is the planned path. Zoho recommends a Sample Migration before full-scale Zwitch migration. Use it to surface format issues without committing the full dataset.If skipped: Going straight to a full Zwitch run without a Sample Migration risks queueing the full load behind a fixable formatting bug.
  • Time the test runs and extrapolate to production volume. Job submit to completion times let you size the production cutover window realistically. Factor in Zwitch's queue-based prioritization if used.
  • Test the historical-timestamp strategy from Phase 3. Spot-check that Created Time and Closed Time landed as intended (preserved via Zwitch, or captured in Source Created Date via UI Import).
  • Have a support agent spot-check Tickets in Sandbox. Real agents find issues data engineers miss: missing thread context, wrong status, lost contact associations, broken inline images.
  • Have a KB content owner spot-check imported Articles. Validate Category placement, translation completeness, status (draft/publish/review), and image rendering.
  • Test the Revert flow on Sandbox. Zoho Desk UI Import supports Revert within a two-week window for the 'Create' action; updates cannot be reverted. Confirm the team knows how to invoke it.If skipped: Discovering revert limitations in production after a bad load means manual cleanup per record.
  • Get written sign-off on Sandbox results before scheduling production cutover. Email or ticket; do not proceed on verbal approval.If skipped: Verbal sign-offs evaporate when reconciliation surfaces an issue post-cutover.
5. Production Cutover14 tasks
  • Confirm source-system freeze. Inspect source-system audit logs to verify no record-modifying activity in the last hour.
  • Take the final delta export of every in-scope object. Same exporter as Phase 2, same field set, new timestamp suffix on filenames.If skipped: Skipping the delta loses every ticket created between Phase 2 export and cutover.
  • Confirm Blueprints, Workflow Rules, Assignment Rules, and Validation Rules are paused. Spot-check the Setup UI. Inadvertent activation between Phase 1 and Phase 5 is a common cause of surprise side effects.If skipped: An active auto-acknowledgement workflow at cutover sends thousands of accidental emails in minutes.
  • Confirm Agents and Teams already exist in production from Phase 1. Agents must exist before any Ticket Owner assignment can resolve.
  • Load parent objects before child objects. Order: Agents -> Accounts -> Contacts -> Products -> Categories -> Sections -> Articles -> Article Translations -> Tickets -> Threads -> Ticket Comments -> Tasks/Events/Calls -> Attachments. Each layer references IDs created in the previous layer.If skipped: Out-of-order loads leave lookup fields blank with no error and require a second pass to repair.
  • Use Skip behavior on re-runs to avoid duplicates. Zoho Desk Import dedup behaviors are Skip, Overwrite, Clone. Skip is the safe default on a re-run; Clone duplicates every record.If skipped: Choosing Clone on a re-run after partial failure duplicates every previously-loaded record.
  • Submit Tickets in batches that fit the ZIP ceilings. UI Import: 10,000 rows per CSV and 30 MB per ZIP. Zwitch: up to 10 GB per upload (contact Zoho support for larger). Split large datasets accordingly.If skipped: Oversize submissions are rejected without partial success.
  • Capture import job IDs, row counts, and error logs for every load step. Store these in a cutover run-book alongside timestamp and operator name. Zoho Desk surfaces error logs under Setup > Data Administration > Import History.
  • Cross-check destination row counts against source row counts at each step. Stop the cutover if any per-module count differs by more than the agreed tolerance (typically 0.1 percent).If skipped: Pushing through with an unexplained count delta makes Phase 6 reconciliation impossible.
  • If any step fails, halt — diagnose — fix the transform — re-run idempotently. Use the Skip dedup behavior on re-runs. Never push partial data through to the next step.
  • Run the Parent-Child Ticket link pass post-load. Walk the parent-child mapping table and apply the link per pair using the Parent-Child extension.
  • Re-enable Workflow Rules, Assignment Rules, Blueprints, and Validation Rules after all loads complete. Document the exact reactivation time in the run-book.
  • Run the Blueprint state-correction pass. Walk each Ticket through the appropriate state transition via Deluge function or manual UI action so it lands in the right Blueprint state.
  • Confirm imported tickets via the Import History page. Each successful import must be Confirmed in Setup > Data Administration > Import History; otherwise the two-week Revert window keeps the option to undo open.If skipped: Failing to Confirm leaves the load in a provisional state and a stray Revert click could delete the imported records.
6. Validate22 tasks
  • Compare total Ticket count per Department: source vs Zoho Desk. Use Zoho Desk reports filtered per Department. Investigate any delta beyond the agreed tolerance.If skipped: Unexplained deltas typically trace to skipped picklist values, missing required fields, or unmapped Departments.
  • Compare open vs closed Ticket counts. Catches Status-mapping errors that flip Tickets between open and closed.
  • Compare Thread counts and Comment counts. Per-ticket thread count and comment count must match source counts within tolerance.If skipped: Missing Threads are the most common cause of post-cutover support escalations because agents lose conversation context.
  • Compare KB Article counts per Section and per Status. Catches articles that landed in the wrong Section or got rejected due to disallowed Status values.
  • Spot-check 25–50 randomly selected Tickets field-by-field. Pick Tickets across Departments, agents, channels, and statuses. Open each in the agent UI and compare to the source export.
  • Verify all Source ID values are populated. Run a query for null Source ID across modules. Any null breaks future incremental syncs and post-migration audits.If skipped: Null Source IDs force every subsequent upsert to treat the record as new, creating duplicates.
  • Verify Ticket-to-Contact links resolve. Pick 30 random Tickets and confirm the Contact name and email match source.
  • Verify Contact-to-Account links resolve. Pick 20 random Contacts and confirm the Account association.
  • Verify Thread sequence and direction on 20 random Tickets. Confirm threads display chronologically and inbound/outbound direction matches source.If skipped: Reversed direction makes agents reply to themselves, which has happened in real migrations.
  • Verify Parent-Child Ticket links via the Parent-Child extension UI. Pick 10 known parent-child pairs and confirm both directions resolve.
  • Verify Attachment files open and download correctly. Click 10 random attachments per module and confirm file integrity.
  • Confirm the Source Created Date (or Zwitch-preserved Created Time) is populated everywhere. Run a query: count of records where the historical timestamp field is null should equal zero.
  • Run a GDPR compliance check on Contacts. Enable Compliance Settings on Zoho Desk if EU residents are in scope; verify the Data Privacy section appears on each Contact.
  • Export the Zoho Desk Audit Log for the cutover window. Navigate Setup > Privacy and Security > Audit Log and Export. Audit log export is limited to 30 days at a time and 50 exports per day.If skipped: Audit-log capture immediately post-cutover is the cheapest SOC 2 evidence; pulling it months later may not be possible.
  • Confirm data residency by reading the org's DC URL. Verify the org sits on the DC selected in Phase 0 (US, EU, IN, AU, JP, CN, CA, or SA).
  • Have 3–5 agents validate their day-to-day workflows in production. Hands-on: open a Ticket, reply via email, post an internal comment, run a Macro, resolve and close. Document every snag.
  • Run a sample SLA report and compare to source. Confirm SLA-breach counts and average response/resolution times reconcile within tolerance.
  • Validate the ASAP customer self-service widget on a test site. Embed the widget snippet on a staging page and confirm KB articles render and ticket submission works.
  • Validate the Zoho Desk mobile app shows migrated data correctly. Mobile uses different rendering paths and can surface field-permission bugs the web app hides.
  • Validate every active channel: email forwarding, web form, SalesIQ chat, Zoho Voice, social, ASAP. Send a test message through each. Confirm a Ticket is created with the correct Channel value and lands in the right Department.If skipped: An unconfigured channel means inbound customer messages vanish silently.
  • Document every UAT issue with severity and owner.
  • Get written sign-off from the migration sponsor. Email or ticket with the success-criteria document attached and each criterion marked pass.If skipped: Proceeding without sign-off leaves the project in a perpetual 'almost done' state.
7. Post-Migration Cleanup16 tasks
  • Communicate go-live to all agents and end users. Login URL, who-to-ask-for-help, link to the role-specific training recording, and the new helpdesk email address.
  • Run live training sessions segmented by role. Agents, supervisors, KB authors, and admins each get a 30–60 minute focused session.
  • Set the source helpdesk to read-only and announce the date. Read-only prevents accidental new writes that would never reach Zoho Desk.
  • Switch email forwarding from the source mailbox to the Zoho Desk Department email. Update DNS or mailbox forwarding rules so inbound email creates Zoho Desk tickets going forward.If skipped: Forgetting this step means customer emails to the support address vanish silently.
  • Rebuild Workflow Rules, Assignment Rules, and Macros. Source-system trigger rules do not migrate. Use the Phase 2 screenshots as the spec.
  • Rebuild Blueprint state machines for each Department. Map every Status value to a Blueprint state and define allowed transitions, mandatory fields per state, and SLA breach behavior.
  • Rebuild SLA policies with response and resolution targets and escalation tiers. Confirm Business Hours and Holiday Lists reference the right time zone before activating SLAs.
  • Rebuild dashboards and reports in Zoho Desk. Reports do not migrate. Recreate the most-used 5–10 first, then expand.
  • Rebuild Gallery Functions or custom Deluge functions from source automations. Zoho Desk Gallery Functions cover common scenarios (auto-merge duplicate tickets, sync Contacts to Zoho CRM, auto-reply outside business hours). Anything outside the Gallery becomes a custom Deluge function.
  • Re-enable integrations: Zoho CRM sync, Zoho Voice, SalesIQ, marketing tools, BI exports. Run each integration in dry-run mode first to confirm no duplicates are created against migrated records.If skipped: Marketing-automation re-sync without Source-ID checks duplicates every contact.
  • Configure the Zoho Desk Data Backup schedule and Audit Log retention. Set automatic backups per the retention policy decided in Phase 0. Audit Log default retention is 3 years.
  • Deploy the ASAP widget into the customer-facing app or website. Embed the snippet, configure which Help Center categories appear, and confirm ticket submission flows end-to-end.
  • Schedule a 30-day post-migration retrospective. Capture what went well, what didn't, and update the migration runbook for the next org.
  • Document the source-system decommission date. Typical pattern: 90 days read-only, then archive the final export to long-term storage and cancel the subscription.
  • Archive all source-system exports and Zoho Desk migration logs to long-term storage. Retain per the legal-hold and retention policies from Phase 0.If skipped: Discarding exports too early eliminates forensic options if a data-quality issue surfaces months later.
  • Close the migration project formally. Final status report, lessons-learned doc, project closure.

Questions, answered

Migrating to Zoho Desk: questions

How long does migration to Zoho Desk take?

A small-business migration with under 5,000 Tickets, standard modules and no Custom Modules runs one to two business days end-to-end through Zwitch. A mid-market project with multilingual Knowledge Base, Blueprint rebuilds, Macros and Workflow Rules runs two to four weeks of elapsed time including Sandbox dry-runs, validation, training and a 48-hour hyper-care window.

Can I migrate from Zendesk to Zoho Desk?

Yes — Zendesk is the most common Zoho Desk migration source. Zwitch supports it natively, mapping Tickets to Tickets, Users to Contacts, Organizations to Accounts, and Help Center articles to Knowledge Base. Triggers, Automations, Macros, Views and SLA policies do not transfer and must be rebuilt as Workflow Rules and Macros.

Can I migrate from Freshdesk to Zoho Desk?

Yes, and Freshdesk-to-Desk is one of the cleaner Zwitch source paths. The object model maps directly — Tickets to Tickets, Contacts to Contacts, Companies to Accounts, Solutions to Knowledge Base — and Zwitch handles ticket conversations, attachments and tags in the standard flow. Automations, scenarios and SLA policies are configuration and must be rebuilt.

Does Zoho Desk preserve original timestamps on import?

Partially. Threads and Ticket Comments accept the original timestamp natively. But Created Time and Modified Time on Tickets, Contacts and most modules are system-managed and stamp to import day on the standard path. Original Created Time can be imported via assisted route — email [email protected] to request the system override.

What's the difference between the native Import wizard and Zwitch?

The native Import wizard handles ZIP uploads up to 30 MB with each CSV capped at 10,000 rows — best for one-shot loads under 100,000 records. Zwitch, run by Zoho's in-house migration team at [email protected], accepts uploads up to 10 GB and handles supported source platforms like Zendesk and Freshdesk end-to-end.

Can I migrate Custom Modules to Zoho Desk?

Yes, but Custom Modules require the Enterprise edition. The schema, Layouts, fields and Lookups for each Custom Module must exist on the destination Department before any record of that type can be imported. Custom Modules are scoped per Department — a Custom Module in one Department is invisible to another.

What happens to ticket history, conversations and attachments during migration?

Tickets, Threads and Ticket Comments migrate as three related records linked by ticketExtId. Threads keep their original timestamps; the ticket's Created Time stamps to import day unless you request the assisted override. Attachments transfer with their parent Ticket through Zwitch; the native wizard does not handle bulk attachment import.

Is there an undo or rollback for Zoho Desk imports?

Yes — Import History under Setup, Data Administration exposes a Revert action on successful or completed-with-error imports for up to two weeks. Only created records can be undone; updated records cannot be reverted because original values are not retained. Beyond two weeks, stamp every imported row with an Import Batch ID instead.

Sources

  1. Zoho Desk — Wikipedia
  2. Managing Fields — Zoho Desk Online Help
  3. Types of Custom Fields — Zoho Online Help
  4. Migrate Data From Other Help Desk Servers to Zoho Desk (Zwitch) — Zoho Desk
  5. Importing Data in Zoho Desk — Online Help
  6. Import Created Time and Modified Time — Zoho Community
  7. Zoho Desk Pricing & Editions
  8. Gallery and Customized Functions — Zoho Desk Knowledgebase
  9. Sandbox feature for Zoho Desk — Zoho Community
  10. Working with Sandbox in Zoho Desk — Online Help
  11. Validation Rules Trigger on Untouched Fields — Zoho Cares
  12. Date Field Import Error — Zoho Cares
  13. Assisted Data Migration Guide — Zoho Desk Knowledgebase
  14. Character encoding on import (UTF-8 requirement) — Zoho Community
  15. Import Data (Skip / Overwrite / Clone behaviour) — Zoho Desk
  16. Understanding Parent-Child Ticketing System — Zoho Cares
  17. Cascading deletes (lookup nulled, not cascaded) — Zoho Cares
  18. Mark a Field as Unique — Zoho
  19. Multi-line field types (small / large / rich) — Zoho
  20. Omnichannel call center software — Zoho Desk
  21. Attachment size — 1 GB max — Zoho Cares
  22. Attachment Control for File Security — Zoho Desk
  23. Work with a Zoho Partner — Zoho Partner Program
  24. Creating and Using Macros — Zoho Desk
  25. Ticket Views — Thread and Conversation Nested — Zoho Desk
  26. Zoho Desk Feature Availability and SLA Tier-gating
  27. Reverting Import — Zoho Desk (two-week window)
  28. Monitoring Audit Log — Zoho Desk
  29. Import History — Confirm or Undo Imported Data — Zoho Desk
  30. Where your data is stored — Zoho data centers (US/EU/IN/AU/CN/JP)
  31. Import file format rules — tags array brackets, agent identifiers, article status
  32. Audit Log export limits (30 days, 50/day) — Zoho Desk
  33. Migration — Owner / Created By / Modified By fallback to import user — Zoho Community
  34. Unable to update Created Date/Time even via upsert — Zoho Cares
  35. Original Created Time and Closed Time import via assisted route — Zoho Community

Get a quote

Moving to Zoho Desk?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Zoho Desk setup with you, then send a quote.

Get a quote