Migrate your Folder HelpDesk data
Lightweight shared-inbox help desk for small teams, built around email routing and basic ticket management with minimal configuration overhead.
In its favor
Why people choose Folder HelpDesk
The signal that keeps Folder HelpDesk on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Simple shared inbox model that mirrors email workflows without requiring agents to learn a new interface or complex ticket management concepts.
Low per-agent pricing starting around $20 per month makes it accessible for small support teams of two to ten people.
Fast initial setup with no mandatory configuration steps — connect an email inbox and start assigning tickets immediately.
Responsive customer support cited positively in user reviews, particularly for small-business users needing hands-on help during onboarding.
Minimal feature bloat — the product focuses on ticket receipt, assignment, and tracking without overwhelming small teams with enterprise-grade complexity.
Limited integrations with tools like Slack, Firebase, and other common support stack components causes workflow fragmentation.
Frequent platform updates introduce performance lags that disrupt daily ticket handling for active support teams.
Too many configuration buttons and options accumulate as the product matures, making simple tasks feel over-complicated.
Server connection issues and technical reliability problems affect access continuity and integration stability.
Limited API documentation and customization capabilities frustrate teams with advanced automation or reporting needs.
Reasons to switch
Why people leave Folder HelpDesk
The recurring reasons buyers give for replacing Folder HelpDesk. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Folder HelpDesk 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
Folder HelpDesk pricing overview
Folder HelpDesk uses a per-agent flat-rate model across three tiers, with monthly and annual billing options. The Starter tier targets small teams under five agents, Professional adds reporting depth and customization, and Enterprise unlocks API access and SLA controls under custom contract terms.
Starter
Tier 1 of 3
$20/user/month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Folder HelpDesk's schedule — see our quote-based pricing →
What gets migrated
Folder HelpDesk object support
Object-by-object support for Folder HelpDesk migrations. Per-pair details surface during scoping.
Tickets
Fully supportedTickets are the core object. We preserve subject, body, status, priority, assignee, created/updated timestamps, and conversation history including internal notes. Thread order is preserved via sequential message timestamps.
Customers
Fully supportedEnd-user contact records linked to tickets. We map name, email, phone, and custom fields. Where the destination has a separate Contact/Person object, we split accordingly and maintain the ticket linkage.
Organizations
Mapping requiredCompany-level records grouping multiple customers. Not all helpdesks have this as a distinct object. We map where it exists and merge into the destination's equivalent company/account object.
Agents
Fully supportedSupport team members who can own tickets. We map agent name, email, role, and group assignment. Agent-to-ticket ownership transfers as-is when the destination agent emails exist.
Attachments
Mapping requiredFile attachments on tickets. We preserve filename, MIME type, and binary content. Large attachments or certain file types may require chunked transfer depending on destination API limits.
Tags
Mapping requiredLabels applied to tickets for categorization. We map tag names and apply them to destination tickets. Some destinations use flat tags vs. hierarchical labels, requiring a flatten or prefix strategy.
Custom Fields
Mapping requiredUser-defined fields on tickets or customers. We inspect the source schema pre-migration and generate a field map. Each custom field requires value-type alignment (text, date, dropdown, checkbox) with the destination field.
SLA Policies
Not in this platformSLA rules and breach timers are configuration-level objects that do not export as data. We document the SLA configuration for manual re-creation in the destination and do not attempt to migrate breach state.
Knowledge Base Articles
Mapping requiredPublic help articles. We export title, body HTML, category/section placement, and attachments. Formatting differences between markdown and HTML wikis require content normalization before import.
Macros/ Templates
Mapping requiredPre-written reply templates and automation rules. We export macro text and variable placeholders. Complex conditional logic often requires manual reconfiguration in the destination.
Time Entries
Mapping requiredBillable or tracking hours logged against a ticket. We map time value, agent, and ticket linkage. Not all destinations track time as a distinct object.
Groups/ Teams
Mapping requiredTeam-level routing assignments for tickets. We map group name and membership. Mapping to the destination's team or queue structure requires a pre-migration alignment review.
| Object | Support | Notes |
|---|---|---|
| Tickets | Fully supported | Tickets are the core object. We preserve subject, body, status, priority, assignee, created/updated timestamps, and conversation history including internal notes. Thread order is preserved via sequential message timestamps. |
| Customers | Fully supported | End-user contact records linked to tickets. We map name, email, phone, and custom fields. Where the destination has a separate Contact/Person object, we split accordingly and maintain the ticket linkage. |
| Organizations | Mapping required | Company-level records grouping multiple customers. Not all helpdesks have this as a distinct object. We map where it exists and merge into the destination's equivalent company/account object. |
| Agents | Fully supported | Support team members who can own tickets. We map agent name, email, role, and group assignment. Agent-to-ticket ownership transfers as-is when the destination agent emails exist. |
| Attachments | Mapping required | File attachments on tickets. We preserve filename, MIME type, and binary content. Large attachments or certain file types may require chunked transfer depending on destination API limits. |
| Tags | Mapping required | Labels applied to tickets for categorization. We map tag names and apply them to destination tickets. Some destinations use flat tags vs. hierarchical labels, requiring a flatten or prefix strategy. |
| Custom Fields | Mapping required | User-defined fields on tickets or customers. We inspect the source schema pre-migration and generate a field map. Each custom field requires value-type alignment (text, date, dropdown, checkbox) with the destination field. |
| SLA Policies | Not in this platform | SLA rules and breach timers are configuration-level objects that do not export as data. We document the SLA configuration for manual re-creation in the destination and do not attempt to migrate breach state. |
| Knowledge Base Articles | Mapping required | Public help articles. We export title, body HTML, category/section placement, and attachments. Formatting differences between markdown and HTML wikis require content normalization before import. |
| Macros/ Templates | Mapping required | Pre-written reply templates and automation rules. We export macro text and variable placeholders. Complex conditional logic often requires manual reconfiguration in the destination. |
| Time Entries | Mapping required | Billable or tracking hours logged against a ticket. We map time value, agent, and ticket linkage. Not all destinations track time as a distinct object. |
| Groups/ Teams | Mapping required | Team-level routing assignments for tickets. We map group name and membership. Mapping to the destination's team or queue structure requires a pre-migration alignment review. |
Gotchas
What to watch for in Folder HelpDesk migrations
Issues we've hit on past Folder HelpDesk migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
SLA breach state does not transfer as live data
Email thread metadata parsing varies by source
Custom field schema varies between account plans
Attachment size limits may truncate large exports
| Severity | Issue |
|---|---|
| High | SLA breach state does not transfer as live data |
| Medium | Email thread metadata parsing varies by source |
| Medium | Custom field schema varies between account plans |
| Low | Attachment size limits may truncate large exports |
Leaving Folder HelpDesk?
Where Folder HelpDesk customers move next
7 destinations Folder HelpDesk can migrate to.
How a Folder HelpDesk migration works
Four steps, Folder HelpDesk-specific
Connect
API key into Folder HelpDesk. Scopes limited to read-only on the data we move.
Map
We translate Folder HelpDesk-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Folder HelpDesk quirks before production.
Migrate
Full migration with Folder HelpDesk rate-limit handling. Rollback available throughout.
FAQ
Folder HelpDesk migration FAQ
Answers to the questions buyers ask most during Folder HelpDesk migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Folder HelpDesk 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 Folder HelpDesk.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Folder HelpDesk setup and destination — written quote back within a business day.