Skip to content
Get a quote

Help Scout to Zendesk migration

We migrate Conversations, Customers, Docs articles, and attachments from Help Scout into Zendesk with the requester email-to-user resolution handled upfront, custom fields pre-created in Zendesk, and the knowledge base hierarchy preserved as Help Center sections and articles before cutover.

Short answer

FlitStack AI migrates tickets, end users, view + groups, ticket fields and help centers from Help Scout to Zendesk, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 2-3 weeks.

By

Source Help Scout
DestinationZendesk
TicketEnd UserView + GroupTicket FieldHelp Center
Mapped field by field · sample run · one-click rollback

What moves from Help Scout to Zendesk?

Moving from Help Scout to Zendesk is a structural migration from an email-first shared inbox to a full ticketing system.

Read the full summary

Help Scout uses Conversations with thread-based replies and internal notes organized in Mailboxes; Zendesk uses Tickets with comments, public updates, and private comments in a Views and Groups structure. We extract Conversations and Customer records via the Help Scout Inbox API, resolve requester email addresses against the Zendesk End User table, and map Custom Fields (Dropdown, Single line, Multi line, Number, Date) to typed Zendesk ticket fields only after confirming the account plan gates. Docs articles organized in Collections migrate to Zendesk Help Center sections and articles with the full hierarchy intact. Workflows, automations, macros, and Saved Replies do not migrate as code; we deliver a written inventory for the customer's admin to rebuild in Zendesk Admin Center. Reports data is not accessible via Help Scout API and must be exported manually from the Reports UI before migration begins.

1:1

Conversation → Ticket

Help Scout Conversations map directly to Zendesk Tickets.

How it maps

We export the full thread history including public replies, internal notes, and attachment references via the Inbox API. The Help Scout thread structure (message sequence, agent vs customer attribution, timestamp) maps to Zendesk Ticket comments with the is_public flag set appropriately. Status (Active, Pending, Solved, Spam) maps to Zendesk Ticket Status (Open, Pending, Solved, Spam). Note that Help Scout does not have a ticket type field, so any problem-incident relationships from Zendesk or other platforms will not be preserved as linked tickets in Help Scout, and this relationship cannot be reconstructed during migration.

1:1

Customer → End User

Help Scout Customer records map to Zendesk End Users.

How it maps

We export all standard customer properties (email, first name, last name, phone, address, company) and preserve Customer Properties custom fields set at the customer record level. Email is the primary lookup key. If a Zendesk End User with the matching email already exists, we link the ticket requester to that record. If no match exists, we create the End User first so that the Ticket requester reference is satisfied at import time. Zendesk End Users do not count against agent-seat billing.

configuration

Mailbox → View + Group

Help Scout Mailboxes are shared inbox containers that hold conversations.

How it maps

Zendesk does not have a direct Mailbox equivalent; conversations live in a central ticket pool filtered by Views. We map each Help Scout Mailbox to a Zendesk View (defining the filter criteria: inbox assignment, status, assignee) and optionally to a Zendesk Group (for team-based routing and assignment). Each Mailbox's custom fields (up to 10 on Help Scout Plus) map to Zendesk Ticket Fields scoped to the resulting Views. The customer chooses the View-and-Group structure during scoping based on team topology.

mapping

Custom Field → Ticket Field

Help Scout Custom Fields (Dropdown, Single line, Multi line, Number, Date) are gated behind the Plus plan and exist per Mailbox.

How it maps

We map them field-by-field to Zendesk Ticket Fields of the matching type. Dropdown fields migrate options to Zendesk tag values or dropdown field options. Critical constraint: Zendesk requires ticket fields to exist before import. We detect the account's plan tier during scoping and either pre-create the fields via the Zendesk API or flag the need to upgrade before migration proceeds. Accounts on Free or Standard do not have Custom Fields in their Help Scout schema, so this object is absent for those tiers.

1:1

Docs (Knowledge Base) → Help Center (Guide)

Help Scout Docs articles organized within Collections map to Zendesk Help Center sections and articles.

How it maps

We export article content, categories, navigation hierarchy, and metadata via the Docs API. Published status and author attribution are preserved. The Collection hierarchy maps to the Help Center section nesting structure. Help Center activation in Zendesk requires a Suite plan (Team at $55/agent or above); we confirm the Zendesk plan tier before migration. Docs articles do not include the Beacon live chat widget configuration, which requires separate Zendesk widget setup post-migration.

1:1

Tag → Tag

Help Scout Tags are applied across Conversations, Customers, and Docs.

How it maps

We preserve all tag assignments during migration and map them directly to Zendesk Tags, which function identically as cross-object labels. Tags on Conversations become Zendesk Ticket tags; Tags on Customers become Zendesk End User tags. The customer may choose to consolidate or rename tags during scoping if the existing taxonomy is overly broad.

What moves10 objects
Help ScoutZendesk
  • ConversationTicket1:1
  • CustomerEnd User1:1
  • MailboxViewtransformed
  • Custom FieldTicket Fieldtransformed
  • DocsHelp Center1:1
  • TagTag1:1

+ 4 more in the mapping below

How Help Scout and Zendesk differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionHelp ScoutZendesk
Core object modelConversations in Mailboxes with thread-based repliesTickets organized in Views with comments and private replies
Contact modelContact-based pricing with unlimited usersPer-agent pricing; contacts do not count against billing
Omnichannel depthEmail and live chat only; phone and SMS via integrationsNative email, chat, phone, SMS, WhatsApp, and community forums
SLA managementNot available natively; no SLA timers or breach escalationFull SLA policies with response and resolution timers from Suite Team ($55/agent)
Knowledge base packagingDocs with Beacon widget; Free plan includes 1 Docs siteHelp Center included in Suite plans; Guide adds self-service articles and community
Workflow automationWorkflows with basic trigger-and-action rules; AI Drafts on all plansTriggers, Automations, and Macros from Suite Team; AI add-ons at extra cost
Reporting data accessCSAT and response-time reports UI-only; no API exportComprehensive reporting API; SLA and agent metrics available

What to watch for in a Help Scout to Zendesk migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Requester email resolution requires End User pre-creation

Help Scout's API export provides the customer email address as the requester identifier for each Conversation, but no pre-existing Zendesk User record ID.

How we handle it

During migration, we must resolve each email against the Zendesk End User table: if a matching End User already exists, we link the Ticket requester to that record; if not, we create the End User first. This two-pass approach (Users first, then Tickets) prevents orphaned tickets with null requesters. A LinkedIn migration case study from May 2025 documented this exact hurdle for an 8,000-ticket migration, noting that failing to resolve requesters results in tickets without a customer link in Zendesk.

high

Organization custom fields do not transfer by default

Help Scout does not have a native Organization object; company data lives on the Customer record.

How we handle it

During migration from Help Scout to Zendesk, Organization-level custom fields from other source platforms (or custom fields set on company properties in Help Scout) do not migrate automatically. A migration service (Help Desk Migration) explicitly states that organization custom fields require a Custom Demo with support team involvement. We either create Zendesk Organizations from the Help Scout customer company field and map company-level custom fields to Organization fields, or we flag this scope for manual configuration after migration.

high

Custom fields must exist in Zendesk before import

Help Scout Custom Fields (Dropdown, Single line, Multi line, Number, Date) are gated behind the Plus plan and must be pre-created in Zendesk with matching field types before any ticket data containing those fields can be imported.

How we handle it

If Zendesk's Admin Center does not have the corresponding ticket fields created, the import fails silently or produces null values. We detect the Help Scout account's plan tier during scoping, confirm the Plus-plan Custom Fields schema, and pre-create all equivalent Zendesk Ticket Fields via the Zendesk API before the migration phase begins. Free and Standard plan accounts have no Custom Fields in their Help Scout schema, so this step is skipped for those tiers.

medium

Workflows and Macros do not migrate as code

Help Scout Workflows automate actions based on triggers such as conversation status, mailbox, or customer properties.

How we handle it

Zendesk uses Triggers, Automations, and Macros as separate objects with a different rule engine. These are fundamentally different automation models with no direct 1:1 mapping. We do not migrate Workflows or Saved Replies as code. We deliver a written inventory of every active Help Scout Workflow with its trigger conditions, actions, and a recommended Zendesk Trigger or Automation equivalent, plus a list of Help Scout Saved Replies that need to be recreated as Zendesk Macros. The customer's Zendesk admin rebuilds these post-migration.

medium

Help Center must be activated before Docs migration

Zendesk Help Center (previously Guide) is only available on Suite plans starting at Team ($55/agent).

How we handle it

If the customer's Zendesk account is on a lower plan or Help Center is not yet enabled, the Docs articles and Collections from Help Scout cannot be imported. We confirm the Zendesk plan tier and Help Center activation status during scoping. If Help Center is inactive, we either defer the Docs migration until the account is upgraded, or we deliver the Docs content as structured JSON for manual import once the plan is activated.

How the migration runs

  1. Discovery and plan confirmation

    We audit the source Help Scout account across plan tier (Free/Standard/Plus), conversation volume (active, closed, archived), customer record count, Docs article and Collection count, Custom Field schema, active Workflows, tag taxonomy, and user/team roster.

    What this step covers

    We pair this with a Zendesk account review: plan tier (Suite Team/Growth/Professional/Enterprise), Help Center activation status, existing ticket field configuration, existing User roster, and Group structure. The discovery output is a written migration scope document specifying record counts per object, the Custom Field mapping matrix, the Mailbox-to-View-and-Group mapping, and the Docs-to-Help-Center section hierarchy.

  2. Schema pre-creation in Zendesk

    Before any data moves, we pre-create the destination schema in Zendesk via the Zendesk API.

    What this step covers

    This includes Ticket Fields matching every Help Scout Custom Field by type (Dropdown options, Single line, Multi line, Number, Date), Help Center sections matching the Docs Collection hierarchy, and Groups matching the Help Scout team structure. We also temporarily disable Zendesk Triggers and Automations that might fire on imported tickets and interfere with migration data. Required field validation and conditional field rules are reviewed and relaxed during the import window to prevent record rejection.

  3. End User reconciliation

    We extract every distinct Customer email from Help Scout and match against the Zendesk End User table.

    What this step covers

    For each email without a matching Zendesk End User, we create the End User record first so that the Ticket requester reference is satisfied at import time. For emails that already exist in Zendesk (from a prior integration or previous data), we link the Ticket to the existing End User. This two-phase approach prevents orphaned tickets with null requesters and is validated before the conversation migration phase begins.

  4. Sandbox migration and reconciliation

    We run a full migration into a Zendesk Sandbox (if available on the destination plan) using a representative data sample.

    What this step covers

    The customer's support operations lead reconciles record counts (Conversations in, Tickets in; Customers in, End Users in; Articles in, Help Center articles in), spot-checks 25-50 random ticket threads against the Help Scout source for message ordering and internal note preservation, and verifies tag assignments and Custom Field values. Any mapping corrections are applied before production migration begins. This step also validates that the Mailbox-to-View mapping produces the expected filter results.

  5. Production migration in dependency order

    We run production migration in record-dependency order: End Users (from Customers, first pass for reconciliation), Groups (from Teams), Articles and Sections (from Docs Collections via Docs API), then Conversations (as Tickets with thread history, internal notes as private comments, attachments re-attached).

    What this step covers

    Custom Field values are set per-ticket after field creation is confirmed. Tags are applied as Zendesk tags on the ticket record. Each phase emits a row-count reconciliation report before the next phase begins. We pace API calls to respect Help Scout's per-account rate limit measured in the 10-minute window, using exponential backoff on 429 responses and chunking batches for accounts over 10,000 conversations.

  6. Cutover, Docs finalization, and handoff

    We freeze Help Scout writes during the cutover window, run a final delta migration of any conversations modified during the migration run, then confirm Zendesk as the system of record.

    What this step covers

    We deliver the Docs content handoff as structured JSON matching the Help Center section hierarchy, the Workflow and Saved Reply inventory document with recommended Zendesk equivalents, and the Custom Field mapping matrix. We support a 72-hour post-migration window where we resolve any ticket threading issues, attachment failures, or End User linkage gaps. We do not rebuild Help Scout Workflows as Zendesk Triggers or configure Help Scout Docs equivalents in Zendesk as part of the migration scope.

Help Scout Zendesk
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · ZendeskRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

2-3 weeksTypical, smaller accounts
5-7 weeksLarge or heavily customised accounts

A quote scales with conversation volume, knowledge base article count, and custom field complexity. Help Scout contact-based billing ends on migration day. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Help Scout to Zendesk →

Why teams move from Help Scout to Zendesk

  • Help Scout's 2024 pricing shift from contact-based to interaction-based billing made monthly costs unpredictable and triggered bill shock for established accounts. A Reddit thread from mid-2025 describes teams receiving notice of the model change and immediately evaluating alternatives. Zendesk's per-agent pricing is more predictable for support teams with high contact volumes, as agent-seat licensing does not fluctuate with conversation counts.
  • Help Scout lacks native SLA timers, skill-based routing, and advanced trigger conditions that enterprise and high-volume support teams require. Feature comparisons across Featurebase, Desk365, and Soft Galley consistently note that Help Scout's Workflows cover day-to-day automation but do not support SLA breach escalation, weighted ticket routing, or multi-condition triggers. Zendesk's Suite Team plan and above includes SLA policies, and Suite Professional adds skills-based routing.
  • Reporting in Help Scout is shallow and data is not accessible via API. Historical CSAT scores, response times, happiness ratings, and channel reports must be manually exported as CSV or XLSX from the Reports UI. Multiple comparison reviews on G2 and Capterra cite limited analytics as a reason for switching to Zendesk, which provides a full reporting API with SLA metrics, agent performance dashboards, and customizable report builder from Suite Team onward.
  • Help Scout supports approximately 100 integrations versus Zendesk's over 1,500 apps on the Marketplace. Teams with complex enterprise tech stacks (ERP connectors, CPQ tools, contract lifecycle management, revenue intelligence platforms) cite the integration depth as a primary driver. eesel's 2026 comparison specifically notes that Zendesk's marketplace breadth accommodates even the most complex enterprise stacks, while Help Scout's ecosystem is suited for common tools.
  • Help Scout's email-first shared inbox lacks native phone and SMS channels, community forums, and deep omnichannel routing. Teams requiring voice support must bolt on third-party VOIP tools. Zendesk natively supports phone with call routing and recording, SMS, and community forums as standard features on Suite plans. The Tidio and Featurebase comparisons both note this gap explicitly, with Zendesk offering a complete omnichannel suite versus Help Scout's email-and-chat focus.

Questions, answered

Help Scout to Zendesk migration questions

How long does a Help Scout to Zendesk migration take?

Most migrations land between two and three weeks for accounts under 5,000 conversations and 500 customers with no knowledge base or a small Docs library under 100 articles. Migrations with large knowledge bases (500+ Docs articles across multiple Collections), active custom field schemas, or multi-mailbox routing structures move to five to seven weeks because of Docs API extraction time, Help Center section hierarchy reconstruction, and per-field type validation. The primary variable is data volume and knowledge base complexity, not team size.

Do Help Scout Workflows and Saved Replies migrate to Zendesk?

No. Help Scout Workflows and Zendesk Triggers are different automation models with different rule engines, triggers, and action types. We do not migrate them as code. We deliver a written inventory of every active Help Scout Workflow with its trigger conditions, actions, and a recommended Zendesk Trigger or Automation equivalent, plus a list of Saved Replies that need to be recreated as Zendesk Macros. The customer's Zendesk admin rebuilds these post-migration. Workflow rebuild is outside standard migration scope.

Will our Help Scout Docs knowledge base migrate to Zendesk Help Center?

Yes, provided the Zendesk account is on a Suite plan with Help Center enabled. We export all Docs articles, Collections, and navigation hierarchy via the Docs API and reconstruct them as Zendesk Help Center sections and articles with the full hierarchy intact. Published status and author attribution are preserved. If Help Center is not yet activated in Zendesk, we either defer this phase until the account is upgraded or deliver the Docs content as structured JSON for manual import. The Beacon live chat widget configuration does not migrate and requires separate Zendesk widget setup.

Can we keep Help Scout Docs as a standalone knowledge base and not migrate it to Zendesk?

Yes. If the customer prefers to keep Help Scout Docs as a standalone knowledge base (perhaps for its Beacon widget and standalone publishing workflow), we scope it out of the migration. The Docs knowledge base would remain accessible at its existing URL and would not be deactivated as part of the Zendesk migration. The customer should plan to update any Zendesk articles or links pointing to the Help Scout Docs domain accordingly. Docs site costs ($20/month annual) continue on the Help Scout side if the account is not fully decommissioned.

Do historical Help Scout reports and CSAT scores migrate?

No. Historical report data including CSAT scores, happiness ratings, response times, and channel reports cannot be extracted via the Help Scout API; it is only available as a manual CSV or XLSX export from the Reports UI. We do not migrate reporting metrics programmatically. We ask customers to export Reports data manually before migration if they need to preserve historical analytics in an external BI tool. Zendesk's reporting API is available post-migration for ongoing analytics.

What happens to internal notes in Help Scout conversations?

Help Scout internal notes (private messages visible only to agents) migrate to Zendesk as private comments on the Ticket. We set the is_public flag to false during import so that they remain visible only to agents. The customer should verify that the Zendesk account's privacy settings allow Light Agents and Agents to view internal notes, as this is configurable in Zendesk Admin Center. Ticket requesters (End Users) will not see the migrated internal notes if permission settings are left at default.

What Zendesk plan is required to receive the migration?

Zendesk Suite Team at $55 per agent per month is the minimum plan that includes the core ticketing API, Views, Groups, and Help Center (Guide). Suite Growth ($89/agent) adds additional features. If the customer needs advanced features like skill-based routing, Advanced AI, or Quality Management, Suite Professional or Enterprise is required. We confirm the target plan tier during scoping and flag any feature dependencies (such as Help Center for Docs migration) before migration begins.

Get a quote

Moving from Help Scout to Zendesk?

Tell us roughly how many records and objects you have. We scope the mapping and the Zendesk setup with you, then send a quote.

Get a quote