Migrate from ManageEngine ServiceDesk Plus MSP to Zendesk

ServiceDesk Plus MSP Accounts (customer organizations) map to Zendesk Organizations. The Account name becomes the Organization name, and we use the Account ID as an external ID field on the Organization for deduplication. If the MSP uses Account-level billing or Contract records, we attach contract metadata as Organization fields or tags at the destination. For MSPs with many small Accounts, this mapping is straightforward; for MSPs with hierarchical Account structures (parent-child relationships), we flatten to a single Organization level and tag parent relationships separately.

ServiceDesk Plus MSP Requesters map to Zendesk Users. We use the Requester email as the dedupe key. For MSPs, Requesters belong to an Account, which maps to the corresponding Zendesk Organization. We also preserve the Account-Requester relationship by setting the user's Organization field to the mapped Zendesk Organization. The user's Created At timestamp migrates from the SDP Requester creation date. Technicians in ServiceDesk Plus MSP map to Zendesk Agents, and we separate technician and requester records using the is_technician flag before import.

ServiceDesk Plus MSP Requests are the core ticket object and map directly to Zendesk Tickets. The Request subject becomes the Ticket subject, the Request description becomes the Ticket description, and the Request status (Open, Pending, Resolved, Closed) maps to Zendesk Ticket status (Open, Pending, Solved, Closed). We pull priority and category fields and map them to Zendesk Priority and Tags. The SDP Request ID is stored as an external ID on the Zendesk Ticket for cross-reference during reconciliation.

Conversation threads on ServiceDesk Plus MSP Requests are not included in standard XLS exports. We extract full conversation history via the REST API v3 (GET /api/v3/requests/{request_id}/conversations) using paginated responses, pre-fetching before the 15-request-per-10-second rate-limit window resets. Each conversation entry (technician reply, requester reply, public note, private note) becomes a Zendesk Ticket Comment, with the author mapped to the corresponding Zendesk User by email. Comment timestamps are preserved for audit continuity.

ServiceDesk Plus MSP distinguishes between Request Notes (internal technician notes) and Request Conversations. Internal notes in SDP migrate to Zendesk Ticket comments with the is_public=false flag, preserving the internal-only nature of the communication. If the MSP uses Notes to track internal debugging steps or billing-relevant context, we recommend mapping them to a Zendesk Ticket field rather than a comment so that the information is structured and searchable rather than buried in comment threads.

IT and Non-IT Assets in ServiceDesk Plus MSP include workstations, network gear, software licenses, and components. If the destination Zendesk account is on Suite Enterprise, Assets migrate natively. For Suite Professional and below (where native Assets are not available), we export Asset records as a lookup table and map the asset relationship to a Zendesk Ticket custom field (dropdown or text) so that technicians can reference the source asset identifier. Asset-Request associations are exported as a separate lookup table and re-linked at the destination via the Asset Import feature or custom field mapping.

ServiceDesk Plus MSP Contracts are billing instruments tied to Accounts. We export contract records via CSV and preserve the Account-Contract relationship. At the destination, contract terms (billing model, contract value, renewal date) migrate to Organization custom fields or to a Ticket custom field depending on whether the MSP needs contract context at the organizational level or per-ticket. Contract terms and billing rules require manual verification post-migration because billing automation is not portable.

ServiceDesk Plus MSP Solutions serve as the Knowledge Base for known errors and resolutions. Solutions are exportable via the dedicated KB export tool referenced in the ManageEngine PitStop community. We map Solutions to Zendesk Articles, preserving the topic/category structure from SDP as Zendesk Sections. Article content migrates with formatting intact. The article publication status (Draft, Published) maps to Zendesk Draft or Published. For Solutions with attachments, we migrate files as Article Attachments.

Change Management records in ServiceDesk Plus MSP track CAB approvals, change types, risk levels, and schedules. Change records migrate to Zendesk Tickets with a Change-specific tag and structured custom fields (Change Type, Risk Level, Approval Status, Scheduled Date). Change-specific workflows and Approved Change Records are not portable and require manual rebuild in Zendesk. If the MSP uses change management as a formal ITIL process, we recommend establishing Zendesk Tickets with a dedicated view rather than relying on standard ticket fields alone.

Problem records in ServiceDesk Plus MSP link to multiple Incidents (Requests). We export Problem records and their linked Request associations. At the destination, we create a Zendesk Ticket for each Problem record and tag linked Incident tickets for cross-reference. Problem workflows and closure rules are not portable and must be reconfigured. The Problem-Incident relationship is preserved by tagging all related Zendesk Tickets with the Problem ID.

Additional Fields on ServiceDesk Plus MSP Requests migrate to Zendesk Ticket Fields. We validate Additional Field values against published maximum constraints (additional_cost up to stated limits, estimated_effort_* fields with 9999-day and 999-hour maximums) before migration. Records that exceed tightened field constraints are flagged in a cleanup report for the customer to resolve before the migration run. Field types (text, numeric, date/time, pick list) map to equivalent Zendesk field types.