Helpdesk migration
Field-level mapping, validation, and rollback between trueAct and Zoho Desk. We move data and schema; workflows are rebuilt natively in Zoho Desk.
trueAct
Source
Zoho Desk
Destination
Compatibility
10 of 12
objects map 1:1 between trueAct and Zoho Desk.
Complexity
CModerate
Timeline
3-5 weeks
Overview
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.
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 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
Zoho Desk
Ticket
1:1trueAct 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
Zoho Desk
Contact
1:1trueAct 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
Zoho Desk
Account
1:1trueAct 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
Zoho Desk
Agent/User
1:1trueAct 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
Zoho Desk
Team
1:1trueAct 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
Zoho Desk
Custom Fields
1:1trueAct 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
Zoho Desk
Feedback / Custom Field
1:manytrueAct 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
Zoho Desk
Thread / Channel Metadata
1:1trueAct 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
Zoho Desk
Attachments
1:1File 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
Zoho Desk
Workflow Rules
lossytrueAct 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
Zoho Desk
Products
1:1If 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
Zoho Desk
Tasks
1:1Task 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.
| trueAct | Zoho Desk | Compatibility | |
|---|---|---|---|
| Case | Ticket1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Organization | Account1:1 | Fully supported | |
| Agent | Agent/User1:1 | Fully supported | |
| Team | Team1:1 | Fully supported | |
| Custom Fields | Custom Fields1:1 | Mapping required | |
| NPS Surveys | Feedback / Custom Field1:many | Mapping required | |
| Multi-channel Sources | Thread / Channel Metadata1:1 | Mapping required | |
| Attachments | Attachments1:1 | Mapping required | |
| Workflows | Workflow Ruleslossy | Mapping required | |
| Products | Products1:1 | Mapping required | |
| Tasks | Tasks1:1 | Mapping required |
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.
trueAct gotchas
Deployment model must be identified before migration scoping
Workflow automation does not export as structured data
NPS score history may exceed simple field mapping
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 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.
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.
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.
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.
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.
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
trueAct
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 trueAct 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
trueAct: Not publicly documented — enterprise customers receive per-deployment limits in their contract..
Data volume sensitivity
trueAct 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 trueAct to Zoho Desk migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave trueAct
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.