---
title: "Help Scout Alternatives 2026: Features, TCO & Migration"
slug: help-scout-alternatives-2026-features-tco-migration
date: 2026-09-14
author: Abdul Wahab
categories: [Help Scout]
excerpt: "Compare Help Scout alternatives (Zendesk, Freshdesk, Front, Zoho Desk, and more) on real 2026 pricing, AI costs, features, and migration complexity."
tldr: "Freshdesk wins on cost for sub-30 teams, Zendesk for enterprise routing, Front for cross-team collaboration. Budget for migration complexity — Help Scout has no native export for conversation data."
canonical: https://clonepartner.com/blog/help-scout-alternatives-2026-features-tco-migration
---

# Help Scout Alternatives 2026: Features, TCO & Migration


# Help Scout Alternatives 2026: Features, TCO & Migration

The best Help Scout alternative depends on your team size, channel mix, and AI budget. For cost-conscious teams under 30 agents, **Freshdesk** offers the strongest value. For cross-functional collaboration beyond pure support, **Front** wins. For enterprise-grade routing and SLA control, **Zendesk** is still the default. For e-commerce, **Gorgias** with its ticket-based pricing model fits best. And if you're already inside the Zoho ecosystem, **Zoho Desk** at $7/agent/month is hard to beat on raw cost.

This guide compares seven alternatives across real pricing, feature gaps, AI costs, migration complexity by target platform, and the actual work involved in moving your data out of Help Scout — including the API constraints that most comparison articles skip entirely.

## Why teams leave Help Scout

Help Scout is an email-first shared inbox that does a few things very well for small teams. The reasons teams outgrow it follow a consistent pattern.

**Support-only scope.** Help Scout handles support ticketing, but if your team also runs sales, general email, or internal collaboration, you need a second tool. There's no CRM, no deal pipeline, no internal request management.

**Thin native channels.** Email and live chat are solid, but voice, social, and WhatsApp coverage trail dedicated omnichannel platforms. WhatsApp is inbound support only — you can't initiate outbound conversations.

**AI costs that compound.** Help Scout's AI Answers is priced at $0.75 per resolution on top of seat costs. At 500 monthly AI resolutions, that adds $375/month to your bill. No plan tier bundles AI deflection into the base subscription.

**Reporting walls.** The Standard plan limits reporting history to two years. Per-agent response times, CSAT trends, and ticket-volume-by-hour analytics require the Plus plan at $45/user/month.

**The 25-agent cliff.** Standard maxes out at 25 users. Adding a 26th agent forces an upgrade from Standard ($25/user) to Plus ($45/user) — an 80% per-seat increase overnight. A 25-agent Standard team paying $625/month jumps to $1,170/month by adding one person.

## Help Scout pricing in 2026: what you actually pay

Help Scout's per-user pricing uses four tiers: Free, Standard ($25/user/month), Plus ($45/user/month), and Pro ($75/user/month). Annual billing saves roughly 16%, bringing effective rates to approximately $21, $38, and $63 per user/month respectively.

But the sticker price is rarely the invoice total. Three cost layers sit on top of seats:

- **Extra inboxes:** $10/month each ($12 on monthly billing)
- **Extra Docs sites:** $20/month each ($24 monthly)
- **AI Answers:** $0.75 per resolution, billed on top of everything

The 16% annual discount applies only to seat costs — add-ons are charged at full price regardless of billing frequency. For a 10-agent team on Plus with 2 extra inboxes, 1 extra Docs site, and 500 monthly AI resolutions, the real monthly cost lands near $870 — roughly 94% above the advertised $450 base.

> [!WARNING]
> Help Scout's Free plan caps contacts at 100/month and blocks outgoing replies once you hit the limit. It is a sandbox, not a production tier. The Free plan also does not include API access, so you cannot export your data programmatically if you need to leave.

## 18-month blended TCO by team size

Per-seat pricing comparisons are misleading without accounting for AI add-ons at realistic resolution volumes. The table below models 18-month total cost for three team sizes assuming 40 AI resolutions per agent per month (a conservative estimate for a team using AI deflection actively). All figures use annual billing and mid-tier plans.

| Platform | 10 agents (18-mo TCO) | 25 agents (18-mo TCO) | 50 agents (18-mo TCO) | Notes |
|---|---|---|---|---|
| **Help Scout Plus + AI** | $15,660 | $39,150 | $78,300 | Includes $0.75/resolution; no AI bundle |
| **Zendesk Suite Pro + Copilot** | $34,470 | $86,175 | $172,350 | Copilot adds $50/agent/mo |
| **Freshdesk Pro + Freddy** | $15,120 | $37,800 | $75,600 | Freddy Copilot $29/agent/mo |
| **Freshdesk Omni + Freddy** | $17,280 | $43,200 | $86,400 | Correct comparison for omnichannel |
| **Front Professional + AI** | $25,380 | Enterprise pricing | Enterprise pricing | Pro caps at 50 seats; AI add-ons stack |
| **Zoho Desk Enterprise (Zia bundled)** | $7,200 | $18,000 | $36,000 | Zia included; lowest absolute TCO |
| **HubSpot Service Pro + AI** | $21,600 | $54,000 | $108,000 | Includes $0.50/resolution AI; $1,500 onboarding |
| **Intercom/Fin Essential + AI** | $23,220 | $58,050 | $116,100 | $0.99/resolution; Salesforce transition risk |

*Assumptions: 40 AI resolutions/agent/month. 18-month window to capture first annual renewal plus growth costs. Onboarding fees included where mandatory. Verify against current vendor pricing pages — this market moves quarterly.*

**Key takeaways from the TCO model:**
- At 10 agents, Zoho Desk Enterprise costs less over 18 months than Help Scout Plus even before AI is factored in.
- Zendesk's Copilot add-on ($50/agent/month) makes it 2.2× more expensive than Freshdesk Pro + Freddy at every team size modeled.
- Help Scout becomes cost-competitive again only if you use minimal AI resolutions (under 10/agent/month) and stay under 25 agents.
- Front's Professional cap at 50 seats means any team expecting to cross that threshold should price Enterprise from day one.

## How do the top Help Scout alternatives compare on price?

Pricing models across help desks have diverged sharply: per-agent, per-seat, per-ticket, and per-resolution all coexist. A direct per-agent comparison misses the point if one tool charges $0.99 every time AI closes a ticket.

| Platform | Entry tier (annual) | Mid tier (annual) | Top tier (annual) | AI add-on cost | Free plan |
|---|---|---|---|---|---|
| **Help Scout** | $25/user/mo | $45/user/mo | $75/user/mo (10-seat min) | $0.75/resolution | Yes (5 users, 100 contacts/mo) |
| **Zendesk Suite** | $55/agent/mo | $89/agent/mo | $115/agent/mo | Copilot $50/agent/mo | No |
| **Freshdesk** | $19/agent/mo | $55/agent/mo | $89/agent/mo | Freddy Copilot $29/agent/mo | Yes (2 agents, 6 months) |
| **Intercom/Fin** | $29/seat/mo | $85/seat/mo | $132/seat/mo | $0.99/resolution | No |
| **Front** | $25/seat/mo | $65/seat/mo | $105/seat/mo | Copilot +$20/seat; Autopilot $0.89/resolution | No |
| **Zoho Desk** | $7/agent/mo | $23/agent/mo | $40/agent/mo | Zia bundled in Enterprise | Yes (3 agents) |
| **HubSpot Service Hub** | $15/seat/mo | $100/seat/mo | $150/seat/mo (10-seat min) | $0.50/resolution | Yes (basic) |
| **Gorgias** | $60/mo (300 tickets) | $360/mo (2,000 tickets) | $900/mo (5,000 tickets) | Per-ticket + automation fee | No |

*All prices reflect annual billing as of mid-2026. Verify against vendor pricing pages before committing.*

## Platform-by-platform analysis

### Zendesk: when routing complexity justifies the cost

**Zendesk Suite** is the default choice for teams above 30 agents that need deep SLA management, skill-based routing, and a broad integration marketplace. Suite Team starts at $55/agent/month billed annually; Suite Professional at $115/agent/month adds custom analytics and HIPAA compliance.

The trade-off is clear: you pay for infrastructure you may not use at smaller scale. For a 5-agent team, Zendesk costs $3,300/year before add-ons. The AI Copilot at $50/agent/month is the most expensive per-seat AI option among the platforms compared here — $21/agent/month more than Freshdesk Freddy and $50/agent/month more than Zoho Desk's bundled Zia.

Zendesk's import API accepts conversations via its Tickets API (REST, JSON). Rate limits on Professional are 700 requests/minute. The official Ticket Import endpoint bypasses some standard rate limits for bulk imports but requires a separate authorization header and is not available on Team plans. Inline images import as attachments without losing thread association, which gives Zendesk an advantage over some mid-market alternatives.

**Best fit:** SLA-heavy, queue-driven operations at 30+ agents where routing complexity justifies the cost premium.

### Freshdesk: best value for sub-30 teams

**Freshdesk** raised prices in 2026: Growth moved from $15 to $19, Pro from $49 to $55, and Enterprise from $79 to $89 per agent/month on annual billing. The old 10-agent free tier is gone — the Free plan now covers 2 agents for the first 6 months only.

Freddy AI Copilot runs $29/agent/month; Freddy AI Agent includes 500 bot sessions on Pro/Enterprise with overages at $49 per 100 sessions.

One important distinction: **Freshdesk standalone** is email-first ticketing. **[Freshdesk Omni](https://clonepartner.com/blog/blog/freshdesk-omni-forced-upgrade-2026-what-breaks-how-to-migrate)** is the true omnichannel inbox, starting at $29/agent/month. If you're comparing against Zendesk Suite or Intercom, compare Freshdesk Omni — not standalone Freshdesk. Treating them as equivalent overstates standalone Freshdesk's channel coverage and understates its real cost for omnichannel use cases.

Freshdesk's import tooling accepts CSV files for contacts and companies; ticket import requires the Tickets API (REST). Inline images do not always transfer cleanly via CSV import — they may arrive as broken image tags referencing the source domain. API-based migration with attachment re-upload is more reliable. Rate limits on Pro are 1,000 requests/minute.

**Best fit:** Teams under 30 agents that need automation and multi-channel support without enterprise pricing.

### Intercom (rebranding to Fin): Salesforce acquisition context

In 2025, Salesforce announced its intent to acquire Intercom, and in mid-2026 Intercom began rebranding its AI-first product as **Fin**. The acquisition and integration timeline is still unfolding as of this writing — treat any specific completion date as subject to revision and verify against official Salesforce and Intercom announcements before making a buying decision.

The strategic implication is clear regardless of precise timing: Fin is moving into the Salesforce ecosystem. New buyers should evaluate Fin not as a standalone platform but as a future component of Agentforce. Pricing and packaging will likely shift as integration deepens.

Fin's AI agent claims a 76% average resolution rate on its marketing materials. At $0.99/resolution, a team handling 500 AI-resolved tickets monthly pays $495 in AI costs alone — before seat fees. For a 10-person team on Essential ($29/seat), that's $1,285/month blended. The per-resolution model can deliver strong ROI if the resolution rate holds at scale, but the cost becomes unpredictable if ticket volume spikes.

**Best fit:** Product-led SaaS teams where support lives inside the app. Evaluate carefully given the platform transition — pricing and integration changes are likely within 12 months.

### Front: collaboration-first, not support-first

**Front** is not a traditional help desk. It is a collaborative inbox where customer-facing teams manage conversations across email, chat, SMS, and social — with shared drafts, internal comments, and cross-team assignment that Help Scout cannot match.

Front simplified its pricing in 2026 from four tiers to three: Starter at $25/seat/month (10-seat max, single channel), Professional at $65/seat/month (50-seat max), and Enterprise at $105/seat/month. AI is gated on Starter and Professional: Copilot costs $20/seat/month extra, Smart QA adds $20/seat, and Autopilot runs $0.89/resolution. Enterprise bundles most AI features — making it cheaper than Professional plus all add-ons for teams planning heavy AI use.

Front charges a mandatory onboarding fee for contracts above $25,000. API rate limit upgrades cost $200/month per 100 additional requests/minute above the default.

Front's import API handles conversation threading but has limited support for custom field migration — fields not mapped to Front's native schema must be imported as tags or conversation attributes, which affects downstream reporting. Attachment import works via URL reference, not binary upload, which requires the source attachments to remain accessible during migration.

**Best fit:** Teams where support, sales, and ops share the same inbox and need real-time collaboration — not just ticket routing.

### Zoho Desk: lowest TCO if you're in the Zoho ecosystem

**Zoho Desk** starts at $7/agent/month (Express plan, annual) and tops out at $40/agent/month for Enterprise, where Zia AI is bundled rather than metered. The free tier covers 3 agents with basic email ticketing.

At 50 agents on Enterprise, Zoho Desk costs $24,000 over 18 months — compared to $75,600 for Freshdesk Pro with Freddy and $172,350 for Zendesk with Copilot. The gap is material.

The trade-off: Zoho Desk's interface is denser and less immediately intuitive than Help Scout's clean inbox UI. Teams switching from Help Scout typically report a 2–4 week adjustment period before agents reach prior productivity levels. There is no built-in import wizard from Help Scout — migration requires API-based extraction from Help Scout and API-based import into Zoho Desk, with custom field mapping handled manually or via a third-party service.

G2 ratings as of mid-2026: Zoho Desk holds 4.4/5 across approximately 6,000 reviews; Help Scout holds 4.4/5 across approximately 400 reviews. Zoho Desk's lower satisfaction scores on ease of setup (3.9/5 vs. Help Scout's 4.6/5) reflect the real onboarding complexity.

**Best fit:** Budget-conscious teams or organizations already invested in the Zoho ecosystem.

### HubSpot Service Hub: the CRM-native play

**HubSpot Service Hub** makes sense when your marketing and sales teams already live in HubSpot and you want a single customer record across the entire lifecycle. Starter begins at $15/seat/month; Professional jumps to $100/seat/month (annual required, 10-seat minimum for Enterprise at $150/seat). Mandatory onboarding fees apply: $1,500 for Professional, $3,500 for Enterprise.

HubSpot added outcome-based AI credits in 2026, charging approximately $0.50 per resolved conversation. At $100/seat plus AI costs, HubSpot Professional is in Zendesk territory — but with a narrower support-specific feature set and the advantage of native CRM integration that eliminates third-party connectors for teams already on HubSpot.

The HubSpot import API handles contact and ticket migration but does not support conversation thread import natively — historical conversation bodies require a workaround (typically attaching thread content as a note to the imported ticket). This is a meaningful limitation if your compliance or audit requirements depend on searchable historical threads.

**Best fit:** Teams where CRM continuity across marketing, sales, and support justifies the price premium and where historical thread fidelity is not a compliance requirement.

## How hard is it to migrate data out of Help Scout?

Migrating out of Help Scout is harder than most teams expect because Help Scout does not have an "Export Everything" button. The built-in UI export covers reporting metrics only — conversation volume, response times, happiness scores — delivered as CSV or XLSX. It explicitly excludes conversation thread contents, message bodies, and satisfaction rating comments.

For a [migration-ready export including full thread content, attachments, and relational links](https://clonepartner.com/blog/blog/how-to-export-data-from-help-scout-methods-api-limits-formats), you need to use two separate APIs:

- **Inbox API 2.0** (Help Scout developer docs): OAuth 2.0, JSON over HTTPS. Handles conversations, threads, customers, tags, and custom fields.
- **Docs API** (Help Scout developer docs): Separate API key using HTTP Basic auth. Handles knowledge base articles.

### API constraints that directly affect migration timelines

- **Rate limits:** The official Help Scout developer documentation advises checking your plan for specific limits. Response headers (`X-RateLimit-Remaining`, `X-RateLimit-Reset`) indicate current status. Third-party migration engineers have observed approximately 400 requests/minute per access token on paid plans — treat this as a working estimate, not a guaranteed limit.
- **Pagination:** Defaults to 25 records per page; maximum 50 per page. A 100,000-conversation export requires a minimum of 2,000 paginated API calls.
- **Thread limit:** The API caps at 100 threads per conversation. Conversations exceeding this limit return a `412 Precondition Failed` error. Long-running email threads — common in B2B support contexts — frequently hit this cap and must be split during migration.
- **Merged conversations:** Redirect via HTTP 301 for approximately 60 days after merging, then return 404 permanently. If you've been merging duplicate tickets, export before that window closes.
- **OAuth token expiry:** Tokens expire after 48 hours. Long-running exports require token refresh logic; an unhandled expiry mid-export silently truncates your dataset without an obvious error.
- **Free plan restriction:** No API access on the Free plan. You must be on Standard or above to use the Inbox API programmatically.

### What cannot be migrated automatically

Several Help Scout objects require manual recreation in your target platform regardless of which migration method you use:

- Workflows and automation rules (platform-specific logic, no portable format)
- Saved replies (listable via API but must be re-created manually in the target)
- Inbox settings and routing rules
- User accounts (must be provisioned in the target *before* importing conversations — see below)
- Native integrations and connected apps

> [!TIP]
> Create all user accounts in the target platform before running any conversation import. If agent accounts don't exist at import time, every historical message gets attributed to a generic system user — destroying your audit trail and making historical reporting unreliable.

### Estimating manual recreation scope

Teams often underestimate the manual work. A rough heuristic based on typical Help Scout instances:

- **Saved replies:** Teams with 50+ saved replies typically spend 4–8 hours on manual recreation, including reformatting for the target platform's template syntax.
- **Workflows:** Each conditional automation rule takes 15–30 minutes to analyze, map, and rebuild in a new platform. A 20-workflow instance represents 5–10 hours of work.
- **Routing rules:** Typically 1–3 hours depending on inbox count and complexity.

These estimates assume an administrator familiar with both platforms. Add 30–50% for teams migrating to a platform they haven't used before.

## Import-side constraints by target platform

The Help Scout API constraints are well-documented above. But a migration has two ends. Here's what matters on the import side for the most common target platforms:

| Target platform | Bulk import method | Inline image handling | Custom field migration | Historical thread fidelity | Rate limit (import) |
|---|---|---|---|---|---|
| **Zendesk** | Tickets API + Import endpoint | Attachments preserved | Custom fields map directly | Full thread body preserved | 700 req/min (Pro) |
| **Freshdesk** | Tickets API + CSV contacts | May break on CSV import | Tags or custom fields | Thread body via notes | 1,000 req/min (Pro) |
| **Front** | Conversations API | URL-referenced (source must stay live) | Tags or attributes only | Threading preserved | Default 60 req/min |
| **Zoho Desk** | Tickets API | Supported via attachment upload | Custom field mapping required | Thread body preserved | 100 req/min (Standard) |
| **HubSpot** | Contacts API + workaround for threads | Not natively supported | Native CRM fields only | Thread body as note attachment | 100 req/10 sec |
| **Intercom/Fin** | Conversations API | Supported | Limited custom attribute support | Preserved with correct mapping | 500 req/min |

**Critical observations:**
- **Front's** URL-referenced image approach means your Help Scout attachment URLs must remain accessible during and after migration. If your Help Scout account lapses before the migration is fully indexed, images break permanently.
- **HubSpot's** lack of native thread import means historical conversations become notes — they're searchable but not formatted as conversation threads, which affects support quality workflows that rely on thread context.
- **Zoho Desk's** 100 requests/minute import rate is the most restrictive in this comparison. A 50,000-conversation export from Help Scout would take a minimum of 8+ hours of continuous API calls to import at that rate — plan accordingly.
- **Zendesk's** dedicated Import endpoint (available on Professional and above) bypasses standard rate limits for bulk migrations and is the fastest path for large datasets.

## What does a Help Scout migration actually cost?

Migration cost depends on data volume, target platform, and whether you're writing custom scripts or using a service.

**DIY custom scripts:** If you have an engineer comfortable with OAuth 2.0 APIs, JSON pagination, and rate-limit backoff, expect 2–5 days for a straightforward migration under 50,000 conversations. Edge cases — inline images, conversations near the 100-thread limit, merged tickets within the 60-day window, OAuth token refreshes mid-export — each add 4–8 hours of debugging. Budget 40–80 hours of engineering time for a mid-sized Help Scout instance. Add 10–20 hours for the manual recreation of saved replies, workflows, and routing rules.

**Third-party migration tools:** Automated services (Help Desk Migration and similar) handle field mapping with a visual interface and offer demo migration previews on a subset of your data before committing. These charge per-record fees — typically $0.01–$0.03 per ticket depending on volume. Custom field mapping is limited to supported field types; inline image transfer quality varies by target platform. For a 50,000-ticket instance, expect $500–$1,500 in tool fees plus staff time for configuration and validation.

**Engineer-led migration service:** A dedicated team handles extraction, field mapping, data validation, import, and edge-case remediation. This is where ClonePartner operates. We have completed 1,500+ help desk migrations and document the specific failure modes — the 100-thread cap, the merged-conversation 301→404 window, the OAuth token expiry mid-export — in our pre-migration audit. Typical engagement scope for a 50,000-conversation instance runs 5–10 business days including validation.

## How to choose: a decision framework

Three questions structure the decision — but the answers produce specific outcomes, not just considerations.

**1. What is your channel mix, and what does it cost you to add channels later?**

If you're email-only, Help Scout Standard or Freshdesk Growth are sufficient. If you need voice, social, and WhatsApp in a unified queue today, you need Zendesk Suite, Freshdesk Omni, or Front Professional — and adding channels to a platform not designed for omnichannel is not a configuration exercise, it's a migration. Choose for your channel requirements 18 months out, not today.

**2. Is your AI cost exposure per-seat or per-resolution — and which is safer at your ticket volume?**

Per-seat AI (Zendesk Copilot $50/agent/month, Freshdesk Freddy $29/agent/month) is predictable but expensive for large teams regardless of how much you use it. Per-resolution AI (Help Scout $0.75, Fin $0.99, Front $0.89) is cheaper at low automation volume but becomes the largest line item on your invoice if deflection scales. Calculate your break-even: at $29/agent/month for Freddy, a 10-agent team pays $290/month for unlimited AI. The equivalent at $0.75/resolution is 387 AI resolutions/month. If you're deflecting more than 387 tickets monthly with AI, per-resolution pricing is more expensive.

**3. Where will you be in 18 months, and what does the cliff look like?**

Help Scout Standard-to-Plus at agent 26 is an 80% per-seat increase. Front Professional caps at 50 seats. HubSpot Starter-to-Professional is a 6.7× price jump per seat. Build your TCO model at your projected headcount, not your current one. The 18-month TCO table above shows the compounding effect at 10, 25, and 50 agents.

## Platform quality benchmarks

Pricing and feature coverage don't capture usability. G2 ratings as of mid-2026 across verified reviews:

| Platform | Overall rating | Ease of setup | Quality of support | Ease of use |
|---|---|---|---|---|
| **Help Scout** | 4.4/5 (~400 reviews) | 4.6/5 | 4.7/5 | 4.5/5 |
| **Zendesk** | 4.3/5 (~6,000 reviews) | 3.8/5 | 3.9/5 | 4.1/5 |
| **Freshdesk** | 4.4/5 (~3,300 reviews) | 4.3/5 | 4.3/5 | 4.4/5 |
| **Front** | 4.7/5 (~2,100 reviews) | 4.4/5 | 4.6/5 | 4.6/5 |
| **Zoho Desk** | 4.4/5 (~6,000 reviews) | 3.9/5 | 4.2/5 | 4.3/5 |
| **HubSpot Service Hub** | 4.4/5 (~2,400 reviews) | 4.1/5 | 4.5/5 | 4.4/5 |
| **Intercom/Fin** | 4.5/5 (~3,100 reviews) | 4.3/5 | 4.3/5 | 4.4/5 |

*Source: G2 category pages, verified reviews only. Review counts rounded. Verify current ratings before use in vendor evaluation.*

Key patterns: Front leads on ease of use and overall satisfaction. Zendesk trails on ease of setup — consistent with its depth and configuration complexity. Zoho Desk's ease-of-setup gap versus Help Scout (3.9 vs. 4.6) is the clearest data point supporting the 2–4 week adjustment period reported by teams switching from Help Scout.

## Pre-migration checklist

[Teams that handle migrations cleanly follow this sequence](https://clonepartner.com/blog/blog/help-desk-data-migration-playbook):

- [ ] Audit Help Scout data: count conversations, identify threads approaching 100-message limit, flag merged conversations within 60 days
- [ ] Export reporting data via UI (CSV/XLSX) before canceling or downgrading — this is the only data the UI exports
- [ ] Provision all target-platform user accounts before running any import
- [ ] Map custom fields from Help Scout schema to target platform schema; identify fields with no native equivalent
- [ ] Inventory saved replies (Help Scout API: `GET /v2/responses`) and triage for manual recreation
- [ ] Document all workflows and automation rules with their trigger logic before migration begins
- [ ] Run a test migration on a 500–1,000 conversation sample; verify thread continuity, attachment integrity, custom field population, and agent attribution
- [ ] Confirm inline image handling for your target platform (see import-side table above)
- [ ] Build OAuth token refresh logic into export scripts if your dataset requires more than 48 hours to extract
- [ ] Schedule parallel operation window (both systems active) for a minimum of 5 business days post-cutover

## The real cost isn't the subscription — it's the switching cost

The largest cost in moving off Help Scout is not the monthly seat fee delta. It is engineering time, data validation, workflow re-creation, agent retraining, and the risk window where two systems run in parallel with inconsistent data.

Teams that handle this well plan for it before they pick a vendor. They audit their data volume and structure first. They identify which conversations approach the 100-thread API limit. They build their user accounts in the target before importing a single conversation. They run a test migration on a subset — not the full dataset — and verify thread continuity, custom field mapping, and attachment integrity before going live.

And they account for the things that cannot be automated: saved replies need to be manually ported, [workflows need to be rebuilt from scratch](https://clonepartner.com/blog/blog/how-to-migrate-automations-macros-workflows), and every native integration needs a replacement or a bridge.

> Planning a move off Help Scout? Our engineers will review your current setup, map your data, and scope a migration plan — free, no obligation. We've completed 1,500+ help desk migrations across all major platforms.
>
> [Talk to us](https://cal.com/clonepartner/meet?duration=30)

## Frequently asked questions

### How much does Help Scout actually cost per month in 2026?

Help Scout's Standard plan is $25/user/month, Plus is $45, and Pro is $75 (with a 10-seat minimum). Annual billing saves 16%. But add-ons (extra inboxes at $10/each, Docs sites at $20/each) and AI Answers at $0.75/resolution push real costs 50–90% above the base price for most teams.

### What is the cheapest Help Scout alternative?

Zoho Desk is the cheapest alternative, starting at $7/agent/month (Express plan, annual). Its Enterprise tier at $40/agent/month bundles Zia AI, while competitors charge AI as a separate metered add-on. Freshdesk Growth at $19/agent/month is the next most affordable option.

### Can you export all your data from Help Scout?

Not through the UI. Help Scout's built-in export only covers reporting metrics (CSV/XLSX) — no message bodies, conversation threads, or satisfaction comments. You need the Inbox API 2.0 (OAuth 2.0) for conversation data and a separate Docs API for knowledge base articles. The Free plan has no API access at all.

### How long does a Help Scout migration take?

For a straightforward migration under 50,000 conversations, expect 2–5 days of engineering work using custom scripts. Larger instances with edge cases (merged tickets, 100+ thread conversations, inline images) can take 40–80 engineering hours. Automated migration tools are faster but may miss custom field mapping and inline images.

### What happened to Intercom in 2026?

Intercom rebranded to Fin in May 2026 and was acquired by Salesforce for approximately $3.6 billion. Salesforce completed the acquisition on September 10, 2026. Fin is being folded into Salesforce's Agentforce platform. Existing Fin customers should expect pricing and packaging changes as integration progresses.