Migrate from HelpCrunch to HubSpot Service Hub

HelpCrunch Customers map directly to HubSpot Contacts. The customer's standard fields (name, email, userId) map to HubSpot's firstname, lastname, email, and hs_object_id properties. Custom properties on the HelpCrunch customer record (text, number, date, checkbox types) map to HubSpot custom contact properties, which we pre-create in the destination HubSpot portal before import. The HubSpot Contact is created first so that any subsequent Chat or Ticket import can resolve the ContactId lookup.

HelpCrunch chat threads map to HubSpot Tickets organized by inbox and assignee, with individual messages preserved as Conversation records threaded to the Ticket. Each HelpCrunch chat has metadata (timestamp, status, assignee, channel) that maps to HubSpot Ticket properties (hs_ticket_subject, hs_task_body, hubspot_owner_id, hs_ticket_priority, hs_pipeline, hs_ticket_status) plus the hs_conversation_thread_type field. HelpCrunch's unified channel inbox (live chat, email, WhatsApp, Instagram) resolves to HubSpot's inbox configuration, where each channel type becomes a separate thread source in the shared queue.

HelpCrunch WYSIWYG knowledge base articles migrate to HubSpot Knowledge Base articles with their HTML body content, title, slug (mapped to HubSpot slug), and article metadata. Article SEO fields (meta title, meta description) transfer to HubSpot's knowledge_base_article data model. HelpCrunch's embedding context (standalone page vs in-widget) does not persist; we export the content and metadata, and the embedding configuration is recreated manually in HubSpot's KB settings. Articles are the most time-intensive object to migrate accurately due to HTML content validation.

HelpCrunch Saved Replies are structured key-value text snippets scoped to the team. They migrate as HubSpot Canned Responses (Snippets), which are organizational text templates available in the CRM and inbox. We export the reply title and body content including variable placeholders and import them as HubSpot Snippets. Because Canned Responses in HubSpot are tied to the inbox and agent context rather than a flat key-value store, we include a written mapping table of HelpCrunch category groupings to HubSpot Snippet folders during the handoff.

HelpCrunch Email Templates include subject, body HTML, and variable placeholders. We export template content via the HelpCrunch API and map to HubSpot's Content Template system (if available on the customer's Service Hub tier) or to Salesforce Email Templates accessible within the HubSpot inbox. Variable placeholders from HelpCrunch (%customer_name%, %ticket_id%) map to HubSpot personalization tokens or are documented as a variable substitution table for the customer's admin to reconfigure post-migration.

HelpCrunch Auto Messages (triggered popups and proactive chat invitations) have targeting rules tied to HelpCrunch's behavioral conditions that have no direct HubSpot equivalent. We export the message content, subject, and trigger logic description as a written inventory. The trigger rules themselves — behavioral conditions, timing, targeting criteria — must be rebuilt as HubSpot Service Automation rules or Workflows by the customer's admin post-migration. This is a documented inventory deliverable, not an automated transfer.

HelpCrunch chatbot flows are node-based automation trees with branching logic and limited AI agent nodes. We export the flow content, node structure, and branching conditions as a written flow inventory. HubSpot's Conversational Bots and Service Automation features provide equivalent capabilities (triggered bot responses, conditional routing, CRM field updates), but the automation logic does not migrate automatically. We deliver a node-by-node flow map with recommended HubSpot equivalents for the customer's admin to rebuild.

HelpCrunch tags are flat string labels applied to customers and chats. We export the complete tag taxonomy and reapply all tag associations during HubSpot import, mapping them to HubSpot Labels on Tickets. Tags on HelpCrunch Customers transfer as Label associations on the corresponding HubSpot Contacts. The flat tag namespace in HelpCrunch maps cleanly to HubSpot Labels with no structural transformation required.

HelpCrunch custom properties on Customer records (text, number, date, checkbox types) map to HubSpot custom contact properties of equivalent type. We pre-create the destination schema in HubSpot before any Contact import, converting HelpCrunch field types to HubSpot property types. For example, HelpCrunch date-type properties map to HubSpot date properties, and checkbox properties map to HubSpot booleans. Text properties map to single-line or multi-line text depending on expected content length. This ensures custom field data is preserved and queryable post-migration.

HelpCrunch Reports (Team Members, Customer Satisfaction, Total Chats) are exportable as CSV and XLSX from the dashboard. We extract these datasets and deliver them as structured import files for HubSpot Reports or as a reference for manual rebuild in HubSpot's analytics dashboard. Aggregate metrics transfer as static data; interactive drill-down state, filter presets, and dashboard layouts do not persist. We flag which HelpCrunch reports have direct HubSpot equivalents and which require manual rebuild.

HelpCrunch Agent records (name, email, role) map to HubSpot Users. We resolve agents by email match against the HubSpot destination portal's User table. Permissions and access level assignments (HelpCrunch roles) must be manually reconfigured in HubSpot's User roles and permissions settings post-migration. Any inactive or deleted HelpCrunch agents are held in a reconciliation queue for the customer's admin to provision or map before ticket reassignment proceeds.

HelpCrunch unifies live chat, email, WhatsApp, and Instagram into a shared inbox. Channel configuration (not individual messages, which are handled in the Chat object mapping) transfers as metadata describing which channels were connected and their settings. Each channel must be reconnected individually in HubSpot Service Hub's inbox configuration. We provide a written channel inventory with the connection settings documented for the customer's admin to re-enter, including any webhook URLs, API keys, or OAuth credentials required for each channel.

HelpCrunch Popup configurations include design, timing rules, and targeting conditions. We export popup content and the trigger logic description as part of the Auto Message inventory. Popup design (colors, copy, layout) is not structurally transferable because HelpCrunch's popup builder schema is proprietary. The popup builder UI must be recreated in HubSpot Marketing (if the customer has HubSpot Marketing Hub) or in a third-party popup tool. We deliver a popup content and targeting inventory as part of the configuration handoff.

HelpCrunch chat widgets are customized per website or app via a JavaScript installation snippet. Widget customization settings (colors, greeting text, agent avatars, behavior settings) are exported as a written configuration inventory. The widget installation code itself is destination-platform specific and must be re-implemented post-migration. HubSpot's chat widget is installed via the HubSpot tracking code or native HubSpot Conversations widget embed. We provide a detailed widget configuration map so the customer's dev team can re-implement the widget appearance and behavior in HubSpot.