Migrate from Thena to Zoho Desk with precision & ease

A seamless, customizable migration solution for moving your Thena data with perfect fidelity and minimal disruption.

Book free consultation

Last updated August 2026

Thena
Zoho Desk
MIGRATION OVERVIEW

Why teams migrate from Thena to Zoho Desk

The core problem
Migrating from Thena to Zoho Desk requires a fully custom ETL pipeline — no native migration path, third-party connector, or CSV import tool supports this source-to-destination pair with conversation threading intact. The two platforms have fundamentally different data architectures: Thena organizes support around a Slack-native Account → Contact → Request → Messages model, while Zoho Desk enforces a Organization → Department → Ticket → Threads/Comments hierarchy where every ticket must be assigned to a department — a concept Thena does not have. Core transformation work includes resolving Slack user identities to email addresses, converting Slack mrkdwn to HTML for thread content, building a department routing table before any ticket is created, and managing Zoho Desk's credit-based API limits rather than simple rate limits. Budget 72–120 engineer-hours for a mid-size dataset of 5,000–30,000 requests.
Why this matters for your migration
KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Thena to Zoho Desk migration.

Most Critical

Mandatory Department Assignment

Zoho Desk requires a valid departmentId on every ticket creation request, but Thena has no native department concept, so a routing table mapping Thena Slack channels or teams to Zoho departments must be fully defined and loaded before any ticket write operations begin.

Blocks all downstream imports if mapped wrong

Slack Identity Resolution

Thena stores user identity as Slack User IDs and Slack display names rather than email addresses, requiring a resolution step that maps each Slack identity to a verified email before Zoho Desk contacts can be created or matched.

Mrkdwn-to-HTML Conversion

Thena message bodies are stored in Slack's mrkdwn format, which must be transformed into HTML before being written as Zoho Desk threads, since Zoho Desk's thread API expects HTML-formatted content.

Credit-Based API Rate Limits

Zoho Desk enforces a daily credit pool — not a per-minute request rate — where ticket creates, thread creates, and attachment uploads each consume credits, and the pool is shared across all integrations in the org, requiring careful throughput budgeting across migration days.

Two-Step Attachment Upload Flow

Attachments must first be downloaded from time-limited Thena or Slack CDN URLs during extraction, then uploaded to Zoho Desk via a two-step API flow with a 20 MB per-file ceiling, making attachment handling one of the most operationally complex parts of the pipeline.

Thread vs. Comment Separation

Thena stores all conversation entries in a single message array, but Zoho Desk distinguishes between customer-visible Threads and internal Comments, requiring each Thena message to be correctly classified and routed to the appropriate Zoho Desk endpoint during load.

COMPLETE COVERAGE

Intelligent Human-Verified Data Mapping

Our migration engineer precisely maps every data point from Thena to Zoho Desk, ensuring perfect continuity for your customer support operations.

Thena
Zoho Desk
Conversations
Tickets
Messages
Ticket Threads
Customers
Accounts
Contacts
Contacts
Agents
Agents
Teams
Teams
Channels
Departments
Tags
Ticket Tags
Custom Fields
Custom Fields
Custom Fields
Contact Custom Fields
Kanban Boards
null
SLA Policies
SLA Policies
Request Types
Departments
Macros
null
Webhooks
null
Internal Notes
Ticket Comments
Attachments
Attachments
CSAT Responses
null
Analytics Reports
null
Automations
null
Knowledge Base Articles
Knowledge Base Articles

Looking for more entity mappings?

Contact our team
MIGRATION RISK ASSESSMENT

Every migration risk, already solved

Migration between platforms is full of edge cases. Our engineers have identified every risk from Thena to Zoho Desk and built proven solutions for each one.

High complexity
  • Conversation Threads
    Threaded message history is not preserved by Zoho Desk's CSV import and must be written via the Threads API individually, with mrkdwn-to-HTML conversion applied per message and customer versus agent direction correctly identified for each entry.
    Solved
  • Attachments
    Slack CDN attachment URLs are authenticated and time-limited, meaning any attachment not downloaded during the extraction phase will be permanently inaccessible, and files exceeding the 20 MB Zoho Desk ceiling must be handled or excluded before the load phase.
    Solved
  • API Credit Budget
    Zoho Desk's credit-based daily limits are shared org-wide across all integrations, meaning an Enterprise org with 50 agents has roughly 150,000 credits per day, and a dataset of 10,000 tickets with average thread depth can consume 50,000–60,000 credits per day, requiring the migration to be staged across multiple days.
    Solved
Custom engineering
  • Tickets (Requests)
    Requests map directly to Zoho Desk tickets, but every ticket requires a departmentId that Thena does not provide, making the department routing table a hard prerequisite and a source of bulk failure if incomplete.
    Handled
  • Internal Notes / Comments
    Internal notes must be posted as Zoho Desk Comments with isPublic set to false; misclassification during the Thena message-type mapping step would expose internal notes to customers.
    Handled
  • Contacts
    Zoho Desk requires either a lastName or an email address for every contact record, and Thena contacts identified only by Slack display names will fail creation unless Slack identity resolution is completed upstream.
    Handled
  • Custom Fields (AI Metadata)
    Thena AI-generated fields such as tags, summaries, and sentiment scores have no native equivalents in Zoho Desk and must be pre-created as cf_* custom fields in the target org before ticket creation, otherwise all custom field writes will silently fail or error.
    Handled
  • Request Status
    Thena statusName values are free-form strings that do not map one-to-one to Zoho Desk's fixed ticket status vocabulary, requiring an explicit status translation table to avoid all migrated tickets defaulting to a single open state.
    Handled
  • Unformalized Requests
    Thena workspaces may contain request objects that were never converted into formal tickets, and a scoping decision on whether to migrate, skip, or flag these records must be made before extraction begins to avoid polluting the Zoho Desk ticket queue.
    Handled
Clean transfer
  • Accounts
    Accounts map directly between platforms with accountName as the required field, making this the most straightforward entity to migrate provided names are clean and deduplicated before load.
    Clean
What Our Customers Say

Real migration stories

Soubhi Alhayek
Direct Review
“Overall a great experience. We had to go back a few times to get everything just right, which was totally expected. The transition was smooth, and there was no data loss.”
Soubhi Alhayek Head of Customer Experience, Kilgour MD
Jacs Orr
Direct Review
“One of the easiest migrations I've ever been through. The team took care of everything — all our data, customer interactions and macros. The process was clear, straightforward and we felt supported all the way. An absolutely seamless experience for our support team and our customers.”
Jacs Orr Operations Manager, New Zealand Honey Co.
Morgan Newlon
Direct Review
“Fantastic at both guiding us through the process and helping us fix things as they come up and dial them in.”
Morgan Newlon Dir. of Sales and Operations, Roofnest
Alec D.
Reviewed on G2
“The ease of the process and that ClonePartner was informing me what was going on at every step. If you're on the fence, do it. ClonePartner are great!”
Alec D. Customer Experience Manager
Jamie Lenda
Direct Review
“They were SO helpful. We had a few hiccups because our migration was in the middle of the process, but they were really flexible and did multiple delta migrations for us. We were able to map a lot of our old ticket data so it's usable for comparisons in the future.”
Jamie Lenda Director of Ecom Operations, Natural Life
See all customer stories →
CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Thena to Zoho Desk exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Conversation Type

Filter by chat, email, or social media conversations

Tag-Based Selection

Migrate tickets with specific tags only

User Selection

Migrate tickets for specific users or agents

Time Range

Migrate tickets from a specific time period

Data Types

Tickets & Conversations

Full conversation history with all metadata

Automations & Macros

Workflows, templates, and automation rules

Knowledge Base

Articles, categories, and help center content

Customer Profiles

Customer information and interaction history

ZERO DOWNTIME

Your timeline. Our engineers.

A dedicated engineer runs your migration, planned around your schedule and your data.

No babysitting a wizard. Avoid debugging errors yourself.

Looking for a more detailed migration timeline?

Contact our team

Speed

The migration timeline depends on both our turnaround time and yours.

We can complete a migration in under a day when the accounts are connected and the sample migration is approved promptly.

Background Sync

We also support migrating the newest records first, so you can go live faster while the rest of the data is synced in the background.

Data Volume Impact

Larger data volumes may require longer migration windows.

Continuous Operation

Weekend migrations minimize disruption to your customer service operations.

MIGRATION TIMELINE

Your Thena to Zoho Desk migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M 2M 5M 10M+
Checklist ~3 days
Sample 1 day
Review ~2 days
Full 2 days
Delta 1 day
Your team ClonePartner

Estimated total

~9 business days

1

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

2

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

3

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

4

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new Zoho Desk, with real-time progress tracking and comprehensive logging.

5

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Timeline is an estimate. Actual duration depends on API rate limits, data complexity, and your team's availability.

Get an exact timeline

Related Guides

Thena to Zoho Desk Migration: A Technical Guide

Complete Technical Guide

Thena to Zoho Desk Migration: A Technical Guide

No native Thena-to-Zoho Desk path exists. Build a custom ETL pipeline, budget for Zoho's credit-based limits, and plan for Slack mrkdwn conversion and 20 MB attachment caps.

19 min read Read
How to Export Data from Thena: Methods, API Limits & Formats

Export Guide

How to Export Data from Thena: Methods, API Limits & Formats

Thena offers ticket CSV and legacy XLSX/JSON exports plus a REST API at 60 req/min. Full extraction needs the Platform API — no bulk export exists for conversations, KB articles, or configs.

22 min read Read
Zoho Desk Alternatives 2026: Features, Migration, and Real Costs

Alternatives Guide

Zoho Desk Alternatives 2026: Features, Migration, and Real Costs

Zoho Desk is still the cheapest capable help desk at $7–$40/agent/month, but teams outgrowing its AI or channels face 2–4× cost increases moving to Freshdesk, Help Scout, Zendesk, or Intercom.

21 min read Read

Pros and cons of different migration options

Choosing the right approach is key because migrating from Thena to Zoho Desk isn't just about moving data – it's about protecting customer relationships.

Feature / Criteria ClonePartner Automated Tools CSV Import In-house migration
Custom Scripting for complex data ✓ Engineers build & maintain ✗ No ⚠ Manual ✓ Yes – but costly
Sandbox & Pilot Migrations ✓ Full sandbox + pilot plans ⚠ Limited ✗ No ⚠ Often Informal
Manual validation & reconciliation ✓ Automated + manual QA ✗ No ✓ Yes (Manual) ✓ Heavy manual effort
Backup & rollback plan ✓ Robust procedures ✗ No ✗ No ⚠ Often incomplete
Handles automation and integrations ✓ Full support ⚠ Partial ✗ No ⚠ Possible but fragmented
Post-migration engineer support ✓ Dedicated engineers ✗ No ✗ No ⚠ Limited SLA
Adaptable to API changes ✓ Proactive adaptation ✗ No ⚠ Manual fixes ⚠ Slower response
Turnaround / SLA predictability ✓ Predictable SLAs ⚠ Fast but brittle ⚠ Slow and manual ⚠ Often slower
Data Security & Compliance ✓ High – enterprise grade ⚠ Medium (depends) ⚠ Low (manual) ⚠ Hidden gaps common
Pricing predictability ✓ Transparent & fixed ⚠ Low (per-job) ⚠ Low (manual hours) ⚠ High/variable OPEX
End-to-end project management ✓ Full E2E delivery & PM ✗ No ✗ No ⚠ Often partial
Business impact & opportunity cost ✓ No diversion of staff ✗ No ✗ No ⚠ Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

  1. Speed of automation for bulk record migration
  2. Precision of engineers verifying integrity and business logic
  3. Pilot migrations and sandbox testing to catch issues early
  4. Real-time validation reports and rollback readiness
Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The Thena and Zoho Desk APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

  1. Field mapping and transformation
  2. Pagination, rate-limit handling, and throttling
  3. Preserving conversation threads, attachments, and internal notes
  4. Syncing custom fields, SLAs, and macros without breaking structure
Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

  1. 100% record-count parity between your Thena data and Zoho Desk
  2. Zero downtime during staged cutovers
  3. 99.9% attachment integrity (verified via checksum)
  4. Full automation and preservation of all business rules
Our standard: Includes full SLA preservation and 30 days of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure Thena or Zoho Desk exactly the same way—with unique automations and data. We customize every migration script to fit your exact workflow, tags, and triggers.

Our engineers adapt for:

  1. Custom fields, ticket forms, and workflows
  2. Multi-brand or multi-language setups
  3. Historical imports and partial (date-based) migrations
  4. Integration re-mapping for CRMs, chat, or feedback tools
The promise: If your data doesn't fit a standard template, we build one just for you.

Enterprise-Grade Security & Compliance

Your customer data is precious. Our migration process maintains the highest standards of security and regulatory compliance.

SOC 2 Type II

Independently audited compliance with rigorous security standards

ISO 27001

Certified information security management system

GDPR

Full compliance with EU data protection regulations

HIPAA

Certified for handling protected health information

AES-256 Encryption

Bank-grade encryption for all stored credentials

Latest TLS

Secure transfer protocol for all data in transit

Role-Based Access

We follow role-based access control for every migration project

Scheduled Deletion

Automatic data purging after migration completion

FAQ

Frequently Asked Questions

Everything you need to know about migrating from Thena to Zoho Desk. Can't find what you're looking for? Talk to our team.

Can I migrate from Thena to Zoho Desk using CSV import?
Only partially. Zoho Desk's CSV import handles accounts, contacts, and base ticket records, but it does not preserve ticket threads, attachments, comments, or conversation history. API-driven migration is required for full ticket history.
What are Zoho Desk API rate limits for a migration?
Zoho Desk uses a credit-based system, not simple rate limits. Daily credits depend on your edition and user count — for example, Enterprise gets 100,000 base + 1,000 per user. Creating a ticket costs 1 credit. Org-wide concurrency limits (5–25 simultaneous calls depending on edition) also apply.
How long does a Thena to Zoho Desk migration take?
For a mid-size dataset (5K–30K requests), expect 72–120 engineer-hours including pipeline development. The load phase alone can take 1–3 days depending on your Zoho Desk credit budget and concurrency limits.
How do I handle Slack user identities when migrating to Zoho Desk?
Thena stores Slack user IDs that must be resolved to email addresses. Build a Slack-to-email mapping using the Slack users.info API, then create or match Zoho Desk contacts with those emails. Store the original Slack handle in a custom field for reference.
What happens to Thena AI metadata like summaries and tags in Zoho Desk?
Zoho Desk has no native fields for AI summaries or sentiment. Pre-create custom fields (cf_ai_summary, cf_thena_source) in your Zoho Desk layout before migration. Thena tags can be mapped to Zoho Desk's tag system via the associateTag API.
How long does the Thena to Zoho Desk migration take?
Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.
Will my team lose access to Thena during the migration?
No. Your source system remains fully operational throughout the entire migration. We run the migration in the background with zero downtime to your current operations.
Will there be downtime when migrating from Thena to Zoho Desk?
No. Our migration process is designed for zero downtime. We use a staged approach with background sync and a fast cutover, ensuring no disruption to your live business operations.
How do I validate that everything migrated correctly?
Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.
Do I need professional help for this migration?
While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.
Does ClonePartner provide guidance before committing?
Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Still have questions?

Book a free 30-minute consultation with our migration engineers. We'll walk you through the exact approach for your Thena→Zoho Desk migration.

Contact our team

Ready to start your
Zoho Desk Migration?

Join hundreds of businesses who have successfully migrated with ClonePartner. Let's discuss your migration needs and build a plan that works for you.

Book free consultation

Attention to Detail

We meticulously handle every aspect of your migration, ensuring no data is lost during transfer and mapping every field correctly between platforms.

Custom Solutions

Every business is unique. We tailor your migration strategy to match your specific requirements, workflows, and data structures.

Security & Compliance

Your customer data is handled with enterprise-grade security protocols, ensuring compliance with GDPR, HIPAA, and industry standards.