Migrate from ManageEngine ServiceDesk Plus MSP to Salesforce Service Cloud

ManageEngine Requests map directly to Salesforce Cases. We pull the full Request payload via the REST API v3, including conversation threads (which the standard XLS export excludes), because Salesforce CaseOrigin and Description fields must carry the complete communication history. The Request priority maps to Salesforce Case Priority (1=High, 2=Medium, 3=Low), Request status maps to Case Status, and the linked Account becomes the Case.AccountId lookup. Conversation threads are stored as EmailMessage records linked to the Case. Technicians and groups map to Salesforce User and Queue lookups respectively.

ManageEngine Requesters split into two Salesforce objects based on role. End-user Requesters who submit tickets become Salesforce Contacts linked to the corresponding Account. Technician Requesters who resolve tickets become Salesforce Users with the appropriate Service Cloud profile and permission sets. We resolve the split using the istechnician boolean flag in the ManageEngine REST API response and preserve the requester email as the Contact.Email or User.Email dedupe key.

ManageEngine Accounts (customer organizations) map 1:1 to Salesforce Account records. Account Name, industry, phone, website, and address fields map directly. Customer Domains do not transfer from On-Premises to Cloud deployments per ManageEngine's own migration documentation; we flag this for manual verification post-migration. Accounts must be created before Contacts and Cases because Case.AccountId is a required lookup during Case insert.

ManageEngine Assets (IT, Non-IT, Software Licenses, and Contract items) map to Salesforce Asset records. Asset discovery scans do not carry over to Salesforce, so each Asset is re-registered at the destination using the Asset Import template. The source Request-Asset associations are preserved as a lookup table during extraction and re-established via a post-migration script. Assets in In Use state that have a resigned user with no department association migrate as In Stock per ManageEngine's own migration limitation rules.

ManageEngine Contracts map to Salesforce Contract records with AccountId set to the corresponding Account lookup. Contract terms, start and end dates, and billing terms migrate. The MSP-specific billing automation (per-ticket-hour and contract-tier invoicing) has no direct Salesforce equivalent and is documented as a post-migration billing configuration item for the customer to reconfigure using Salesforce CPQ or a third-party billing connector.

ManageEngine Solutions (the Knowledge Base for known errors and resolutions) map to Salesforce Knowledge Articles. We export via the KB export tool and import using Salesforce's Knowledge Import API. Topic categorization in ManageEngine maps to Salesforce Data Category Groups. The Solution Owner field and Workaround type do not migrate because Salesforce Knowledge Articles do not have equivalent fields; Solution Description (which is mandatory in Salesforce) receives a placeholder entry if the source Description is empty. Solutions with Review Date on or after Expiry Date are excluded per ManageEngine migration rules.

ManageEngine Change records map to Salesforce Change Request objects, which are available in Salesforce ITSM and Service Cloud with the appropriate permission set. Change type (Standard, Minor, Major, Significant) maps to Salesforce ChangeRequest.Type, and CAB approval records map to ProcessInstance records. Change requests not in Approved or Denied status at migration time display with empty status per ManageEngine's own migration limitations documentation; we flag these for manual resolution. Change Request tasks are limited to 300 per change during migration per the platform limitation.

ManageEngine Problem records map to Salesforce Cases (or a custom Problem object if the customer uses Salesforce ITSM). Problem records linked to multiple Incidents (Requests) are resolved by creating the Problem as a parent Case with related Cases linked via the ParentId field or a custom lookup. Problem workflows and closure rules have no migration path and must be rebuilt using Salesforce Flow. Problem Analysis, Workaround, and Resolution fields migrate as long-text Case Description or custom fields.

ManageEngine Projects and Milestones (Enterprise tier) map to Salesforce custom Project objects or the Service Cloud Workforce Engagement Platform Projects module if licensed. Estimated effort fields in ManageEngine have documented maximum values (estimated_hours up to 99,999; estimated_cost up to 999,999,999,999) that we validate before migration. Projects with effort values exceeding these limits receive a cleanup report before the migration run per ManageEngine's migration limitations documentation. Milestone tasks migrate as related custom Task records on the Project object.

ManageEngine Change Approval Levels in Pending Approval status with non-login approvers convert to To Be Sent status during migration. Approval auto-rejection rules from ManageEngine (where a percentage of denied approvers triggers automatic rejection) cannot be replicated in Salesforce because ProcessInstance uses step-by-step approval logic rather than percentage thresholds. We document the original approval configuration for the customer to redesign in Salesforce Flow Approvals post-migration.