---
title: "Kustomer to Zendesk Migration: Field Mapping & Rollback"
description: "Migrate Kustomer to Zendesk with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/helpdesk/kustomer/to/zendesk"
---

# Kustomer to Zendesk migration

We migrate Customers, Companies, Conversations, and message history from Kustomer into Zendesk, resolving the 30-day CSV export cap with a rolling-export strategy, mapping Kustomer's channel-first timeline to Zendesk's ticket model, and recreating every KObject definition as a Zendesk Custom Object before any data moves.

Short answer

FlitStack AI migrates end users, tickets, ticket comments, agents and groups from Kustomer to Zendesk, 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-6 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/helpdesk/kustomer/to/zendesk#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Kustomer ![](https://flitstack.ai/platforms-trim/kustomer.webp)

Destination Zendesk ![](https://flitstack.ai/platforms-trim/zendesk.webp)

End User Ticket Ticket Comment Agent Group

Mapped field by field · sample run · one-click rollback

## What moves from Kustomer to Zendesk?

Moving from Kustomer to Zendesk requires resolving two structurally different data models.

Read the full summary

Kustomer is built around a customer timeline that consolidates all channels and messages under one record; Zendesk is built around individual tickets that belong to a requester and can be grouped into views. We handle that translation by treating each Kustomer Conversation as a Zendesk Ticket, mapping Done/Open status to Solved/Open while flagging Zendesk's 28-day auto-close automation that will silently close migrated Solved tickets. KObject schemas have no direct equivalent in Zendesk by default; we discover every custom Klass definition during pre-migration, recreate them in Zendesk's Custom Objects (GA as of 2024), and import the records after the standard object migration. The 30-day CSV export cap in Kustomer's standard export requires a rolling-export workaround or an events-stream contract for accounts needing multi-year history. We do not migrate Workflows, routing rules, SLA policies, or Reports as code; we deliver a written inventory of every automation and saved report for the customer's admin to rebuild in Zendesk.

1:1

### Customer → End User (User)

Kustomer Customers map to Zendesk End Users (the requester on a ticket).

How it maps

We use email as the primary dedupe key during import. Phone, name, and custom properties migrate as user fields and custom user fields. Customer Id from Kustomer is preserved in a custom field kustomer\_id\_\_c for cross-reference. All Customers are imported before Conversations so that requester references are satisfied at ticket creation time.

1:1

### Conversation → Ticket

Each Kustomer Conversation becomes a Zendesk Ticket.

How it maps

The conversation subject becomes the ticket Subject, the most recent message body becomes the ticket Description, and the conversation status (Done/Open) maps to Zendesk Ticket Status (Solved/Open). We flag Zendesk's 28-day auto-close automation on Solved tickets — the customer's admin should either disable it or accept that migrated Solved conversations will transition to Closed 28 days after migration. Conversation priority and SLA flags map to Zendesk Priority and SLA Policy assignment.

1:1

### Message (public) → Ticket Comment (public)

Public Kustomer Messages (customer-facing, agent replies) map to Zendesk Ticket Comments with the public boolean set to true.

How it maps

Author attribution resolves to the Zendesk agent or end-user record by email match. Message timestamps become comment timestamps to preserve the conversation sequence.

1:1

### Note (private) → Ticket Comment (private)

Kustomer internal Notes map to Zendesk private Ticket Comments.

How it maps

We set the public boolean to false. Private notes authored by agents who are not provisioned in Zendesk are assigned to a default agent specified during scoping and flagged for the customer's admin to reattribute post-migration.

1:1

### User (Agent) → Agent (User)

Kustomer Users (agents and admins) map to Zendesk Agents.

How it maps

Email is the match key. We extract agent roles (admin, agent) from Kustomer and map them to Zendesk's role structure (light agent, agent, admin), adjusting for the destination plan tier. Agent availability status (active/inactive) migrates; suspended agents in Kustomer become suspended in Zendesk.

1:1

### Team → Group

Kustomer Teams map directly to Zendesk Groups.

How it maps

Group membership is resolved during user provisioning so that agents belong to the correct group before ticket import begins. Routing assignments in Kustomer (which conversation goes to which team) are preserved as ticket Group assignments in Zendesk.

******What moves 12 objects

Kustomer Zendesk

- Customer End User 1:1
- Conversation Ticket 1:1
- Message Ticket Comment 1:1
- Note Ticket Comment 1:1
- User Agent 1:1
- Team Group 1:1

\+ 6 more in the mapping below

## How Kustomer and Zendesk 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.

| Dimension                   | Kustomer                                                                      | Zendesk                                                                           |
| --------------------------- | ----------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| Data model                  | Customer timeline — all channels and messages attached to one customer record | Ticket-centric — each interaction is a separate Ticket with requester and subject |
| Custom objects              | KObjects (Klasses) available at all tiers with custom relationships           | Custom Objects GA 2024; Legacy Custom Objects retiring July 2026                  |
| Billing cycle               | Annual-only, 8-seat minimum, $89/user/mo Enterprise                           | Monthly and annual, starting at $19/agent/mo Team plan                            |
| Conversation history export | 30-day CSV cap; events-stream contract required for full history              | Full history available via API; no historical cap on exports                      |
| AI pricing                  | AI Agents $0.60/conversation + Agent Copilot $40/user/mo (additive)           | Advanced AI add-on $50/agent/mo, bundled in higher tiers                          |
| Automation rebuild          | Workflows and SLA policies not migratable to Zendesk                          | Triggers, Macros, and SLA Policies require manual rebuild                         |
| Ticket lifecycle            | Done/Open with channel-first status semantics                                 | New/Open/Pending/Solved/Closed with 28-day auto-close on Solved                   |

## What to watch for in a Kustomer to Zendesk migration

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

high

### Kustomer's 30-day CSV export cap limits conversation history

Kustomer's standard CSV export covers at most 30 days of data per run.

How we handle it

Accounts needing multi-year conversation history cannot export all records in a single pass. We discuss the events-stream export option with every customer during scoping — it requires a separate contract with Kustomer but delivers the full history in a structured format. Without it, we run a rolling 30-day export in tranches, which is time-consuming for accounts with several years of data. The 30-day cap is a Kustomer platform limitation, not a FlitStack AI limitation, and we disclose it upfront so customers can decide on export scope before migration begins.

high

### Zendesk requires tagging to be enabled before import

Zendesk's tagging feature is disabled by default in Admin > Security settings for new accounts.

How we handle it

If tagging is not enabled before migration, Kustomer Tags import silently — the import completes with no error but no tags appear on the migrated records. We verify tagging is enabled in the target Zendesk account during the pre-migration checklist and document the exact setting path for the customer's admin to confirm.

medium

### Kustomer's timeline model requires structural translation to Zendesk tickets

Kustomer's Customer record holds all conversation history in a chronological timeline.

How we handle it

Zendesk separates each conversation into its own Ticket. A Kustomer Customer with five open conversations across three channels becomes five Zendesk Tickets each linked to the same End User. We make this translation explicit during field mapping and validate the one-to-many expansion with the customer before production migration, since it affects ticket count reporting expectations in Zendesk.

medium

### Zendesk auto-closes Solved tickets after 28 days

Zendesk's built-in automation closes tickets marked Solved after 28 days of inactivity (and archives them after 120 days of Closed status).

How we handle it

Kustomer's Done status is a terminal state with no automatic transition. Migrated Solved conversations will be subject to this automation. We document the 28-day auto-close behavior for the customer's admin and recommend disabling the automation or setting a longer interval before cutover if the customer needs migrated Solved tickets to remain open indefinitely.

medium

### KObject relationships must be manually recreated in Zendesk Custom Objects

Kustomer's KObject system supports custom relationship definitions between Klasses (for example, an Order Klass linked to a Line Items Klass).

How we handle it

Zendesk Custom Objects support lookup fields, but relationship cardinality and referential integrity rules are not exported automatically. We document every KObject relationship during discovery and create the corresponding lookup fields in Zendesk. The customer validates the relationship graph in Zendesk's sandbox before we import KObject records.

## How the migration runs

1. ### Pre-migration discovery and export scope

   We audit the source Kustomer account across all tiers, enumerating every Customer, Conversation, Company, User, Team, Channel, KObject definition, and custom property.

   What this step covers

   We confirm the export scope strategy with the customer: standard 30-day CSV (with rolling tranches if multi-year history is needed) or events-stream contract. We verify tagging is enabled in the target Zendesk account. We document the KObject relationship graph for every custom Klass, including field types and cross-Klass lookups, and map them to Zendesk Custom Objects using the new Custom Objects API.

2. ### Schema design and Zendesk Custom Object provisioning

   We create the destination schema in Zendesk before any data moves.

   What this step covers

   This includes provisioning Zendesk Custom Objects to match every KObject definition, creating custom ticket fields for Kustomer custom properties, configuring Organization fields for Kustomer Companies, and setting up Group structure to match the Kustomer Team hierarchy. We deploy to a Zendesk sandbox for the customer's admin to validate field labels, data types, and required-field settings before production.

3. ### Sandbox migration and reconciliation

   We run a full migration into the Zendesk sandbox using representative data volume.

   What this step covers

   The customer's admin spot-checks 25-50 random tickets against the Kustomer source, verifies tag application, validates that Customer-to-End-User and Company-to-Organization linkages are correct, and confirms KObject records link to the right parent objects. Any field-mapping corrections and schema adjustments happen in sandbox before production migration begins.

4. ### Rolling CSV export and user provisioning

   For accounts using the standard 30-day export, we run the first tranche immediately while schema work is in progress.

   What this step covers

   Subsequent tranches run on a scheduled cadence to capture the full history before the production migration window. Simultaneously, we extract all Kustomer Users, match them by email against the Zendesk User table, and hold any unmatched agents in a reconciliation queue for the customer's admin to provision in Zendesk before ticket import.

5. ### Production migration in dependency order

   We run production migration in strict record-dependency order: Zendesk Agents and Groups first (required for ticket attribution), then End Users (from Kustomer Customers), then Organizations (from Kustomer Companies), then Tickets (from Kustomer Conversations with status translation), then public Comments and private Notes (mapped from Messages and Notes), then Tags (with tagging enabled verified), then Attachments, then Custom Objects last (because they reference standard objects).

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins.

6. ### Cutover, delta migration, and automation rebuild handoff

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

   What this step covers

   We deliver the Automation Inventory document listing every Kustomer Workflow, SLA Policy, and routing rule with a recommended Zendesk equivalent (Trigger, Macro, SLA Policy, or Group assignment) for the customer's admin to rebuild. We do not migrate Reports as code; we deliver a written map of every saved report and dashboard requiring re-creation in Zendesk Explore. We support a one-week hypercare window for reconciliation issues.

![](https://flitstack.ai/platforms/kustomer.png) Kustomer ![](https://flitstack.ai/platforms/zendesk.svg) Zendesk

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Zendesk Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3-6 weeks** Typical, smaller accounts

**8-12 weeks** Large or heavily customised accounts

A quote scales with conversation volume, KObject count, and export-scope strategy. The events-stream export option from Kustomer is a separate contractual arrangement that we coordinate but does not affect our migration fee. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Kustomer to Zendesk →](https://flitstack.ai/contact)

## Why teams move from Kustomer to Zendesk

- Kustomer's annual-only billing with an 8-seat minimum creates a high-commitment entry point at $89 per user per month before AI pricing or implementation fees. Zendesk offers monthly billing starting at $19 per agent per month on the Team plan, letting smaller teams pilot without a 12-month commitment. G2 and Capterra reviewers cite the billing rigidity as a primary driver for switching, particularly for teams under 15 agents that cannot justify the minimum spend.
- Kustomer's separate AI pricing model ($0.60 per conversation plus $40 per user per month for Agent Copilot) on top of the base seat cost produces billing surprises that inflate the effective per-agent price. Zendesk bundles Advanced AI at $50 per agent per month on Professional and above, giving teams a more predictable AI cost envelope without per-conversation metering.
- Kustomer's performance degrades under high data volumes or concurrent load, with reviewers reporting lag, slow loading, and occasional backend outages. Zendesk's architecture handles higher concurrent loads and offers a more mature global infrastructure, which matters for teams processing over 1,000 tickets per day or managing large historical datasets.
- Zendesk's ecosystem has over 1,400 native integrations in its marketplace versus Kustomer's narrower set of certified integrations. Teams with existing CRM, ERP, or communication tool dependencies find the Zendesk integration ecosystem more complete, reducing the need for custom middleware or Zapier workarounds that Kustomer often requires.
- Kustomer's steep learning curve and non-intuitive areas require significant training investment before teams become productive. Zendesk's interface has a larger talent pool of experienced administrators, faster onboarding for new agents, and more available community resources, which reduces the total cost of ownership for teams that turnover agents regularly or onboard frequently.

Questions, answered

## Kustomer to Zendesk migration questions

How long does a Kustomer to Zendesk migration take?

Standard migrations under 10,000 conversations and no KObjects land between three and five weeks. Migrations with KObject schemas, multi-year conversation history requiring rolling 30-day export tranches, or over 30,000 message records move to six to twelve weeks. The timeline depends heavily on whether the customer has an events-stream export contract with Kustomer, because a standard 30-day CSV export requires multiple tranches to capture full history, each requiring coordination and validation.

Do Kustomer Workflows and routing rules migrate to Zendesk?

No. Kustomer Workflows are platform-specific automation definitions that cannot be meaningfully translated to Zendesk Triggers, Macros, or SLA Policies. We do not migrate them as code. We deliver a written Automation Inventory listing every active Kustomer Workflow and routing rule with its trigger, conditions, and actions, plus a recommended Zendesk equivalent (Trigger, Macro, SLA Policy, or Group assignment) for the customer's admin to rebuild. SLA Policies are configuration files rather than records and are handled the same way.

Can we migrate all our conversation history, or are we limited by Kustomer's export cap?

You can migrate all history, but the method depends on your Kustomer contract. Standard CSV export is limited to 30 days per run, which requires rolling tranches for multi-year history. If Kustomer's events-stream export is available under your contract, it delivers the full history in a structured format without the 30-day window. We discuss export scope strategy during discovery and price accordingly. The 30-day cap is a Kustomer platform constraint, not a FlitStack AI constraint, and we disclose it upfront in the scoping document.

What happens to Kustomer's KObject data in Zendesk?

KObject schemas have no direct standard equivalent in Zendesk. We discover every KObject definition during the pre-migration audit — all custom fields, data types, and cross-Klass relationships — and recreate them as Zendesk Custom Objects using the new Custom Objects API (GA 2024). We avoid Zendesk's Legacy Custom Object endpoint because Zendesk retires it in July 2026. KObject records import after all standard objects because they typically contain lookup relationships to Customers and Companies. The customer's admin validates the relationship graph in sandbox before production KObject import.

Do we lose our Kustomer Reports and dashboards?

Pre-built reports and saved dashboard definitions in Kustomer are platform-specific configurations that do not migrate to Zendesk. Historical data in those reports is included in the conversation export (subject to the 30-day cap unless events-stream is in use). We deliver a written Report Inventory listing every saved Kustomer report and its recommended Zendesk Explore equivalent, including which migrated fields map to the original report dimensions and metrics. The customer's admin rebuilds reports in Zendesk Explore post-migration.

How does the timeline-versus-ticket model difference affect our migrated data?

Kustomer attaches all conversations to a single Customer record in a chronological timeline. Zendesk creates a separate Ticket for each conversation. A Kustomer Customer with five open conversations becomes five Zendesk Tickets all linked to the same End User. We make this explicit during scoping because it changes ticket count reporting in Zendesk. The conversation subject and most recent message body map to the ticket Subject and Description, and the original Kustomer Conversation Id is preserved in a custom field for cross-reference.

Will migrated Solved tickets auto-close in Zendesk?

Yes. Zendesk's default automation closes tickets marked Solved after 28 days of inactivity. Kustomer's Done status is a terminal state with no automatic transition. Migrated Solved conversations will be subject to Zendesk's 28-day auto-close behavior. We document this for the customer's admin during cutover and recommend either disabling the automation in Zendesk Admin > Automations or setting a longer interval if migrated Solved tickets need to remain open for an extended period.

## Related migrations

[![](https://flitstack.ai/platforms-trim/zendesk.webp) Migrate to **Zendesk** Every source we move into Zendesk, native options and the checklist. Guide, checklist & sources ](https://flitstack.ai/migrations/helpdesk/zendesk) [**LiveAgent to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/liveagent/to/zendesk) [**Help Scout to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/help-scout/to/zendesk) [**Crisp to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/crisp/to/zendesk) [**Jira Service Management to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/jira-service-management/to/zendesk) [**Freshservice to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/freshservice/to/zendesk) [**Zoho Desk to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/zoho-desk/to/zendesk) [**Kustomer to Intercom** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/kustomer/to/intercom)

## Sources: official documentation

1. [About ticket import — Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408886248218-About-ticket-import)
2. [How can I bulk update users — Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408888554394-How-can-I-bulk-update-users)
3. [About custom objects — Zendesk help](https://support.zendesk.com/hc/en-us/articles/6034114094618-About-custom-objects)
4. [Bulk importing user data with the data importer — Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408893496218-Bulk-importing-user-data-with-the-data-importer)
5. [How do I format the date field in Sell — Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408830289946-How-do-I-format-the-date-field-in-Sell-)
6. [About custom ticket fields — Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408884482330-About-custom-ticket-fields)
7. [About lookup relationship fields — Zendesk help](https://support.zendesk.com/hc/en-us/articles/4408888227482-About-lookup-relationship-fields)

Get a quote

## Moving from Kustomer to Zendesk?

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

[Get a quote](https://flitstack.ai/contact)
