Troubleshooting Common LiveAgent Migration Pitfalls

After switching away from LiveAgent, many teams notice that something didn't carry over cleanly — tickets are missing, attachments won't open, agents can't see the right queues, or inbound email stops creating new records. The symptoms usually point to a handful of recurring causes. Below each cause is ordered by how often it appears, with a quick way to confirm the problem and a practical fix.

1. Incomplete ticket export

How to confirm – Compare the total ticket count in LiveAgent with the number of records that appear in the new system. Check the export log for errors or truncated batches. How to fix – Re‑run the export using the full date range and all status filters (open, closed, pending). If you used the UI export, try the API endpoint for a complete dump. The How to Export Tickets from LiveAgent guide shows the exact steps. Verify the CSV or JSON file line count before importing again.

2. Attachment loss or corruption

How to confirm – Open a sample of migrated tickets and try to download each attachment. Look for zero‑byte files or mismatched file names. How to fix – Export attachments separately from LiveAgent (often a separate ZIP). Ensure the target platform’s storage limits allow the total size. Re‑import the attachment archive and link files to their parent tickets by matching the ticket IDs.

3. User and role mapping errors

How to confirm – Agents report missing queues, inability to assign tickets, or permission errors when replying. How to fix – Build a mapping table before migration: LiveAgent role → new system role. Apply the mapping during the user import, then run a permission audit. Adjust any custom roles that have no direct equivalent.

4. Email routing and auto‑reply failures

How to confirm – Send a test email to the support address. If it doesn’t appear as a ticket, check the forwarding rule in LiveAgent and the MX records for the domain. How to fix – Update the forwarding address to the new help desk’s inbound email. Disable the old LiveAgent forwarding rule. Verify SPF/DKIM settings for the new address. The troubleshooting article on Why Incoming Emails Aren’t Creating Tickets covers the DNS steps in detail.

5. Custom fields and tags not transferred

How to confirm – Open migrated tickets and look for empty custom‑field values or missing tags that were used for routing. How to fix – Export the custom‑field definitions and tag list from LiveAgent. Recreate them in the new platform with identical names and data types. During the ticket import, map each field by its API name. A Data Migration Checklist for Switching Help Desk Platforms can help you track every field.

6. Workflow and automation breakage

How to confirm – Rules that previously auto‑assigned, escalated, or sent notifications no longer fire. How to fix – Document each LiveAgent rule (conditions, actions). Recreate them in the new system one by one, testing with a sandbox ticket after each. Pay special attention to time‑based triggers that may use a different scheduler syntax.

7. Data format mismatches (date, encoding)

How to confirm – Dates appear as raw timestamps, special characters show as garbled text, or numeric fields contain commas instead of periods. How to fix – Ensure the export file is UTF‑8 encoded. Convert date columns to ISO‑8601 (YYYY‑MM‑DDTHH:MM:SSZ) before import. Use a script or spreadsheet find‑and‑replace to normalise number formats.

What to do if nothing worked

If you have verified each of the above and the migration still leaves gaps, run a small‑scale test migration with a single department or a date‑range slice. Compare the results line by line. Engage the new platform’s support team with the exact error logs. Consider a phased cut‑over: keep LiveAgent read‑only for a week while the new system handles live traffic. If the current tool still feels too costly or complex, a free alternative such as NeuraDesk can replace LiveAgent without per‑agent fees — try NeuraDesk free.