Helpdesk migration

Migrate from trueAct to Zoho Desk

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

trueAct logo

trueAct

Source

Zoho Desk

Destination

Zoho Desk logo

Compatibility

83%

10 of 12

objects map 1:1 between trueAct and Zoho Desk.

Complexity

CModerate

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from trueAct to Zoho Desk is a helpdesk platform consolidation that requires mapping trueAct's case-centric data model to Zoho Desk's department-organized ticket hierarchy. trueAct organizes work around Cases, Contacts, and Organizations with multi-channel aggregation; Zoho Desk uses Tickets organized under Departments with Agents and Teams. We preserve the full case history chain including thread continuity for email and chat channels, map Organizations to Zoho Desk Accounts, and handle the NPS survey history by consolidating response data into Zoho's feedback fields or a linked notes attachment depending on the customer's reporting needs. Agent and Team records migrate with permission structures mapped to Zoho Desk's role system. trueAct workflow automation does not export as structured data; we document the existing triggers and conditions for the customer's admin to rebuild in Zoho Desk's workflow rules. We do not migrate Workflows, Sequences, Automations, or Forms as code.

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

trueAct logo

trueAct

What's pushing teams away

  • Pricing is quote-only with no public tier breakdown, making it difficult to compare cost against competitors or forecast scaling expenses.
  • On-premise and private cloud deployments require internal IT resources for upgrades, patching, and infrastructure maintenance that not all teams can sustain.
  • Limited public documentation and smaller community compared to major CRM platforms makes self-service troubleshooting harder.
  • Workflow automation is less mature than enterprise platforms, with customers citing limited branching logic and conditional escalation options.

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 trueAct objects map to Zoho Desk

Each row shows how a trueAct 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.

trueAct

Case

maps to

Zoho Desk

Ticket

1:1
Fully supported

trueAct Cases migrate to Zoho Desk Tickets with full case history chain preserved. Standard fields (case status, priority, assigned agent, timestamps) map to Zoho Ticket fields. Multi-channel source metadata (email, chat, phone, web) transfers as thread channel indicators. We preserve Created Time and Modified Time via Zoho's assisted migration format or via API injection where the standard import tool drops created dates. Cases are imported before Contacts and Accounts so that the requester and account lookups are satisfied at insert time.

trueAct

Contact

maps to

Zoho Desk

Contact

1:1
Fully supported

trueAct Contact records (name, email, phone, custom fields, multi-address) map directly to Zoho Desk Contacts. Email address serves as the dedupe key. We handle multi-address records without splitting across objects, mapping the primary address to the standard contact fields and secondary addresses to custom fields or the description. Contact created and modified timestamps migrate via the assisted migration CSV format or API batch insert.

trueAct

Organization

maps to

Zoho Desk

Account

1:1
Fully supported

trueAct Organizations map to Zoho Desk Accounts, preserving the parent-child hierarchy where it exists. The Organization ID mapping carries through the migration so that linked Contacts attach to the correct Account via AccountExtId. Account-level fields (phone, email, website, industry, street, city) map to their Zoho Desk equivalents. Annual Revenue migrates as a numeric field if the Zoho Desk edition supports custom fields in that position.

trueAct

Agent

maps to

Zoho Desk

Agent/User

1:1
Fully supported

trueAct Agents (name, email, role, team assignment) map to Zoho Desk agents. We match by email address during import. If an agent with the given email already exists in Zoho Desk, the system maps to the existing user. Agents are migrated first, before Accounts, Contacts, and Tickets, so that the OwnerId and Assigned To lookups resolve correctly. Role translation from trueAct's role model to Zoho Desk's Agent, Light Agent, and Support Administrator roles is handled during scoping based on the customer's role matrix.

trueAct

Team

maps to

Zoho Desk

Team

1:1
Fully supported

trueAct Teams map to Zoho Desk Teams. Zoho Desk's native migration tool (Zwitch) does not transfer Teams, but we recreate the team structure and map agent memberships via the API or CSV format. Team Assignment must be turned on in Zoho Desk Settings before the migrated agents are assigned to teams. We coordinate this setting activation with the customer during the cutover phase.

trueAct

Custom Fields

maps to

Zoho Desk

Custom Fields

1:1
Mapping required

trueAct custom fields on Cases, Contacts, and Organizations map to Zoho Desk custom fields. Zoho Desk custom field labels are limited to 50 characters (we truncate with an underscore suffix if needed) and can only contain A-Z, 0-9, and _ - . $ @ ? , : ' / !. Other characters are replaced with underscores. The maximum total custom field count varies by edition: 50 (Standard), 150 (Professional), 230 (Enterprise), and 0 (Free edition). We flag any trueAct custom fields that exceed the target edition's limit during scoping and discuss field reduction or premium upgrade with the customer.

trueAct

NPS Surveys

maps to

Zoho Desk

Feedback / Custom Field

1:many
Mapping required

trueAct NPS responses include score, open-ended comment, timestamp, and the originating contact. Zoho Desk does not have a native NPS object. We consolidate NPS data by migrating the most recent score to a custom Contact field (nps_score__c) and archiving the full response history (all scores, comments, timestamps) into a linked Notes attachment on the Contact record. The customer chooses during scoping whether to use the consolidated score approach or archive all responses in the Notes field. We confirm the target schema handling before importing.

trueAct

Multi-channel Sources

maps to

Zoho Desk

Thread / Channel Metadata

1:1
Mapping required

trueAct aggregates cases from email, chat, phone, and web forms. We migrate the source channel metadata and preserve thread continuity for email and chat channels. The channel type (EMAIL, CHAT, PHONE, WEB) migrates as a Ticket field or tag. For email threads, we preserve the full reply chain with author attribution. Chat transcripts transfer as threaded comments. Phone case metadata transfers as a notes entry or custom field depending on available schema slots.

trueAct

Attachments

maps to

Zoho Desk

Attachments

1:1
Mapping required

File attachments on Cases and Contacts migrate to Zoho Desk's native attachment storage. We handle inline images and linked documents separately, preserving the association back to the parent Ticket or Contact record. Zoho Desk's assisted migration requires ZIP files with one CSV per module, with individual file sizes up to 30MB and a maximum of 10,000 rows per CSV. Large attachment sets are chunked accordingly. Zwitch does not migrate Knowledge Base attachments, but ticket attachments are included when the Ticket module is selected.

trueAct

Workflows

maps to

Zoho Desk

Workflow Rules

lossy
Mapping required

trueAct automation rules (routing, escalation, SLA timers) do not export as structured data and require manual documentation for rebuild in Zoho Desk. We provide a workflow audit questionnaire during scoping to capture triggers, conditions, and actions. Zoho Desk's workflow rules are scoped per module (Tickets, Contacts, Accounts) and gated by edition (5 per module on Standard, 15 on Professional, 30 on Enterprise). The rebuild is the customer's admin responsibility post-migration; we deliver the documented inventory as a rebuild guide.

trueAct

Products

maps to

Zoho Desk

Products

1:1
Mapping required

If trueAct tracks Products linked to Cases, we migrate Product records to Zoho Desk Products. Products file pattern follows Accounts_XX.csv naming convention in Zoho's assisted migration format. Product name and product code map from trueAct's product fields.

trueAct

Tasks

maps to

Zoho Desk

Tasks

1:1
Mapping required

Task records linked to Cases migrate to Zoho Desk Tasks. We preserve the task subject, due date, status, assigned agent, and any linked contact or account references. Tasks are imported after Contacts and Accounts so that the Lookup relationships resolve correctly. Zoho Desk's CSV import follows the Tasks.csv naming pattern with required fields subject and due date.

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.

trueAct logo

trueAct gotchas

High

Deployment model must be identified before migration scoping

Medium

Workflow automation does not export as structured data

Medium

NPS score history may exceed simple field mapping

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

  • Zoho Desk custom field limits vary by edition

    Zoho Desk enforces a maximum custom field count per edition: 50 on Standard, 150 on Professional, and 230 on Enterprise. The Free edition does not support custom fields. If your trueAct instance has more custom fields than the target Zoho Desk edition can accommodate, we flag the overflow during scoping and discuss field reduction (consolidating low-usage fields into a JSON-typed custom field or dropping rarely referenced fields) or upgrading the Zoho Desk edition. Custom field labels are also limited to 50 characters with a restricted character set (A-Z, 0-9, and _-.$@?,:'/!). We transform labels that exceed these constraints during the migration transform step.

  • Created date does not migrate through Zoho's standard import

    Zoho Desk's standard import tool does not preserve the Created Time of Tickets, Contacts, or Accounts by default. Records receive the import timestamp instead of the original trueAct creation date. We address this through Zoho's assisted migration format which supports YYYY-MM-DDTHH:MM:SS.000Z in the Created Time column, or via API batch insertion with the createdTime field set explicitly. We confirm the preferred method during scoping based on the customer's reporting requirements and the target Zoho Desk edition's API access level.

  • Deactivated agent cases cannot be migrated

    Zoho Desk does not migrate cases assigned to deactivated agents. If your trueAct instance has open or historically significant cases assigned to agents who are no longer active, we identify these records during the pre-migration audit and discuss reassignment options: either reactivate the agent in Zoho Desk (and map them back to the original agent), reassign the cases to an active agent before migration, or archive the affected cases in a separate status. We resolve this before the Tickets phase begins to avoid silent data loss.

  • Workflow automation does not export as structured data from trueAct

    trueAct workflow rules (case routing rules, escalation triggers, SLA timers) are stored as application configuration with no standalone export format. When migrating to Zoho Desk, automation logic must be manually documented and rebuilt. We provide a workflow audit questionnaire during scoping to capture the existing triggers, conditions, and actions, and we deliver a written workflow inventory document with recommended Zoho Desk equivalents. The actual rebuild is outside migration scope; it is the customer's admin responsibility or a separate services engagement.

  • NPS score history requires consolidation strategy

    trueAct NPS surveys store multiple response events per contact (score, comment, timestamp, originating contact). Zoho Desk has no native NPS object. We map the most recent NPS score to a custom Contact field and archive full response history in a linked Notes attachment. If the customer requires longitudinal NPS reporting in Zoho, we recommend connecting Zoho Desk to Zoho Analytics for reporting or migrating NPS data to a dedicated CX tool post-migration. We confirm the target handling approach with the customer before importing.

Migration approach

Six steps for a successful trueAct to Zoho Desk data migration

  1. Discovery and deployment model confirmation

    We audit the source trueAct environment across deployment type (on-premise, private cloud, or SaaS), record volumes by module (Cases, Contacts, Organizations, Agents, Teams, Products), active custom fields, NPS survey history, and workflow complexity. On-premise migrations require coordination with the customer's IT team for VPN access or database-level read access. We also confirm the target Zoho Desk edition (Express, Standard, Professional, or Enterprise) based on the customer's agent count, required workflow rules, and custom field limit needs. The discovery output is a written migration scope document with record counts and edition recommendation.

  2. Object mapping and field schema design

    We design the Zoho Desk destination schema including departments (mapped from trueAct's team structure or case categories), custom fields (with 50-character label limits and restricted character sanitization), and workflow rule slots per module. We flag any trueAct custom fields that exceed the target edition's limit and propose consolidation or upgrade paths. For NPS data, we finalize the consolidation strategy (most recent score to custom field plus full history in Notes) with the customer. Agent role translation from trueAct to Zoho Desk roles is documented for the User provisioning step.

  3. Agent provisioning and team structure recreation

    We extract every distinct trueAct agent and map them to Zoho Desk users by email. Teams are recreated in Zoho Desk (since Zwitch does not transfer teams automatically) and agents are assigned to teams during the CSV import or API batch. We confirm with the customer that Team Assignment is enabled in Zoho Desk Settings before migration begins. Cases assigned to deactivated trueAct agents are flagged and reassigned to active agents or archived per the agreed strategy before the Tickets phase.

  4. Accounts and Contacts migration

    Organizations migrate to Zoho Desk Accounts first, preserving parent-child hierarchy and Account IDs for Contact linking. Contacts import second with AccountExtId resolved to the correct Account lookup. Custom fields on both objects are created in Zoho Desk before import using the field schema from the mapping step. Email serves as the dedupe key for Contacts. Created and Modified timestamps use the assisted migration CSV format or API injection to preserve the original dates. NPS scores and archived response history attach to the Contact record post-import.

  5. Tickets with thread continuity

    Cases migrate to Tickets in dependency order: Accounts and Contacts must be present so that the requester and account lookups resolve. Multi-channel thread metadata (EMAIL, CHAT, PHONE, WEB) transfers as channel type indicators on the ticket thread. Email thread continuity is preserved with full reply-chain attribution. Chat transcripts and phone metadata land as threaded comments. We use the assisted migration format or API batch insertion to preserve Created Time. Attachments on cases transfer to Zoho Desk's native attachment storage with parent record linkage. Any remaining open cases on deactivated agents are resolved before this phase.

  6. Cutover, delta sync, and workflow handoff

    We freeze trueAct 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 workflow audit questionnaire output as a written rebuild inventory document for the customer's admin, with each trueAct automation mapped to a recommended Zoho Desk workflow rule equivalent. We support a one-week post-migration validation window. We do not rebuild workflows, automations, or forms inside the migration scope; those are the customer's admin responsibility post-migration.

Platform deep dives

Context on both ends of the pair

trueAct logo

trueAct

Source

Strengths

  • Aggregates cases from email, chat, phone, and web channels into one queue
  • Offers on-premise, private cloud, and public SaaS deployment flexibility
  • Includes native NPS survey and satisfaction tracking
  • API access enables custom integrations with ERP and billing systems
  • AI-assisted routing and suggested responses for agent productivity

Weaknesses

  • Quote-only pricing model creates friction in sales evaluation
  • Smaller user community and limited public documentation versus major platforms
  • Workflow automation capabilities lag behind enterprise-grade service desk tools
  • Requires IT overhead for on-premise and private cloud maintenance
  • Scaling cost predictability is poor without published tier thresholds
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 trueAct 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

    trueAct: Not publicly documented — enterprise customers receive per-deployment limits in their contract..

  • Data volume sensitivity

    B

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

Estimator

Estimate your trueAct 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 trueAct to Zoho Desk data migrations

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

Can't find your answer?

Walk through your trueAct to Zoho Desk 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 Cases and 5,000 Contacts with no NPS history complexity. Migrations with NPS response history spanning multiple years, on-premise trueAct environments (requiring VPN or database-level access), large Teams structures with complex routing rules, or multi-channel thread continuity requirements move to seven to eleven weeks because of deployment-relative URL handling, NPS consolidation mapping, and thread metadata preservation. We scope the timeline during discovery based on record counts and deployment model.

Adjacent paths

Related migrations to explore

Ready when you are

Move from trueAct.
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