Migrate from Helpmonks to Salesforce Service Cloud

Helpmonks Conversations map directly to Salesforce Case records. The Conversation subject becomes Case Subject, body and thread history migrate as CaseComments (public) or a custom private-comment field (internal notes), and assignee history is preserved in a custom field migration log. Status from Helpmonks (open, pending, resolved, closed) maps to Salesforce Case Status picklist values that we configure in the destination org before migration. Priority and Labels map to Case Priority and custom topic fields respectively.

Helpmonks Customer records map 1:1 to Salesforce Contact. Email address serves as the primary dedupe key. Company association in Helpmonks (customer.company) maps to AccountId on Contact, requiring that Account records are created before Contact migration to satisfy the Lookup. Any custom fields on the Helpmonks Customer object are mapped to Salesforce custom Contact fields of equivalent type.

Helpmonks Mailboxes (up to 250 included) map to Salesforce Queues. Each Mailbox name becomes a Queue label, and the Queue ID is assigned to Cases migrated from that Mailbox's Conversations. If the destination org uses Salesforce Service Cloud Omni-Channel, we map Mailbox assignment to Skills so that routing is preserved during the migration window before Omni-Channel is reconfigured in the destination.

Helpmonks Label names and taxonomy migrate to Salesforce Topics (via TopicAssignment records linked to Cases) or to a custom multi-select picklist field, depending on the customer's preference at scoping. Label-colour metadata and label-based automation rules do not migrate; we document every label in use and the recommended replacement strategy (Topic-based reports or custom picklist values) in the migration handoff.

Helpmonks User records (name, email, role, SSO identity) map to Salesforce User by email match. Agent and admin roles in Helpmonks map to Salesforce Service Cloud agent profiles that we configure during schema design. SSO-configured Helpmonks accounts may require re-authentication against the Salesforce IdP post-migration. Any Helpmonks User without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before Case migration resumes.

Attachments embedded within Helpmonks Conversations migrate as Salesforce ContentVersion records linked to the parent Case via ContentDocumentLink. Large binary blobs are chunked to avoid payload size limits during API ingestion. We validate attachment integrity (file hash comparison) after load. If Helpmonks stores attachments externally (via URL reference), we migrate the URL as a custom Case field rather than the binary.

Helpmonks custom fields on Customer records migrate to Salesforce custom fields on Contact. Field type mapping is verified at scoping: text, number, date, and picklist types map directly; multi-checkbox and complex custom types require transformation. CSAT ratings stored as custom fields on Helpmonks Customer migrate to a Salesforce custom number field on Contact with range validation matching the original scale.

Helpmonks custom fields on Conversations (beyond standard subject, body, assignee, status) map to Salesforce custom fields on Case. We pre-create the destination custom fields via the Salesforce metadata API or change set before migration, including any dependent picklist values. Validation rules on the destination org are reviewed and temporarily relaxed during migration to avoid rejection of records with legacy data that predates current picklist constraints.

Helpmonks chat history stored as part of the Conversations object migrates to Salesforce Case with the channel recorded as Chat. Live Chat widget configuration, trigger rules, proactive chat scripts, and site-specific widget IDs do not migrate; these are Salesforce Live Agent or Einstein Bots configuration that the customer's admin rebuilds in the Service Cloud console. Chat transcripts migrate as CaseComments with a Chat subtype marker.

Helpmonks Knowledge Base article content and category taxonomy migrate to Salesforce Lightning Knowledge (ArticleType and DataCategory). Article body text, titles, and categories migrate directly. Formatting, embedded media references, and knowledge-base-to-conversation linking behavior do not migrate as functional rules; we deliver a written map of each article's category structure for manual rebuild in the Service Cloud Knowledge sidebar and Help Center.

Helpmonks email campaign names, audience segments, and template content migrate to Salesforce Campaign records as informational metadata. Campaign send settings, sequence step order, trigger conditions, and delay rules do not migrate; these require rebuild in Salesforce Marketing Cloud or Marketing Cloud Account Engagement (Pardot). We deliver a campaign inventory document listing each Helpmonks campaign with its audience size and recommended Salesforce equivalent.