Helpdesk migration

Migrate from ITsDone Help Desk to Salesforce Service Cloud

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 logo

ITsDone Help Desk

Source

Salesforce Service Cloud

Destination

Salesforce Service Cloud logo

Compatibility

58%

7 of 12

objects map 1:1 between ITsDone Help Desk and Salesforce Service Cloud.

Complexity

CModerate

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

ITsDone Help Desk logo

ITsDone Help Desk

What's pushing teams away

  • Scalability limitations become apparent as teams grow beyond 50–100 agents, driving migration to platforms like Jira Service Management or ServiceNow.
  • Lack of advanced AI features and modern automation builders leads teams to switch to Zendesk Suite or Freshdesk for AI-powered triage.
  • International expansion creates pressure to move to globally-supported platforms with multi-language knowledge bases and 24/7 support.
  • Teams report that reporting and analytics fall short compared to competitors, prompting migration to platforms with richer dashboards.
  • Integration ecosystem limitations push organizations toward platforms like Zendesk with broader third-party marketplace support.

Choosing

Salesforce Service Cloud logo

Salesforce Service Cloud

What's pulling them in

  • Deep Salesforce ecosystem integration with Sales Cloud, Marketing Cloud, and custom Apex apps creates a single pane of glass for enterprise customer data and cross-functional workflows.
  • Omnichannel case routing — email, chat, phone, social, and messaging — unified under one case object means agents do not lose context when customers switch channels mid-interaction.
  • AI for customer service (Einstein AI / Agentforce) offers automated case classification, suggested replies, and chatbot routing that reduces Tier-1 ticket volume without manual rule authoring.
  • Entitlement and milestone tracking enforces SLA compliance natively, automatically calculating breach windows and surfacing violations to supervisors in dashboards.
  • Salesforce's massive AppExchange ecosystem provides pre-built connectors, industry-specific managed packages, and third-party tools that extend Service Cloud beyond its out-of-box capabilities.

Object mapping

How ITsDone Help Desk objects map to Salesforce Service Cloud

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

maps to

Salesforce Service Cloud

Case

1:1
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

CaseComment + EmailMessage

1:1
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

Contact + Account

1:1
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

User

1:1
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

Queue

lossy
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

Topic or Multi-Select Picklist

lossy
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

Knowledge__kav

1:1
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

Entitlement Process + Milestone

lossy
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

ContentDocument + ContentVersion

1:1
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

Custom Field (__c)

lossy
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

Case Status

lossy
Fully supported

ITsDone 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

maps to

Salesforce Service Cloud

Custom Object (__c)

1:1
Fully supported

ITsDone 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.

Gotchas + challenges

What specifically takes care here

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 logo

ITsDone Help Desk gotchas

Medium

Attachment URLs may expire after migration window

High

Workflow automations do not export from ITsDone

Medium

Custom field schema varies by ITsDone edition

Salesforce Service Cloud logo

Salesforce Service Cloud gotchas

High

Data Export 512MB file size cap breaks large org exports

High

API Daily Request Limits vary by license edition

High

No automatic data backup in base Salesforce

Medium

Picklist dependencies silently break records when unmapped

Medium

Workflow rules fire unexpectedly during data load

Pair-specific challenges

  • ITsDone does not expose an API for workflow automations

    ITsDone Help Desk does not expose triggers, auto-assignment rules, or escalation workflows through its export interface. Any automated actions configured in ITsDone must be manually rebuilt in Salesforce Flow, Assignment Rules, or Omni-Channel routing after migration. We provide a structured automation audit report documenting every ITsDone rule (trigger event, conditions, actions) so the destination admin has an actionable rebuild checklist. Workflow rebuild is outside standard migration scope and requires a separate engagement or internal Salesforce admin work.

  • ITsDone stores attachment URLs rather than embedded binaries

    ITsDone Help Desk references attachments as URLs. When migrating over multiple sessions or if the source account is deactivated mid-migration, these URLs can expire and return 404 errors. We re-validate all attachment URLs at the start of the full migration and re-download from source on demand. Any attachments that cannot be retrieved are flagged in the reconciliation report for manual re-upload. This step is mandatory for legal or compliance migrations where attachment completeness is auditable.

  • Custom field schema varies by ITsDone edition

    ITsDone Help Desk editions differ in the number and type of custom fields available. Some editions restrict the total custom field count or limit field types (for example, no dependent dropdowns or calculated fields). We query the schema at the start of scoping and flag any ITsDone fields that cannot be represented in Salesforce (for example, a calculated field may become a read-only Formula field, or a dependent picklist may require a custom Visualforce component). Edition mismatches are documented before migration begins.

  • Salesforce field-level security blocks import without coordination

    Salesforce orgs enforce field-level security and validation rules that the migration user must bypass during data load. We coordinate with the customer's Salesforce admin to grant the migration user profile Modify All Data and API Enabled permissions, and we either temporarily suspend validation rules during load or extend them with a migration-context check (for example, ISBLANK(itsdone_ticket_id__c)). Skipping this step typically results in 5-30 percent record rejection on the first import attempt, particularly on Contact and Case which often have required field configurations.

  • KB article HTML fidelity requires post-migration review

    ITsDone Knowledge Base articles may contain embedded media links, internal ITsDone asset references, or HTML structures that do not render identically in Salesforce Knowledge. We migrate the article body as-is and flag any articles containing img tags with src attributes pointing to itsdone.helpdesk domains. The customer reviews these flagged articles post-migration and re-uploads media assets to Salesforce Files or an external CDN as needed.

Migration approach

Six steps for a successful ITsDone Help Desk to Salesforce Service Cloud data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

ITsDone Help Desk logo

ITsDone Help Desk

Source

Strengths

  • Strong fit for German-speaking IT services teams requiring native-language interface and support
  • Designed for small-to-mid-sized IT departments, typically under 100 agents
  • Simple agent management and SLA configuration without complex enterprise configuration
  • Microsoft 365 integration for teams already in the Microsoft ecosystem
  • GDPR-compliant data residency options valued by European customers

Weaknesses

  • Limited scalability above 100 agents compared to enterprise platforms
  • Minimal AI and automation capabilities versus modern competitors
  • Sparse third-party integration ecosystem
  • Reporting and analytics features lag behind Zendesk, Freshdesk, and Jira Service Management
  • International support availability is limited compared to global vendors
Salesforce Service Cloud logo

Salesforce Service Cloud

Destination

Strengths

  • Enterprise-grade security, compliance certifications, and audit logging available across all paid editions with Shield offering enhanced event monitoring.
  • Scalable multi-tenant cloud architecture supporting orgs from 5 users to 150,000+ seat enterprises without infrastructure management overhead.
  • Omnichannel contact center unifying email, live chat, phone, messaging, and social into a single Case timeline per customer interaction.
  • Rich workflow automation via Salesforce Flow, Process Builder, and Apex triggers enabling complex case escalation, routing, and field updates.
  • Native AI capabilities (Agentforce / Einstein) for case auto-routing, classification, suggested responses, and chatbot escalation without third-party add-ons.

Weaknesses

  • Per-seat pricing model with no contact limits creates unpredictable cost scaling for large organizations adding many agents over time.
  • No automatic data backup — organizations must purchase a third-party backup solution or build manual Data Loader exports to protect against data loss from human error, failed deployments, or integrations overwriting records.
  • Steep learning curve for non-technical users requiring dedicated admin resources and formal training investment before teams reach productive velocity.
  • Annual contract requirements and limited pro-ration on exit create significant switching cost friction, especially for organizations evaluating alternatives mid-cycle.
  • Add-on licensing (CPQ, Einstein Activity Capture, Shield, Data Cloud) can double effective per-seat cost without clear documentation of which features are included in base tiers.

Complexity grading

How hard is this migration?

Moderate Helpdesk migration. 1 of 7 objects need a manual workaround.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across ITsDone Help Desk and Salesforce Service Cloud.

  • Object compatibility

    C

    1 of 7 objects need a manual workaround.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    ITsDone Help Desk: Not publicly documented.

  • Data volume sensitivity

    B

    ITsDone Help Desk doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your ITsDone Help Desk to Salesforce Service Cloud migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about ITsDone Help Desk to Salesforce Service Cloud data migrations

Answers to the questions buyers ask most during ITsDone Help Desk to Salesforce Service Cloud migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between three and five weeks for accounts under 10,000 tickets, 2,000 contacts, and one active SLA policy with no knowledge base exceeding 200 articles. Migrations with large historical archives (over 50,000 tickets), multiple SLA entitlement policies, a knowledge base set exceeding 200 articles, or ITsDone editions with restricted API access extend to eight to fourteen weeks because of delta validation cycles, entitlement milestone configuration, and knowledge base HTML review scope.

Adjacent paths

Related migrations to explore

Ready when you are

Move from ITsDone Help Desk.
Land in Salesforce Service Cloud, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day