Migrate your Kustomer data
Intelligent CX platform for mid-market and enterprise teams that unify all customer conversations across channels into a single timeline, with a highly extensible KObject data model and growing AI layer.
In its favor
Why people choose Kustomer
The signal that keeps Kustomer on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Unified customer timeline that consolidates conversations across all channels—phone, email, chat, SMS, social—into a single chronological view, eliminating agent context-switching.
Automation capabilities that handle routine ticket routing, customer tagging, and SLA assignments without manual agent intervention, freeing staff for complex cases.
Highly extensible KObject (Klass) data model that lets enterprises define custom objects matching their specific business events, from order history to reservations.
Deep Shopify integration rated 5.0 in the Shopify App Store, enabling agents to process refunds, cancellations, and order changes directly within the customer timeline.
Flexible object relationships and nested Klasses let companies model complex, real-world customer interactions beyond standard ticket-field pairs.
Performance degrades under high volume or when the platform handles large datasets, with agents reporting lag, slow loading, and occasional outages that disrupt daily operations.
Steep learning curve and complexity: reviewers describe the tool as confusing in some areas, requiring significant training investment before teams become productive.
Annual-only billing with an 8-seat minimum makes Kustomer uneconomical for small teams, and forces mid-market teams into a 12-month commitment before validating fit.
Separate AI pricing ($0.60 per conversation, $40/user/month for copilot) on top of the base seat cost creates billing surprises that inflate the effective per-agent price.
Technical issues on the back end occur regularly according to reviews, and while Kustomer support resolves most, the frequency of backend instability frustrates enterprise teams expecting reliability.
Reasons to switch
Why people leave Kustomer
The recurring reasons buyers give for replacing Kustomer. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Kustomer fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Kustomer pricing overview
Kustomer charges per agent seat on an annual-only contract with an 8-seat minimum, starting at $89/user/month on Enterprise. AI features are priced separately—AI Agents per conversation ($0.60) and Agent Copilot per user ($40/month)—making the effective cost significantly higher than the base seat price for teams that adopt the AI layer.
Enterprise
Tier 1 of 4
$89/user/month (annual)
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Kustomer's schedule — see our quote-based pricing →
What gets migrated
Kustomer object support
Object-by-object support for Kustomer migrations. Per-pair details surface during scoping.
Customers
Fully supportedKustomer's primary person record. Standard fields include name, email, phone, and custom properties. We migrate Customers first as a dependency for all Conversation and Company linkages.
Conversations
Fully supportedThe core ticket/case object in Kustomer. A Conversation belongs to one Customer, spans multiple Channels, and contains Messages and Notes. We migrate conversations with full message history, preserving timeline order and channel attribution.
Users (Agents)
Fully supportedAgents who handle conversations. We map Users to Owners/Assignees in the destination and preserve team membership. Email addresses are used as the primary match key.
Teams
Fully supportedGroups of agents used for routing and queue management. We recreate team structure in the destination and map conversation routing rules accordingly.
Companies
Fully supportedBusiness accounts that can be linked to multiple Customers. We migrate Company records and re-link associated Customer records during the import phase.
Channels
Mapping requiredKustomer's Channel model (email, phone, chat, SMS, social) is a first-class object. We map channel types to the destination's channel equivalents, flagging any non-standard or app-added channels for manual review.
KObjects (Custom Objects/Klasses)
Mapping requiredKustomer's extensible custom object system. KObjects are user-defined schemas that can relate to Customers, Conversations, or each other. We inspect the source KObject definitions, map them to custom objects in the destination, and handle relationship fields on a per-schema basis.
Custom Attributes (Properties)
Mapping requiredCustom fields attachable to any standard or KObject. We enumerate all custom properties during discovery, map them to destination custom fields, and flag any unsupported field types (e.g., validation rules, nested lists).
Tags
Mapping requiredTags are applied across Conversations and Customers for categorization. We preserve all tags and re-apply them in the destination, noting any tag-limit differences between platforms.
Messages
Fully supportedIndividual communication entries within a Conversation, including agent replies, customer messages, and internal notes. We preserve message content, timestamps, author attribution, and message type.
Attachments
Mapping requiredFiles attached to Messages and Notes. We extract attachments from the export, re-upload to the destination, and relink to the parent message record.
Class Relationships (Custom)
Mapping requiredKustomer supports custom relationships between Klasses (e.g., Orders to Line Items). We map these relationship definitions and ensure referential integrity is maintained during the import.
Routing Rules and SLA Policies
Not in this platformWorkflow automation rules that determine queue assignment and response-time commitments. These are platform-specific configuration files that cannot be meaningfully migrated to a different system and must be rebuilt manually.
Reports and Metrics
Not in this platformPre-built dashboards and saved report definitions are Kustomer-internal configurations. Report data is included in the 30-day CSV export window; historical report definitions require manual re-creation in the destination.
| Object | Support | Notes |
|---|---|---|
| Customers | Fully supported | Kustomer's primary person record. Standard fields include name, email, phone, and custom properties. We migrate Customers first as a dependency for all Conversation and Company linkages. |
| Conversations | Fully supported | The core ticket/case object in Kustomer. A Conversation belongs to one Customer, spans multiple Channels, and contains Messages and Notes. We migrate conversations with full message history, preserving timeline order and channel attribution. |
| Users (Agents) | Fully supported | Agents who handle conversations. We map Users to Owners/Assignees in the destination and preserve team membership. Email addresses are used as the primary match key. |
| Teams | Fully supported | Groups of agents used for routing and queue management. We recreate team structure in the destination and map conversation routing rules accordingly. |
| Companies | Fully supported | Business accounts that can be linked to multiple Customers. We migrate Company records and re-link associated Customer records during the import phase. |
| Channels | Mapping required | Kustomer's Channel model (email, phone, chat, SMS, social) is a first-class object. We map channel types to the destination's channel equivalents, flagging any non-standard or app-added channels for manual review. |
| KObjects (Custom Objects/Klasses) | Mapping required | Kustomer's extensible custom object system. KObjects are user-defined schemas that can relate to Customers, Conversations, or each other. We inspect the source KObject definitions, map them to custom objects in the destination, and handle relationship fields on a per-schema basis. |
| Custom Attributes (Properties) | Mapping required | Custom fields attachable to any standard or KObject. We enumerate all custom properties during discovery, map them to destination custom fields, and flag any unsupported field types (e.g., validation rules, nested lists). |
| Tags | Mapping required | Tags are applied across Conversations and Customers for categorization. We preserve all tags and re-apply them in the destination, noting any tag-limit differences between platforms. |
| Messages | Fully supported | Individual communication entries within a Conversation, including agent replies, customer messages, and internal notes. We preserve message content, timestamps, author attribution, and message type. |
| Attachments | Mapping required | Files attached to Messages and Notes. We extract attachments from the export, re-upload to the destination, and relink to the parent message record. |
| Class Relationships (Custom) | Mapping required | Kustomer supports custom relationships between Klasses (e.g., Orders to Line Items). We map these relationship definitions and ensure referential integrity is maintained during the import. |
| Routing Rules and SLA Policies | Not in this platform | Workflow automation rules that determine queue assignment and response-time commitments. These are platform-specific configuration files that cannot be meaningfully migrated to a different system and must be rebuilt manually. |
| Reports and Metrics | Not in this platform | Pre-built dashboards and saved report definitions are Kustomer-internal configurations. Report data is included in the 30-day CSV export window; historical report definitions require manual re-creation in the destination. |
Gotchas
What to watch for in Kustomer migrations
Issues we've hit on past Kustomer migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Annual billing with 8-seat minimum inflates entry cost
30-day CSV export cap limits conversation history
API rate limits vary by pricing tier
Custom KObject schemas must be manually recreated in the destination
UTF-8 CSV encoding requirement can silently corrupt non-ASCII data
| Severity | Issue |
|---|---|
| High | Annual billing with 8-seat minimum inflates entry cost |
| High | 30-day CSV export cap limits conversation history |
| Medium | API rate limits vary by pricing tier |
| Medium | Custom KObject schemas must be manually recreated in the destination |
| Low | UTF-8 CSV encoding requirement can silently corrupt non-ASCII data |
Leaving Kustomer?
Where Kustomer customers move next
7 destinations Kustomer can migrate to.
How a Kustomer migration works
Four steps, Kustomer-specific
Connect
Bearer token into Kustomer. Scopes limited to read-only on the data we move.
Map
We translate Kustomer-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Kustomer quirks before production.
Migrate
Full migration with Kustomer rate-limit handling. Rollback available throughout.
FAQ
Kustomer migration FAQ
Answers to the questions buyers ask most during Kustomer migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Kustomer migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate Kustomer.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Kustomer setup and destination — written quote back within a business day.