Helpdesk migration

Migrate from ITsDone Help Desk to Zoho Desk

Field-level mapping, validation, and rollback between ITsDone Help Desk and Zoho Desk. We move data and schema; workflows are rebuilt natively in Zoho Desk.

ITsDone Help Desk logo

ITsDone Help Desk

Source

Zoho Desk

Destination

Zoho Desk logo

Compatibility

75%

9 of 12

objects map 1:1 between ITsDone Help Desk and Zoho Desk.

Complexity

CModerate

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

ITsDone Help Desk is a German-market niche platform without a published API, which makes data extraction the first technical constraint to solve before any migration work begins. We use a structured UI-based export process to pull Tickets, Customers, Agents, Tags, and Knowledge Base Articles, then map each object against Zoho Desk's department-centric schema. Attachment URLs stored in ITsDone can expire across multiple extraction sessions, so we re-validate and re-download every binary before re-attaching to destination Tickets. Workflow automations, triggers, and escalation rules do not export from ITsDone; we inventory every rule and deliver a Zoho Desk Blueprint rebuild checklist. Zoho Desk's credit-based API, multi-department structure, and per-department custom field scoping require schema planning before records move, particularly for teams migrating from ITsDone editions with limited field type support.

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

Zoho Desk logo

Zoho Desk

What's pulling them in

  • Deep Zoho ecosystem integration lets support data tie directly to CRM contacts, invoice records in Zoho Books, and custom apps built in Zoho Creator, providing a unified customer view without third-party middleware.
  • Pricing undercuts comparable platforms significantly: Enterprise at roughly $40 per agent per month versus Zendesk at comparable tiers, making it attractive for cost-sensitive teams scaling past 10 agents.
  • Blueprints and multi-level escalations allow teams to codify support workflows and enforce SLA routing automatically, reducing manual triage for mid-size support operations.
  • Multi-channel ticket ingestion unifies email, social media, live chat, and phone into a single queue view, giving agents one inbox without context-switching across channels.
  • The free tier up to 3 agents lets small teams validate the platform before committing, reducing financial risk for startups and micro-businesses evaluating help desk software.

Object mapping

How ITsDone Help Desk objects map to Zoho Desk

Each row shows how a ITsDone Help Desk object lands in Zoho Desk, 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

Zoho Desk

Ticket

1:1
Fully supported

ITsDone Tickets map to Zoho Desk Tickets with full thread history, internal notes, status, priority, and creation or modification timestamps preserved. We resolve ITsDone ticket ID references during scoping and establish the mapping table before import. Ticket status values from ITsDone normalize to Zoho Desk's status enumeration (Open, Pending, On Hold, Resolved, Closed). Priority maps directly. We handle the distinction between public replies and internal notes by routing them to Zoho Desk's Comments with the appropriate isPublic flag.

ITsDone Help Desk

Ticket Comment / Thread

maps to

Zoho Desk

Ticket Comment / Thread

1:1
Fully supported

ITsDone conversation threads map to Zoho Desk Ticket Comments. Author attribution (agent vs customer) migrates as the Zoho Desk commenter reference. Thread ordering preserves by ActivityDate. Internal notes from ITsDone map to isPublic=false in Zoho Desk so that the visibility boundary is maintained at migration completion.

ITsDone Help Desk

Customer

maps to

Zoho Desk

Contact and Account

many:1
Fully supported

ITsDone Customer records with a company association map to Zoho Desk Account (company name) plus Contact (individual). Customers without a company association map to Contact only. Email, phone, and any standard metadata fields migrate directly. Custom attributes on ITsDone customers parse into Zoho Desk custom fields on Contact, scoped to the department into which the ticket is imported.

ITsDone Help Desk

Agent

maps to

Zoho Desk

Agent

1:1
Fully supported

ITsDone Agent profiles (name, email, role, group assignment) transfer to Zoho Desk Agents. Role naming conventions differ: ITsDone role names map to Zoho Desk Role names via a scoping table we create during discovery. Agent group assignments from ITsDone map to Zoho Desk Teams. Any Agent without a matching Zoho Desk user email is placed in a reconciliation queue for the customer to provision before record import.

ITsDone Help Desk

Tag

maps to

Zoho Desk

Tag

1:1
Fully supported

Tags associated with ITsDone Tickets migrate as Tags in Zoho Desk. Zoho Desk enforces character restrictions and length limits on tag names, so we normalize tag values during extraction by removing restricted characters and truncating to the maximum length before import. The normalization rule is documented in the mapping table delivered during scoping.

ITsDone Help Desk

Knowledge Base Article

maps to

Zoho Desk

Knowledge Base Article

1:1
Fully supported

ITsDone Knowledge Base Articles, sections, and category structure migrate to Zoho Desk Help Center articles organized within their respective sections and categories. HTML content formatting carries over; post-migration review is recommended for embedded media, internal ITsDone links, and image references that point to ITsDone-hosted assets. We flag any internal asset URLs during extraction for customer remediation.

ITsDone Help Desk

SLA Policy

maps to

Zoho Desk

SLA Policy

1:1
Fully supported

ITsDone SLA configurations including business hours, first-response targets, and resolution targets transfer to Zoho Desk SLA Policies. Zoho Desk requires SLA Policies to be assigned at the department level, so we map ITsDone SLA rules to Zoho Desk SLA Policies scoped to the target department during migration. Teams without a Zoho Desk Professional license receive a written SLA configuration document for manual setup.

ITsDone Help Desk

Custom Ticket Field

maps to

Zoho Desk

Custom Field (Tickets module)

lossy
Fully supported

ITsDone custom ticket fields are parsed from the schema export and mapped to Zoho Desk custom fields on the Tickets module. Zoho Desk custom fields are scoped per department, which requires mapping each ITsDone custom field to a specific Zoho Desk department during schema design. Some ITsDone editions restrict field types, which we identify during discovery and document as pre-migration blockers or workaround notes.

ITsDone Help Desk

Attachment (Ticket)

maps to

Zoho Desk

Attachment (Ticket)

1:1
Fully supported

ITsDone stores attachment references as URLs rather than embedding binaries. We re-validate every attachment URL at the start of the extraction session, re-download assets from the ITsDone cloud storage endpoint, and re-attach binaries to the corresponding Zoho Desk Ticket after import. Attachment URL expiration (ITsDone Help Desk source platform gotcha) is mitigated by completing binary re-download before the migration window closes or the source account is deactivated.

ITsDone Help Desk

Workflow Automation

maps to

Zoho Desk

Blueprint (Manual Rebuild Required)

1:1
Fully supported

ITsDone workflow rules, triggers, auto-assignments, and escalation rules are not accessible through any export interface. We do not migrate automations as code. We deliver a structured automation audit report that inventories every ITsDone workflow with its trigger conditions, actions, and target records, paired with recommended Zoho Desk Blueprint equivalents and Macro configurations. The customer's admin uses this document as a rebuild checklist post-migration.

ITsDone Help Desk

Products

maps to

Zoho Desk

Products

1:1
Mapping required

ITsDone product records (if present in the source account) map to Zoho Desk Products with name, SKU, and description fields. Product associations on Tickets migrate as product link records in Zoho Desk.

ITsDone Help Desk

Historical Timestamps

maps to

Zoho Desk

Ticket Created Time / Modified Time

lossy
Fully supported

ITsDone preserves original ticket creation and modification timestamps. Zoho Desk sets the Created Time to the import timestamp unless a specific API handling path is used. We set ticket creation dates to the original ITsDone values via the Zoho Desk API during import to preserve the full historical record. Created-by attribution maps to the importing agent on tickets where the original creator is not provisioned in the destination.

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

Zoho Desk logo

Zoho Desk gotchas

High

Agent email identity determines comment ownership after migration

High

Blueprints and SLA policies do not export via API

Medium

File upload capped at 10GB per migration batch

Medium

Tier-gated export and migration capabilities

Low

Inbound migration is two-phase with a hard Phase 2 cutoff

Pair-specific challenges

  • ITsDone Help Desk has no published API

    ITsDone Help Desk does not expose a REST API or programmatic export endpoint according to current platform documentation. All data extraction must be performed through the platform's UI-based export layer, which limits extraction speed, field fidelity, and automation repeatability compared to API-led migrations from other platforms. We mitigate this by structuring a staged, multi-phase extraction process that pulls Tickets, Customers, Agents, Tags, and KB Articles through the available export interfaces, validating completeness at each phase before proceeding. Migration timelines are longer as a result, and record volume limits on UI exports may require multiple extraction sessions.

  • Workflow automations do not export from ITsDone

    ITsDone Help Desk does not expose workflow rules or automated actions through its export interface. Any triggers, auto-assignment rules, escalation timers, or macro sequences configured in ITsDone cannot be carried forward 1:1. We provide a structured automation audit report documenting every ITsDone rule (name, trigger type, conditions, and actions) so that the destination team has an actionable Zoho Desk Blueprint rebuild checklist. Macros (Zoho Desk Standard+) provide simpler replacements; Blueprint (Zoho Desk Professional+) covers complex multi-step process automation.

  • Attachment URL expiration mid-extraction

    ITsDone Help Desk stores attachment references as URLs rather than embedding binary files. When migrations run across multiple sessions or if the source account is deactivated mid-extraction, attachment URLs can expire and return 404 errors. We re-validate all attachment URLs at the start of each extraction phase and re-download assets from the ITsDone storage endpoint before attaching them to destination Zoho Desk Tickets. This adds extraction time proportional to the attachment volume but ensures no binary is missed.

  • Knowledge base attachments do not migrate to Zoho Desk

    Zoho Desk's native Zwitch migration tool explicitly notes that Knowledge Base attachments will not be migrated from the source platform. This limitation applies to any Zoho Desk migration method. We handle KB article body images by exporting them from ITsDone, uploading to Zoho Desk's media storage, and updating internal image URLs in the article HTML before import. This requires post-migration review of every KB article to confirm images render correctly in the destination help center.

  • Custom field schema depends on ITsDone edition

    ITsDone Help Desk editions vary in the number and type of custom fields available. Some lower-tier editions restrict the total number of custom fields or limit field types (for example, dependent dropdowns or calculated fields may not be exposed). We query the full field schema during scoping and flag any fields that cannot be represented in Zoho Desk's per-department custom field model. Edition constraints that cannot be resolved are documented as pre-migration blockers for the customer to address before data extraction begins.

Migration approach

Six steps for a successful ITsDone Help Desk to Zoho Desk data migration

  1. Discovery and export feasibility assessment

    We audit the source ITsDone Help Desk account through its UI export layer to identify available record types, field coverage, custom field schemas, tag taxonomy, Knowledge Base structure (articles, sections, categories), SLA policy configurations, and attachment volume. Because ITsDone has no API, we map the UI export capabilities against the migration scope and flag any record types or field types that cannot be extracted cleanly. This phase also captures the automation inventory needed for the rebuild checklist and confirms the ITsDone edition's custom field constraints.

  2. Object mapping and schema design for Zoho Desk

    We design the Zoho Desk destination schema based on the ITsDone export findings. This includes provisioning Zoho Desk departments (required for multi-department accounts), setting up Roles and Teams to match the ITsDone agent group structure, creating custom fields on Tickets and Contacts (scoped per department), configuring SLA Policies mapped from ITsDone SLA rules, and designing the Knowledge Base section and category hierarchy. Custom fields in Zoho Desk are department-specific, so we align the ITsDone field schema to the target department during design rather than after import.

  3. Attachment URL validation and binary pre-download

    We extract and validate every attachment URL referenced in ITsDone Tickets before any ticket records are extracted. Expired URLs are flagged for customer action (re-upload to ITsDone or accept as unavailable). Valid attachments are pre-downloaded to our migration staging environment. This step prevents the 404 cascade that occurs when ticket records are imported before their attachment binaries are available in the destination.

  4. Demo migration into a Zoho Desk sandbox

    We run a representative subset migration (typically 50-100 tickets, 20-50 contacts, and a sample Knowledge Base section) into a Zoho Desk department to validate object mapping, custom field population, tag normalization, SLA assignment, and thread fidelity. The customer's Zoho Desk admin reviews the demo output, spot-checks 25-50 records against the source, and signs off before production migration begins. Mapping corrections at this stage avoid rework in production.

  5. Production migration in dependency order

    We run the production migration in Zoho Desk's required dependency sequence: Agents first (to provision User references), then Accounts (from ITsDone company records), Contacts (with AccountId resolved), Tickets (with ContactId and AccountId resolved, thread comments and internal notes routed correctly, attachments re-attached from pre-downloaded binaries), Tags (normalized and linked to Tickets), Knowledge Base Articles (with HTML content and corrected image URLs), SLA Policies, and Products. Custom field data migrates as a separate phase after standard fields to ensure all parent lookups are satisfied first.

  6. Cutover, validation, and automation rebuild handoff

    We freeze ITsDone writes during cutover, run a final delta migration of any records modified during the migration window, then enable Zoho Desk as the system of record. We deliver the full migration reconciliation report (record counts per object, attachment log, and any records that could not be migrated with reasons) and the Zoho Desk Blueprint automation rebuild checklist to the customer's admin team. We do not rebuild ITsDone automations as Zoho Desk Blueprint flows within the migration scope; that work is performed by the customer's Zoho Desk admin using the checklist we deliver.

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
Zoho Desk logo

Zoho Desk

Destination

Strengths

  • Generous free tier for teams of up to 3 agents with no time limit, reducing financial risk for small support operations.
  • Per-agent flat pricing across tiers is significantly lower than Zendesk, Freshdesk, or Intercom at equivalent feature levels.
  • Tight integration with Zoho CRM, Zoho Books, and Zoho Creator provides a unified data ecosystem without third-party middleware.
  • Multi-channel ticket aggregation consolidates email, social, chat, and phone into a single queue view.
  • Assisted migration service handles the two-phase transfer process with Zoho's own migration team for inbound moves.

Weaknesses

  • The UI is frequently described as dated, clunky, and inconsistent across modules compared to modern SaaS competitors.
  • Advanced automation features including Blueprints, multi-brand, and live chat are tier-gated, limiting the free and Express plans to basic ticketing.
  • Non-Zoho integrations require custom Deluge scripting or external middleware, reducing flexibility for heterogeneous tech stacks.
  • Steep learning curve and complex customization options mean slower onboarding for new agents and ongoing training investment.
  • Export and migration capabilities are gated by plan tier, with data backup only available on higher plans.

Complexity grading

How hard is this migration?

Moderate Helpdesk migration. 4 of 7 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

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

  • Object compatibility

    C

    4 of 7 objects need a mapping; the rest are 1:1.

  • 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 Zoho Desk 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 Zoho Desk data migrations

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

Can't find your answer?

Walk through your ITsDone Help Desk to Zoho Desk migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most ITsDone to Zoho Desk migrations land between two and four weeks for accounts under 5,000 tickets, 2,000 contacts, and a straightforward custom field set. Migrations with high attachment volume (binary re-download extends extraction time), complex Knowledge Base structures exceeding 500 articles, multi-department Zoho Desk targets, or extensive custom field schemas move to five to ten weeks. The absence of a native ITsDone API adds conservative time to the extraction phase compared to API-led migrations from platforms with documented export endpoints.

Adjacent paths

Related migrations to explore

Ready when you are

Move from ITsDone Help Desk.
Land in Zoho Desk, 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