A LiveAgent to Zendesk migration requires API v3 extraction, Zendesk's Ticket Import API to preserve history, and manual rebuild of automations and SLAs. CSV export loses threads.
Step-by-step guide to migrating from LiveAgent to Zendesk. Covers API rate limits, data mapping, status translation, thread preservation, and known limitations.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
TL;DR: LiveAgent to Zendesk Migration
A LiveAgent to Zendesk migration is moderate to high complexity and typically takes 1 to 3 weeks depending on ticket volume, attachment size, and custom field depth. The single biggest risk is losing conversation thread history: LiveAgent's built-in CSV export captures ticket metadata but not full message threads, internal notes, or inline attachments. You must use LiveAgent API v3 (GET /tickets/{ticketId}/messages) and Zendesk's Ticket Import API (/api/v2/imports/tickets) to preserve original timestamps and full conversation threads. LiveAgent's 7+ ticket statuses must be collapsed into Zendesk's 6 statuses, and LiveAgent Departments must be manually mapped to Zendesk Groups. Automation Rules, SLA Rules, Canned Messages, and Predefined Answers cannot be migrated programmatically and must be rebuilt in Zendesk. Teams with fewer than 5,000 tickets and simple custom fields can self-serve with API scripting. For anything larger or compliance-sensitive, a managed migration service is the safer path.
Status mapping is a business decision, not a technical one
The engineering team can implement any mapping, but the customer success team must decide what "Answered" means in Zendesk's lifecycle. Get sign-off before writing a single line of code. If no clean mapping exists, store the original LiveAgent status in a dedicated custom text field for reference. (support.liveagent.com)
Throughput optimization
Use multiple API keys if your plan supports it, or batch your extraction by date range to parallelize safely. For the initial backfill, use date_created windows. For delta passes, use date_changed.
LiveAgent 5.62 note handling change
Since LiveAgent version 5.62, note handling changed and note group IDs can be UUID strings instead of integers. Parsers that assume old note types or integer IDs will silently corrupt history. Test with tickets that contain both old and new internal note patterns before the full run (support.liveagent.com).
Help Center API traffic uses a separate rate limit budget from Support API traffic
If you are moving tickets and Zendesk Guide content in parallel, these two workloads will not compete for the same rate limit quota.
Duplicate customers
LiveAgent allows multiple customer records with the same email address. Zendesk does not. Your transformation layer must deduplicate customers by email before import, or the Zendesk API will create merge conflicts. Decide a merge strategy upfront: keep the most recently active record, merge custom field values, or flag for manual review.
Tag imported tickets
Add a tag like liveagent-import to all imported tickets and exclude them from SLA reports and metrics. Imported tickets generate incomplete SLA data and should not skew your active reporting.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of LiveAgent
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm Zendesk can hold your support model
Walk your current workflow through Zendesk: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated LiveAgent → Zendesk timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
LiveAgent → Zendesk specifics
- Integration ecosystem
- Zendesk's marketplace lists over 1,500 pre-built integrations compared to LiveAgent's approximately 40 native integrations. Teams outgrow LiveAgent when they need deeper connections to CRMs, BI tools, and developer platforms.
- Advanced automation and AI
- Zendesk offers Intelligent Triage, AI Agents, and a mature trigger/automation engine that LiveAgent's Rules system cannot match at scale.
- Enterprise compliance and reporting
- Zendesk provides HIPAA-eligible configurations, SOC 2 Type II compliance, Explore analytics, and a sandbox environment for testing changes before production. LiveAgent's reporting is functional but less flexible for enterprise audit requirements.
- DIY API scripting
- Engineering time only (80–160 hours at your loaded engineer cost). No external fees, but opportunity cost of pulling an engineer off product work.
- Third-party self-serve tools (e.g., Help Desk Migration)
- Record-based pricing. Typical cost ranges from $1 to $3 per 100 records for tickets. Attachments and comments usually do not increase cost. A 50,000-ticket migration typically costs $500–$1,500 for the tool license.
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full LiveAgent export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the LiveAgent export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in LiveAgent where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
LiveAgent → Zendesk specifics
- LiveAgent Departments
- handle both agent assignment and SLA routing in one object. In Zendesk, you split this into Groups (for assignment) and SLA Policies (for response time rules).
- Predefined Answers and Canned Messages
- are exportable via LiveAgent API v3 but cannot be imported into Zendesk via API. They must be recreated manually as Macros.
- Call recordings
- stored in LiveAgent cannot be attached to Zendesk tickets natively. Store them in external storage (S3, Google Cloud Storage) and reference them via a custom URL field.
- LiveAgent forums, topics, and suggestion categories
- do not have a clean first-class destination in Zendesk Guide. Archive them, remodel them as articles, or move them to a community product outside Guide (support.liveagent.com).
- Gamification data
- (badges, levels, rewards) does not transfer.
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass LiveAgent → Zendesk field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the LiveAgent → Zendesk field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where Zendesk has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a Zendesk sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Zendesk sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under Zendesk's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in Zendesk, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while LiveAgent stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from Zendesk's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze LiveAgent and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep LiveAgent read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile LiveAgent and Zendesk record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in Zendesk, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep LiveAgent read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
How Do LiveAgent Objects Map Zendesk Objects
| LiveAgent field | Zendesk field | Notes |
|---|---|---|
| Ticket | Ticket | Use Ticket Import API to preserve created_at, updated_at, and solved_at timestamps (developer.zendesk.com) |
| Message (public) | Comment (public) | Preserve author_id and original timestamp on each comment |
| Message (internal note) | Comment (public: false) | Set public: false in imported comments |
| Customer | User (role: end-user) | Match on email. Zendesk requires unique email addresses for all users |
| Agent | User (role: agent/admin) | Create agents before importing tickets to maintain assignment history. If you set assignee_id, Zendesk also requires a group_id on the ticket |
| Company | Organization | Cleanest 1:1 mapping. LiveAgent assigns each contact to one company; Zendesk users have one organization_id (support.liveagent.com) |
| Department | Group | Both are internal routing structures. Departments in LiveAgent also control SLA routing; in Zendesk, you need separate SLA Policies |
| Tag | Tag | Direct mapping. LiveAgent tags have colors (not supported in Zendesk) |
| Custom Field (ticket) | Custom Ticket Field | Recreate fields in Zendesk first. Dropdown fields must match exact tag values or the import fails |
| Custom Field (contact) | Custom User Field | Create in Zendesk before import. Normalize list values before load |
| Knowledge Base Article | Help Center Article | Requires Zendesk Guide. Inline images must be downloaded and rehosted. No native import tool for HTML content |
| Canned Messages / Predefined Answers | Macros | Cannot be migrated via API. Content can be ported; IDs and permissions cannot |
| Rules (automation) | Triggers / Automations | Cannot be migrated. Must be rebuilt in Zendesk |
| SLA Rules | SLA Policies | Cannot be migrated. Historical SLA metrics on imported tickets are not supported |
| Attachments / Files | Attachments | Must be downloaded from LiveAgent and re-uploaded to Zendesk via Upload API |
| Call Recordings | Not natively supported | Store externally and link via custom fields or tags |
| Chat Transcripts | Ticket Comments | Import as comments on the parent ticket with original timestamps |
| Contact Group | User tag or org tag | No first-class equivalent in Zendesk (support.liveagent.com) |
| Complex custom data structures | Sunshine Custom Objects | For teams with relational or multi-entity custom data that exceeds what custom fields can represent, Zendesk Sunshine Custom Objects provide a structured alternative (developer.zendesk.com) |
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
How long does a LiveAgent to Zendesk migration take?
A LiveAgent to Zendesk migration typically takes 1 to 3 weeks from planning to go-live. The data transfer itself can complete in hours to days depending on volume, but planning, field mapping, and validation consume the majority of the timeline. Teams with fewer than 10,000 tickets can often complete the full process in 5 to 7 business days.
Can I migrate LiveAgent to Zendesk without losing data?
Yes, if you use the LiveAgent API v3 for extraction and Zendesk's Ticket Import API for loading. The Ticket Import API preserves original timestamps (created_at, updated_at, solved_at) and supports multiple comments per ticket. The native CSV export does not preserve full message threads and will result in data loss. Canned Messages, Rules, and SLA configurations cannot be migrated and must be rebuilt manually.
Does Zendesk preserve ticket IDs from LiveAgent?
No. Zendesk assigns new ticket IDs during import. There is no way to set or preserve the original LiveAgent ticket ID. Store the LiveAgent ticket code in external_id or a dedicated custom text field on the Zendesk ticket so agents can search for it.
What data cannot be migrated from LiveAgent to Zendesk?
LiveAgent Rules, Time Rules, SLA Rules, Predefined Answers, and Canned Messages cannot be exported as working Zendesk objects. They must be rebuilt manually as Triggers, Automations, Macros, and SLA Policies. Call recordings, gamification data, IVR routing, and forum-style KB content also have no direct equivalent in Zendesk.
What is the LiveAgent API rate limit?
LiveAgent enforces a rate limit of 180 requests per minute per API key on cloud accounts. This limit cannot be increased on cloud-hosted instances. Standalone self-hosted installations can override this limit in server configuration. The /tickets endpoint also caps filter results at 10,000 records per query, requiring date-windowed extraction for large datasets.