Migrate from Service Desk Panel to Zendesk

Service Desk Panel tickets map directly to Zendesk tickets. The subject maps to Zendesk subject, description maps to the first public comment, status maps to Zendesk status (open/new/pending/on-hold/solved/closed), and priority maps to Zendesk priority (low/normal/high/urgent). The source assignee email resolves to the Zendesk Agent user, and the source requester email maps to the Zendesk End User or existing Zendesk user. We preserve the original ticket ID as a custom field for audit.

Service Desk Panel customer records map to Zendesk End Users. The customer email is the primary matching and dedupe key. If a Zendesk user with that email already exists, we link to it; otherwise we create a new End User. The customer name, phone, and any custom fields migrate to the corresponding Zendesk user fields. Customers without an email address are created with a generated placeholder and flagged for manual review.

Service Desk Panel agents map to Zendesk Agents by email match. We extract every agent email referenced on ticket records, compare against the Zendesk user list, and provision the Zendesk Agent role for any missing users before migration. Agent status (active/inactive) is preserved as the Zendesk user active flag.

Service Desk Panel team assignments on tickets map to Zendesk Groups. If the source team name matches an existing Zendesk Group by name, we assign the ticket to that Group. If no match exists, we create the Group in Zendesk before migration. Group membership for agents requires manual configuration in Zendesk Admin post-migration.

Service Desk Panel conversation threads migrate to Zendesk ticket comments in chronological order. Each message has an author (agent or end user), body text, and timestamp. Public comments remain public in Zendesk; internal notes migrate as private Zendesk comments. HTML formatting in source comments is stripped to plain text to avoid rendering issues in Zendesk's comment interface.

Attachments export from Service Desk Panel as file references or URLs. If the source platform exposes a direct download URL, we fetch the file body and attach it to the corresponding Zendesk ticket via the Zendesk API upload endpoint. If the source only provides a filename reference without a downloadable URL, we flag this during scoping and include a manual export checklist item for the customer.

Service Desk Panel tags are simple string arrays attached to tickets. They migrate to Zendesk tags as-is. Zendesk deduplicates tags automatically on import, and the customer can review tag distribution post-migration to consolidate or rename tags as needed.

Service Desk Panel custom ticket fields map to Zendesk custom ticket fields. We match by field label and infer the Zendesk field type (text, dropdown, checkbox, date, integer) from the source data. The customer reviews the mapping during a pre-import review step to confirm dropdown fields land in Zendesk dropdown fields rather than text fields. Custom fields must be created in Zendesk Admin before migration begins.

SLA policies are not migrated. Service Desk Panel SLA configuration (first response time targets, resolution time targets, business hours, escalation rules) is documented during discovery and handed to the customer for manual recreation in Zendesk Admin. SLA policies must be configured before go-live to avoid SLA breaches from day one.

If Service Desk Panel exposes a knowledge base or FAQ export via API, we migrate article title, body, category, and publish status to Zendesk Guide articles and sections. Formatting differences between platforms may require post-migration review of article layout. If the source platform does not expose KB articles via API, we flag this for manual export.

Automated routing rules, trigger conditions, and ticket escalation logic are not migrated. We document every active automation in Service Desk Panel during discovery with its trigger, conditions, and actions, and deliver a rebuild guide mapping each rule to the equivalent Zendesk Trigger or Automation. The customer admin rebuilds these in Zendesk Admin post-migration.

Reports and dashboards are not migrated. Historical ticket metrics (volume by status, agent performance, CSAT) may be available as raw data for reimport into Zendesk Explore or a BI tool, but the report configurations themselves must be rebuilt in Zendesk Explore.