Migrate your Helpmonks data

Conversations is the core email thread object in Helpmonks. The API exposes a POST /api/v1/conversation/create endpoint specifically for importing existing conversations. We replicate full thread history including message body, timestamps, and assignee changes. Internal notes are preserved as private message flags where the destination supports it; otherwise we expose them as a custom field.

The Customer data model maps cleanly to standard CRM contact objects. Helpmonks stores contact name, email, company association, and interaction history. We migrate Customer records 1:1 and preserve the linked conversation history against each record.

Helpmonks allows up to 250 shared mailboxes on the Unlimited plan. The destination platform may structure shared inboxes differently (as Teams, Inboxes, or Queue objects). We map source Mailboxes to the equivalent destination container and flag any Mailbox-specific routing rules for manual reconfiguration post-migration.

Helpmonks uses a Label system for tagging conversations — comparable to Tags or Categories on other platforms. Label names and taxonomy migrate, but the label-colour metadata and any label-based automation rules require explicit review during the mapping phase since naming conventions differ between systems.

Helpmonks User objects store name, email, role, and SSO identity. We map Users to Owners or Agents in the destination. SSO-configured accounts may need re-authentication against the destination IdP post-migration, and we flag this as a manual step in the cutover checklist.

Helpmonks includes email campaign and sequence functionality — comparable to Audiences or Campaigns in platforms like Mailchimp or HubSpot. Campaign templates, audience segments, and send settings migrate; automated sequence timing and trigger conditions require reconfiguration since automation logic is destination-specific.

Helpmonks Live Chat installs on multiple websites as separate widgets. Chat history stored as part of the Conversations object migrates, but widget configuration, trigger rules, and proactive chat scripts are platform-specific and must be rebuilt at the destination.

The Knowledge Base in Helpmonks supports both private and public sites. We migrate article content and categories, but formatting, embedded media, and any knowledge-base-to-conversation linking behaviour require post-migration review to ensure parity in the destination.

Attachments embedded within Conversations migrate as binary blobs linked to the parent message. Large attachments are chunked to avoid payload size limits. We validate attachment integrity after load and flag any files that exceed the destination platform's size cap.

Helpmonks supports custom fields on Customers and Conversations, including CSAT ratings. Custom field definitions migrate as metadata, but values require explicit field-level mapping to the destination custom field schema. We flag any CSAT fields for review since not all platforms expose CSAT as a first-class object field.

Email sequences in Helpmonks are comparable to drip campaigns or automation workflows. We preserve sequence names, step order, and email templates, but the trigger conditions and delay rules must be re-implemented in the destination's automation engine.