---
title: "Migrate from Kustomer to Intercom | ClonePartner"
description: "There is no native migration path from Kustomer to Intercom. Kustomer structures support around standard objects and KObjects, while Intercom uses a conversatio"
source: Kustomer
target: Intercom
canonical: "https://clonepartner.com/migrate/kustomer-to-intercom/"
---

# Kustomer → Intercom migration

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

## Why teams migrate from Kustomer to Intercom

There is no native migration path from Kustomer to Intercom. Kustomer structures support around **standard objects and KObjects**, while Intercom uses a **conversation parts model** with contacts, admins, and data attributes.



Every migration requires custom API work to reconstruct messages as conversation parts via the **reply workaround**, and careful mapping of data attribute types and naming conventions.

## Key migration challenges

- **Message Threading Workaround** — Messages cannot be directly uploaded. You must use the reply API to reconstruct conversation history on behalf of admins or customers.
- **Data Attribute Matching** — Kustomer custom attributes use type suffixes like Num or Bool that must precisely match Intercom Data Attribute type definitions.
- **Tiered Rate Limits** — Contacts allow 600 updates per 10 minutes but companies and messages are limited to 100, requiring differentiated throttling.
- **Manual Admin Setup** — Users cannot be created via API and must be manually invited as Admins with correct team assignments before migration.

## Entity mappings

- **Customers** (Kustomer) → **Contacts (Users)** (Intercom)
- **Conversations** (Kustomer) → **Tickets** (Intercom)
- **Messages** (Kustomer) → **Messages** (Intercom)
- **Notes** (Kustomer) → **Notes** (Intercom)
- **Tags** (Kustomer) → **Tags** (Intercom)
- **Companies** (Kustomer) → **Companies** (Intercom)
- **Knowledge Base Articles** (Kustomer) → **Articles** (Intercom)
- **Knowledge Base Categories** (Kustomer) → **Article Collections** (Intercom)
- **Users (Agents)** (Kustomer) → **Not Available** (Intercom)
- **Customer Custom Attributes** (Kustomer) → **Data Attributes** (Intercom)
- **Conversation Custom Attributes** (Kustomer) → **Data Attributes** (Intercom)
- **Shortcuts (Macros)** (Kustomer) → **Not Available** (Intercom)
- **SLA Policies** (Kustomer) → **Not Available** (Intercom)
- **Satisfaction Ratings (CSAT)** (Kustomer) → **Not Available** (Intercom)
- **Hooks (Webhooks)** (Kustomer) → **Not Available** (Intercom)

## What breaks during migration

- **Messages → Conversation Parts** [Breaks] — Requires reply workaround to reconstruct threaded history
- **KObjects → Custom Object Instances** [Breaks] — Schema definitions must be created before instance data can import
- **Conversations → Conversations** [Breaks] — Each conversation must be built part-by-part via API replies
- **Custom Attributes → Data Attributes** [Workaround] — Type suffixes must match exactly or data will be rejected
- **Shortcuts → Macros** [Workaround] — Dynamic text placeholders require syntax updates for Intercom
- **Workflows → Series/Workflows** [Workaround] — Automation logic must be manually rebuilt with Intercom branching paths
- **KB Articles → Articles** [Direct] — Direct mapping to Intercom Articles with collection structure
- **Companies** [Direct] — Standard field mapping between platforms
- **Tags** [Direct] — Direct one-to-one mapping between platforms

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