Migrate your HelpCrunch data
All-in-one customer communication platform bundling live chat, email automation, and a lightweight help desk for small to mid-market teams on a budget.
In its favor
Why people choose HelpCrunch
The signal that keeps HelpCrunch on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Cost-effective Intercom replacement — multiple reviews highlight HelpCrunch delivering comparable live chat and help desk features at a significantly lower price point for small businesses and startups.
Bundled functionality eliminates subscription sprawl — live chat, email automation, knowledge base, and ticketing in one dashboard reduces the need for multiple SaaS tools.
Responsive human support — G2 reviews consistently praise HelpCrunch's customer support team for quick, knowledgeable responses without bot or scripted answers.
Simple setup and integration — users report that chat widget installation and configuration requires minimal technical effort and completes quickly.
AI chatbot and automation on mid-tier plans — even the Pro plan includes AI agents and chatbot flows, which smaller teams find valuable without enterprise pricing.
Reliability concerns and bugs — reviews describe recurring issues with integrations and core features that break unexpectedly, disrupting support workflows.
AI capabilities fall short of modern standards — the platform's AI is described as a hybrid of rule-based flows and limited newer AI agents, not competitive with purpose-built AI-first solutions.
Constrained feature set on lower tiers — the Basic plan caps automation at 3 auto messages and 3 popups, and lacks AI entirely, pushing teams toward expensive upgrades.
Hidden escalation costs for AI — while the Pro plan includes some AI conversations, additional AI chats cost $29/month for just 100 more, which adds up quickly at scale.
Limited customization options — G2 reviews cite restrictions on customizing workflows and the chat widget appearance, particularly on lower-priced plans.
Reasons to switch
Why people leave HelpCrunch
The recurring reasons buyers give for replacing HelpCrunch. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where HelpCrunch 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
HelpCrunch pricing overview
HelpCrunch uses per-seat per-month pricing with three tiers. Basic starts at $15/user/month and tops out around $105 for 5 seats; Pro ranges from $25–$205 depending on seat count; the Unlimited flat plan is $620/month regardless of team size. AI conversation add-ons are priced separately and can increase the effective cost significantly for high-volume support teams.
Basic
Tier 1 of 3
$15–$105/month (per-seat, annual or monthly)
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on HelpCrunch's schedule — see our quote-based pricing →
What gets migrated
HelpCrunch object support
Object-by-object support for HelpCrunch migrations. Per-pair details surface during scoping.
Customers
Fully supportedContacts are the primary object in HelpCrunch. They support standard fields (name, email, userId) plus custom properties. We export full contact records including custom fields via REST API (GET /customers) or CSV/XLSX from the dashboard. Imports map 1:1.
Chats (Conversations)
Mapping requiredChat history is accessible via REST API. Each chat has metadata (timestamp, status, assignee, channel). Message content transfers, but chat widget display state and active session context do not persist post-migration.
Articles (Knowledge Base)
Mapping requiredHelpCrunch's WYSIWYG knowledge base articles can be exported. Their SEO metadata and embedding context (standalone vs widget-embedded) requires field-level mapping to the destination's equivalent KB structure.
Saved Replies
Fully supportedSaved responses are key-value pairs scoped to the team. We export these as structured text objects and import them into the destination's equivalent saved replies or snippets feature.
Email Templates
Fully supportedEmail templates include subject, body HTML, and variables. We extract them via API and map them to the destination's email template schema, preserving variable placeholders.
Auto Messages
Mapping requiredTriggered auto messages (popups, proactive chat invitations) have targeting rules tied to HelpCrunch's behavioral conditions. We export the message content and trigger logic; destination triggers must be rebuilt using equivalent conditions.
Chatbots
Mapping requiredChatbot flows are node-based automation trees with branching logic. HelpCrunch supports rule-based flows and limited AI agents. We export flow content and structure; node-by-node rebuilding in the destination platform is required.
Tags
Fully supportedTags are flat string labels applied to customers and chats. We export the full tag taxonomy and reapply tag associations during import.
Custom Properties (Fields)
Mapping requiredCustom properties on customers include types (text, number, date, checkbox). We map these to equivalent custom fields in the destination, handling type conversion where schema differs.
Reports and Analytics
Mapping requiredReports (Team Members, Customer Satisfaction, Total Chats) are exportable as CSV/XLSX from the dashboard. Aggregate metrics transfer, but interactive drill-down state does not.
Agents (Team Members)
Mapping requiredAgent records include name, email, and role. We transfer agent profiles, but permissions and access level assignments must be manually reconfigured at the destination.
Channels
Mapping requiredHelpCrunch unifies live chat, email, WhatsApp, and Instagram into a shared inbox. Channel configuration (not individual messages) transfers as metadata; each channel must be reconnected at the destination.
Popups
Mapping requiredPopup configurations include design, timing rules, and targeting. We export content and trigger logic; the popup builder UI must be recreated at the destination.
Widgets
Mapping requiredChat widgets are customizable per website or app. Widget installation code (snippet) is destination-platform specific and must be re-implemented post-migration.
| Object | Support | Notes |
|---|---|---|
| Customers | Fully supported | Contacts are the primary object in HelpCrunch. They support standard fields (name, email, userId) plus custom properties. We export full contact records including custom fields via REST API (GET /customers) or CSV/XLSX from the dashboard. Imports map 1:1. |
| Chats (Conversations) | Mapping required | Chat history is accessible via REST API. Each chat has metadata (timestamp, status, assignee, channel). Message content transfers, but chat widget display state and active session context do not persist post-migration. |
| Articles (Knowledge Base) | Mapping required | HelpCrunch's WYSIWYG knowledge base articles can be exported. Their SEO metadata and embedding context (standalone vs widget-embedded) requires field-level mapping to the destination's equivalent KB structure. |
| Saved Replies | Fully supported | Saved responses are key-value pairs scoped to the team. We export these as structured text objects and import them into the destination's equivalent saved replies or snippets feature. |
| Email Templates | Fully supported | Email templates include subject, body HTML, and variables. We extract them via API and map them to the destination's email template schema, preserving variable placeholders. |
| Auto Messages | Mapping required | Triggered auto messages (popups, proactive chat invitations) have targeting rules tied to HelpCrunch's behavioral conditions. We export the message content and trigger logic; destination triggers must be rebuilt using equivalent conditions. |
| Chatbots | Mapping required | Chatbot flows are node-based automation trees with branching logic. HelpCrunch supports rule-based flows and limited AI agents. We export flow content and structure; node-by-node rebuilding in the destination platform is required. |
| Tags | Fully supported | Tags are flat string labels applied to customers and chats. We export the full tag taxonomy and reapply tag associations during import. |
| Custom Properties (Fields) | Mapping required | Custom properties on customers include types (text, number, date, checkbox). We map these to equivalent custom fields in the destination, handling type conversion where schema differs. |
| Reports and Analytics | Mapping required | Reports (Team Members, Customer Satisfaction, Total Chats) are exportable as CSV/XLSX from the dashboard. Aggregate metrics transfer, but interactive drill-down state does not. |
| Agents (Team Members) | Mapping required | Agent records include name, email, and role. We transfer agent profiles, but permissions and access level assignments must be manually reconfigured at the destination. |
| Channels | Mapping required | HelpCrunch unifies live chat, email, WhatsApp, and Instagram into a shared inbox. Channel configuration (not individual messages) transfers as metadata; each channel must be reconnected at the destination. |
| Popups | Mapping required | Popup configurations include design, timing rules, and targeting. We export content and trigger logic; the popup builder UI must be recreated at the destination. |
| Widgets | Mapping required | Chat widgets are customizable per website or app. Widget installation code (snippet) is destination-platform specific and must be re-implemented post-migration. |
Gotchas
What to watch for in HelpCrunch migrations
Issues we've hit on past HelpCrunch migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
API rate limit of 120 req/min blocks bulk migrations
AI conversation caps throttle history migration
Legacy API key deprecation requires key rotation
Knowledge base articles require manual re-embedding
HelpCrunch branding on chat widget in Basic plan
| Severity | Issue |
|---|---|
| High | API rate limit of 120 req/min blocks bulk migrations |
| Medium | AI conversation caps throttle history migration |
| Medium | Legacy API key deprecation requires key rotation |
| Low | Knowledge base articles require manual re-embedding |
| Low | HelpCrunch branding on chat widget in Basic plan |
Leaving HelpCrunch?
Where HelpCrunch customers move next
7 destinations HelpCrunch can migrate to.
How a HelpCrunch migration works
Four steps, HelpCrunch-specific
Connect
API key via Bearer token in Authorization header into HelpCrunch. Scopes limited to read-only on the data we move.
Map
We translate HelpCrunch-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate HelpCrunch quirks before production.
Migrate
Full migration with HelpCrunch rate-limit handling. Rollback available throughout.
FAQ
HelpCrunch migration FAQ
Answers to the questions buyers ask most during HelpCrunch migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your HelpCrunch 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 HelpCrunch.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your HelpCrunch setup and destination — written quote back within a business day.