Migrate from HelpNinja to Zendesk

HelpNinja Tickets map directly to Zendesk Tickets. Subject, description, status, priority, and created/updated timestamps transfer to their Zendesk equivalents. HelpNinja ticket IDs are preserved in a custom field helpninja_ticket_id__c for cross-referencing after cutover. Zendesk requires a requester (end-user) and will not import tickets where the Customer reference cannot be resolved; we flag unresolved requester references during scoping and map them to a placeholder user or escalate for admin resolution before the migration phase.

HelpNinja Customer records map to Zendesk End-Users. Email, name, phone, and organization affiliation transfer. If HelpNinja Customers are linked to an Organization-like construct, we map that to a Zendesk Organization record created prior to User import so the relationship is satisfied at insert time. Zendesk suspended users become unsuspended on import; suspended HelpNinja customers are imported as active and must be manually re-suspended in Zendesk Admin post-migration if that status must persist.

HelpNinja Agent records map to Zendesk Agents (Users with Agent role). We match by email address against the destination Zendesk account's User list. Agents without a matching Zendesk User are held in a reconciliation queue; the customer's Zendesk admin provisions missing agent accounts before record import resumes. Agent status (active/inactive) maps to the Zendesk user status field. Agent groups from HelpNinja map to Zendesk Groups, which the admin configures in Zendesk Admin before migration.

HelpNinja Tags transfer to Zendesk Tags as a plain string array. Zendesk does not enforce a tag limit per ticket, but tags are used in reporting and automation scoping. Note that Zendesk also mirrors custom drop-down and multi-select field values to Tags automatically; if HelpNinja used custom fields as the primary tag mechanism, Zendesk will generate additional tags beyond the explicit HelpNinja tag set, and the customer should review the combined tag inventory post-migration.

HelpNinja custom fields map to Zendesk Ticket Fields. Field type mapping is critical: text fields map to Zendesk text fields; numeric fields map to Zendesk numeric fields; date fields map to Zendesk date fields. Drop-down and multi-select fields map to Zendesk drop-down and multi-select, but Zendesk enforces a 3,500-row cap on field values and mirrors these values to Tags. We pre-create the Zendesk custom field schema and import field values via CSV before migrating ticket records so that the picklist is populated at the time of ticket insert.

HelpNinja ticket attachments transfer via the Zendesk API as inline images or file attachments linked to the parent ticket. Attachments over 1MB may be excluded from JSON-based export paths; we use direct API access for binary attachment transfer to ensure files over 1MB are not silently dropped. After migration, we spot-check a random sample of tickets to verify attachment presence and correct ticket linkage.

HelpNinja ticket conversations (customer replies and agent responses) map to Zendesk Ticket Comments. The author reference resolves to the Zendesk User record (Agent for internal notes, End-User for public comments). Comment timestamps and public/internal visibility flags transfer directly. Thread ordering is preserved by processing comments in chronological sequence during migration.

If HelpNinja exposes an Organization-like grouping on Customers, we map it to Zendesk Organization. Organization fields map to Zendesk Organization fields and custom organization fields. Organization is created before User import so that the OrganizationId lookup is satisfied on User insert. If HelpNinja does not expose organizations, this step is skipped and Customers are migrated as standalone users.

HelpNinja does not ship a native Knowledge Base, but if the customer maintained documentation in HelpNinja-adjacent tools or exports, those articles map to Zendesk Guide Articles. Categories map to Sections, and articles map within sections. The account owner must activate Zendesk Guide in Admin Center before the knowledge base import phase begins; we cannot migrate articles into an inactive Guide instance. Article translations, internal links, and attachments require post-migration review.

HelpNinja macros or saved replies map to Zendesk Macros as text templates. We do not migrate macros as active workflow components; Zendesk macros are independent objects that the admin can activate after migration. We extract the macro body and conditions from HelpNinja's export and document them in the handoff inventory. The customer's Zendesk admin recreates the macro in Zendesk Admin under Macros > Add Macro. This is a configuration step, not a data migration step.