Migrate your Herodesk data
Lightweight eCommerce helpdesk built in Denmark, focused on simplicity and multi-channel ticket management for small teams without enterprise complexity or cost.
In its favor
Why people choose Herodesk
The signal that keeps Herodesk on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Lowest cost entry point for small eCommerce teams — Free tier with 1 user and 2 channels lets solo operators validate fit before paying anything.
Tight webshop integrations with Shopify, WooCommerce, Magento, and Prestashop surface order context inside tickets without agents switching tabs.
AI Agents handle automatic replies and translations out of the box, reducing manual triage for teams with international customer bases.
Simple control panel with no technical skills required means support teams set up channels and widgets without developer involvement.
Competitively priced against larger platforms — Herodesk Plus at €14.95/user/month with no usage caps appeals to small and mid-sized webshops.
Teams outgrow the single-user Lite tier quickly when multiple agents need independent Inboxes, forcing an unplanned upgrade to Plus.
No enterprise tier, custom SLAs, or white-glove onboarding limits appeal for growing companies that eventually need enterprise-grade governance and support.
Limited advanced automation capabilities compared to Zendesk or Salesforce Service Cloud — power users report hitting feature ceilings.
Absence of a public bulk-export API makes data portability awkward; teams migrating away must rely on per-object API pulls or manual CSV exports.
Reasons to switch
Why people leave Herodesk
The recurring reasons buyers give for replacing Herodesk. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Herodesk 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
Herodesk pricing overview
Herodesk uses straightforward per-user pricing with three tiers. The Free plan is genuinely free forever, Lite costs €9.95/user/month for solo use, and Plus costs €14.95/user/month with no feature or usage limits. No volume-based surcharges, no AI add-ons, and no enterprise tier exist.
Free
Tier 1 of 3
€0/month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Herodesk's schedule — see our quote-based pricing →
What gets migrated
Herodesk object support
Object-by-object support for Herodesk migrations. Per-pair details surface during scoping.
Customers
Fully supportedCustomers are the core contact records in Herodesk, linked to orders from connected webshops. We map them 1:1 to the destination Contact/Customer object, preserving email, name, and any custom properties.
Tickets (Conversations)
Fully supportedTickets are the primary work unit in Herodesk — they contain the conversation thread, status, assignee, and timestamps. We migrate all open and closed tickets, preserving message history and internal notes.
Inboxes
Mapping requiredInboxes aggregate channels and are tied to user access. On Lite plan only 1 inbox is permitted; Plus supports multiple. We map each Herodesk Inbox to a corresponding team Inbox or label in the destination system.
Channels
Mapping requiredHerodesk supports Email, Facebook, Instagram, and Chat channels per inbox. We map each active channel to the equivalent channel type in the destination and flag any that have no direct equivalent.
Tags and Auto-tagging Rules
Mapping requiredTags are applied manually and by workflow rules. We preserve tag names and map them to Labels or Tags in the destination. Auto-tagging logic requires manual recreation as a workflow in the destination.
Workflow Automations
Mapping requiredHerodesk automations handle routing, auto-replies, and tagging based on a rules engine. These are not directly transferable — we document the active rules and assist the customer in recreating equivalent logic in the destination.
AI Agents
Mapping requiredAI Agents provide automatic replies and translations. We flag whether the destination has comparable AI capabilities; if not, we preserve the agent configuration as a written specification for the customer to evaluate alternatives.
Orders (Webshop Context)
Mapping requiredOrder data from connected webshops (Shopify, WooCommerce, etc.) appears inside Customer and Ticket context. We migrate the linked order references and key fields; full order records belong in the ecommerce platform, not the helpdesk.
Users / Agents
Mapping requiredHerodesk Users map to Agents in most destination helpdesks. We migrate name, email, and role. Lite plan limits to 1 user — we flag this constraint when scoping a migration out of Herodesk.
Attachments
Fully supportedFile attachments on tickets and messages are migrated via the API and re-uploaded to the destination. We handle inline images and documents with original filenames preserved.
| Object | Support | Notes |
|---|---|---|
| Customers | Fully supported | Customers are the core contact records in Herodesk, linked to orders from connected webshops. We map them 1:1 to the destination Contact/Customer object, preserving email, name, and any custom properties. |
| Tickets (Conversations) | Fully supported | Tickets are the primary work unit in Herodesk — they contain the conversation thread, status, assignee, and timestamps. We migrate all open and closed tickets, preserving message history and internal notes. |
| Inboxes | Mapping required | Inboxes aggregate channels and are tied to user access. On Lite plan only 1 inbox is permitted; Plus supports multiple. We map each Herodesk Inbox to a corresponding team Inbox or label in the destination system. |
| Channels | Mapping required | Herodesk supports Email, Facebook, Instagram, and Chat channels per inbox. We map each active channel to the equivalent channel type in the destination and flag any that have no direct equivalent. |
| Tags and Auto-tagging Rules | Mapping required | Tags are applied manually and by workflow rules. We preserve tag names and map them to Labels or Tags in the destination. Auto-tagging logic requires manual recreation as a workflow in the destination. |
| Workflow Automations | Mapping required | Herodesk automations handle routing, auto-replies, and tagging based on a rules engine. These are not directly transferable — we document the active rules and assist the customer in recreating equivalent logic in the destination. |
| AI Agents | Mapping required | AI Agents provide automatic replies and translations. We flag whether the destination has comparable AI capabilities; if not, we preserve the agent configuration as a written specification for the customer to evaluate alternatives. |
| Orders (Webshop Context) | Mapping required | Order data from connected webshops (Shopify, WooCommerce, etc.) appears inside Customer and Ticket context. We migrate the linked order references and key fields; full order records belong in the ecommerce platform, not the helpdesk. |
| Users / Agents | Mapping required | Herodesk Users map to Agents in most destination helpdesks. We migrate name, email, and role. Lite plan limits to 1 user — we flag this constraint when scoping a migration out of Herodesk. |
| Attachments | Fully supported | File attachments on tickets and messages are migrated via the API and re-uploaded to the destination. We handle inline images and documents with original filenames preserved. |
Gotchas
What to watch for in Herodesk migrations
Issues we've hit on past Herodesk migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Lite plan single-user and single-inbox constraint blocks real multi-agent migrations
No bulk-export endpoint means API pulls must be sequenced per object
AI Agents and Workflow Automations are not machine-migratable
| Severity | Issue |
|---|---|
| High | Lite plan single-user and single-inbox constraint blocks real multi-agent migrations |
| Medium | No bulk-export endpoint means API pulls must be sequenced per object |
| Medium | AI Agents and Workflow Automations are not machine-migratable |
Leaving Herodesk?
Where Herodesk customers move next
7 destinations Herodesk can migrate to.
How a Herodesk migration works
Four steps, Herodesk-specific
Connect
API key into Herodesk. Scopes limited to read-only on the data we move.
Map
We translate Herodesk-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Herodesk quirks before production.
Migrate
Full migration with Herodesk rate-limit handling. Rollback available throughout.
FAQ
Herodesk migration FAQ
Answers to the questions buyers ask most during Herodesk migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Herodesk 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 Herodesk.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Herodesk setup and destination — written quote back within a business day.