Migrate from HubSpot Service Hub to Zoho Desk

HubSpot Tickets map directly to Zoho Desk Tickets. Standard fields (subject, status, priority, source channel, created date, closed date) migrate cleanly. HubSpot custom ticket properties map to Zoho Desk custom fields created in the Ticket module before migration. Ticket owner (HubSpot Owner) resolves to a Zoho Desk Agent record by email match.

HubSpot Contacts map to Zoho Desk Contacts. Standard properties (first name, last name, email, phone, lifecycle stage) migrate as text fields. Lifecycle stage is preserved as a custom Contact field in Zoho Desk. Multi-value contact properties (phone numbers, address fields) map to Zoho's structured contact fields or custom fields.

HubSpot Company records map to Zoho Desk Accounts. Company domain name becomes the Account Website field. If the Zoho destination already includes Zoho CRM, Accounts are shared between CRM and Desk modules, which is a key ecosystem benefit for teams consolidating on Zoho. We resolve the Account-Contact relationship at migration time before importing Contact records.

HubSpot email engagements do not map to a standalone object in Zoho Desk. We reconstruct each email engagement as a Ticket Thread record with thread type Email, preserving sender, recipient, timestamp, and body content. The parent Ticket is resolved via the HubSpot engagement's associated ticket ID. Thread order is preserved by timestamp sorting.

HubSpot call engagements (calls logged against tickets) map to Zoho Desk Ticket Threads with thread type Phone Call. Call duration, disposition, and recording URL are preserved in custom thread fields. HubSpot does not always expose recording URLs via API; we flag any unavailable recordings for manual re-link post-migration.

HubSpot meeting engagements associated with tickets map to Zoho Desk Ticket Threads with thread type Meeting. Meeting title, attendee list, start/end time, and notes content transfer. HubSpot meeting engagements not linked to a ticket are outside the helpdesk scope and do not migrate; they remain in HubSpot CRM if both CRM and Service Hub are in use.

HubSpot internal notes on tickets map to Zoho Desk Ticket Comments. Comment author is preserved as a name reference note (the Comment Author field is not migratable per Zoho Desk's Zwitch documentation). If the author is a known Zoho Desk Agent, we link by email; otherwise, we leave the author as a name string.

HubSpot task engagements linked to tickets map to Zoho Desk Tasks. Task subject, due date, completion status, and assignment migrate. Standalone tasks not linked to tickets (internal to-dos) do not have a native Zoho Desk equivalent and are flagged for manual recreation.

HubSpot ticket pipelines map to Zoho Desk Departments. Each pipeline name becomes a Department name, and pipeline stages become Department-specific ticket statuses. We preserve stage names, display order, and probability percentages as a reference document for the Zoho admin to reconfigure as Blueprint stages.

HubSpot Owners (agents/users) map to Zoho Desk Agents. We match by email address. Any HubSpot Owner without a corresponding Zoho Desk Agent record is held in a reconciliation queue; the customer's Zoho admin provisions the missing agent before record import resumes. Active/inactive status is preserved.

HubSpot knowledge base articles migrate to Zoho Desk Help Center articles. Article body, category structure, publish status, and SEO metadata transfer. HubSpot-specific features such as AI-readiness flags, Breeze-assigned articles, and article views/feedback counts do not migrate. Knowledge base attachments (files embedded in articles) do not migrate per Zoho Desk Zwitch limitations; we deliver a separate file inventory for manual reattachment.

HubSpot ticket tags migrate as string values into Zoho Desk Ticket Tags. HubSpot does not enforce a global tag taxonomy, so tags from different pipelines or sources may have naming collisions. We deduplicate and prefix with source context where necessary. Zoho Desk tag management is handled post-migration.

File attachments on HubSpot tickets and emails can be exported via HubSpot's API and uploaded to Zoho Desk Ticket Attachments. Large attachment volumes increase migration time and require Zoho Desk storage headroom. We advise customers to audit total attachment size during scoping and factor storage costs into the Zoho Desk plan selection.

HubSpot post-conversation CSAT survey responses do not have a native Zoho Desk equivalent object. We map response scores and free-text answers to custom Ticket fields as a reference record, but Zoho Desk's built-in CSAT survey functionality must be configured post-migration using Zoho Survey or a third-party integration. We document the original survey questions and responses as a CSV for the admin to reconfigure.