---
title: "Migrate from Intercom to Help Scout | ClonePartner"
description: "Intercom focuses on messenger-style engagement with separate Ticket and Conversation objects, while Help Scout excels at shared inbox management where everythin"
source: Intercom
target: Help Scout
canonical: "https://clonepartner.com/migrate/intercom-to-help-scout/"
---

# Intercom → Help Scout migration

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

## Why teams migrate from Intercom to Help Scout

Intercom focuses on **messenger-style engagement** with separate Ticket and Conversation objects, while Help Scout excels at **shared inbox management** where everything is a Conversation. There is no native migration path between the platforms.



Help Scout's API does not support **creating Users**, making manual agent setup a prerequisite before any data import. Intercom Tickets must be converted into Help Scout Conversations with **distinguishing tags** since Help Scout has no separate Ticket object.



The migration requires strict sequential ordering — customers before conversations, conversations before threads — and Intercom Segments must be **manually rebuilt as Workflows or Saved Searches**.

## Key migration challenges

- **Manual User Creation** — Help Scout API has no "Create User" endpoint. Every agent must be manually created before migration so their IDs are available for assignment.
- **Ticket-to-Conversation Merge** — Intercom Tickets have no equivalent in Help Scout and must be migrated as Conversations with a distinguishing tag or custom field.
- **Strict Rate Limits** — Help Scout Docs API enforces strict rate limiting that varies by account setup. Built-in sleep functions are required in migration scripts.
- **Sequential Dependencies** — Objects cannot be imported in parallel. Customers must exist before conversations, and conversations before threads, or the API rejects requests.
- **Segment Recreation** — Intercom Segments cannot be migrated via API and must be manually rebuilt as Help Scout Workflows or Saved Searches.

## Entity mappings

- **Contacts (Users)** (Intercom) → **Customers** (Help Scout)
- **Contacts (Leads)** (Intercom) → **Customers** (Help Scout)
- **Companies** (Intercom) → **Companies** (Help Scout)
- **Conversations** (Intercom) → **Conversations** (Help Scout)
- **Conversation Parts** (Intercom) → **Conversation Threads** (Help Scout)
- **Tags** (Intercom) → **Tags** (Help Scout)
- **Notes** (Intercom) → **Conversation Notes** (Help Scout)
- **Admins (Team Members)** (Intercom) → **Mailboxes** (Help Scout)
- **Articles** (Intercom) → **Not Available** (Help Scout)
- **Conversation Attachments** (Intercom) → **Conversation Attachments** (Help Scout)
- **Tickets** (Intercom) → **Conversations** (Help Scout)
- **Data Attributes** (Intercom) → **Custom Field Values** (Help Scout)
- **Events** (Intercom) → **Not Available** (Help Scout)
- **Segments** (Intercom) → **Not Available** (Help Scout)
- **Teams** (Intercom) → **Not Available** (Help Scout)

## What breaks during migration

- **Knowledge Base (Collections/Articles)** [Direct] — Maps to Help Scout Sites and Collections via the Docs API
- **Companies → Organizations** [Direct] — Direct mapping to Help Scout Organizations
- **Contacts → Customers** [Direct] — Users and Leads consolidate into Help Scout Customers with org linking
- **Conversations** [Workaround] — Direct migration but requires strict sequential ordering
- **Intercom Tickets** [Breaks] — No Ticket object in Help Scout, must convert to tagged Conversations
- **Messages → Threads** [Workaround] — Replies and chats become Help Scout Threads within conversations
- **Notes** [Direct] — Direct mapping to Help Scout Notes for internal context
- **Tags** [Direct] — Applied to conversations and customers via API
- **Data Attributes → Custom Fields** [Workaround] — Must be mapped to Help Scout Custom Fields to preserve customer details
- **Segments** [Breaks] — No API migration path, must rebuild as Workflows or Saved Searches

## 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 Intercom to Help Scout](https://clonepartner.com/blog/intercom-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 Intercom → Help Scout migration.