Migrate from eDesk to Zendesk

eDesk Tickets map directly to Zendesk Tickets. Full conversation threads, attachments, status, priority, and SLA metadata transfer. The primary transformation is channel provenance: eDesk embeds channel identity (Amazon, eBay, Shopify, email) in the ticket record; we extract this as a Zendesk tag in the format channel_amazon, channel_ebay, channel_shopify so that Views and reporting in Zendesk replicate the channel-filtering capability of eDesk's Smart Inbox. Marketplace order IDs attached to tickets migrate as custom ticket fields rather than native Zendesk fields since Zendesk does not have a built-in marketplace context model.

eDesk Contact records map to Zendesk User accounts. Email, name, marketplace identity, and custom contact fields migrate as Zendesk user attributes. The Zendesk User type (end-user vs agent) is determined by whether the eDesk Contact has an associated agent account. Custom contact fields from eDesk become Zendesk ticket fields or user fields depending on whether the field applies per-customer or per-ticket.

eDesk Agent accounts map to Zendesk Team Members. Role assignments (Admin, Agent) migrate with email as the dedupe and reconciliation key. We resolve agents by email match against the Zendesk destination account before migration; any eDesk agent without a matching Zendesk user account enters a reconciliation queue for admin provisioning before record import resumes. Zendesk's per-agent Suite licensing means agent count at cutover determines the first Zendesk invoice.

eDesk KB articles and their categories migrate as Zendesk Help Center articles and sections. Internal/external visibility flags translate to Zendesk's Draft/Published article status and permission settings (authenticated vs anonymous access). Article-to-category assignments map to Help Center section hierarchy. Rich text content with embedded media migrates with attachments preserved as file uploads in the Zendesk Help Center.

eDesk's channel model (200+ marketplace and D2C integrations) has no native equivalent in Zendesk. We resolve channel provenance by tagging each migrated ticket with a channel-derived tag. This allows Zendesk Views to replicate eDesk's Smart Inbox channel-grouping behavior. Tags also enable reporting by channel in Zendesk's Explore module.

eDesk Smart Rules are automation logic triggers that route and categorize tickets. These are eDesk-proprietary and do not have a direct Zendesk equivalent in format. We export Smart Rule logic as a machine-readable configuration document describing trigger conditions, actions, and routing logic. The customer's Zendesk admin uses this document to rebuild equivalent Triggers and Automations in Zendesk's Rule Builder. Message Rules (Professional/Enterprise gated) export separately since they have no Zendesk analog.

eDesk canned response templates migrate as Zendesk Macros. Template variables such as customer_name or order_number are preserved as plain text tokens; variable mapping depends on Zendesk's placeholder syntax (such as {{ticket.requester.name}} or {{ticket.custom_field:xxxxx}}). We document the variable mapping in the migration notes so admins can update macro text post-migration.

Ticket-level tags from eDesk migrate as Zendesk tags on the corresponding ticket. Tag taxonomies differ between platforms, so tag counts and naming conventions may change. Zendesk tags are additive and do not enforce a hierarchical structure; any taxonomy grouping from eDesk is preserved in tag naming convention rather than as a native hierarchy.

eDesk SLA configurations (first-response and resolution time thresholds) migrate as Zendesk SLA Policy definitions. First Response Time and Next Response Time targets map to Zendesk's SLA metric definitions. SLA enforcement in Zendesk requires Business hours configuration to match eDesk's working-hours setup; we flag this for admin configuration before SLA policies activate post-migration.

eDesk's AI Classification taxonomy (used to auto-categorize tickets) is not a standalone exportable object. We capture AI classification data as custom ticket fields during migration, preserving the classification value on each ticket so the historical categorization is queryable in Zendesk. Rebuilding the AI classification logic in Zendesk requires either Zendesk Intelligent Triage (Suite Growth and above) or a third-party AI categorization app.