Migrate from LimeChat to Intercom

LimeChat WhatsApp conversation threads migrate to Intercom Conversation records with full message metadata (timestamps, message direction, read receipts, WhatsApp message type). We preserve the original WhatsApp message ID in intercom_external_id__c for cross-referencing. Agent attribution migrates to Conversation assignments linked to the resolved Intercom User. Unassigned conversations require default assignment settings enabled in Intercom before import per Help Desk Migration guidance.

LimeChat customer profiles with WhatsApp identifiers, contact details, and interaction history map to Intercom Contacts. The WhatsApp phone number becomes the primary identifier; we run phone number validation disable in Intercom settings before migration to prevent invalid numbers from blocking import. Custom contact attributes migrate to Intercom custom_attributes. Any HubSpot Owner email references are resolved to Intercom Admins via the Team member mapping.

LimeChat 2-way WhatsApp campaign structures (targeting rules, message templates, send schedules, audience segments) migrate as plain-text campaign inventory. WhatsApp template message formats are platform-specific and require reconstruction in Intercom's Outbound messaging as email, push, or WhatsApp templates. Campaign performance records (open rates, click rates, delivery stats) migrate as custom attributes on the Campaign record rather than native analytics.

LimeChat bot flows with trigger conditions, decision trees, and response actions export as structured JSON but cannot run in Intercom without reconstruction. We deliver a written inventory of every active LimeChat automation with its trigger type, conditions, branching logic, and actions in plain-text format. The customer's Intercom admin rebuilds these as Intercom Workflows, Custom Bots, or Rules based on the delivered inventory.

LimeChat GPT intent definitions and NLP training labels export as plain-text intent and entity lists. These do not transfer as trained models to Intercom's Fin AI Agent, which requires its own Knowledge Hub article set for FAQ resolution. We extract LimeChat bot response templates as text files for the customer to repurpose as Intercom Help Center articles or Fin knowledge sources.

LimeChat tickets with issue descriptions, status, assigned agents, and conversation linkage migrate to Intercom Conversation records with Ticket attributes (Ticket title, Ticket attributes, Assigned team/teammate). Standard ticket fields migrate cleanly; custom ticket fields map to Intercom Ticket custom_attributes. The migration sequence requires Ticket attributes to be enabled in Intercom workspace settings before import.

LimeChat product catalog entries (SKUs, product names, pricing, images) migrate to Intercom Products. Product-to-conversation surfacing that LimeChat bots perform requires reconstruction in Intercom as part of the bot workflow rebuild. E-commerce platform sync (Shopify, WooCommerce) requires separate integration setup post-migration.

Contact and conversation tags used for segmentation and campaign targeting migrate as Tag records in Intercom. Tag associations to individual contacts and conversations migrate as tag_id references. Intercom's tag limit and naming conventions are validated during mapping to avoid conflicts with existing Intercom tags.

Click-to-WhatsApp ad configurations and campaign attribution data export as metadata records. Meta ad account linking requires reconnection in Intercom's Meta advertising integration post-migration. Customer attribution from ad-clicked conversations migrates as custom attributes on the Contact record.

Aggregated analytics and pre-computed dashboards are derived data not stored as records. We do not migrate LimeChat's analytics outputs. The customer rebuilds reports in Intercom's native reporting using migrated conversation data. Created_at and Updated_at timestamps migrate for conversation records, enabling time-series analysis from day one.