Freshservice to LiveChat is a model conversion, not a copy job. Flatten ITSM data into chat structures, archive what has no LiveChat equivalent, and validate at every step.
Migrating from Freshservice to LiveChat is a data-model conversion, not a simple data copy. Freshservice is a full ITSM platform organized around hierarchical objects — tickets, problems, changes, assets, and service catalogs — while LiveChat uses a flat schema built around customers, chats, threads, and events, with no native equivalents for most ITSM constructs. There is no first-party migration wizard between these platforms, meaning all migration paths require custom extraction, schema flattening, and programmatic loading via the LiveChat Configuration API and Agent Chat API. ITSM-specific data such as assets, change records, problems, releases, and service catalog items have no destination in LiveChat and must be archived, discarded, or routed to a companion product such as HelpDesk.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
LiveChat's native ticketing system has been sunsetted
If you need ticket management alongside chat, you will need HelpDesk (a separate Text platform product) integrated with LiveChat. If your end state still requires long-lived tickets, async case work, and knowledge workflows, design your migration target as LiveChat + HelpDesk — not LiveChat alone. See the HelpDesk integration section below for detailed mapping guidance.
LiveChat's API expects specific JSON structures for thread events
If you push a Freshservice reply without the correct author ID mapped to an existing LiveChat agent or customer, LiveChat will attribute the message to the API service account — ruining historical context. Build and validate your author ID lookup table before loading any events.
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 Freshservice
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 LiveChat can hold your support model
Walk your current workflow through LiveChat: 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 Freshservice → LiveChat 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.
-
Record count comparison
Total tickets in Freshservice vs. total chats in LiveChat. Zero tolerance for discrepancy.
Freshservice → LiveChat specifics
- Channel pivot
- The team is moving from ticket-based IT support to real-time, chat-first customer engagement — typically during a business model shift toward e-commerce or SaaS.
- Cost reduction
- Freshservice's ITSM feature set (asset management, CMDB, change management) is overkill for teams that only need chat and basic ticketing.
- Platform consolidation
- The team is standardizing on the Text platform ecosystem (LiveChat + HelpDesk + ChatBot + Knowledge Base) and wants all customer interactions in one vendor stack.
- Simplicity
- LiveChat's learning curve is significantly lower than Freshservice. Teams without dedicated IT admins often prefer the simpler interface.
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 Freshservice 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 Freshservice 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 Freshservice 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
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 Freshservice → LiveChat 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 Freshservice → LiveChat 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 LiveChat 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 LiveChat sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a LiveChat 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 LiveChat'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 LiveChat, 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 Freshservice 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 LiveChat'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 Freshservice 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 Freshservice read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
-
Keep Freshservice in read-only mode
during migration — not decommissioned. You need a fallback.
Freshservice → LiveChat specifics
- Customer deduplication
- Confirm no duplicate customer records in LiveChat (query by email).
- Agent assignment
- Verify agents are correctly associated with migrated chats and messages are attributed to the right agent.
- Group routing
- Verify migrated chats are assigned to the correct LiveChat groups.
- Private notes (if using HelpDesk)
- Confirm internal notes appear as private notes in HelpDesk tickets, not as public messages.
- Maintain a mapping log
- (Freshservice ticket ID → LiveChat chat ID → LiveChat customer ID) so you can identify and clean up migrated records if needed.
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 Freshservice and LiveChat 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 LiveChat, 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 Freshservice 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.
-
Record counts
Compare total tickets extracted from Freshservice against total chats created in LiveChat. Tolerance: 0% for customers, 0% for chats, <1% for individual events (some events may be skipped due to unresolvable authors).
Freshservice → LiveChat specifics
- Conversation integrity
- Sample 5–10% of records (minimum 50 records). Verify conversation content, timestamps, and customer associations. Compare the first and last message text of each sampled ticket against the corresponding LiveChat chat.
- Author attribution
- For each sampled record, verify that messages are attributed to the correct agent or customer — not the API service account.
- Tag accuracy
- Confirm Freshservice statuses and priorities appear correctly as LiveChat tags.
- Orphaned records
- Check for customers without chats and chats without events.
- Attachment spot-check
- Open 10–20 attachments in LiveChat and confirm they render correctly. Verify no expired S3 URLs remain in message bodies.
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.
Object Equivalent
| Freshservice field | LiveChat field | Notes |
|---|---|---|
| Ticket | Chat + Thread(s) | Each ticket becomes a chat. Conversations become thread events. |
| Requester | Customer | Map email, name, phone. Custom requester fields → customer properties. |
| Agent | Agent | Recreate agents manually or via Configuration API. |
| Agent Group / Department | Group | 1:1 mapping. |
| Ticket Tags | Tags | Direct mapping. |
| Ticket Priority | Tag (e.g., priority:high) | LiveChat has no native priority field on chats. |
| Ticket Status | Tag (e.g., status:resolved) + thread state | LiveChat threads are active or inactive. Map statuses to tags. |
| Ticket Category | Tag | Flatten category hierarchy into prefixed tags (e.g., cat:hardware, subcat:laptop). |
| Conversations (replies) | Thread events (messages) | Preserve sender, timestamp, and body. |
| Internal Notes | System messages or HelpDesk private notes | LiveChat standard chat events have no private flag. Use HelpDesk if you need internal notes. |
| Attachments | File events in threads | Must be re-uploaded; Freshservice attachment URLs are temporary. |
| Assets | ❌ No equivalent | Archive to CSV or external CMDB. |
| Problems | ❌ No equivalent | Archive separately. |
| Changes | ❌ No equivalent | Archive separately. |
| Releases | ❌ No equivalent | Archive separately. |
| Knowledge Base | ❌ (Separate product) | Requires Text platform's Knowledge Base product. |
| Custom Objects | Properties (key-value) | Flatten custom object fields into customer or chat properties. Complex relationships will be lost. |
Object Destination
| Freshservice field | LiveChat field | Notes |
|---|---|---|
| Ticket (chat-originated) | LiveChat Chat + HelpDesk Ticket | Chat handles the real-time record; HelpDesk ticket handles async follow-up |
| Ticket (email-originated) | HelpDesk Ticket only | No LiveChat chat needed |
| Internal Notes | HelpDesk private notes | HelpDesk supports internal notes natively |
| SLA Policies | HelpDesk SLA rules | HelpDesk offers basic SLA: first response time, resolution time |
| Ticket Status | HelpDesk ticket status | HelpDesk supports: new, open, pending, on-hold, solved, closed |
| Canned Responses | HelpDesk canned responses + LiveChat canned responses | Split by channel |
# Freshservice
| Freshservice field | LiveChat field | Notes |
|---|---|---|
| 1 | ticket.id | Cast to string |
| 2 | ticket.subject | Prepend to description |
| 3 | ticket.description_text | Direct (use description_text, not description) |
| 4 | ticket.status | Map: 2→open, 3→pending, 4→resolved, 5→closed |
| 5 | ticket.priority | Map: 1→low, 2→medium, 3→high, 4→urgent |
| 6 | ticket.source | Map: 1→email, 2→portal, 3→phone, 7→chat, 9→feedback_widget |
| 7 | ticket.created_at | Direct (timezone-aware) |
| 8 | ticket.tags | Direct |
| 9 | requester.email | Direct (deduplication key) |
| 10 | requester.name | Direct |
| 11 | requester.phone | Direct |
| 12 | conversation.body_text | Strip HTML if using body field |
| 13 | conversation.from_email | Resolve to LiveChat agent or customer ID via lookup table |
| 14 | conversation.created_at | Direct |
| 15 | conversation.private | Route to HelpDesk API; do not load as LiveChat event |
| 16 | ticket.custom_fields.* | Flatten; cast all values to string; prefix with cf_ |
| 17 | department | Map via lookup table (Freshservice dept ID → LiveChat group ID) |
| 18 | asset_id | Append as text reference; no structural link in LiveChat |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets | medium | Ticket metadata (subject, status, priority, timestamps) can be mapped to LiveChat chat properties, but the conversion is lossy because LiveChat's chat model does not support ticket-lifecycle states such as pending, resolved, or escalated natively. |
| Ticket Conversations | high | Conversation threads must be flattened into LiveChat thread events with correct chronological ordering, and interleaved private notes have no LiveChat equivalent, creating structural gaps that distort the apparent conversation flow. |
| Requesters / Contacts | medium | Freshservice permits multiple requester records sharing the same email address, so deduplication by email is required before loading into LiveChat, which enforces email as the unique customer identifier. |
| Agents | low | Agent records map cleanly by email address to LiveChat agents, provided all agents are pre-created in LiveChat before migration and an email-to-ID lookup table is validated prior to loading any events. |
| Groups / Departments | medium | Freshservice department and group IDs do not map directly to LiveChat group IDs, requiring all LiveChat groups to be created in advance and a cross-system ID lookup table to be built and validated before migrating any chat records. |
| Tags and Categories | medium | Freshservice's three-level category hierarchy (category, subcategory, item category) must be collapsed into LiveChat's flat tag structure, which may require a taxonomy consolidation decision that cannot be automated without business input. |
| Custom Fields | high | Freshservice custom fields support rich types and hierarchical object associations, while LiveChat supports only flat key-value property pairs, meaning complex custom field structures will require schema redesign and partial data loss. |
| Assets and CMDB | high | Freshservice's asset and CMDB data has no structural equivalent in LiveChat and will be entirely unmigratable to the target platform without routing to an external system or archiving outside the migration scope. |
| Knowledge Base Articles | high | LiveChat has no native knowledge base module, so Freshservice knowledge base articles require migration to a separate Text platform Knowledge Base product or a third-party system, which is outside the scope of a LiveChat-only migration. |
| Attachments | medium | Freshservice attachment URLs are temporary and will expire before loading completes unless all binary files are explicitly downloaded and re-hosted during the extraction phase of the migration pipeline. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Hierarchical Schema Flattening
Freshservice's deep object hierarchy (Department → Requester → Ticket → Asset → Change) must be collapsed into LiveChat's flat structure (Group → Customer → Chat/Thread/Event) without losing historical context or relationship integrity.
No Bulk Import API
LiveChat provides no bulk import endpoint, requiring every chat, thread, and event record to be created individually via API, making large-scale migrations slow and rate-limit-sensitive.
Author Attribution Resolution
Freshservice conversation author email addresses must be resolved to valid LiveChat agent or customer IDs before loading events, or all unresolved messages will be attributed to the API service account.
ITSM Data Has No Target
Freshservice-native objects including assets, change records, problem records, releases, and service catalog items have no structural equivalent in LiveChat and require separate archival or routing decisions before migration begins.
Pagination and Volume Limits
Freshservice's REST API silently stops returning results after page 500 (approximately 50,000 records), requiring date-range windowing with the updated_since filter to avoid silent data loss on large datasets.
Attachment URL Expiry
Freshservice attachment URLs are temporary authenticated S3 links that expire, requiring all binary attachments to be downloaded and re-hosted during the extraction phase rather than stored as URL references.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate Freshservice tickets to LiveChat?
Yes, but with significant caveats. Freshservice tickets map to LiveChat chats containing threads and events. Ticket metadata like priority and status must be converted to tags, since LiveChat has no native priority or multi-status fields. Conversations become thread events. ITSM-specific data like assets, changes, and problems has no LiveChat equivalent and must be archived separately. LiveChat's native ticketing has been sunsetted, so if you need async ticket management alongside chat, plan for HelpDesk integration.
What are the Freshservice API rate limits for data migration?
Freshservice rate limits vary by plan: Starter gets 100 requests/minute, Growth gets 200, Pro gets 400, and Enterprise gets 500. These are account-wide limits — even failed requests count. Freshservice also offers a partner-oriented migration process that can raise limits to 700 requests/minute for approved windows. Deep pagination is capped at page 500, so large datasets require date-range windowing with the updated_since parameter.
Does LiveChat have a bulk import API for migration?
No. LiveChat does not offer a bulk import API. Records must be created individually via the Configuration API (for customers, agents, groups) and Agent Chat API (for chats and events). The rate limit is approximately 1,000 requests per 10-minute window per license, which means large migrations require hours of sustained API calls.
What Freshservice data cannot be migrated to LiveChat?
LiveChat has no equivalent for Freshservice assets/CMDB, change management records, problem management records, releases, service catalog items, SLA policies, approval workflows, or time tracking. This data must be archived to CSV, a data warehouse, or a separate tool. Knowledge base articles require the separate Text platform Knowledge Base product.
How long does a Freshservice to LiveChat migration take?
It depends on volume. A small migration (under 1,000 tickets) can be done in a day. For 10,000–50,000 tickets with conversations, expect 3–5 days including extraction, transformation, loading, and validation. Enterprise migrations (50K+ tickets) may take 1–2 weeks. API rate limits on both platforms are the primary bottleneck.