Migrate your LiveChat data
AI-powered live chat and help desk platform for B2B SaaS and ecommerce teams. Agents handle real-time conversations, chatbots automate tier-1 queries, and integrations connect to the broader sales and support stack.
In its favor
Why people choose LiveChat
The signal that keeps LiveChat on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Generous free trial with no credit card required lets teams validate the platform against their actual chat volume before committing to a paid seat.
Agent-focused UI provides real-time visibility into visitor location, system, and typing-preview before messages are sent, making support teams faster.
Chat-to-ticket conversion and message forwarding workflows are reliable out of the box with minimal configuration for teams handling mixed sales and support queues.
Integrates with the broader Text product family including ChatBot and HelpDesk, allowing teams to layer in automation without changing vendors.
Over 76,000 companies use the platform, indicating stable infrastructure and an established ecosystem of third-party integrations.
Pricing scales per agent, and as teams grow, costs increase linearly with headcount rather than conversation volume, making it expensive for large support organizations.
Feature gaps compared to all-in-one platforms: no native AI phone support, limited native CRM depth, and teams that need omnichannel coverage find themselves piecing together multiple Text products.
Starter plan limits to one user, forcing teams to upgrade to Business immediately even for small pilot deployments, which creates friction during evaluation.
Notification sounds and minor UI polish items are flagged in long-term reviews as areas where the product has not kept pace with competitors.
Teams that scale past 50 agents report the platform becomes harder to manage without third-party tools for advanced routing and workload balancing.
Reasons to switch
Why people leave LiveChat
The recurring reasons buyers give for replacing LiveChat. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where LiveChat fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
LiveChat pricing overview
LiveChat uses a per-agent seat model with pricing from $0 to $79 per user per month. The Starter plan is free but limited to one agent, while the Business plan at $79 per agent adds AI features and advanced analytics. Enterprise pricing is custom-negotiated with volume discounts available.
Starter
Tier 1 of 4
$0/user/month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on LiveChat's schedule — see our quote-based pricing →
What gets migrated
LiveChat object support
Object-by-object support for LiveChat migrations. Per-pair details surface during scoping.
Chats
Fully supportedChats are the primary conversation object in LiveChat. We export full chat threads including messages, timestamps, and system events. When importing into Zendesk, Intercom, or similar, we map each chat to a ticket and preserve the message ordering.
Agents
Fully supportedAgents are the seat-based user accounts. We migrate agents 1:1 and preserve their display names, email addresses, and role assignments. Agent-to-user mapping is direct in most destination platforms.
Requesters
Fully supportedRequesters are the customers initiating conversations. We map them to contacts or users in the destination platform, preserving email, name, and any custom requester-level properties.
Tags
Mapping requiredLiveChat tags are applied at the chat level. We migrate tags as labels or ticket tags in the destination. Some platforms limit tag character length or character set, which we handle with normalization.
Custom Fields
Mapping requiredCustom fields exist on both chats and requesters. We export the full field schema and map values to equivalent custom fields in the destination, creating them if the destination supports custom field creation.
Canned Responses
Mapping requiredCanned responses are templates stored at the workspace level. We migrate them as saved replies or snippets where supported, but the migration is not 1:1 as naming conventions and variable syntax differ between platforms.
Chat Ratings
Mapping requiredChat ratings (CSAT scores) are attached to individual chats. We map them to the destination's satisfaction rating field if available, otherwise we flag them for manual record-keeping post-migration.
Integrations Configuration
Not in this platformLiveChat integrations (e.g., Slack, Salesforce, Shopify connectors) are configuration-bound and do not have a portable data format. We document the integration list and recommend re-configuring them in the destination platform post-migration.
Knowledge Base
Mapping requiredLiveChat's built-in Help Center articles can be exported and mapped to the destination's KB or article system. We handle article body HTML, titles, and slugs, but complex nesting structures may require manual reorganization.
Reports and Analytics
Not in this platformAnalytics and reporting data are computed summaries, not raw records. We do not migrate analytics. We recommend exporting screenshots or PDF reports pre-migration for historical reference.
Automated Rules and Workflows
Mapping requiredLiveChat's automated rules trigger based on chat events. We document rule logic in text and map it to equivalent automation logic in the destination where the platform supports rule-builder migration.
Groups and Departments
Fully supportedGroups or departments assign agents to functional teams. We migrate these as teams or groups in the destination platform and update agent assignments accordingly.
| Object | Support | Notes |
|---|---|---|
| Chats | Fully supported | Chats are the primary conversation object in LiveChat. We export full chat threads including messages, timestamps, and system events. When importing into Zendesk, Intercom, or similar, we map each chat to a ticket and preserve the message ordering. |
| Agents | Fully supported | Agents are the seat-based user accounts. We migrate agents 1:1 and preserve their display names, email addresses, and role assignments. Agent-to-user mapping is direct in most destination platforms. |
| Requesters | Fully supported | Requesters are the customers initiating conversations. We map them to contacts or users in the destination platform, preserving email, name, and any custom requester-level properties. |
| Tags | Mapping required | LiveChat tags are applied at the chat level. We migrate tags as labels or ticket tags in the destination. Some platforms limit tag character length or character set, which we handle with normalization. |
| Custom Fields | Mapping required | Custom fields exist on both chats and requesters. We export the full field schema and map values to equivalent custom fields in the destination, creating them if the destination supports custom field creation. |
| Canned Responses | Mapping required | Canned responses are templates stored at the workspace level. We migrate them as saved replies or snippets where supported, but the migration is not 1:1 as naming conventions and variable syntax differ between platforms. |
| Chat Ratings | Mapping required | Chat ratings (CSAT scores) are attached to individual chats. We map them to the destination's satisfaction rating field if available, otherwise we flag them for manual record-keeping post-migration. |
| Integrations Configuration | Not in this platform | LiveChat integrations (e.g., Slack, Salesforce, Shopify connectors) are configuration-bound and do not have a portable data format. We document the integration list and recommend re-configuring them in the destination platform post-migration. |
| Knowledge Base | Mapping required | LiveChat's built-in Help Center articles can be exported and mapped to the destination's KB or article system. We handle article body HTML, titles, and slugs, but complex nesting structures may require manual reorganization. |
| Reports and Analytics | Not in this platform | Analytics and reporting data are computed summaries, not raw records. We do not migrate analytics. We recommend exporting screenshots or PDF reports pre-migration for historical reference. |
| Automated Rules and Workflows | Mapping required | LiveChat's automated rules trigger based on chat events. We document rule logic in text and map it to equivalent automation logic in the destination where the platform supports rule-builder migration. |
| Groups and Departments | Fully supported | Groups or departments assign agents to functional teams. We migrate these as teams or groups in the destination platform and update agent assignments accordingly. |
Gotchas
What to watch for in LiveChat migrations
Issues we've hit on past LiveChat migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Chats Exporter app required for bulk export
Seat-based billing creates migration cost surprises
API rate limits throttle large migrations
Custom field schema is per-widget, not global
Ongoing chats auto-close on reconnect failure
| Severity | Issue |
|---|---|
| High | Chats Exporter app required for bulk export |
| High | Seat-based billing creates migration cost surprises |
| Medium | API rate limits throttle large migrations |
| Medium | Custom field schema is per-widget, not global |
| Low | Ongoing chats auto-close on reconnect failure |
Leaving LiveChat?
Where LiveChat customers move next
7 destinations LiveChat can migrate to.
How a LiveChat migration works
Four steps, LiveChat-specific
Connect
OAuth 2.1 across all Text Platform / LiveChat services. Personal Access Tokens (PATs) are supported for agent authentication and individual scripts. OAuth 2.0 Bearer tokens are issued at https://accounts.livechat.com/v2/token. Scopes such as agents--all:rw / agents--all:ro must be declared at app registration in the LiveChat Developer Console. into LiveChat. Scopes limited to read-only on the data we move.
Map
We translate LiveChat-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate LiveChat quirks before production.
Migrate
Full migration with LiveChat rate-limit handling. Rollback available throughout.
FAQ
LiveChat migration FAQ
Answers to the questions buyers ask most during LiveChat migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your LiveChat migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate LiveChat.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your LiveChat setup and destination — written quote back within a business day.