---
title: "Chatwoot to Zendesk Migration: Field Mapping & Rollback"
description: "Migrate Chatwoot 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/chatwoot/to/zendesk"
---

# Chatwoot to Zendesk migration

We migrate Conversations, Contacts, Messages, Labels, and Custom Attributes from Chatwoot into Zendesk Support with conversation threads preserved through the Zendesk API, channel-to-ticket field mapping resolved before import, and historical data scoped against the source plan's retention window before any records move.

Short answer

FlitStack AI migrates tickets, end users, users, ticket comments and tags from Chatwoot 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-5 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/chatwoot/to/zendesk#what-moves)

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

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

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

Ticket End User User Ticket Comment Tag

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

## What moves from Chatwoot to Zendesk?

Moving from Chatwoot to Zendesk is a move from a self-hostable, open-source tier-gated platform to a SaaS-native enterprise helpdesk.

Read the full summary

Chatwoot organizes support around Inboxes and Conversations; Zendesk organizes around Tickets with a unified Request queue. We map Chatwoot Conversations to Zendesk Tickets, preserving the full message thread with timestamps, attachments, and private notes. Contacts map to End Users and Users depending on whether they are customers or agents. Labels migrate to Tags, and Custom Attributes migrate to Zendesk custom ticket fields after the destination schema is pre-created. We flag that Chatwoot's Help Center, Automation Rules, and SLA Policies require Business or Enterprise tiers on the source and will be absent from the export if the source account is on Hacker or Startups. Zendesk Guide is a separate product requiring activation before article migration; we do not activate Guide as part of the migration scope. Workflows, automation rules, and canned response logic do not migrate; we deliver a written inventory of these for the customer's admin to rebuild.

1:1

### Conversation → Ticket

Chatwoot Conversations map to Zendesk Tickets.

How it maps

Each Conversation's status (open/resolved/pending), priority, assignee, and created\_at timestamp transfer to Ticket fields. The full message array (agent messages, customer messages, private notes) migrates as individual Ticket Comments preserving created\_at order and message type. We tag migrated tickets with a system tag (migrated\_from\_chatwoot) to allow the customer's admin to exclude them from Zendesk Triggers and SLA calculations during initial setup.

1:1

### Contact → End User

Chatwoot Contacts (name, email, phone, custom\_attributes) map to Zendesk End Users.

How it maps

Email address is the dedupe key for import. We preserve any Chatwoot Contact custom\_attributes as Zendesk user fields, which requires pre-creating the schema in Zendesk Admin before migration. Contacts without an email address are imported as Users with a placeholder domain to satisfy Zendesk's required email format.

1:1

### Agent → User

Chatwoot Agents (name, email, role, availability\_status) map to Zendesk Users.

How it maps

Role mapping: Chatwoot administrator maps to Zendesk admin; agent maps to agent. We resolve agents by email match against the Zendesk destination. Any Chatwoot Agent without a matching Zendesk User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

1:1

### Message → Ticket Comment

Chatwoot Messages belong to Conversations and carry content, sender\_type (agent/customer), attachments, and created\_at.

How it maps

We map agent messages to public Zendesk Ticket Comments and customer messages to public Ticket Comments. Chatwoot private notes map to Zendesk internal Ticket Comments. We preserve message order by created\_at timestamp and migrate attachment URLs as references; actual attachment files require separate handling if the Chatwoot storage endpoint is accessible.

1:1

### Label → Tag

Chatwoot Labels are string tags applied to Conversations.

How it maps

We export the full label taxonomy and map to Zendesk Tags. Note that Zendesk Tags are case-sensitive and have a 2,000-tag-per-account limit; we flag if the source label count approaches this boundary during scoping.

configuration

### Custom Attributes → Ticket Fields (custom)

Chatwoot Custom Attributes attach to Conversations or Contacts and support text, number, dropdown, and checkbox types.

How it maps

We pre-create the equivalent Zendesk custom ticket fields (for conversation-attached attributes) and custom user fields (for contact-attached attributes) in Zendesk Admin before migration. Dropdown attributes in Chatwoot require a corresponding Zendesk custom field with matching picklist values. Checkbox attributes map to Zendesk boolean fields.

******What moves 10 objects

Chatwoot Zendesk

- Conversation Ticket 1:1
- Contact End User 1:1
- Agent User 1:1
- Message Ticket Comment 1:1
- Label Tag 1:1
- Custom Attributes Ticket Fields transformed

\+ 4 more in the mapping below

## How Chatwoot 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                   | Chatwoot                                                                                  | Zendesk                                                                                        |
| --------------------------- | ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Deployment model            | Self-hosted Docker with PostgreSQL/Redis or cloud SaaS with tier-gated features           | Cloud SaaS with unified Support Suite across all paid tiers                                    |
| Core support unit           | Conversations organized by Inbox (live chat, email, WhatsApp, API, Facebook, Twitter)     | Tickets organized by Request with unified queue across all channels                            |
| AI features                 | Captain AI credit model ($20 per 1,000 credits beyond tier allocation)                    | Zendesk AI included across Suite Professional and above with no credit model                   |
| SLA policies                | Enterprise Edition only; defines first-response and resolution targets per priority       | Available from Suite Team ($19/agent); built-in first-response and resolution SLA targets      |
| Help Center                 | Startups tier or higher; Markdown-based article editor with category and locale           | Zendesk Guide as a separate product; requires activation before article migration              |
| Feature gating on free plan | Hacker plan caps at 2 agents, 1 inbox, 30-day retention, no Teams/Automations/Help Center | Suite Team starts at $19/agent with all core features; Help Center and AI require higher tiers |
| Automation rules            | Business tier or higher; event-triggered assign/label/send actions                        | Triggers and Automations available from Suite Team; different logic model                      |

## What to watch for in a Chatwoot 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

### Hacker plan 30-day data retention permanently deletes conversations before export

Chatwoot's free Hacker plan retains only 30 days of conversation data.

How we handle it

If the source account is on Hacker and is older than 30 days, historical conversations are permanently deleted from Chatwoot's database and cannot be recovered by any export method. We flag this during scoping and recommend immediate export for any account on Hacker, or upgrading to a paid tier to extend the retention window before migration begins. Source accounts on Startups (1-year retention) or Business (2-year retention) do not face this constraint.

high

### Help Center requires separate Zendesk Guide activation

Zendesk Guide is a separate product from Zendesk Support and must be activated in the Zendesk Admin before article migration can begin.

How we handle it

Chatwoot Help Center Articles (Startups tier or higher) cannot be imported into Zendesk until Guide is enabled, which also requires selecting a Guide plan tier. We do not activate Guide as part of standard migration scope; we document the Guide tier requirements and activation steps, and the customer's admin completes activation before the Help Center phase of migration runs.

medium

### Automation Rules and SLA Policies tier-gated on source; absent from export if lower plan

Chatwoot Automation Rules require Business tier or higher; SLA Policies require Enterprise Edition.

How we handle it

If the source account is on Hacker or Startups, these objects do not exist in the Chatwoot data export regardless of business need. We document which objects are absent based on the source plan tier and flag which ones require manual configuration in Zendesk (Zendesk SLA policies are available from Suite Team without additional cost). We do not rebuild Chatwoot Automation Rules as Zendesk Triggers inside migration scope.

medium

### Channel credentials and webhook URLs do not transfer between platforms

Chatwoot Inbox configurations (webhook URLs, Facebook page tokens, WhatsApp business API credentials, email IMAP/SMTP settings) are credentials-bound to the source Chatwoot instance.

How we handle it

These cannot function at Zendesk because they are tied to the original platform account. We document the inbox taxonomy (channel types, agent assignments, routing rules) and map it to Zendesk Channels and Views. The customer's admin reconfigures channel credentials in Zendesk Admin post-migration. Email channel reconfiguration is the highest-friction item for teams with existing IMAP/pop setups.

low

### Chatwoot private notes require internal comment mapping

Chatwoot Messages with sender\_type of agent and a private note flag map to Zendesk internal Ticket Comments.

How we handle it

Internal comments in Zendesk are visible only to agents and admins, matching Chatwoot's private note behavior. However, Zendesk's permission model for internal comments depends on the admin's role configuration; we document the mapping and recommend that the customer's Zendesk admin verifies internal comment visibility after migration to ensure sensitive notes remain restricted.

## How the migration runs

1. ### Discovery and plan audit

   We audit the source Chatwoot account across plan tier (Hacker/Startups/Business/Enterprise self-hosted), active inboxes, agent count, conversation volume, message count, custom attribute definitions, label taxonomy, canned response count, Help Center article count, and whether Automation Rules or SLA Policies exist.

   What this step covers

   We pair this with a Zendesk edition decision: Suite Team ($19/agent) covers migrations with no Help Center; Suite Growth or Professional is required if Help Center or advanced reporting is needed. The discovery output is a written migration scope with record counts per object and a Zendesk plan recommendation.

2. ### Schema pre-creation and Help Center activation guidance

   We create the destination Zendesk custom fields (ticket fields and user fields) matching every Chatwoot custom attribute before any data import.

   What this step covers

   Dropdown custom attributes require picklist values to be defined in Zendesk Admin before the field is created. We provide the customer with Zendesk Guide activation instructions and Guide tier recommendation if Help Center articles are in scope. We create Zendesk Groups matching Chatwoot Teams, and Macros matching Canned Responses. Channel configurations are documented for the customer's admin to re-enter post-migration.

3. ### Sandbox migration and reconciliation

   We run a full migration into a Zendesk Sandbox (copy of the destination account) using production-like data volume.

   What this step covers

   The customer's support operations lead reconciles record counts (Tickets in, End Users in, Users in, Comments in), spot-checks 25-50 random tickets against the Chatwoot source, and validates label mapping and custom field population. The customer signs off the schema and mapping before production migration begins. Any mapping corrections happen in sandbox, not production.

4. ### Agent and Contact reconciliation

   We extract every distinct Chatwoot Agent and Contact email and match against the Zendesk destination's user table.

   What this step covers

   Agents without a matching Zendesk User go to a reconciliation queue. The customer's Zendesk admin provisions any missing Users before record import resumes. Contacts without emails receive a placeholder domain in Zendesk's required email format so that import does not fail. This step gates the Contact and Agent import phases.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Users (validated), End Users (Contacts), Groups (from Teams), Tickets (Conversations with resolved author references), Ticket Comments (Messages preserving created\_at order), Tags (from Labels), Custom field values (populated after field schema exists), Macros (Canned Responses), and Help Center Articles (after Guide activation is confirmed).

   What this step covers

   We disable Zendesk Triggers and SLA policies before migration to prevent automated notifications from firing on imported tickets. Each phase emits a row-count reconciliation report before the next phase begins.

6. ### Cutover, validation, and automation rebuild handoff

   We freeze Chatwoot writes during cutover, run a final delta migration of any records modified during the migration window, then enable Zendesk as the system of record.

   What this step covers

   We re-enable Zendesk Triggers and SLA policies after migration completes. We deliver the Automation Rule and SLA Policy inventory document to the customer's admin team for manual rebuild in Zendesk Triggers and SLA policies. We support a one-week hypercare window for reconciliation issues. We do not rebuild Chatwoot Automation Rules as Zendesk Triggers or configure Help Center as part of migration scope; those are separate configuration tasks.

![](https://flitstack.ai/platforms/chatwoot.png) Chatwoot ![](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-5 weeks** Typical, smaller accounts

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

A quote scales with conversation volume, custom attribute count, and whether the source is on a tier that includes Help Center and SLA data. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from Chatwoot to Zendesk

- Chatwoot's feature gating forces premature plan upgrades. G2 reviewers highlight that Teams, Automation Rules, Help Center, SLA Policies, SSO, and Audit Logs all require paid tiers, making the real cost far higher than the headline per-agent price. Zendesk Suite Team at $19/agent includes SLA management, triggers, and core reporting out of the box, eliminating the feature cliff that Chatwoot teams hit as they scale.
- Captain AI credit billing surprises grow teams. Chatwoot charges $20 per 1,000 Captain AI credits beyond the monthly tier allocation (300 for Startups, 500 for Business, 800 for Enterprise). Teams that adopt AI features for summarization and reply suggestions find unpredictable line items on their billing cycle. Zendesk AI is bundled into Suite Professional and above without a credit model, providing predictable AI-assisted support costs at scale.
- Enterprise security and compliance requirements point to Zendesk. Featurebase and Techjockey comparison reviews note that Zendesk provides SOC 2 compliance, built-in DDoS protection, automatic weekly backups, and GDPR tooling as standard across paid tiers. Chatwoot's self-hosted model puts security configuration (SSL, firewall, backup scheduling) on the engineering team, which creates operational overhead and compliance risk for regulated industries.
- Zendesk's automation, reporting, and customer data management scale beyond what open-source helpdesk platforms handle without significant engineering effort. Featurebase specifically cites Zendesk's advanced workflow rules, analytics, and data management as the differentiator for businesses requiring reliability at enterprise scale. G2 reviewers note that Chatwoot's interface is clean and simple but that Zendesk's feature depth becomes necessary as ticket volume and team complexity grow.
- Hacker plan 30-day data retention permanently deletes conversation history. Teams on Chatwoot's free tier that do not export within 30 days lose all historical conversations permanently. Zendesk provides data retention policies aligned to compliance requirements without a cliff. Teams migrating from a stale Chatwoot Hacker account may find that historical conversations are unrecoverable regardless of migration intent.

Questions, answered

## Chatwoot to Zendesk migration questions

How long does a Chatwoot to Zendesk migration take?

Most migrations land between three and five weeks for accounts under 50,000 conversations and 10,000 contacts with no Help Center articles or custom attributes. Migrations with large engagement histories (over 200,000 messages), multiple channel types, custom attribute schemas, or Help Center article trees move to eight to twelve weeks because of Zendesk API rate-limit handling, bulk chunking, Help Center activation coordination, and extended reconciliation.

Do Chatwoot Automation Rules, SLA Policies, and Canned Responses migrate to Zendesk?

Automation Rules and SLA Policies require Business or Enterprise tier on Chatwoot and may not exist in the export if the source is on a lower plan. If they exist, we export their definitions but do not rebuild them as Zendesk Triggers or SLA policies inside migration scope. We deliver a written inventory of every Chatwoot Automation Rule and SLA Policy with its trigger conditions, actions, and a recommended Zendesk equivalent. Canned Responses migrate as Zendesk Macros with content and title preserved. Help Center Articles migrate to Zendesk Guide after the customer activates Guide in their Zendesk admin.

What happens to my Chatwoot conversation history if I am on the Hacker plan?

Chatwoot's Hacker plan permanently deletes conversation data after 30 days. If your Chatwoot account is on Hacker and is older than 30 days, historical conversations are unrecoverable and cannot be migrated regardless of method. We recommend exporting immediately if you are on Hacker, or upgrading to a paid tier before migration scoping begins. Accounts on Startups (1-year retention) or Business (2-year retention) retain their full history and face no deletion cliff.

Can we keep Chatwoot's self-hosted infrastructure while using Zendesk for support?

This is not a standard dual-platform setup. Chatwoot and Zendesk are both full helpdesk platforms that serve as the primary system of record for support. Running both simultaneously would require manual synchronization that is not supported by either platform. Most teams migrating to Zendesk close their Chatwoot account and use Zendesk exclusively. If your team needs to retain Chatwoot for a specific use case (such as a live chat widget for a specific product line), that scope requires a separate scoping conversation and is not covered under standard migration pricing.

Do Zendesk Triggers fire on migrated tickets?

By default, Zendesk Triggers fire on any ticket that meets the trigger conditions, including migrated tickets. We disable Triggers and SLA policies before migration to prevent automated notifications from sending to customers about tickets they did not submit. After migration completes and before Zendesk goes live, we re-enable Triggers and SLA policies so that new incoming tickets flow through automation normally. We tag migrated tickets with a system tag to allow the customer's admin to apply additional exclusions if needed.

How do we handle Chatwoot private notes?

Chatwoot private notes (Messages with sender\_type of agent and a private flag) migrate to Zendesk internal Ticket Comments. Internal comments in Zendesk are visible only to agents and admins, which matches Chatwoot's private note behavior. We recommend that the customer's Zendesk admin verifies the internal comment visibility settings in their admin role configuration after migration to confirm that sensitive notes remain restricted to the appropriate roles.

Can FlitStack AI also activate Zendesk Guide and configure SLA policies?

We provide written guidance for Zendesk Guide activation and Help Center tier selection as part of standard migration scope. We do not activate Guide on the customer's behalf because it requires account-level permissions and a Guide plan subscription that only the customer's account admin can authorize. SLA policy configuration in Zendesk is documented during migration discovery if the source Chatwoot account has SLA Policies, but the actual SLA configuration in Zendesk is a separate admin task or a separate Zendesk professional services engagement.

## 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) [**LiveChat to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/livechat/to/zendesk) [**Tidio to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/tidio/to/zendesk) [**Trengo to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/trengo/to/zendesk) [**Crisp to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/crisp/to/zendesk) [**Help Scout to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/help-scout/to/zendesk) [**LiveAgent to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/liveagent/to/zendesk) [**Chatwoot to Freshdesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/chatwoot/to/freshdesk)

## 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 Chatwoot 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)
