Migrate from Service Desk Panel to Salesforce Service Cloud

Service Desk Panel Tickets map directly to Salesforce Case. We resolve the source ticket status, priority, and assignee to their Salesforce equivalents. The Case Record Type is determined at migration time based on the source ticket category or type field, which must be mapped to a pre-configured Salesforce Record Type and Sales Process before import. Subject and Description map to Case Subject and Description. Origin maps from the source channel (email, web, phone) to the Salesforce Case Origin picklist values.

Service Desk Panel Customer records map to Salesforce Contact. For B2B scenarios where the source has company-level context, we create or match an Account first and attach the Contact. The Customer email is the primary dedupe key for matching against existing Salesforce Contacts. If the destination org has duplicate Contacts, we flag records requiring admin review before import rather than auto-merging, which prevents unintended data loss.

Service Desk Panel Agents map to Salesforce User records. We resolve by email match against the destination org's User table. If a source Agent does not have a matching User, we hold those records in a reconciliation queue and document the required Salesforce User provisioning so that your admin can create the accounts before record migration resumes. Active and inactive agent status maps to the Salesforce User IsActive flag.

Service Desk Panel Teams map to Salesforce Groups (for sharing rules and manual assignment) or Queues (for automatic case assignment). We map Team name to the destination Queue label. The Queue must be created and active in Salesforce before Cases that reference it are imported, otherwise the assignment fails and those Cases land in the unassigned state for manual routing.

Service Desk Panel conversation threads migrate to Salesforce EmailMessage records (the email content) linked to the Case by CaseId, plus a Case Feed entry showing the thread for agent visibility in the Service Console. HTML formatting in message bodies is preserved or stripped depending on the destination org's Allow HTML Email setting. Author attribution maps to the Salesforce CreatedById User lookup where the email sender matches a Contact or User; external sender emails land as Case Feed entries without a WhoId reference.

File attachments from Service Desk Panel migrate as Salesforce ContentDocument records (Files) attached via ContentDocumentLink to the parent Case. If the source platform exposes a direct download URL, we retrieve the file body and upload it to Salesforce Files. If the source only exposes a file name reference without a download URL, we flag this for manual export and document the file list so your admin can upload after go-live. We confirm attachment accessibility during scoping.

Service Desk Panel ticket tags migrate to a Salesforce custom field on Case defined as a Multi-Select Picklist. We import the tag array as a semicolon-delimited string that Salesforce renders as individual selectable chips in the Case record. Tag deduplication happens during the transform step. If the destination has more than 150 unique tags, we recommend a Custom Metadata or Custom Object tag store instead of a picklist to avoid the 150-value picklist limit.

Custom ticket fields vary widely in type and naming across platforms. We match by field label and inferred data type (text, number, date, checkbox, dropdown) and create or map to an equivalent Salesforce custom field on the Case object. The customer must review and approve the field mapping during a mapping review step before import, because a source dropdown field mapped to a text field in Salesforce silently changes behavior for agents and reporting.

Service Desk Panel knowledge base articles migrate to Salesforce Knowledge articles if the destination org has Knowledge enabled. We preserve article title, body content, and category structure. Formatting differences between platforms may require post-migration review of article layout, embedded images, and internal links. Article translations and article attachments require separate migration steps and may need manual recreation if the source exposes only title and URL references rather than full content.

SLA policies do not migrate. Service Desk Panel SLA definitions (first response time, resolution time, business hours, escalation rules) are not stored in a portable format. We document the source SLA configuration during discovery and deliver a written rebuild guide for Salesforce Entitlement Processes and Milestones, which your admin configures before go-live to avoid SLA breaches from day one. Entitlement Process is available on Service Cloud Professional and higher tiers.