Migrate from Usedesk to Zoho Desk

Usedesk Tickets map directly to Zoho Desk Tickets with standard fields (status, priority, assignee, timestamps) transferred as-is. Custom fields on Usedesk tickets are discovered during pre-migration audit, mapped to Zoho Desk department-scoped custom fields by data type, and imported via Zoho Desk REST API. Thread direction requires transformation: Usedesk stores messages in a flat thread without explicit Incoming/Outgoing classification, so we reconstruct direction by comparing the message author email against the ticket's requester email and set the Comment direction field accordingly. We handle this in the transform layer before Zoho Desk import.

Usedesk Clients map to Zoho Desk Contacts, and if the Client has an organisational name field we create a Zoho Desk Account and link the Contact to it. Email serves as the dedupe key. Phone number formats vary by region and we normalise during transform. Custom client properties migrate to Contact-scoped custom fields on Zoho Desk. Clients without an email are handled by generating a placeholder identifier and flagging for the customer's admin to enrich post-migration.

Usedesk Agents map to Zoho Desk Agents by email match. Role and permission parity requires manual review because Usedesk role definitions do not export cleanly. We flag each Usedesk role permission that needs reassignment in Zoho Desk (Support Administrator, Agent, or custom profile) in the handoff document. The agent roster is reconciled against Usedesk's per-agent billing seats before migration so that any inactive or duplicate agents are deactivated in Usedesk before the final export to avoid billing discrepancies post-cutover.

Usedesk supports up to 20 channel types (email, chat, social, messengers). Zoho Desk does not expose channels as distinct record objects; instead, channel metadata attaches as properties on the ticket. We map each active Usedesk channel to a Zoho Desk Department (for channel-based routing) and preserve the original channel name as a ticket custom field so the source channel is auditable post-migration.

Usedesk Knowledge Base articles migrate to Zoho Desk Solutions articles with their content, categories, and publication status preserved. Article-to-ticket linking is reconstructed as ticket custom fields in Zoho Desk since the linking semantics differ between platforms. Attachments within articles migrate to Zoho Desk file storage with links updated in the article body. Zoho Desk's Zwitch tool explicitly does not migrate KB attachments, which is a documented limitation we handle through a separate migration pass using the Zoho Desk API.

Usedesk tags migrate as flat label sets to Zoho Desk Tags. Where Usedesk uses hierarchical tag groups, we flatten the structure and flag what needs reorganising in Zoho Desk's flat tag model in the validation report. Tags are migrated after Tickets so that each tag is associated with the correct ticket records.

File attachments embedded in tickets or the knowledge base migrate to Zoho Desk storage. We flag oversized files (Zoho Desk's Zwitch caps at 10GB per upload) early in scoping and handle large file batches via the Zoho Desk REST API with multipart upload support. Inline images in ticket threads migrate as attachments linked to the Comment record.

Historical analytics and reporting data do not transfer. Usedesk's reporting structure is not exportable, and Zoho Desk's reporting engine is built on migrated records. We advise customers to capture screenshots of key Usedesk reports before migration day and to plan for a reporting rebuild period in Zoho Desk once records are live.

Usedesk automation triggers, conditions, and actions are exported as structured JSON but cannot be imported into Zoho Desk because the automation engine semantics differ. We deliver a written inventory of each Usedesk automation with its nearest Zoho Desk Blueprint (for multi-step ticket processes) or Macro (for template responses) equivalent, along with the specific trigger configuration. The customer's admin rebuilds these post-migration.

Account-level settings, SLA configurations, and third-party integrations (CRM sync, analytics connectors) are not migrated. These are documented in the pre-migration checklist for manual reconfiguration in Zoho Desk. SLA policies are an exception: if the customer has structured SLA data in Usedesk, we create Zoho Desk SLAs with the same thresholds and attach them to the relevant departments and ticket types.

If Usedesk stores product records linked to tickets, these migrate to Zoho Desk Products. ProductCode maps from Usedesk's product identifier field, and product names migrate as-is. Products are imported before Tickets so that the lookup relationship is satisfied at the moment of ticket insert.

Usedesk is based in Estonia with timestamps potentially in EET/EEST. All timestamps are normalised to UTC during transformation. Any ambiguous datestamps (for example, if the original server time was misconfigured) are flagged in the validation report for customer review before the Zoho Desk import begins.