---
title: "Migrate from Enchant to Help Scout | ClonePartner"
description: "There is no native migration path from Enchant to Help Scout. Enchant organizes support through tickets and messages within inboxes, while Help Scout uses conve"
source: Enchant
target: Help Scout
canonical: "https://clonepartner.com/migrate/enchant-to-help-scout/"
---

# Enchant → Help Scout migration

Seamless Enchant to Help Scout migration — all records moved with accuracy and care.

## Why teams migrate from Enchant to Help Scout

There is no native migration path from Enchant to Help Scout. Enchant organizes support through **tickets and messages** within inboxes, while Help Scout uses **conversations and threads** within mailboxes.



Both platforms share a similar customer/contact model, but the key challenge lies in the **two-step attachment process** — files must be uploaded first to generate unique IDs before being linked to specific threads.



Every migration requires careful sequencing of customers, attachments, and conversations, plus manual setup of users and mailboxes since Help Scout's API does not support creating these programmatically.

## Key migration challenges

- **Attachment Pre-upload** — Attachments must be uploaded to Help Scout first to generate unique identifiers before they can be attached to specific messages.
- **User & Mailbox Setup** — Help Scout's API does not support creating users or mailboxes, requiring manual setup before any automated migration can begin.
- **Rate Limit Differences** — Enchant uses a credit-based system (100/min) while Help Scout allows requests per ten-minute windows based on active sites.
- **HTML Format Preservation** — Enchant tracks message body format via a boolean field; failing to respect this causes historical messages to display as broken code.

## Entity mappings

- **Tickets (Conversations)** (Enchant) → **Conversations** (Help Scout)
- **Messages (Replies)** (Enchant) → **Conversation Threads** (Help Scout)
- **Notes (Internal)** (Enchant) → **Conversation Notes** (Help Scout)
- **Customers** (Enchant) → **Customers** (Help Scout)
- **Users (Agents)** (Enchant) → **Not Available** (Help Scout)
- **Teams** (Enchant) → **Not Available** (Help Scout)
- **Inboxes (Mailboxes)** (Enchant) → **Mailboxes** (Help Scout)
- **Labels** (Enchant) → **Tags** (Help Scout)
- **Attachments** (Enchant) → **Conversation Attachments** (Help Scout)
- **Knowledge Base Categories** (Enchant) → **Not Available** (Help Scout)
- **Knowledge Base Articles** (Enchant) → **Not Available** (Help Scout)
- **Custom Fields** (Enchant) → **Custom Field Values** (Help Scout)
- **Satisfaction Ratings** (Enchant) → **Not Available** (Help Scout)
- **Webhooks** (Enchant) → **Webhooks** (Help Scout)
- **Canned Responses (Templates)** (Enchant) → **Not Available** (Help Scout)

## What breaks during migration

- **Attachments** [Breaks] — Must be pre-uploaded for ID generation; each attachment can only be linked to one message
- **Conversations (Tickets)** [Workaround] — Require correct mailbox ID mapping and customer association during creation
- **Threads (Messages)** [Workaround] — Must preserve reply vs note distinction using different Help Scout thread types
- **Customers & Contacts** [Direct] — Similar model between platforms allows relatively direct mapping
- **Tags (Labels)** [Direct] — Direct mapping from Enchant labels to Help Scout conversation tags
- **Users (Agents)** [Workaround] — Cannot be created via API; must be manually configured before migration
- **Mailboxes (Inboxes)** [Workaround] — Cannot be created via API; manual setup required with ID recording
- **Workflows** [Workaround] — Must be manually rebuilt within Help Scout interface after migration

## What we migrate

### Migration Filter

- **User Selection** — Migrate tickets for specific users or agents
- **Time Range** — Migrate tickets from a specific time period
- **Conversation Type** — Filter by chat, email, or social media conversations
- **Tag-Based Selection** — Migrate tickets with specific tags only

### Data Types

- **Knowledge Base** — Articles, categories, and help center content
- **Tickets & Conversations** — Full conversation history with all metadata
- **Customer Profiles** — Customer information and interaction history
- **Automations & Macros** — Workflows, templates, and automation rules

## Complete technical guide

For a deep-dive into the technical process, data mapping, and step-by-step migration workflow, read our full guide: [The Complete Guide to Migrating from Enchant to Help Scout](https://clonepartner.com/blog/enchant-to-help-scout-migration-guide/).

## Frequently asked questions

### Who can view my data?

For each migration project, you'll be assigned a migration engineer. Only the migration engineer can view your data. No one else at ClonePartner can view your data.

### Can I sign an NDA?

If you are reaching out to us via one of our partners, we already have an NDA signed with them that unilaterally applies to all their customers. If you are reaching us directly and need an NDA signed, we'll be happy to sign your NDA or ours.

## Get a fixed-price quote

[Talk to an engineer](https://cal.com/clonepartner/meet?duration=30&utm_source=xtoy&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click) about your Enchant → Help Scout migration.