Migrate from Usedesk to Zendesk

Usedesk Tickets map to Zendesk Tickets with status, priority, assignee, and timestamps preserved. Usedesk's channel metadata (email, chat, social, messenger source) migrates as Zendesk Ticket custom fields or as channel tags depending on the destination Zendesk plan. Custom fields on Usedesk Tickets require pre-creation in Zendesk before migration; we discover each custom field during the pre-migration audit and create the equivalent Zendesk Ticket custom field in the destination schema before the import pass begins.

Usedesk Client records (end customers) map to Zendesk End User records. Email, name, and phone number migrate directly. Phone number formats may vary; we normalise to E.164 format during transformation. Any custom properties on the Usedesk Client record become Zendesk user custom fields pre-created in the destination schema. Role assignment in Zendesk (End User versus Agent) is determined by whether the Usedesk client has ticket history (End User) or agent permissions (mapped to Agent in step 6).

Usedesk Agent records map to Zendesk Agent (staff) users. We extract every Usedesk agent referenced on a ticket and resolve them by email against the Zendesk destination user table. Any Usedesk agent without a matching Zendesk User goes to a reconciliation queue for the customer's Zendesk admin to provision before record import resumes. Usedesk role permissions (viewer, agent, admin) map to Zendesk roles, but permission parity is not 1:1; we document each Usedesk role and its nearest Zendesk equivalent in the validation report.

Usedesk supports up to 20 channel types (email, chat, social, messengers) and consolidates channel metadata into the ticket. Zendesk manages channels as separate integrations rather than objects, but the originating channel for each ticket can be preserved as a Zendesk Ticket custom field or as a tag. We extract the channel source from Usedesk ticket metadata and write it to a Zendesk custom field during transformation. Channel routing logic (which group or agent receives tickets from a given channel) requires manual reconfiguration in Zendesk post-migration.

Usedesk Knowledge Base articles migrate to Zendesk Guide articles with content, categories, and publication status preserved. Article-to-ticket linking (if used in Usedesk to surface related articles in ticket views) is noted as a post-migration manual step because Zendesk Guide does not expose article-to-ticket linking as a native field. The Zendesk Help Centre must be activated before article import; we coordinate with the customer's Zendesk admin to enable Guide before the article pass begins.

Tags used for ticket categorisation in Usedesk migrate as flat label sets to Zendesk Tags. Where Usedesk uses a hierarchical tag structure, we flatten it during transformation and flag what requires reorganisation in Zendesk's flat tag model. Zendesk automatically converts tag values into tagger field values for reporting; we account for this in the validation report by comparing tag counts before and after migration.

Historical analytics and reporting data are not migrated. Usedesk reporting metrics are generated from underlying ticket data, which does migrate. We regenerate reports from migrated tickets in Zendesk post-cutover using Zendesk's native reporting suite or any connected BI tool.

Usedesk automation rules (triggers, conditions, and chained actions) are exported as structured JSON for documentation purposes only. The automation engine semantics differ significantly between Usedesk and Zendesk, so we do not migrate them as executable code. We deliver a written automation inventory document listing each Usedesk rule with its trigger, conditions, actions, and a recommended Zendesk trigger and macro equivalent for the customer's admin to rebuild post-migration.

File attachments embedded in tickets migrate to Zendesk as ticket attachments stored in Zendesk's file hosting. We flag oversized files early during scoping. Knowledge base article attachments migrate as Zendesk Guide article attachments. Links to attachments embedded in ticket comments are preserved by migrating the full comment body with inline attachment references resolved to Zendesk-hosted file URLs.

Account-level settings, SLA configurations, and third-party integrations (CRM connections, analytics tools) are not migrated. We document each Usedesk integration identified during the pre-migration audit in a settings checklist so the customer's Zendesk admin can reconfigure each integration individually post-migration. SLA policies require manual recreation in Zendesk Admin with the customer's target SLA definitions.