---
title: "Migrate from Enchant to Intercom | ClonePartner"
description: "There is no native migration path from Enchant to Intercom. Enchant is a streamlined shared inbox for ticket-based support, while Intercom is a comprehensive cu"
source: Enchant
target: Intercom
canonical: "https://clonepartner.com/migrate/enchant-to-intercom/"
---

# Enchant → Intercom migration

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

## Why teams migrate from Enchant to Intercom

There is no native migration path from Enchant to Intercom. Enchant is a **streamlined shared inbox** for ticket-based support, while Intercom is a **comprehensive customer platform** with unified contact models and conversation-part architecture.



The fundamental gap is architectural: Enchant separates tickets, messages, and customers as distinct entities, while Intercom uses a **unified Contact model** and treats all communication as conversation parts within tickets.



Every migration requires manual admin and team setup, custom API work to map customer contacts, sequence ticket creation, and handle attachments via URL embedding since Intercom handles file uploads differently.

## Key migration challenges

- **Attachment URL Embedding** — Intercom handles attachments differently, requiring direct URLs to be embedded in message bodies rather than traditional file uploads.
- **Search Indexing Delay** — Intercom has a delay between contact creation and searchability, requiring built-in pauses to prevent failed ticket-to-contact linking.
- **Admin & Team Setup** — Team members and departmental groupings cannot be created programmatically and must be configured manually in Intercom.
- **Rate Limit Constraints** — Enchant limits API credits to 100 per minute, requiring retry logic and throttling for large-volume ticket extraction.
- **Data Sanitization** — Intercom prefers clean HTML or plain text, requiring message body sanitization to prevent formatting errors in historical conversations.

## Entity mappings

- **Tickets (Conversations)** (Enchant) → **Tickets** (Intercom)
- **Messages (Replies)** (Enchant) → **Messages** (Intercom)
- **Notes (Internal)** (Enchant) → **Notes** (Intercom)
- **Customers** (Enchant) → **Contacts (Users)** (Intercom)
- **Users (Agents)** (Enchant) → **Not Available** (Intercom)
- **Teams** (Enchant) → **Not Available** (Intercom)
- **Labels** (Enchant) → **Tags** (Intercom)
- **Attachments** (Enchant) → **Not Available** (Intercom)
- **Knowledge Base Categories** (Enchant) → **Article Collections** (Intercom)
- **Knowledge Base Articles** (Enchant) → **Articles** (Intercom)
- **Custom Fields** (Enchant) → **Data Attributes** (Intercom)
- **Satisfaction Ratings** (Enchant) → **Not Available** (Intercom)
- **Canned Responses (Templates)** (Enchant) → **Not Available** (Intercom)
- **Automation Rules** (Enchant) → **Not Available** (Intercom)
- **Contact Forms** (Enchant) → **Not Available** (Intercom)

## What breaks during migration

- **Attachments** [Breaks] — No direct upload path; must embed Enchant attachment URLs within message bodies
- **Contacts (Customers)** [Workaround] — Enchant's separate customer/contact model must be unified into Intercom's single Contact model
- **Tickets** [Workaround] — Must be linked to correct customer and assigned to the right team or admin
- **Messages & Notes** [Workaround] — Both become conversation parts; original timestamps must be preserved for thread coherence
- **Tags (Labels)** [Direct] — Can be set up and applied directly via Intercom's tag system
- **Admins (Users)** [Workaround] — Must be invited manually; no programmatic creation available
- **Teams (Inboxes)** [Workaround] — Must be created manually to mirror Enchant inbox structure
- **Message Body Format** [Workaround] — Flexible Enchant formats must be sanitized to clean HTML or plain text for Intercom
- **Workflows** [Workaround] — Must be recreated using Intercom's workflow builder 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 Intercom](https://clonepartner.com/blog/enchant-to-intercom-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 → Intercom migration.