Migrate from HelpNinja to Zoho Desk

HelpNinja Agents map to Zoho Desk Agent records. Resolution is by email address match. We extract all distinct agent emails from HelpNinja Tickets and Conversations, match against Zoho Desk Users during scoping, and flag any agent without a destination account for manual provisioning before migration begins. Deactivated HelpNinja agents cannot be assigned to records in Zoho Desk; their tickets must be reassigned to an active agent or the migration lands those records as unassigned.

HelpNinja Customer records map to Zoho Desk Contacts. First name, last name, email, phone, and company name migrate as standard Contact fields. We resolve the email address as the dedupe key during import to prevent duplicate Contact creation. If HelpNinja Customers contain organization-level data, we map to both Contact and Account in Zoho Desk and link them via the Account Lookup.

HelpNinja Customers that represent organizations (identified by a non-empty company name or domain field) map to Zoho Desk Account records in addition to Contacts. Multiple HelpNinja Customers sharing the same company name are consolidated into a single Zoho Desk Account with each individual Contact linked to it.

HelpNinja Tickets map to Zoho Desk Tickets. Subject, description, status, priority, and channel field migrate directly. The Assignee resolves via the Agent email mapping. Ticket External IDs from HelpNinja are preserved in a custom field hn_original_ticket_id__c so that conversation thread links back to the source record. Status values (Open, Pending, Resolved, Closed) map to Zoho Desk ticket status values with a customer-provided mapping table during scoping.

HelpNinja Conversation entries (agent replies, customer replies, internal notes) map to Zoho Desk Ticket Comments. The author (Agent or Customer) resolves to the corresponding Contact or Agent in Zoho Desk. Public replies map as public comments; internal notes map as private comments if the Zoho Desk role permits. Thread ordering is preserved by Created At timestamp, which is set as the comment timestamp rather than the system date because Zoho Desk cannot set Created At on tickets or comments via import.

HelpNinja Tags map to Zoho Desk Tags. Tags are imported as a multi-select picklist on the Ticket record and as Tag records linked via TicketTag associations. If a HelpNinja tag contains a colon-separated namespace (e.g., product:widget), we preserve the full string in Zoho Desk's tag rather than splitting it.

HelpNinja does not have a native Knowledge Base module. If the customer has used solved ticket descriptions as an informal knowledge base (a common pattern in small-team help desks), we extract unique, non-personal information from resolved ticket descriptions and deliver them as a structured CSV inventory titled 'Potential Knowledge Base Articles' for the customer's admin to evaluate and rebuild in Zoho Desk's Knowledge Base module. This deliverable is outside the standard migration scope and priced separately.

HelpNinja file attachments on Tickets and Conversations migrate as Zoho Desk Attachments linked to the parent Ticket. Zoho Desk's assisted migration limits file uploads to 10GB total; we flag if the HelpNinja attachment volume exceeds this and negotiate an exclusion (skip attachments) or a staged transfer with the customer before migration begins.

HelpNinja custom fields on Tickets and Customers (e.g., product line, contract tier, account region) map to Zoho Desk custom fields of equivalent type: text fields to single-line text, number fields to numeric fields, date fields to date fields, and dropdown fields to picklist fields. We create the destination custom fields in Zoho Desk during the pre-migration schema setup phase, before any records are imported. Picklist values are created automatically on import per Zoho Desk's import behavior.

HelpNinja's SLA configuration (if any) maps to Zoho Desk SLA Policies. First Response Time and Next Response Time from HelpNinja become Zoho Desk SLA Policy entries scoped to department or ticket channel. We document the existing SLA targets from HelpNinja during scoping and deliver a Zoho Desk SLA Policy configuration guide as part of the migration scope.

HelpNinja Teams map to Zoho Desk Teams. Migration Wizard and Zoho Desk's native import cannot transfer Teams automatically; we create the Teams in Zoho Desk during pre-migration setup and assign the migrated Agents to the corresponding Teams based on the source team membership extracted from HelpNinja. The customer provides the team structure during scoping.

We inventory every unique HelpNinja ticket URL referenced in customer communications, email threads, or documentation. For each URL, we generate a Zoho Desk URL Redirect rule or document the equivalent Zoho Desk ticket URL so that the customer's admin can configure redirects in Zoho Desk's portal settings. This prevents broken links in archived emails and external references after cutover.