Helpdesk migration
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
Source
Zoho Desk
Destination
Compatibility
9 of 12
objects map 1:1 between ITsDone Help Desk and Zoho Desk.
Complexity
CModerate
Timeline
2-4 weeks
Overview
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.
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.
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 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
Zoho Desk
Ticket
1:1ITsDone 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
Zoho Desk
Ticket Comment / Thread
1:1ITsDone 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
Zoho Desk
Contact and Account
many:1ITsDone 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
Zoho Desk
Agent
1:1ITsDone 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
Zoho Desk
Tag
1:1Tags 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
Zoho Desk
Knowledge Base Article
1:1ITsDone 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
Zoho Desk
SLA Policy
1:1ITsDone 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
Zoho Desk
Custom Field (Tickets module)
lossyITsDone 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)
Zoho Desk
Attachment (Ticket)
1:1ITsDone 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
Zoho Desk
Blueprint (Manual Rebuild Required)
1:1ITsDone 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
Zoho Desk
Products
1:1ITsDone 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
Zoho Desk
Ticket Created Time / Modified Time
lossyITsDone 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.
| ITsDone Help Desk | Zoho Desk | Compatibility | |
|---|---|---|---|
| Ticket | Ticket1:1 | Fully supported | |
| Ticket Comment / Thread | Ticket Comment / Thread1:1 | Fully supported | |
| Customer | Contact and Accountmany:1 | Fully supported | |
| Agent | Agent1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Knowledge Base Article | Knowledge Base Article1:1 | Fully supported | |
| SLA Policy | SLA Policy1:1 | Fully supported | |
| Custom Ticket Field | Custom Field (Tickets module)lossy | Fully supported | |
| Attachment (Ticket) | Attachment (Ticket)1:1 | Fully supported | |
| Workflow Automation | Blueprint (Manual Rebuild Required)1:1 | Fully supported | |
| Products | Products1:1 | Mapping required | |
| Historical Timestamps | Ticket Created Time / Modified Timelossy | 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
Zoho Desk gotchas
Agent email identity determines comment ownership after migration
Blueprints and SLA policies do not export via API
File upload capped at 10GB per migration batch
Tier-gated export and migration capabilities
Inbound migration is two-phase with a hard Phase 2 cutoff
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
ITsDone Help Desk
Source
Strengths
Weaknesses
Zoho Desk
Destination
Strengths
Weaknesses
Complexity grading
Moderate Helpdesk migration. 4 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across ITsDone Help Desk and Zoho Desk.
Object compatibility
4 of 7 objects need a mapping; the rest are 1:1.
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 Zoho Desk migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave ITsDone Help Desk
Other ways to arrive at Zoho Desk
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.