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

# LiveChat to Zendesk migration

We migrate LiveChat conversations, agents, and requesters into Zendesk tickets, users, and end-users with threading preserved from chat to ticket, widget-level custom fields deduplicated across the destination schema, and knowledge base articles rebuilt in the Zendesk Guide.

Short answer

FlitStack AI migrates tickets, users, end users, tags and custom fields from LiveChat 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/livechat/to/zendesk#what-moves)

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

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

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

Ticket User End User Tag Custom Field

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

## What moves from LiveChat to Zendesk?

Moving from LiveChat to Zendesk is a migration from a focused real-time chat platform to a full omnichannel service desk.

Read the full summary

LiveChat organizes data around Chats (conversations), Agents (operators), and Requesters (customers), while Zendesk uses Tickets, Users (agents), and End Users (customers) with an Account hierarchy option for B2B contexts. The primary migration challenge is transforming session-based chat threads into persistent tickets with full conversation history preserved, since LiveChat's default mode is ephemeral while Zendesk's is record-based. We extract chat transcripts via the LiveChat API, map agents 1:1 to Zendesk users, and resolve requesters against the Zendesk end-user table before inserting. Widget-level custom fields in LiveChat require deduplication during the mapping phase when the account uses multiple chat widgets. We do not migrate automated rules, chatbot flows, or integrations as configuration; we document them for your admin to rebuild in Zendesk.

1:1

### Chat → Ticket

LiveChat Chats map to Zendesk Tickets with the full message thread preserved as ticket comments.

How it maps

We sequence messages chronologically, mapping agent messages to public comments and customer messages to public comments in the Zendesk conversation view. System events (chat started, transferred, rated) are preserved as private comments with a migration note so agents can audit thread context. Chat ID is stored in a custom field ticket\_custom\_field\_livechat\_id for cross-referencing after migration.

1:1

### Agent → User

LiveChat Agents map directly to Zendesk Users.

How it maps

We match by email address, preserving display name, role, and group assignment. Agents with the Agent role in LiveChat map to Zendesk Agents; administrators map to Zendesk Admins. The customer provisions the Zendesk users before migration so that OwnerId references are satisfied at insert time.

1:1

### Requester → End User

LiveChat Requesters map to Zendesk End Users.

How it maps

Email, name, and any requester-level custom properties migrate directly. If the customer uses Zendesk Organizations (Accounts), we attach End Users to the matching Organization during import by matching on domain or a pre-agreed organization name field. Requester avatar URLs do not migrate as Zendesk does not support avatar import via API.

1:1

### Tag → Tag

LiveChat chat tags migrate as Zendesk ticket tags.

How it maps

We normalize tag character set (Zendesk allows alphanumeric, hyphen, underscore, and colon only) and enforce the 100-character per-tag limit. Multi-word tags with spaces are converted to hyphen-separated strings.

configuration

### Custom Field (Chat) → Custom Field (Ticket)

LiveChat custom fields attached to chats map to Zendesk ticket custom fields.

How it maps

We detect widget-level field overlap during the discovery scan: if the same field name exists in multiple widgets but with different internal IDs, we consolidate to a single Zendesk custom field and map all widget-level values to it. Field type mapping follows: text inputs to text, dropdowns to dropdown, checkboxes to boolean, date pickers to date.

configuration

### Custom Field (Requester) → Custom Field (End User)

LiveChat requester custom properties map to Zendesk End User custom fields.

How it maps

These are created under Admin > People > End User Fields before migration. Field type mapping follows the same rules as ticket custom fields.

******What moves 12 objects

LiveChat Zendesk

- Chat Ticket 1:1
- Agent User 1:1
- Requester End User 1:1
- Tag Tag 1:1
- Custom Field Custom Field transformed
- Custom Field Custom Field transformed

\+ 6 more in the mapping below

## How LiveChat 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              | LiveChat                                                                      | Zendesk                                                                                           |
| ---------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| Conversation model     | Session-based chat threads, ephemeral by default unless archived              | Persistent ticket-based threads with conversation history across channels                         |
| Channel scope          | Real-time web chat primarily with proactive invitations                       | Omnichannel: web, email, social, voice, messaging, and chat unified in one inbox                  |
| Pricing starting point | $20/agent/month (Team plan), $79/agent/month (Business plan)                  | $25/agent/month (Suite Team), scaling to $115+/agent for full Suite access                        |
| Analytics depth        | Standard chat reports: duration, CSAT, response times                         | Advanced cross-channel analytics, SLA reporting, and custom report builder                        |
| Knowledge base         | Separate KnowledgeBase product, exported as articles                          | Integrated Guide with hierarchical sections, article management, and end-user self-service portal |
| Custom field scope     | Per-widget custom fields that can duplicate across widgets with different IDs | Global custom fields scoped to ticket, user, or organization with account-wide consistency        |
| Integrations ecosystem | Around 200 integrations focused on chat and CRM connectors                    | Over 1,500 integrations including ERP, telephony, messaging, and enterprise software              |

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

### LiveChat bulk export requires the Chats Exporter app

LiveChat has no built-in bulk-export UI.

How we handle it

The official Chats Exporter app costs $7 and generates JSON or CSV per widget per date range. Accounts with multiple widgets or multi-year histories must run multiple export jobs and merge the results. We automate this stitching process and validate that no conversations are truncated at widget or date boundaries. If the account uses more than five widgets, we recommend the customer provision a temporary trial account for the export window to avoid creating excessive export jobs.

high

### Conversation persistence semantics differ between platforms

LiveChat's default chat mode is session-based and ephemeral: a chat closes when the session ends, and without explicit archiving, transcript history may be incomplete.

How we handle it

Zendesk Tickets are persistent by default. If LiveChat chats in the migration window include open sessions that were never closed, we close them before export to ensure the full thread is captured. Any chat with a last\_activity timestamp within 24 hours of the migration date is flagged as potentially active and held until the customer confirms no live chats are running.

medium

### Widget-level custom fields duplicate across the destination schema

LiveChat custom fields are created per chat widget, not globally at the account level.

How we handle it

The same field name (e.g., 'Order ID') may exist in Widget A and Widget B but with different internal IDs. If we map them directly to Zendesk, Zendesk creates two separate custom fields with the same display name, causing agent confusion. We detect this during the discovery scan and consolidate duplicate field definitions to a single Zendesk custom field, then validate that all widget-level values map to it before inserting tickets.

medium

### Zendesk suspended End Users cannot be requesters on imported tickets

Zendesk does not allow a suspended End User to be the requester on a ticket.

How we handle it

If any LiveChat Requesters in the migration data have suspended status in the destination Zendesk account, we change them to active before importing the associated tickets. If the customer needs to preserve the suspended status for compliance reasons, we flag those tickets and their requester records for manual review.

medium

### Agent seat deactivation in LiveChat must happen post-migration

LiveChat bills per agent seat. Agents who are migrated to Zendesk Users must be explicitly deactivated in the LiveChat admin panel to stop billing; deactivation is not automatic.

How we handle it

We provide a deactivation checklist at cutover listing every migrated agent and the LiveChat admin panel steps to deactivate them. If agents remain active post-migration, LiveChat billing continues for unused seats.

## How the migration runs

1. ### Discovery and export preparation

   We audit the source LiveChat account: widget count, agent count, requester volume, chat history date range, custom field schema per widget, canned response count, knowledge base article count, and active automated rules.

   What this step covers

   We identify the Chats Exporter app requirement and coordinate with the customer to install it and provision export credentials. We confirm which Zendesk Suite tier the customer is provisioning (Team through Enterprise Plus) and whether Organizations are in scope. The discovery output is a written migration scope with record counts per object and a Zendesk configuration readiness checklist.

2. ### Zendesk schema provisioning and custom field creation

   We provision the Zendesk destination schema before any data moves.

   What this step covers

   This includes creating Zendesk ticket custom fields to match LiveChat chat custom fields (consolidated across widgets), creating End User custom fields to match LiveChat requester properties, setting up Groups to match LiveChat groups, creating Macro categories if the customer uses canned response categorization, and activating Zendesk Guide for knowledge base migration. The Help Center must be activated by the account owner under Guide > Settings before article import can proceed.

3. ### Widget-level export stitching and data validation

   We run LiveChat chat exports per widget per date window using the Chats Exporter API, stitching results across widgets and date ranges into a single chronological dataset.

   What this step covers

   We validate completeness against the total chat count reported by the LiveChat API, checking for truncation at widget boundaries and date boundary gaps. Chat ratings, tags, and custom field values are extracted from the export payload and validated for type consistency before transformation.

4. ### Test migration and mapping reconciliation

   We run a test migration into the customer's Zendesk sandbox (or a trial environment) using a representative sample of 500-1,000 chats.

   What this step covers

   The customer reconciles ticket threading, custom field values, agent assignments, and requester records against the LiveChat source. Any field type mismatches, missing custom fields, or tag normalization issues are corrected before the production migration begins. This step also validates that the canned response to Macro conversion and knowledge base article structure are acceptable.

5. ### User and agent provisioning

   We provide the customer with a user provisioning spreadsheet listing every LiveChat agent mapped to a Zendesk User.

   What this step covers

   The customer provisions the Zendesk Users (with appropriate roles and group memberships) before production migration begins. OwnerId references on Tickets are required at insert time, so User provisioning must be complete and validated before we proceed with ticket imports.

6. ### Production migration in dependency order

   We run the production migration in dependency order: Groups first (referenced by agent group memberships), then Users (Agents from LiveChat), then End Users (Requesters), then Articles (if Guide is activated), then Macros (Canned Responses), then Tickets (Chats with thread preserved as comments).

   What this step covers

   Each phase emits a row-count reconciliation report. Chat threads are inserted chronologically with system events logged as private comments. Custom fields are resolved at ticket insert time using the consolidated field schema.

7. ### Cutover, validation, and automation handoff

   We freeze LiveChat writes during cutover, run a final delta migration of any chats created or modified during the migration window, and enable Zendesk as the system of record.

   What this step covers

   We deliver the automated rule inventory document listing every LiveChat automated rule with its trigger, conditions, and recommended Zendesk Trigger equivalent. We do not rebuild automated rules as Zendesk triggers inside the migration scope; the customer's Zendesk admin rebuilds them post-migration. We support a one-week post-cutover reconciliation window for data issues raised by the support team.

![](https://flitstack.ai/platforms/livechat.png) LiveChat ![](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

**6-10 weeks** Large or heavily customised accounts

A quote scales with chat volume, widget count, and custom field deduplication scope. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from LiveChat to Zendesk

- Teams requiring omnichannel coverage find LiveChat's chat-centric model insufficient as support volume grows across email, phone, and social. Zendesk unifies these channels into a single ticket inbox with consistent agent experience and conversation persistence across channel switches, eliminating the need to manage separate systems or manually correlate email threads with chat history.
- LiveChat's analytics focuses on chat-specific metrics like duration, CSAT, and response times. Reviewers on G2 and comparison sites cite Zendesk's advanced reporting engine as a reason for switching when leadership needs cross-channel visibility, SLA compliance tracking, agent performance benchmarking, and custom report builder without exporting to a BI tool.
- Zendesk's built-in Help Center with customizable articles, sections, and community forums provides end-user self-service that complements the ticketing system natively. LiveChat's KnowledgeBase is a separate product requiring its own export and maintenance. Teams moving to Zendesk consolidate their help desk and knowledge base under one admin panel and one URL.
- As teams scale past 20-50 agents, LiveChat's routing options and workload balancing become constrained without third-party tools. Zendesk's advanced automation, SLA policies, routing based on ticket fields, and agent collision detection support larger support organizations without piecing together multiple vendor products.
- Zendesk's App Marketplace lists over 1,500 integrations versus LiveChat's approximately 200. Companies needing native ERP connectors, telephony integrations, contract management, or enterprise software connectivity cite the broader ecosystem as a driver for consolidation onto Zendesk as their primary service desk.

Questions, answered

## LiveChat to Zendesk migration questions

How long does a LiveChat to Zendesk migration take?

Most migrations land between three and five weeks for accounts under 50,000 chats, one widget, and no knowledge base migration. Migrations with multiple widgets requiring custom field deduplication, large knowledge base articles, or concurrent Guide activation move to six to ten weeks because of widget-level export stitching and Help Center configuration. The customer's responsiveness during User provisioning and test reconciliation is the most common timeline variable.

Do LiveChat automated rules and chatbot flows migrate to Zendesk?

No. LiveChat automated rules (triggers based on chat events) and chatbot flows built in the ChatBot product are configuration-bound and do not have a portable data format. We document every active automated rule with its trigger condition, action, and a recommended Zendesk Trigger equivalent, and the customer's Zendesk admin rebuilds them post-migration. Chatbot flows require a separate rebuild project using Zendesk's AI Agent builder or a third-party chatbot platform.

How do we migrate the LiveChat knowledge base to Zendesk Guide?

We export LiveChat KnowledgeBase articles with HTML body, title, slug, and section hierarchy, and create them as Zendesk Guide articles under the corresponding Section and Subsection. The Help Center must be activated by the account owner before import. Embedded images from LiveChat CDN are downloaded and re-uploaded as Zendesk Guide attachments. Complex nested article structures more than three levels deep may require manual reorganization in Zendesk Guide post-migration.

What happens to open LiveChat conversations during migration?

LiveChat chats with a last\_activity timestamp within 24 hours of the migration date are flagged as potentially active and held until the customer confirms no live chats are running. We recommend scheduling the migration export outside business hours and setting all LiveChat agents to Away status during the export window. Closed chats migrate normally. If any open chats must be preserved, the customer should close them in LiveChat before export to capture the full thread.

Will we lose chat history if LiveChat is session-based?

LiveChat's default mode is session-based, meaning conversations without explicit archiving may not retain full transcript history. We close all open sessions before export to ensure completeness, and we extract archived history via the Chats Exporter app. If the account relies on session-only mode with no archiving, some older transcripts may be unavailable. We confirm archiving status during discovery and flag any gaps in the migration scope document.

Can we run LiveChat and Zendesk side-by-side during migration?

Yes, but with caution. Active LiveChat chats during the migration window may be auto-closed by LiveChat's reconnect failure handling (30-second timeout). We recommend setting all LiveChat agents to Away and scheduling the migration export outside business hours to minimize interference. New tickets created in Zendesk during the migration window do not automatically sync back to LiveChat; customers running both systems simultaneously should assign a point person to manually correlate Zendesk ticket numbers against LiveChat chat references.

How do we stop LiveChat billing after migration?

LiveChat bills per agent seat. Deactivating agents in LiveChat is the customer's responsibility after cutover and is not handled by FlitStack AI. We provide a deactivation checklist at cutover listing every migrated agent with the LiveChat admin panel steps (Admin > Agents > select agent > Deactivate). Agents must be explicitly deactivated; pausing or archiving accounts does not stop billing. Zendesk subscription begins separately and is independent of the LiveChat billing cycle.

## 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) [**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) [**Intercom to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/intercom/to/zendesk) [**Chatwoot to Zendesk** Mapping · history · rollback](https://flitstack.ai/migrations/helpdesk/chatwoot/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)

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