Skip to content
Get a quote

Kustomer to Intercom migration

We migrate Customers, Companies, Conversations, and KObjects from Kustomer into Intercom with Customers as the primary anchor, conversation history replayed in original sequence, and KObject schemas audited for recreation as Intercom custom attributes before any import begins.

Short answer

FlitStack AI migrates contacts, companies, conversations, conversation parts and admins from Kustomer to Intercom, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

By

Source Kustomer
DestinationIntercom
ContactCompanyConversationConversation PartAdmin
Mapped field by field · sample run · one-click rollback

What moves from Kustomer to Intercom?

Moving from Kustomer to Intercom is a conversation-centric migration that prioritizes timeline fidelity and channel continuity.

Read the full summary

Kustomer's Customer object maps directly to Intercom's Contact object, but Kustomer's omnichannel Conversations must be replayed with the original message sequence, author attribution, and channel type preserved to maintain the agent-facing timeline. Kustomer's KObject system—used by enterprises to model business events like orders, reservations, and subscriptions—requires a full schema audit and manual recreation in Intercom as custom data attributes. The 30-day CSV export window is a hard constraint that we address by coordinating a rolling export or events-stream contract before migration day. Workflows, Shortcuts, snooze rules, and satisfaction survey responses do not migrate as configuration; we deliver a written inventory of these for the customer's team to rebuild in Intercom's workflow builder.

1:1

Customer → Contact

Kustomer Customer records map directly to Intercom Contact.

How it maps

The primary match key is email address. We migrate standard fields (name, email, phone, social handles) and all custom properties as Intercom custom data attributes on the Contact. Kustomer's customer-avatar URL migrates as a custom attribute. Customer is created first as the parent dependency for all Conversation imports.

1:1

Company → Company

Kustomer Company records map to Intercom Company.

How it maps

Domain from Kustomer becomes the Company website field and is used as the dedupe key during import. Company is created before Contact import so that the company_id reference is satisfied at Contact insert time. If a Kustomer Customer has multiple linked Companies, we create all Companies first, then create Contact-Company associations during Contact import.

1:1

Conversation → Conversation

Kustomer Conversations map to Intercom Conversations with the conversation state (open, done, snoozed) preserved.

How it maps

We replay the full message sequence within each Conversation in original timestamp order, maintaining the agent-customer attribution and channel attribution. Kustomer's Conversation subject or title becomes the Intercom Conversation title field if populated; otherwise the first message body serves as the thread opener. Status is preserved as Open versus Closed.

1:1

Message → Conversation Part

Kustomer Messages (agent replies, customer messages, internal notes) map to Intercom Conversation Parts.

How it maps

Message type from Kustomer (message, note, activity, channelmessage) maps to the Intercom part_type (comment, note, activity, assignment). Author attribution (agent vs customer) is preserved. Attachments on messages are extracted, re-uploaded to Intercom, and relinked to the parent Conversation Part.

1:1

User (Agent) → Admin

Kustomer Users map to Intercom Admins.

How it maps

Email address is the primary match key. We extract all agent profiles including display name, role, and avatar URL. The agent must be manually invited to the Intercom workspace by the customer's admin before migration day; we provide a reconciliation list of agents that need provisioning. Agent status (active vs inactive) is preserved as a custom attribute.

1:1

Team → Team

Kustomer Teams map to Intercom Teams.

How it maps

We extract team membership for every agent and recreate the team structure in Intercom during the pre-import configuration phase. Conversation assignment rules from Kustomer are documented for recreation in Intercom's routing and assignment workflows.

What moves12 objects
KustomerIntercom
  • CustomerContact1:1
  • CompanyCompany1:1
  • ConversationConversation1:1
  • MessageConversation Part1:1
  • UserAdmin1:1
  • TeamTeam1:1

+ 6 more in the mapping below

How Kustomer and Intercom differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionKustomerIntercom
Conversation threading modelMulti-channel Conversations with channel-first timeline and nested MessagesConversation with threaded Conversation Parts ordered by activity type and timestamp
Customer record structureCustomer with linked Companies, KObjects, and multi-channel interaction historyContact with company link and activity timeline as the primary timeline
Custom object architectureKObject (Klass) system with user-defined schemas, relationships, and validation rulesCustom data attributes per object (Contacts, Companies, Conversations) without cross-object relationship graphs
AI pricing$0.60 per AI conversation plus $40/user/month for Agent Copilot on top of base seat costFin AI at $0.99 per resolution with Advanced or Expert plan required for full capabilities
Billing commitmentAnnual-only with 8-seat minimum ($89/user/month on Enterprise)Monthly available from $29/seat on Essential with no minimum seat count
Bulk exportCSV export capped at 30 days unless events-stream contract is in placeFull conversation and contact export via API without a rolling window limit
Automation rebuild scopeWorkflows, Shortcuts, and SLA policies are Kustomer-internal configurationWorkflows, macros, and routing rules must be rebuilt in Intercom's builder

What to watch for in a Kustomer to Intercom migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

30-day CSV export cap limits conversation history

Kustomer's built-in CSV export covers at most 30 days of data per run.

How we handle it

Teams using Kustomer as a long-term knowledge base may have years of conversation history that falls outside this window. We discuss the events-stream export option (a separate Kustomer contract) with customers who need full history, or coordinate a rolling 30-day export in tranches before migration day. Without the events-stream contract, conversations older than 30 days are archived rather than migrated, and we flag this clearly during scoping so it is not a post-migration surprise.

high

KObject schemas must be manually recreated in Intercom

Kustomer's KObjects are defined per-organization with custom field schemas, relationships, and validation rules that have no equivalent in Intercom's attribute model.

How we handle it

We discover all KObject definitions during the pre-migration audit, document the field types and relationship graph, and recreate them as Intercom custom data attributes on the relevant Contact, Company, or Conversation object. KObject relationship hierarchies cannot be replicated; we flatten them to a primary-linked attribute. The destination schema must be validated and signed off before we import any KObject records.

high

Intercom Workflows do not accept migrated conversations as automation triggers

Intercom's Workflow engine cannot trigger on conversations that were imported rather than created through the live messenger widget.

How we handle it

Migrated conversations will not fire assignment, routing, or SLA workflows on import. We recommend disabling all Workflows during the import window and re-enabling them after cutover. For SLA policies, we deliver a written reconstruction plan so the customer's admin can validate SLA state on migrated open conversations manually after the migration completes.

medium

Intercom API rate limit of 1,000 req/min requires batch sizing

Intercom's default API rate limit for public apps is 1,000 requests per minute, distributed over 10-second periods (166 operations per 10 seconds).

How we handle it

Private apps have a 10,000 req/min limit. We monitor the X-RateLimit-Remaining header continuously and throttle batch sizes accordingly. For migrations exceeding 100,000 records, we schedule jobs outside peak business hours to avoid impacting live agent traffic. If the customer requests a private app setup to increase throughput, we coordinate with their Intercom account team during scoping.

medium

Satisfaction survey responses and snooze rules have no direct migration path

Kustomer's Satisfaction (CSAT) survey responses and snooze definitions use Kustomer-internal state machines that do not map to any Intercom feature.

How we handle it

We extract the available survey response data (respondent, score, comment, timestamp) as a CSV export for the customer's admin to re-import as a custom attribute on the relevant Contact or Conversation. Snooze behavior is documented as a workflow note; it is recreated manually in Intercom's Workflows or inbox settings post-migration.

How the migration runs

  1. Discovery and export planning

    We audit the source Kustomer portal for Customer count, Conversation volume, Company count, User count, Team count, KObject definitions, Channel types in use, and any Shortcuts or SLA policies configured.

    What this step covers

    We assess the CSV export window (30-day cap) and determine whether the events-stream export contract is in place for full history or whether the customer accepts a rolling 30-day export strategy. The discovery output is a written migration scope document covering record counts per object, the list of KObject schemas to recreate, and the export strategy decision.

  2. KObject schema audit and Intercom attribute design

    We enumerate every KObject definition in the source Kustomer portal, capturing field names, field types, relationship definitions, and validation rules.

    What this step covers

    We then design the equivalent Intercom custom data attributes on the appropriate Contact, Company, or Conversation object. KObject relationships are flattened to a primary-linked attribute with the relationship type noted in the schema documentation. We deploy these attributes to the customer's Intercom workspace as a pre-import configuration step and obtain sign-off before any data moves.

  3. Intercom workspace pre-configuration

    Before any import, we configure the Intercom workspace to receive migrated data.

    What this step covers

    This includes recreating Teams with the same membership structure as Kustomer, defining custom data attributes (from the KObject audit), setting up tag consolidations if needed, and disabling all active Workflows and SLA policies that would fire on imported conversations. We provide the customer with a pre-flight checklist confirming that Admins are provisioned in Intercom for every agent in scope.

  4. Rolling export or events-stream extraction

    If the events-stream contract is in place, we extract the full conversation history via the events-stream API in chronological order.

    What this step covers

    If the events-stream contract is not available, we coordinate a rolling 30-day CSV export with the customer, running exports in sequential tranches and combining them before transformation. All exports are validated for UTF-8 encoding before processing. Any conversations older than the export window are flagged as archival-only and excluded from active migration.

  5. Data transformation and dependency-ordered import

    We transform exported data into Intercom API-compatible payloads.

    What this step covers

    Import runs in strict dependency order: Companies (first, as parent), then Contacts (with company_id resolved), then Admins (manually provisioned and reconciled by email), then Conversations (with Contact_id and Admin_id resolved), then Conversation Parts (with Conversation_id resolved in timestamp order). KObject records are imported last with parent lookups resolved. We batch records to stay within the 1,000 req/min Intercom API limit and monitor rate limit headers continuously. Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, post-migration validation, and rebuild handoff

    We freeze writes to Kustomer during the cutover window, run a final delta migration of any records created or modified during the migration, then mark Intercom as the system of record.

    What this step covers

    We validate a statistical sample of migrated records (approximately 2% of total) against the source data for field fidelity. We deliver the Shortcut inventory, Routing Rule and SLA Policy inventory, and Satisfaction survey data export to the customer's admin team. We do not rebuild Kustomer Workflows or Shortcuts as Intercom Workflows inside the migration scope; that is a separate rebuild engagement or an internal admin task.

Kustomer Intercom
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · IntercomRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
8-12 weeksLarge or heavily customised accounts

A quote scales with record volume, KObject complexity, and conversation history depth. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Kustomer to Intercom →

Why teams move from Kustomer to Intercom

  • Annual-only billing with an 8-seat minimum forces a 12-month commitment before validating fit. Reviewers on G2 and Capterra consistently cite this as a pain point for teams evaluating Kustomer who need to scale down or pivot within the contract year. Intercom offers monthly billing from $29/seat on Essential without a seat minimum, which reduces the commitment risk for mid-market teams at the proof-of-concept stage.
  • Performance degrades under high volume or when the platform handles large datasets, with agents reporting lag, slow loading, and occasional outages. Multiple G2 reviews from 2024-2025 describe backend instability disrupting daily operations for enterprise teams. Intercom's infrastructure is frequently cited as more stable at scale for teams processing over 5,000 conversations per week.
  • Separate AI pricing on top of the base seat cost creates billing surprises. At $0.60 per AI conversation plus $40/user/month for Agent Copilot, the effective per-agent cost exceeds the listed price significantly for teams adopting the AI layer. Intercom's Fin AI resolution pricing is also per-resolution ($0.99), but it is available on Advanced and Expert tiers that include broader platform capabilities rather than as a separate add-on to a base tier that already requires 8 seats annually.
  • The steep learning curve and non-intuitive areas require significant training investment before teams become productive. Reviewers describe Kustomer as complex and confusing in some workflow areas, especially for teams without a dedicated admin. Intercom's messenger-centric UI is consistently described as more approachable for support teams transitioning from chat-first tools, and its workflow builder, while also complex, has more community documentation and partner resources available.
  • Teams needing omnichannel depth and a larger partner ecosystem move to Intercom for its established marketplace of integrations, workflow templates, and certified implementation partners. Kustomer's Shopify integration is rated highly, but the broader integrations ecosystem is smaller. Intercom's App store and partner network are cited as reasons teams choose it as a long-term platform for customer engagement at scale.

Questions, answered

Kustomer to Intercom migration questions

How long does a Kustomer to Intercom migration take?

Most migrations land between three and five weeks for accounts under 10,000 Customers and 50,000 Conversations with no KObject custom schemas. Migrations involving multiple KObject schemas, multi-year conversation histories, or teams relying on the events-stream export for full history move to eight to twelve weeks because of KObject schema design work, parent-record resolution across multiple custom objects, and the sequencing needed to replay long conversation threads correctly. The export preparation phase (30-day rolling or events-stream setup) adds one to three weeks to the front end of the timeline.

Do Kustomer Workflows, Shortcuts, and SLA policies migrate to Intercom?

No. Kustomer Workflows, Shortcuts, and SLA policies are platform-specific automation configurations that do not migrate as code to Intercom. We do not migrate them. We deliver a written inventory of every active Shortcut (name, body content, and available-for context), every routing rule, and every SLA policy with their trigger conditions, assignment targets, and time windows. The customer's admin rebuilds these in Intercom's Workflow builder and Saved Replies. SLA policies do not have a direct Intercom equivalent; they are recreated manually using Intercom's SLA features or a third-party SLA tool as a post-migration step.

What happens to my conversation history if I only have the 30-day CSV export?

If the events-stream export contract is not in place, Kustomer's CSV export is limited to 30 days of data per run. We coordinate rolling 30-day exports with the customer to capture as much history as possible before migration day, but conversations older than the most recent 30-day window cannot be exported via CSV. These older conversations are archived rather than actively migrated. We flag the archival boundary clearly during scoping so the customer can decide whether to negotiate an events-stream contract with Kustomer before migration day if the full history is required.

Can Kustomer KObjects be migrated to Intercom?

KObject records migrate as attribute values on the linked Contact, Company, or Conversation record in Intercom, but the KObject schema itself must be manually recreated. Kustomer's KObjects are defined per-organization with custom field types, relationships, and validation rules that do not have a direct Intercom equivalent. We audit every KObject definition during discovery, document the schema, and recreate it as Intercom custom data attributes. KObject relationship hierarchies (parent-child Klasses) cannot be replicated; we flatten them to a primary-linked attribute and note the original relationship structure for the customer's admin.

Do we lose the customer timeline when migrating to Intercom?

No. We replay the full conversation history within each migrated Conversation in original timestamp order, preserving agent-customer attribution and channel attribution. Kustomer Messages map to Intercom Conversation Parts with the correct part_type (comment, note, activity) for each entry. The activity timeline in Intercom will reflect the same sequence and timestamps as the source Kustomer timeline. Notes (internal team notes) migrate as Intercom notes attached to the relevant Conversation.

What about Kustomer's Satisfaction survey responses?

Satisfaction survey responses use Kustomer-internal state that has no direct Intercom equivalent. We extract the available data (respondent Contact, score, optional comment, and timestamp) as a CSV export during migration. The customer's admin can re-import this as custom attribute values on the relevant Contact records in Intercom, or use a third-party CSAT tool. We document the data fields and format so the admin can build a simple re-import workflow post-migration.

Will migrated conversations trigger Intercom's Workflows and routing rules?

No. Intercom's Workflow engine cannot trigger on conversations that were imported via API rather than created through the live messenger widget. Migrated conversations will not fire assignment, routing, or SLA workflows on import. We disable all Workflows during the import window and re-enable them after cutover. Open conversations from the migration should be manually reviewed by the customer's admin after migration to confirm routing and SLA state is correct.

Get a quote

Moving from Kustomer to Intercom?

Tell us roughly how many records and objects you have. We scope the mapping and the Intercom setup with you, then send a quote.

Get a quote