Migrate from LiveChat to HubSpot Service Hub

LiveChat Chats map to HubSpot Tickets as the primary case record. Each chat thread becomes a Ticket with the full message history (agent and visitor messages) written to the HubSpot conversation timeline using the Conversations API or ticket property updates. Chat start time, end time, and duration migrate as ticket properties. The chat thread structure (ordered messages with timestamps) maps to HubSpot's conversation feed, which displays chronologically within the ticket record.

LiveChat chat status values (active, pending, resolved, closed) map to HubSpot Ticket status values (open, pending, closed). If the customer uses LiveChat chat rating (CSAT) attached to the chat, the score migrates to a HubSpot custom ticket property. HubSpot ticket pipelines and stages are configured before migration to mirror the LiveChat chat department or team assignment if the customer uses multiple queues.

LiveChat Requesters (chat-initiating customers) map to HubSpot Contacts. Email address is the primary dedupe key. Requester display name maps to HubSpot firstname/lastname or full name fields, and any requester-level custom properties migrate to HubSpot Contact custom properties. Requester session data (location, browser, referring page) migrates as custom properties if the customer wants to preserve visitor context on the Contact record.

LiveChat Agents map to HubSpot Users. We resolve agents by email address and preserve display name, role (admin, agent), and group membership. Groups or departments in LiveChat map to HubSpot Teams. HubSpot User provisioning requires the customer to assign appropriate Service Hub seat types (Full or Light) during migration; we flag the recommended seat type per agent based on their LiveChat role.

LiveChat chat tags migrate to HubSpot Ticket tags. HubSpot allows multiple tags per ticket with alphanumeric character support. We normalize any LiveChat tags that contain characters unsupported in HubSpot (special characters, spaces) before import. Tags used for routing or department assignment in LiveChat also map to a HubSpot Teams field if the customer wants to preserve team context post-migration.

LiveChat custom fields attached to chats migrate as HubSpot custom ticket properties. HubSpot requires these properties to be created in the portal before migration; we include schema creation in the discovery phase. If the customer uses multiple chat widgets with overlapping field names but different internal IDs (a known LiveChat per-widget field behavior), we consolidate duplicates into a single HubSpot property and document the widget-source mapping for the customer.

LiveChat custom fields attached to requester records migrate as HubSpot Contact custom properties. Same consolidation logic applies for multi-widget duplicate fields. These properties are visible on the Contact record and appear in HubSpot contact lists, workflows, and reporting filters.

LiveChat canned responses (message templates stored at the workspace level) do not have a native HubSpot Service Hub equivalent. HubSpot does not ship a saved reply library for tickets. We export the canned response body, shortcut code, and category, and deliver them as a structured document the customer's admin can import into a third-party tool (Snippets app from the HubSpot App Marketplace) or recreate manually in HubSpot's UI.

LiveChat chat ratings (1-5 star or thumbs up/down) attached to individual chats migrate to HubSpot Customer Satisfaction Survey responses on the ticket. HubSpot's native CSAT survey sends a post-ticket email; migrated ratings land as historical data points on the ticket record. If the customer used custom rating scales in LiveChat, we normalize to HubSpot's 1-5 numeric scale.

LiveChat Groups (agent teams assigned to functional queues) map to HubSpot Teams. Agent-to-team membership migrates as part of the User mapping. HubSpot Teams control ticket assignment routing, inbox visibility, and reporting segmentation. We configure Teams during the HubSpot schema setup phase before ticket import begins.

LiveChat's KnowledgeBase articles export as HTML bodies with titles and slugs. We migrate them to HubSpot's Knowledge Base on Professional and above. Article categories and sections map to HubSpot article categories. HubSpot Knowledge Base articles can be attached to tickets as help links; we document this linking strategy during scoping. Complex nested category hierarchies may require manual restructuring post-migration.

LiveChat automated rules (triggered by chat events such as new chat, visitor info, or tag change) do not migrate as automation code to HubSpot. We document every active rule with its trigger condition, conditions, and actions in a written inventory delivered to the customer's admin. The admin rebuilds equivalent logic in HubSpot's Workflows using ticket properties, contact properties, or conversation events as triggers.