Migrate from ManageEngine ServiceDesk Plus to Zendesk

Requests are the central ticket object in ServiceDesk Plus and map to Zendesk Tickets. We extract all standard request fields (ID, subject, description, status, priority, category, subcategory, technician, requester) via the REST API. The critical nuance is that custom ticket fields are stored in a separate database table and do not appear in the GET requests bulk list response. We call the individual request detail endpoint per record or use the custom field API during scoping to enumerate all custom field names and data types before migration. Status, priority, and category values map to Zendesk ticket Status, Priority, and a custom field or tag set. Conversation threads (internal notes and public replies) migrate as Zendesk Comments with the author and timestamp preserved.

Requesters represent end users who submit tickets. We export all requester records including name, email, phone, department, and site via the REST API. Requester-to-request associations are preserved as the ticket's Requester field in Zendesk. If a Requester email matches an existing Zendesk User, we link by email; otherwise we create a new Zendesk End User. Technicians (staff) map to Zendesk Agents with their role and group assignments preserved as Agent custom fields or group memberships.

Assets (hardware, software, components) in ServiceDesk Plus are only available on Professional and Enterprise editions. If the destination Zendesk instance includes Asset Tracking (Zendesk Suite Enterprise), we export asset records with name, type, serial number, purchase date, and vendor, then create Zendesk Asset records linked to the corresponding End User or Location. If Asset Tracking is not available in the target Zendesk tier, asset data migrates to ticket custom fields or a related object table. Asset-to-request associations migrate as custom field values on the ticket referencing the asset identifier.

Solutions are the knowledge base articles in ServiceDesk Plus. We extract article content, category assignments, approval status, and summary fields. Inline images and formatting are preserved where the source content is HTML-compatible. The Solutions structure maps to Zendesk Help Center Articles, with categories mapping to Zendesk Sections. We preserve author and created/updated timestamps. Note that the Solution Owner field and Workaround type in ServiceDesk Plus have no Zendesk equivalent and are documented as field gaps.

Problem records are ITIL Problem management entities that link multiple incidents (requests). Zendesk does not have a native Problem object in standard or Suite plans. We document each Problem record with its linked request IDs as a pre-migration decision item. Options include recreating Problems as linked ticket groups in Zendesk, using Zendesk Explore to build a problem-incident relationship view, or adopting a Zendesk partner ITSM app. Problem-to-incident associations are preserved as structured data in the migration handoff document.

Change records in ServiceDesk Plus capture change requests with approval workflows, risk assessments, and implementation plans. Zendesk has no native Change Management object. We export Change records with their request associations, status history, and approval board configurations as a separate structured data file. Approval Board content is not migratable as executable workflow. The customer receives a written Change Management handoff with each Change's linked request IDs, planned dates, and risk level so the team can rebuild in Zendesk or an external ITSM tool.

Releases track deployment packages and rollout plans in ServiceDesk Plus Enterprise. Zendesk does not have a native Release management object. We export release records, associated change requests, and deployment checklist items as structured data. The customer receives a written inventory of all active and planned Releases with their dependencies for manual rebuild or integration with a release management tool.

Service Catalog items in ServiceDesk Plus define orderable services with request templates, approval workflows, and step-based fulfillment processes. Zendesk's native product does not include a service catalog. We export catalog item definitions and request form structures as a data dictionary. The customer receives a written catalog inventory documenting each item's workflow steps, approvers, and request template for rebuild in Zendesk or a third-party catalog tool.

Projects in ServiceDesk Plus track IT initiatives linked to requests and changes. Projects, milestones, tasks, and resource assignments are exported as structured data. Zendesk does not have a native project management object. We preserve project metadata and project-to-request associations in the migration handoff document for rebuild in a project management tool or as linked Zendesk ticket groups.

Attachments associated with requests are stored as file references in ServiceDesk Plus. There is no standard bulk export for attachments. We call the file attachment endpoint per request, download the binary content where API access permits, and re-upload to Zendesk as ticket comments with file attachments. Inline images embedded in request descriptions and Solutions articles are handled separately via the content extraction workflow. This requires per-record API calls, which multiplies against the 60 req/min read throttle on ServiceDesk Plus.

Contracts in ServiceDesk Plus Professional and Enterprise capture vendor agreements with start/end dates, terms, and costs. Zendesk does not have a native Contracts object. If the customer uses Zendesk Asset Tracking (Enterprise), contract data migrates as structured fields on the related Asset record. Otherwise, contracts are exported as structured data in the migration handoff document for rebuild in a contract lifecycle management tool.