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

# LiveAgent to Zendesk migration

We migrate Tickets, Customers, Companies, Conversations, and Knowledge Base articles from LiveAgent into Zendesk with the 180 req/min API export throttle managed through request throttling and batch chunking, custom field schemas discovered dynamically at scoping, and all Zendesk Forum and Guide structures rebuilt alongside the Help Center import.

Short answer

FlitStack AI migrates tickets, users, organizations, comments and tags from LiveAgent 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: 2-4 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/liveagent/to/zendesk#what-moves)

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

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

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

Ticket User Organization Comment Tag

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

## What moves from LiveAgent to Zendesk?

Moving from LiveAgent to Zendesk is a cross-platform helpdesk migration that requires resolving differences in data model structure, rate-limit constraints, and automation handling.

Read the full summary

LiveAgent structures its support data as Tickets linked to Customers (contacts) and optionally to Companies, with all messages stored as threaded Conversations; Zendesk uses Tickets linked to Users (which serves as both contact and requester) and Organizations, with Comments attached to Tickets. We export from LiveAgent via its REST API within the 180 req/min cloud rate limit using paginated batches and exponential backoff, then import into Zendesk using the Tickets API, Users API, and Organizations API, resolving the LiveAgent Customer-to-Zendesk User and LiveAgent Company-to-Zendesk Organization lookups before ticket import. Knowledge Base articles transfer into Zendesk Guide, with categories and sections mapped to Guide sections. LiveAgent Macros and Rules are not exposed via the public API and do not migrate; we deliver a written automation inventory for the customer's admin to rebuild in Zendesk as Triggers and Automations. The staggered migration strategy keeps LiveAgent handling live support while historical data loads into Zendesk in the background, so there is no required downtime on the source system during the migration window.

1:1

### Ticket → Ticket

LiveAgent Tickets map directly to Zendesk Tickets.

How it maps

The LiveAgent ticket status (Open, Resolved, Archived) maps to Zendesk Ticket Status (Open, Pending, Solved, Closed) via a status mapping table defined at scoping. Priority, assignee email, customer email, subject, and custom field values transfer directly. We preserve the original LiveAgent ticket ID in a Zendesk custom ticket field for cross-reference after cutover. The 180 req/min export throttle requires paginated fetching; we use cursor-based pagination and chunk tickets into batches of 100 to stay within the limit.

1:1

### Customer (Contact) → User

LiveAgent Customer records map to Zendesk Users.

How it maps

Each Customer's name, email, phone, and address fields map to the corresponding Zendesk User fields. Custom field values on the Customer record transfer to Zendesk custom user fields, which we create dynamically if they do not exist in the destination. Email serves as the primary dedupe key; if a Zendesk User with the same email already exists, we update rather than create.

1:1

### Company → Organization

LiveAgent Company records map to Zendesk Organizations.

How it maps

Some LiveAgent accounts do not use Companies; we check the account schema during scoping and only create the Organization mapping if Companies are actively used. The Organization is created before any linked Tickets to satisfy Zendesk's Organization lookup requirement. Company custom fields map to Zendesk Organization custom fields in the same dynamic manner as User custom fields.

1:1

### Conversation (Message) → Comment

LiveAgent Conversation records on a Ticket map to Zendesk Comments on the corresponding Ticket.

How it maps

Each Conversation has an author (agent or customer), message body, timestamp, and optional attachment references. We preserve the author identity by resolving the LiveAgent agent email to a Zendesk User; customer-authored messages attach to the end-user (requester) on the Zendesk Ticket. Message ordering is preserved by setting the Comment creation timestamp to the original Conversation timestamp. Comments with public/internal visibility in LiveAgent map to public/private comments in Zendesk.

lookup

### Agent → User (Agent role)

LiveAgent does not expose a standalone Agents API object; agent identity is embedded in ticket assignments and conversation author fields.

How it maps

We extract all distinct agent emails from Tickets and Conversations during scoping, then map them to Zendesk User records by email match. The customer's Zendesk admin provisions any missing agent accounts before migration, and we flag agents without a Zendesk User record in a reconciliation queue.

1:1

### Tag → Tag

LiveAgent Tags applied to Tickets migrate to Zendesk Tags.

How it maps

Tags are created at migration time in Zendesk using the Tags API if they do not already exist, and then assigned to the corresponding Tickets via the Ticket Tags relationship. Tag name casing is preserved. Tags used for conversation-level labeling in LiveAgent apply to the parent Ticket in Zendesk.

******What moves 11 objects

LiveAgent Zendesk

- Ticket Ticket 1:1
- Customer User 1:1
- Company Organization 1:1
- Conversation Comment 1:1
- Agent User transformed
- Tag Tag 1:1

\+ 5 more in the mapping below

## How LiveAgent 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               | LiveAgent                                                                         | Zendesk                                                                                   |
| ----------------------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| Data model              | Tickets → Customers (Contacts) → Companies                                        | Tickets → Users (combined contact/requester) + Organizations                              |
| Message threading       | Conversations stored as separate linked records on Tickets                        | Comments stored inline on Tickets as a thread                                             |
| Automation access       | Macros and Rules not exposed via public REST API                                  | Triggers, Automations, and Macros accessible via Admin API                                |
| Knowledge base          | Built-in Knowledge Base with categories, sections, and articles                   | Zendesk Guide as a separate product tier with Section hierarchy                           |
| Agent management        | Agent info embedded in ticket assignments; no standalone Agents object            | Users API with Agent roles, Groups, and granular permissions                              |
| API rate limit (export) | 180 req/min hard limit on cloud accounts, enforced per API key                    | 700 req/min on Zendesk Suite Team; 2,000 req/min on Enterprise                            |
| Custom objects          | Custom fields on Customers and Tickets supported; no standalone custom object API | Custom Objects (Sunshine) available from Suite Professional with relational lookup fields |

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

### LiveAgent resolved-ticket email notifications fire on import

LiveAgent's default 'Ticket resolved' email notification triggers automatically when a ticket is set to Resolved status.

How we handle it

During an inbound migration to Zendesk, tickets may be set to Solved or Closed as part of the status mapping, which can cause LiveAgent to fire resolution emails to customers while their tickets are being re-imported into the destination system. We deactivate this notification template in LiveAgent Configuration > Email > Customer before initiating any migration export and re-enable it only after migration is complete and verified. This prevents customer-facing notification spam during the data transfer window.

high

### LiveAgent Macros and Rules have no migration path

LiveAgent Macros (canned responses and automated actions) and Rules (ticket routing, SLA policies, auto-assignment) are not exposed via the public REST API.

How we handle it

There is no automated export available. Zendesk's Triggers, Automations, and Macros are fully accessible via the Admin API, but the logic cannot be migrated directly because the trigger conditions, action sets, and delay configurations differ structurally between the two platforms. We deliver a written inventory of every LiveAgent Macro and Rule with a description of its logic and a recommended Zendesk Trigger or Automation equivalent. The customer's admin rebuilds these in Zendesk post-migration.

medium

### Knowledge Base Guide activation and hierarchy mismatch

Zendesk Guide is a separate product tier that must be explicitly activated before Knowledge Base import.

How we handle it

LiveAgent's Knowledge Base categories map to Zendesk Guide Sections, but LiveAgent supports a flatter category-section-article hierarchy that may not map cleanly to Zendesk Guide's Section permissions and article visibility settings. If the LiveAgent Knowledge Base uses per-category access controls, these must be reimplemented in Zendesk Guide's permission sets post-migration. We flag any category ACLs during scoping and document the reimplementation steps for the admin.

medium

### Custom object data cannot transfer between platforms at the object level

LiveAgent's custom fields on Customers and Tickets provide a flat key-value store for account-specific data.

How we handle it

Zendesk's Custom Objects (available from Suite Professional) use a relational model with lookup fields that can reference other custom objects or standard objects. Flat LiveAgent custom field values can migrate to Zendesk ticket or user custom fields, but if the customer uses LiveAgent custom fields to simulate a related-data pattern (e.g., linking a customer to a project record), that relationship must be redesigned in Zendesk's Custom Objects schema before the migration runs. We identify these patterns during scoping and recommend the redesign before any data moves.

medium

### Agent accounts must be pre-provisioned in Zendesk before ticket import

LiveAgent does not expose a standalone Agents API; agent identity lives in ticket assignment records and conversation authors.

How we handle it

We extract agent emails from the export but cannot create Zendesk User accounts via the API without admin credentials with provisioning rights. Zendesk requires every agent referenced on a ticket (as assignee or requester) to have a corresponding User record in the destination. We reconcile the agent list against the destination org before migration begins and flag any agents without Zendesk accounts for the customer's admin to provision.

## How the migration runs

1. ### Discovery and schema audit

   We audit the source LiveAgent account via the REST API to enumerate all active Ticket statuses, Customer custom fields, Ticket custom fields, Company records, Customer Group names, Tags, and Knowledge Base structure (categories, sections, article count).

   What this step covers

   We also identify any standalone installation (on-premise) deployments where the 180 req/min rate limit can be overridden via a database setting. The discovery output is a written migration scope document with record counts per object, a field-level mapping table for all standard and custom fields, and a Knowledge Base structure map for Guide section hierarchy design in Zendesk.

2. ### Zendesk destination setup and Guide activation

   We configure the Zendesk destination account before any import.

   What this step covers

   This includes activating Zendesk Guide (if not already active), creating the Guide section hierarchy to mirror the LiveAgent Knowledge Base structure, provisioning User fields and Organization fields for each discovered custom field, and defining the Ticket status mapping table. We set up Zendesk Groups to correspond to LiveAgent Departments if agent-based routing is in use. The migration user API token is provisioned with the permissions required for the Tickets, Users, Organizations, Tags, Help Center, and Attachments APIs.

3. ### Deactivate LiveAgent resolved-ticket notifications

   Before initiating any export, we access LiveAgent Configuration > Email > Customer and deactivate the 'Ticket resolved' email notification template.

   What this step covers

   This prevents LiveAgent from sending resolution emails to customers whose tickets are in the process of being re-imported into Zendesk. We verify the deactivation, document the change, and re-enable the template only after migration is complete and the customer has confirmed no notification spam was generated.

4. ### Demo migration and reconciliation

   We run a demo migration using a representative subset of the LiveAgent data — typically 100-200 tickets, 50 customers, and a sample of Knowledge Base articles — into a Zendesk sandbox or the production org with a test flag.

   What this step covers

   The customer reconciles the demo results against the source, checks field mapping accuracy, confirms that custom field values landed in the correct Zendesk fields, and verifies Knowledge Base article content and section hierarchy. Mapping corrections are applied before the production migration begins. This step typically runs over two to five business days.

5. ### Production migration in dependency order

   We run the production migration in the following order: Users (from LiveAgent Customers, with custom field values), Organizations (from LiveAgent Companies), Tags (created in Zendesk), Help Center articles (into Zendesk Guide sections), then Tickets (with Conversations mapped to Comments, and Attachments re-uploaded).

   What this step covers

   The LiveAgent API export is throttled to stay within the 180 req/min limit using request-level backoff and batch sizes of 100 records. Each phase emits a row-count reconciliation report before the next phase begins. During this window, LiveAgent continues handling live support; Zendesk is loaded in the background with no downtime on the source.

6. ### Cutover, validation, and automation inventory delivery

   We freeze writes in LiveAgent during the cutover window, run a final delta migration of any records created or modified during the migration window, then redirect support channels (email routing, chat widget, social channels) to Zendesk.

   What this step covers

   We validate ticket count reconciliation, spot-check 25-50 random ticket-comment pairs against the LiveAgent source, and confirm that Knowledge Base articles are accessible in Zendesk Guide. We deliver the Macros and Rules inventory document to the customer's admin team with Zendesk Trigger and Automation equivalents documented per rule. We provide a one-week hypercare window for reconciliation issues raised by the support team.

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

**2-4 weeks** Typical, smaller accounts

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

A quote scales with ticket volume, conversation density, custom field count, and Knowledge Base article size. Every quote is scoped with you; there is no self-serve pricing.

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

## Why teams move from LiveAgent to Zendesk

- LiveAgent's interface and onboarding draw consistent complaints on G2 and Capterra, with reviewers describing the control panel as dated and new agents taking weeks to become productive with ticket routing and rule configuration. Zendesk's out-of-the-box usability and intuitive agent interface allow teams to go live faster, which is a primary driver for teams migrating as their headcount scales.
- Zendesk's workflow automation — Triggers, Automations, and Macros — is fully accessible via the Admin API, meaning teams can export automation configurations, modify them programmatically, and rebuild them without manual recreation. LiveAgent's Macros and Rules are not exposed via the public REST API, forcing admins to rebuild every automation by hand when switching platforms. Zendesk's API-accessible automation model is a structural advantage for teams that rely heavily on routing rules.
- Zendesk's 700-2,000 req/min API rate limits on Suite Team through Enterprise far exceed LiveAgent's 180 req/min cloud cap. For teams running large historical migrations or integrating with downstream systems post-migration, the Zendesk API provides substantially more headroom for data throughput and real-time sync without the throttling constraints that limit LiveAgent export performance.
- Zendesk Guide provides a more structured and customizable Help Center experience compared to LiveAgent's built-in Knowledge Base. For teams migrating with extensive article histories, Zendesk's Guide supports Section hierarchies up to five levels deep, article versioning, and permission-based article visibility that integrates directly with Zendesk's permission sets and end-user authentication. CRM.org's comparison scores Zendesk higher on Knowledge Base and Learning (5/5 vs LiveAgent's 3/5).
- LiveAgent's plan-tier email address limits (the Small plan caps at three email addresses, forcing upgrades for additional channels) create pricing friction as teams grow. Zendesk's Suite plans include unlimited email addresses on every paid tier, removing the email channel ceiling. CRM.org's pricing comparison gives Zendesk the win on pricing flexibility, and multiple G2 reviewers cite plan scaling constraints as a pain point that pushed them toward platforms with more predictable per-agent pricing.

Questions, answered

## LiveAgent to Zendesk migration questions

How long does a LiveAgent to Zendesk migration take?

Migrations under 5,000 tickets with no custom objects and a straightforward status map land in two to four weeks. Migrations with extensive multi-year conversation history, more than 20 custom fields, or Knowledge Base articles exceeding 500 items move to four to eight weeks because of pagination overhead during the LiveAgent 180 req/min export, custom field schema creation in Zendesk, and Guide section hierarchy reconstruction. Discovery and demo migration account for the first one to two weeks regardless of volume.

Do LiveAgent Macros, Rules, and SLA policies migrate to Zendesk?

No. LiveAgent Macros and Rules are not exposed via the public REST API, and there is no automated export path for workflow automation logic. Zendesk's Triggers, Automations, and Macros are API-accessible, but the logic structures are not compatible for direct migration. We deliver a written inventory of every active LiveAgent Macro and Rule with its trigger conditions, actions, and a recommended Zendesk equivalent. The customer's admin rebuilds these in Zendesk Admin > Objects and Rules post-migration. SLA policies similarly do not migrate; we document the existing SLA tiers and response-time thresholds for manual reconfiguration in Zendesk Service Level Agreements.

What LiveAgent data do you migrate to Zendesk?

We migrate Tickets with full conversation history, Customers (contacts) with all custom field values, Companies (mapped to Zendesk Organizations), Tags, Knowledge Base categories, sections, and articles, and file attachments on tickets and conversations. We preserve the original LiveAgent ticket ID in a Zendesk custom ticket field for cross-reference after cutover. We do not migrate LiveAgent Macros, Rules, SLA configurations, or agent-based routing rules as these require manual rebuild in Zendesk.

Will there be downtime during the migration?

No required downtime. We run the migration in a staggered model: LiveAgent continues handling live support while historical data loads into Zendesk in the background. Only the final cutover step — redirecting email routing, chat widget, and social channels to Zendesk — requires a brief switchover window, typically under 30 minutes. During the migration window, new tickets created in LiveAgent are migrated as a delta after the bulk load is verified and before the cutover is finalized.

How do you handle LiveAgent's 180 req/min API rate limit during export?

We throttle our LiveAgent API export requests to stay within the 180 req/min cloud limit. We use paginated batch fetching (100 records per page), exponential backoff on any 429 responses, and sequential page traversal rather than concurrent requests. For large accounts (over 50,000 tickets), we run the export in off-peak hours to maximize batch throughput within the rate limit window. If we are migrating from a LiveAgent standalone installation, we configure the database override to raise or remove the rate limit before export begins.

Can you migrate our LiveAgent Knowledge Base to Zendesk Guide?

Yes. We migrate Knowledge Base categories, sections, and articles into Zendesk Guide. LiveAgent categories map to Zendesk Guide Sections with the article hierarchy preserved. Draft versus published status transfers to Zendesk article draft/published states. Note that Zendesk Guide must be activated as a product in the destination account before import; we configure Guide in setup mode and handle the permission structure during migration. If the LiveAgent Knowledge Base uses per-category access controls, these must be reimplemented as Zendesk Guide permission sets post-migration — we document the required steps during scoping.

What happens to our LiveAgent custom fields after migration?

We discover all LiveAgent Customer and Ticket custom fields dynamically via the API during scoping, create matching Zendesk custom fields (of equivalent type) in the destination org before import, and map the values during the Customer and Ticket import phases. Dropdown and multi-select custom fields require the LiveAgent picklist options to be mirrored as Zendesk tag or custom field options during the field creation step. Any LiveAgent custom fields that encode a related-data relationship (as opposed to a simple key-value) must be redesigned in Zendesk's Custom Objects schema; we identify these patterns during scoping and recommend the redesign before migration begins.

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

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