Migrate from LimeChat to HubSpot Service Hub

LimeChat WhatsApp conversation threads map to HubSpot Service Hub Tickets. Each thread's message metadata, customer identifiers, agent attribution, and timestamps migrate as Ticket properties and internal notes. WhatsApp-specific message types (template messages, interactive buttons) are preserved as plain-text notes since HubSpot Tickets do not render WhatsApp native message components. We set the Ticket subject from the conversation's first message or a synthetic subject derived from the customer name and thread timestamp.

LimeChat customer profiles map to HubSpot CRM Contacts. We preserve WhatsApp identifiers (phone number in E.164 format) in a custom contact property whatsapp_phone__c so that if the customer later reconnects WhatsApp via HubSpot's native WhatsApp integration, the identifier is available for re-linkage. Contact custom fields migrate as HubSpot contact properties with type mapping (text to single-line text, number to number, date to date).

LimeChat WhatsApp marketing campaigns map to HubSpot CRM Campaigns. Campaign targeting rules, audience segments, and message template content migrate as Campaign properties and Campaign Member status records. WhatsApp-specific template message formats (Meta-approved templates) are documented as text notes because HubSpot Campaigns use email and other channel templates; the customer must re-create WhatsApp-specific templates in HubSpot's WhatsApp integration settings post-migration.

LimeChat bot flows define trigger conditions, decision trees, and response actions. We extract flow logic as structured JSON and deliver it as a written automation inventory document with each flow's trigger, conditions, actions, and recommended HubSpot workflow equivalent. The flows themselves do not migrate as executable code because LimeChat's flow builder uses GPT-powered intent triggers that have no direct HubSpot equivalent. The customer's admin rebuilds flows in HubSpot's workflow builder using the inventory as a blueprint.

LimeChat bot settings include NLP intent definitions, entity extraction rules, and handoff configurations. We export intent mappings and trigger phrases as plain-text labels in a bot configuration inventory document. GPT-powered AI model settings are proprietary to LimeChat's infrastructure and cannot be transferred. If the customer requires chatbot functionality in HubSpot, they rebuild intents using HubSpot Breeze AI Agents (Enterprise tier) or third-party AI integrations.

LimeChat helpdesk tickets map directly to HubSpot Service Hub Tickets. Standard ticket fields (subject, description, status, priority, assigned agent) migrate cleanly. Custom ticket fields are mapped individually during scoping, with field types converted to equivalent HubSpot property types. Conversation linkage from LimeChat threads attaches as internal Ticket notes.

LimeChat product catalog entries (SKUs, names, pricing) used in bot-served product information migrate to HubSpot CRM Products. Product associations to conversations and campaigns are documented in the migration scope but do not carry over as linked records in HubSpot; the customer recreates product associations in HubSpot post-migration.

LimeChat contact and conversation tags used for segmentation migrate as HubSpot contact properties. We map tags to a multi-select contact property during scoping, with the customer choosing between a multi-select picklist (if tag cardinality is under 200) or a text array property (if tag cardinality is higher). Tag names and their associations to individual records preserve fully.

Click-to-WhatsApp ad configurations and associated Meta campaign attribution data export from LimeChat as campaign metadata. The actual Meta ad account linking requires reconnection in HubSpot's Facebook and Instagram integration settings post-migration. Campaign Member records from LimeChat audiences migrate as HubSpot Campaign Members with Status mapped appropriately.

LimeChat aggregated analytics and pre-computed dashboards are derived data, not raw records. We do not migrate dashboards. The customer rebuilds service reports in HubSpot's analytics tools using migrated Ticket data as the source. We deliver a written analytics inventory document listing every LimeChat metric and dashboard for the customer's admin to replicate in HubSpot's reporting module.

If the LimeChat account uses company-level customer organization (common in B2B-adjacent D2C setups with wholesale or distributor accounts), we map LimeChat company records to HubSpot CRM Companies. Company domains, names, and custom properties migrate as HubSpot company properties.

LimeChat operates as a WhatsApp Business Solution Partner, meaning the customer's WhatsApp Business Account is registered through LimeChat's Meta partnership. Migrating to HubSpot requires re-registering the WABA under HubSpot's Meta partnership or initiating a WABA transfer request through Meta Business Manager. We coordinate the transfer request during cutover to minimize WhatsApp campaign downtime, which typically takes 2-4 weeks per Meta's verification process.