Migrate from TeamSupport to Zoho Desk

TeamSupport Tickets map directly to Zoho Desk Tickets with status, priority, type, assignee, and department mapped 1:1. The TeamSupport AssigneeUserId resolves to a Zoho Desk Agent record (pre-created before migration), and TeamSupport GroupId maps to a Zoho Desk Department via the Team pre-creation worksheet. Custom fields on tickets migrate to department-scoped custom fields that we define in each destination department during schema setup. Ticket history and thread chronology are preserved by ordering thread entries chronologically on insert.

TeamSupport Agents (Users) cannot be created via API and must be pre-created in Zoho Desk before migration begins. We extract every distinct Agent from TeamSupport (email, name, role), provide a pre-creation worksheet with exact email matches, and confirm System Admin status translates to Support Administrator role in Zoho Desk. Agent-to-ticket assignments resolve at migration time against the pre-created Agent records. Any Agent without a matching Zoho Desk user is held in a reconciliation queue for the customer's admin to provision.

TeamSupport Groups do not have a direct Zoho Desk equivalent. We map Groups to Zoho Desk Departments or Teams depending on the customer's usage: if Groups function as organizational buckets, Departments is the right target; if they function as team-based routing, Teams within a Department is more appropriate. We make this determination during discovery and configure the Department or Team structure in Zoho Desk before ticket migration begins. Ticket-to-group associations map to Department or Team assignment on the Zoho Desk Ticket record.

TeamSupport Customer records map to Zoho Desk Contacts. If a TeamSupport Customer has an associated Company name, we create a Zoho Desk Account first and link the Contact to it via AccountExtId. Email serves as the dedupe key. If the TeamSupport Customer record has no company association, the Contact is created without an Account link. We preserve customer-to-ticket linkage so that opening a Zoho Desk Ticket shows the linked Contact immediately.

TeamSupport Products map to Zoho Desk Products. The Product name, product code (SKU), and custom fields migrate directly. Product-to-ticket linkage is preserved via a custom field on the Zoho Desk Ticket that stores the source TeamSupport Product ID, since Zoho Desk does not have a native product-to-ticket association model. If the customer relies heavily on product tracking in tickets, we recommend configuring a multi-select custom field on the Ticket department to capture the linked product.

Zoho Desk does not have a native Product Versions object. We evaluate two approaches during discovery: (1) storing version names as a custom field on the Zoho Desk Product record, suitable for products with fewer than 10 versions; (2) creating a separate Asset or custom object to track product versions linked to Products. The choice depends on how the customer uses versions in ticket context. We configure whichever approach is selected during Zoho Desk schema setup before data migration.

Zoho Desk does not have a native Product Lines object. If the customer uses Product Lines to categorize tickets or filter reporting, we map Product Line to a Zoho Desk custom field on the Product record or to a Knowledge Base category hierarchy. We determine the right approach during discovery based on how Product Lines appear in ticket data and reporting.

TeamSupport custom fields on Tickets, Users, Products, Product Versions, Product Lines, and Inventory Assets map to Zoho Desk custom fields. Custom fields in Zoho Desk are scoped per department, which means we must define the same custom field in each Zoho Desk department that will receive tickets. Dropdown custom fields require explicit value mapping: TeamSupport picklist values that do not exist in Zoho Desk default to null. We produce a value-mapping table during discovery and the customer approves it before migration. Custom field label length in Zoho Desk is capped at 50 characters.

TeamSupport does not expose a bulk-attachment export endpoint. We download each attachment individually via the TeamSupport API and re-upload to Zoho Desk using the Zoho Desk attachment endpoint. Large attachment batches are chunked with retry logic and exponential backoff to handle transient timeouts. Original filenames and MIME types are preserved. For accounts with over 2,000 attachments, the sequential nature of this process extends the migration timeline and requires sufficient API rate-limit headroom on the Zoho Desk destination. Zoho Desk's native Zwitch tool explicitly drops attachments, which is why a custom API-led migration is the appropriate method.

TeamSupport Conversations (internal notes and public replies) migrate to Zoho Desk Ticket Thread entries in chronological order. Agent versus customer authorship is flagged so the destination applies the correct display logic (public reply vs internal note). We set the CommentType field to indicate whether each entry was an internal or external communication in the source system. Thread chronology is preserved by setting the comment timestamp to the original TeamSupport timestamp.

TeamSupport Knowledge Base articles and categories migrate to Zoho Desk Knowledge Base with category hierarchy preserved. Article-to-category assignments and article visibility settings map directly. Article content migrates as HTML. If TeamSupport articles include embedded images, we download and re-upload them as Zoho Desk attachment references to preserve display in the Knowledge Base.

TeamSupport Ticket Tags migrate as flat tags in Zoho Desk. If the source uses a nested tag hierarchy, we flatten it to a single-level tag structure. Zoho Desk's tag system is a flat array per ticket, so multi-level taxonomy requires a custom field to preserve hierarchy context. We make this determination during discovery and configure accordingly.

Zoho Desk does not have a native Inventory Assets object. TeamSupport Inventory Asset records (linked to Products and Tickets) are migrated as a set of custom fields on the related Zoho Desk Product or Account, or as a custom Zoho Creator application if the customer's asset inventory is complex. We assess asset record complexity during discovery and recommend the appropriate landing structure before migration.

TeamSupport workflow automation rules (Create, Update, and Time-Based triggers) are not accessible via the TeamSupport public API. We cannot migrate them as code. We document current routing and escalation logic by analyzing historical ticket assignments, and we deliver a written automation inventory with a Zoho Desk Blueprint rebuild worksheet during scoping. The customer's admin or a Zoho implementation partner rebuilds escalation and routing automation manually post-migration. This is standard scope for all helpdesk migrations.