Migrate from Helpmonks to Zendesk

Helpmonks Conversations map to Zendesk Tickets. The Conversation subject becomes Ticket Subject, the full thread history becomes Ticket Comments (public comments for customer-facing replies, private comments for internal notes). Helpmonks internal notes flagged during extraction map to Zendesk private comments if the destination is Enterprise or to a custom field migration_note__c on the Ticket if the destination tier does not support private comments at the API level. We use Zendesk's POST /api/v2/tickets endpoint with comment injection and preserve thread ordering by setting the Ticket created_at timestamp to the original Conversation created_at.

Helpmonks Customer records map to Zendesk End User records. The customer email becomes the User email, name maps to name, and any company association maps to Zendesk organization_id via an Organization lookup we pre-create from Helpmonks company data. Customer interaction history is preserved as Ticket comments on any migrated Tickets linked to that User.

Helpmonks Mailboxes (up to 250 supported) map to Zendesk Inboxes or Views depending on destination configuration. If the Zendesk account uses multiple Inboxes for channel separation, we map each Helpmonks Mailbox to a corresponding Zendesk Inbox. If the account uses a single Inbox with Views for segmentation, we map Mailboxes to Views with a filter on the mailbox_origin tag. The customer decides inbox architecture during scoping.

Helpmonks Labels are flat tag strings. We map them to Zendesk Tags on the Ticket. Label color metadata does not have a Zendesk equivalent and is not preserved. Label-based automation rules in Helpmonks do not migrate; we document each label-assignment trigger as a Zendesk Trigger rebuild recommendation in the automation inventory deliverable.

Helpmonks User records with agent roles map to Zendesk Agent records. We match by email address. Role and permission data migrates to Zendesk by mapping Helpmonks role names (Admin, Agent, Viewer) to Zendesk role equivalents (Admin, Agent). SSO-configured Helpmonks accounts require re-authentication against the Zendesk IdP post-migration; we flag this in the discovery output.

Attachments embedded in Helpmonks Conversation messages migrate as Zendesk Ticket comment attachments via the Zendesk comments endpoint. Files exceeding 20 MB are chunked using multipart upload to avoid payload limits. We validate attachment integrity by comparing file hash after load against the source hash. Zendesk enforces a 50 MB per-attachment limit; files above this threshold are flagged for the customer to store in an external asset manager and link by URL.

Helpmonks custom fields on Conversations (including CSAT ratings) map to Zendesk custom ticket fields. We create the Zendesk custom field with the matching type (dropdown, text, numeric, checkbox) before migration. Dropdown and multi-select custom field values in Zendesk copy to Tags automatically per Zendesk behavior; we document this in the scoping report and advise whether to keep or suppress the tag copy behavior. CSAT numeric scores migrate as integer custom fields.

Helpmonks Knowledge Base articles migrate to Zendesk Guide Articles. We map article title, body content, and category assignment to Zendesk Article, Section, and Category hierarchy. Zendesk Guide requires manual activation before migration; we include a Guide activation checklist in the pre-migration preparation steps. Article formatting and embedded media migrate as-is; any media that cannot render in Zendesk's article editor is flagged for manual correction post-migration.

Helpmonks Knowledge Base categories map to Zendesk Guide Sections. Nested category depth in Helpmonks maps to Zendesk section hierarchy; however, Zendesk Guide on non-Enterprise tiers limits subsection depth. We advise customers on their Guide tier and adjust the category mapping accordingly. Enterprise Zendesk Guide allows up to five subsection levels and 20 subsections per parent section, which covers most Helpmonks Knowledge Base structures.

Helpmonks email campaigns and sequences are marketing automation objects with trigger conditions and delay rules that have no direct Zendesk equivalent. Zendesk does not include an email campaign module at the Support tier. We extract campaign names, sequence step order, and email template bodies as a written inventory document. The customer's admin rebuilds these in an email marketing tool (Mailchimp, HubSpot, Klaviyo) or a Zendesk partner integration if the customer licenses Zendesk Sunshine or a third-party cadence tool.