Migrate from Helpmonks to Zoho Desk

Helpmonks Conversations are the core ticket thread object and map directly to Zoho Desk Tickets. We preserve thread history (all message entries), assignee assignment, status, priority, and creation timestamp. Internal notes on a Conversation map to Zoho Desk Comments with the isPublic flag set to false; if the destination Zoho Desk account does not have departments configured, we create a default department to hold the private comment context. The Helpmonks Conversation subject becomes the Ticket subject, and the full message thread becomes Ticket Threads ordered by the original timestamp.

Helpmonks Customer records with an associated company map to Zoho Desk Contact linked to an Account. Lone Customers with no company association map to Zoho Desk Contact records without an AccountId (orphaned contacts are flagged for the admin to merge). We use Customer email as the dedupe key. Helpmonks Customer properties (name, email, phone, company, interaction history) map to Zoho Desk Contact fields. If the customer uses Zoho CRM integration, Contacts sync to the CRM Contact object natively.

Helpmonks Mailboxes (up to 250 shared mailboxes included) map to Zoho Desk Departments. Each Mailbox becomes a Zoho Desk Department with a support email address. Department-level routing rules (incoming email to specific Mailbox) translate to Zoho Desk email parsing rules scoped per Department. If a team has multiple mailboxes pointing to a single support team, we consolidate them into one Department to avoid ticket duplication. Department-level SLAs and business hours are configured in Zoho Desk post-migration as part of the admin setup.

Helpmonks Users map to Zoho Desk Agents by email match. We extract role information from Helpmonks (admin vs standard user) and set the corresponding Zoho Desk role (Support Administrator for Helpmonks admins, Agent for standard users). SSO-configured Helpmonks accounts may need re-authentication against the destination IdP post-migration. Deactivated Helpmonks Users are migrated as inactive Zoho Desk agents with their ticket history preserved but their open assignments reassigned via a reconciliation step.

Helpmonks Labels (used for tagging Conversations) map to Zoho Desk Tags. Label names migrate as Tag values. Label-colour metadata is platform-specific and does not transfer. Any label-based filtering or automation rules in Helpmonks do not migrate as code; we document them in the automation inventory for the customer's admin to rebuild in Zoho Desk as workflow rules or macro conditions.

Attachments embedded within Helpmonks Conversation messages migrate as binary blobs linked to the parent Ticket Thread. We chunk large attachments to respect Zoho Desk's API payload limits and validate attachment integrity (file name, size, MIME type) post-load. Zoho Desk's Zwitch import documentation confirms that attachments migrate for Tickets automatically when the Ticket module is selected, but our API-based approach handles this independently and provides explicit validation against the source file list.

Helpmonks custom fields on Customers and Conversations migrate to Zoho Desk custom fields on the corresponding module (Contacts or Tickets). Custom field data types are matched: string to string, integer to number, checkbox to checkbox, CSAT ratings to Zoho Desk's native Ticket CSAT field or a custom decimal field. Custom fields are scoped per Department in Zoho Desk, so we confirm which departments receive migrated tickets and create matching field definitions in each department's layout before import.

Helpmonks Knowledge Base article content (title, body text, categories) migrates to Zoho Desk Help Center Articles. Formatting, embedded media URLs, and knowledge-base-to-conversation linking behavior do not transfer. Articles are published to the Help Center under the same category structure as the source. We flag any articles with broken image links or interactive content for the customer's admin to review post-migration. This object adds significant scope to the migration timeline.

Helpmonks Email Campaigns (part of the bundled marketing suite) are comparable to Zoho Campaigns or Mailchimp. We do not migrate campaign data as functional records. We deliver a written inventory of existing Helpmonks campaigns including audience segments, template names, and send history for the customer's marketing team to reproduce in Zoho Mail campaigns or a third-party email platform. The customer chooses the replacement during scoping.

Helpmonks Live Chat installs as website widgets with trigger rules and proactive chat scripts. Chat history stored as part of the Conversations object migrates as Tickets, but widget configuration, chat triggers, and proactive message rules do not transfer. We deliver a configuration inventory of existing Helpmonks chat widgets (widget ID, triggering pages, automated message content) for the customer to re-implement in Zoho SalesIQ. This is a separate integration scope outside the ticket migration.

Helpmonks email sequences (drip campaign behavior attached to Customer records) have no direct Zoho Desk equivalent. Zoho Desk does not include sales engagement cadences as a standard feature. We deliver a written inventory of Helpmonks sequences including sequence names, step order, email templates, and trigger conditions for the customer's admin to rebuild in Zoho Mail or a dedicated sales engagement platform. This work is outside the ticket migration scope.

Helpmonks stores conversation reply history as part of the Conversation object. All reply entries migrate as Zoho Desk Ticket Threads (the chronological message log) and Comments (individual entries within a thread). Internal notes migrate as private Comments visible only to agents. We preserve the original timestamp on each Thread entry. The engagement history does not include standalone engagement objects separate from the Conversation, so no standalone Activity migration step is required.