Helpdesk migration
Field-level mapping, validation, and rollback between ITsDone Help Desk and Salesforce Service Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Service Cloud.
ITsDone Help Desk
Source
Salesforce Service Cloud
Destination
Compatibility
7 of 12
objects map 1:1 between ITsDone Help Desk and Salesforce Service Cloud.
Complexity
CModerate
Timeline
3-5 weeks
Overview
ITsDone Help Desk targets German-speaking IT services teams under 100 agents with a straightforward ticketing system and native-language interface. Salesforce Service Cloud is an enterprise CRM with built-in Einstein AI, omni-channel case routing, and an AppExchange ecosystem that scales globally without the platform limits teams eventually hit in ITsDone Help Desk. We map ITsDone Tickets to Salesforce Cases, Customers to Contacts (with Account resolution), and Agents to Users. Because ITsDone does not expose an API for workflow automations, we deliver a structured automation audit inventory documenting every rule for your Salesforce admin to rebuild in Flow. Attachment URLs in ITsDone are time-limited; we validate and re-download every binary before inserting into Salesforce ContentDocument records tied to the correct Case. SLA configurations from ITsDone map to Salesforce Entitlement Processes and Milestones so response and resolution targets carry forward.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
ITsDone Help Desk platform overview
Scorecard, SWOT, gotchas, and pricing for ITsDone Help Desk.
Destination platform
Salesforce Service Cloud platform overview
Scorecard, SWOT, gotchas, and pricing for Salesforce Service Cloud.
Data migration guide
The complete Salesforce Service Cloud migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Salesforce Service Cloud migration checklist
Pre- and post-cutover tasks for moving onto Salesforce Service Cloud.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a ITsDone Help Desk object lands in Salesforce Service Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
ITsDone Help Desk
Ticket
Salesforce Service Cloud
Case
1:1ITsDone Tickets map to Salesforce Case records. The ITsDone ticket status (open, pending, resolved, closed) maps to Salesforce Case Status, with a custom field itsdone_original_status__c preserving the source value. ITsDone priority (low, normal, high, urgent) maps to Salesforce Case Priority. Created date and last modified date migrate as CreatedDate and LastModifiedDate respectively. ITsDone ticket ID is stored in a custom field itsdone_ticket_id__c for cross-system reference.
ITsDone Help Desk
Ticket Comment
Salesforce Service Cloud
CaseComment + EmailMessage
1:1ITsDone ticket thread entries (public replies and internal notes) migrate to Salesforce CaseComment records ordered by timestamp. Email channel entries migrate as EmailMessage records linked to the Case, preserving FromAddress, ToAddress, Incoming flag, and HTML body. Thread ordering is preserved via the CreatedDate timestamp so agent and customer exchanges appear in correct sequence.
ITsDone Help Desk
Customer
Salesforce Service Cloud
Contact + Account
1:1ITsDone Customers map to Salesforce Contact records. Where ITsDone stores a company name on the customer record, we create or match a Salesforce Account and populate Contact.AccountId. Customer email, phone, and address fields map to typed Salesforce Contact fields. Any ITsDone custom customer properties migrate to custom fields on Contact, with type matching (text, picklist, date) confirmed during scoping.
ITsDone Help Desk
Agent
Salesforce Service Cloud
User
1:1ITsDone Agent profiles (name, email, role, group assignment) map to Salesforce User records. We match by email address against the destination Salesforce org. Role naming conventions differ between platforms, so we create a mapping table during scoping and flag any ITsDone roles with no direct Salesforce Profile equivalent for the admin to assign. Agent group membership maps to Salesforce Queues membership.
ITsDone Help Desk
Agent Group
Salesforce Service Cloud
Queue
lossyITsDone agent groups migrate to Salesforce Queues. We create a Queue for each ITsDone group, add the corresponding mapped Users as QueueMembers, and associate the Queue with the Case object for case assignment routing. Queue API names are normalized to remove spaces and special characters per Salesforce naming conventions.
ITsDone Help Desk
Tag
Salesforce Service Cloud
Topic or Multi-Select Picklist
lossyITsDone ticket tags migrate to Salesforce Topics via TopicAssignment records linked to the Case. Alternatively, if the customer prefers a structured field, tags migrate to a custom multi-select picklist on Case with character set normalization (ITsDone may allow characters that Salesforce restricts on picklist values). The customer chooses the tag strategy during scoping.
ITsDone Help Desk
Knowledge Base Article
Salesforce Service Cloud
Knowledge__kav
1:1ITsDone Help Desk Knowledge Base articles, sections, and categories migrate to Salesforce Knowledge with Salesforce Knowledge Article Version (Knowledge__kav) records. Article body HTML is inserted as the Summary or Body field depending on the Salesforce edition. We flag embedded media links to internal ITsDone assets for manual remediation post-migration. ITsDone article publish status maps to Salesforce PublishStatus (Draft, Published, Archived). Data category groups are created in Salesforce if the customer requires taxonomy-based article access control.
ITsDone Help Desk
SLA Policy
Salesforce Service Cloud
Entitlement Process + Milestone
lossyITsDone SLA configurations (business hours, first-response target, resolution target) map to Salesforce Entitlement Processes and Milestones. Each ITsDone SLA policy becomes a Salesforce Entitlement record on the Account or Contact, with FirstResponseTime and ResolutionTime milestones configured to match the original target values. Business hours definition migrates to Salesforce Business Hours linked to the Entitlement.
ITsDone Help Desk
Attachment
Salesforce Service Cloud
ContentDocument + ContentVersion
1:1ITsDone stores attachments as URL references rather than embedded binaries. We validate every attachment URL at migration start, re-download the binary content, and insert it as a Salesforce ContentVersion linked to the parent Case via ContentDocumentLink. Attachment filename and content type (MIME type) are preserved. If any URL has expired (returning 404), we flag the record in the reconciliation report for the customer to re-upload manually.
ITsDone Help Desk
Custom Field
Salesforce Service Cloud
Custom Field (__c)
lossyITsDone custom ticket fields and custom customer fields are parsed from the schema export and mapped to Salesforce custom fields on Case or Contact respectively. Field types are matched during scoping: ITsDone text fields map to Text, picklist to Picklist, date to Date, number to Number. Dependent dropdowns and calculated fields that cannot map directly are flagged with recommended Salesforce equivalents (for example, a calculated field may become a Formula field or a read-only custom field requiring post-migration manual entry). Custom field API names append __c per Salesforce convention.
ITsDone Help Desk
Ticket Status
Salesforce Service Cloud
Case Status
lossyITsDone ticket status values (open, pending, resolved, closed, on-hold) map to Salesforce Case Status values. We configure the Case Status picklist in Salesforce during schema setup to include all active ITsDone statuses, ensuring no closed-loop value is lost during migration. The Case Status field is included in the Case Record Type assignment.
ITsDone Help Desk
Custom Object
Salesforce Service Cloud
Custom Object (__c)
1:1ITsDone custom objects beyond standard Tickets, Customers, and Agents migrate to Salesforce custom objects of equivalent API name with the __c suffix. We pre-create the destination schema including all custom fields and lookup relationships to Case, Contact, or Account before any data import. Lookup field references are resolved at migration time using the parent-record mapping tables.
| ITsDone Help Desk | Salesforce Service Cloud | Compatibility | |
|---|---|---|---|
| Ticket | Case1:1 | Fully supported | |
| Ticket Comment | CaseComment + EmailMessage1:1 | Fully supported | |
| Customer | Contact + Account1:1 | Fully supported | |
| Agent | User1:1 | Fully supported | |
| Agent Group | Queuelossy | Fully supported | |
| Tag | Topic or Multi-Select Picklistlossy | Fully supported | |
| Knowledge Base Article | Knowledge__kav1:1 | Fully supported | |
| SLA Policy | Entitlement Process + Milestonelossy | Fully supported | |
| Attachment | ContentDocument + ContentVersion1:1 | Fully supported | |
| Custom Field | Custom Field (__c)lossy | Fully supported | |
| Ticket Status | Case Statuslossy | Fully supported | |
| Custom Object | Custom Object (__c)1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
ITsDone Help Desk gotchas
Attachment URLs may expire after migration window
Workflow automations do not export from ITsDone
Custom field schema varies by ITsDone edition
Salesforce Service Cloud gotchas
Data Export 512MB file size cap breaks large org exports
API Daily Request Limits vary by license edition
No automatic data backup in base Salesforce
Picklist dependencies silently break records when unmapped
Workflow rules fire unexpectedly during data load
Pair-specific challenges
Migration approach
Scoping and API availability audit
We audit the ITsDone Help Desk account across edition tier, schema (custom fields, SLA policies, agent roles, group structure), and record volumes for Tickets, Customers, Agents, Tags, Knowledge Base Articles, and Attachments. We confirm API availability for the specific ITsDone edition; if the edition lacks API access, we use the CSV export path with enhanced validation. We also query the Salesforce destination org for existing custom fields, Record Types, and Business Hours configurations to avoid namespace collisions.
Schema design and Salesforce configuration
We design the destination Salesforce org schema before any data moves. This includes creating custom fields on Case and Contact to receive ITsDone data, configuring Case Status values to match ITsDone ticket statuses, provisioning Queues for each ITsDone agent group, creating Entitlement Processes and Business Hours for SLA policies, and setting up Salesforce Knowledge with appropriate data category groups if a knowledge base migrates. Schema deploys to a Salesforce Sandbox first for validation against sample data.
Sandbox migration and reconciliation
We run a full migration into the Salesforce Sandbox using production-like record volumes. The customer's support operations lead reconciles record counts (Cases in, Contacts in, Entitlements in, Articles in), spot-checks 25-50 random Cases against the ITsDone source for field accuracy, and validates attachment integrity. The automation audit inventory document is delivered at this stage for the admin team to begin Flow rebuild planning. Sign-off on the sandbox migration gates the production cutover.
User provisioning and agent mapping
We extract every distinct ITsDone Agent and map by email to the Salesforce destination org's User table. Any ITsDone agent without a matching Salesforce User goes to a reconciliation queue; the customer's admin provisions missing Users before record migration resumes. Queue membership is assigned per the agent-to-group mapping so case routing is active from day one in production.
Production migration in dependency order
We run production migration in record-dependency order: Salesforce Users validated, then Accounts (from ITsDone company data on Customers), then Contacts (with AccountId resolved), then Cases (with ContactId and OwnerId resolved), then CaseComments and EmailMessages (thread ordering preserved by timestamp), then Entitlements and Business Hours linked to Accounts, then Knowledge Articles, then Attachments via ContentVersion and ContentDocumentLink. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and handoff
We freeze ITsDone writes during cutover, run a final delta migration of any Cases modified during the migration window, then enable Salesforce Service Cloud as the system of record. We deliver the automation audit inventory, attachment gap report, and knowledge base HTML review checklist to the customer. We support a one-week hypercare window where we resolve any reconciliation issues raised by the support team. Workflow rebuilds and SLA policy fine-tuning in Salesforce Flow are outside standard scope and require a separate engagement.
Platform deep dives
ITsDone Help Desk
Source
Strengths
Weaknesses
Salesforce Service Cloud
Destination
Strengths
Weaknesses
Complexity grading
Moderate Helpdesk migration. 1 of 7 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across ITsDone Help Desk and Salesforce Service Cloud.
Object compatibility
1 of 7 objects need a manual workaround.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
ITsDone Help Desk: Not publicly documented.
Data volume sensitivity
ITsDone Help Desk doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during ITsDone Help Desk to Salesforce Service Cloud migration scoping. Not seeing yours? Book a call.
Walk through your ITsDone Help Desk to Salesforce Service Cloud migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave ITsDone Help Desk
Other ways to arrive at Salesforce Service Cloud
Same-Helpdesk migrations
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.