Open-source alternative to YouTrack Helpdesk: the short answer
If your team pays for YouTrack Helpdesk agents beyond the free three, or your support email must stay on your own servers, Zammad fits multi-team, enterprise-style helpdesk needs and FreeScout fits lighter shared inbox needs, and both can run self-hosted next to a new issue tracker. The key point is that a helpdesk and an issue tracker are separate systems. Neither Zammad nor FreeScout replaces YouTrack's issue model, so the work is to connect a ticketing system to a tracker such as OpenProject, Plane or Redmine, not to find a single product that does both. YouTrack Helpdesk does its job inside JetBrains' ecosystem, and this page is about whether a separate, self-hosted helpdesk is the better fit for your organization.
Zammad is licensed under AGPL-3.0 and is the better match when you need several teams, queues, roles and third-party login through SAML, OpenID Connect or other providers. Its self-hosted install needs PostgreSQL 15 or newer and Redis 7 or newer, and Elasticsearch is optional but strongly recommended for search and for finding text inside email attachments. FreeScout is licensed under AGPL-3.0, runs on PHP and Laravel with MySQL, MariaDB or PostgreSQL, and lists unlimited agents, tickets and mailboxes in its README. Its paid modules, including LDAP Integration and SAML SSO, are sold as lifetime licenses per instance. Confirm which features you need, such as SSO, reporting or SLA rules, against each product's documentation before you pick one. Ask each vendor or consultant for a written quote that lists the modules and support tier you need.
Before you choose, decide how a reporter's email thread will become a development work item and who owns the link back to the customer. Both helpdesks keep the conversation in email, so the tracker needs a stable reference to each ticket, and the reporter should receive updates from the helpdesk, not from the tracker. Test this with a sample thread in a staging environment, and confirm how each product handles replies, attachments and duplicate detection before you commit. That test, along with a list of the email domains and mailboxes to migrate, will show whether Zammad's depth or FreeScout's simplicity suits your environment.
Which YouTrack Helpdesk capabilities Zammad and FreeScout cover
This table maps the helpdesk capabilities teams typically use in YouTrack Helpdesk to Zammad and FreeScout, and marks where each one is a gap or depends on a paid module. Treat each cell as a starting point to verify against the release you plan to deploy, especially for SSO, portal and reporting features. The main takeaway is that neither product links tickets to issue-tracker work items natively, so that link has to be designed and tested as part of the migration.
| Capability | Zammad | FreeScout |
|---|---|---|
| Shared inbox and email threading | Email-first ticketing with threaded conversations. Confirm how reply threading behaves with your mail provider. | Shared mailboxes over SMTP, IMAP and POP3 with conversation threads. Confirm threading with your mail flow. |
| Ticket states and assignment | Configurable states and assignment rules. Confirm the state model matches your triage process. | Statuses and assignment to agents or teams. Confirm workflow depth against your requirements. |
| Agent roles and permissions | Role-based access for agents and administrators. Confirm group-level permissions for your structure. | Agent and admin roles per mailbox. Confirm fine-grained permissions in the current release. |
| Single sign-on | SAML, OpenID Connect, Microsoft, Google, GitHub and GitLab login are documented. | SAML SSO is a paid module on the official modules page. OAuth covers Microsoft 365 and Google Workspace. |
| Customer portal or knowledge base | Customer-facing portal and knowledge base features. Confirm current scope in the release you deploy. | Knowledge Base is a paid module. Confirm what the free core provides for customers. |
| API and webhooks | Application programming interface for tickets and data. Confirm webhook options in your release. | API and Webhooks are a paid module. Zapier and Make integrations are linked from the README. |
| Native link to issue-tracker work items | No native link to YouTrack issues. Plan a ticket reference convention and an integration. | No native link to YouTrack issues. Plan a ticket reference convention and an integration. |
| Reporting | Reporting features depend on search configuration. Confirm with your Elasticsearch setup. | Reporting depends on installed modules and configuration. Confirm the reports you need. |
Zammad or FreeScout: when each fits
Both tools are open-source help desks that can run next to a self-hosted issue tracker and keep reporter email threads in one place. The choice depends on how many integrations, identity features and operational components your team is willing to run, and on how much of the paid module set you expect to need.
Zammad as the full-featured option
Zammad is licensed under AGPL-3.0 and stores its content in PostgreSQL 15 or newer, with Redis 7 or newer for realtime updates. Elasticsearch is optional but strongly recommended for search, reporting and attachment content, and multi-instance deployments need Memcached. SAML, OpenID Connect and other third-party logins are included. Plan for the extra services and confirm which deployment method your platform team will support, since Zammad documents package installation, Docker Compose and a Helm chart.
FreeScout as the lightweight option
FreeScout is licensed under AGPL-3.0 and built with PHP on Laravel. It runs on Nginx, Apache or IIS with MySQL, MariaDB or PostgreSQL, and its README describes no minimum CPU or RAM requirements. Unlimited agents, tickets and mailboxes are listed in the README, which suits a team that mainly needs a shared inbox that feeds development tickets. Confirm the PHP and database versions your environment supports before you commit.
Single sign-on and API costs
In FreeScout, LDAP integration, SAML SSO and the API and webhooks sit in paid modules sold as lifetime licenses for a single instance. Zammad includes third-party login in the product. If your identity provider and ticket-to-issue routing are required from day one, price the FreeScout modules against the Zammad support tiers and the engineering time to build the integration yourself.
Routing tickets to development work
Routing reporter emails into development work items usually requires a webhook or API call from the help desk to the issue tracker. FreeScout's API and webhooks module is a paid add-on, while Zammad exposes its API as part of the product. Either way, test the link with a sample bug report and confirm that the reporter's email thread and ticket reference survive the round trip.
Support and upgrade model
Zammad sells self-hosted support subscriptions, and its release line includes security fixes on more than one major series at the same time. FreeScout releases roughly weekly and relies on the community and paid module vendor for help. Ask who will patch the server within your change window, how long older lines receive security fixes, and whether a support contract is required for compliance evidence.
Pilot checks before you choose
Run both tools against a copy of one real mailbox for two weeks, measuring how long threads take to import, how attachments are indexed, and whether shared inbox assignment matches your team's routing. Check that SMTP and IMAP settings, OAuth for Microsoft 365 or Google Workspace, and backup restore all work before production cutover.
How tickets route to development work items
The core pattern is simple to state: a support email arrives in Zammad or FreeScout and becomes a ticket, the ticket is linked to a work item in the new issue tracker, and the reporter stays on the original email thread so replies still reach them. Engineers work in the tracker, support works in the help desk, and the link between the two is the only thing that connects them. Before any build starts, confirm the exact link logic against the chosen tracker's API, because the field names, permissions and link types differ between OpenProject, Plane and Redmine and must be checked on the version you will run.
Integration options differ by help desk. FreeScout can use its API and webhooks, which are part of its paid API and Webhooks module, and it can also connect through Zapier or Make, which suits simple one-way creation of work items but adds a third-party service to the data path. Zammad has no ready-made connector to the trackers covered here, so the link is typically custom development against the Zammad API and the tracker's API, scoped in writing before work starts. In both cases, the reporter's email address and ticket number should be written into the work item so that engineers can answer the customer from the tracker without losing the thread.
Two design decisions prevent most failures. First, define a shared reference field on both sides: a ticket number stored on the work item and a work item ID stored on the ticket, so every link can be traced in either direction and duplicates can be detected. Second, write a sync rule for status changes: decide which tracker states close or reopen a ticket, whether comments flow back to the reporter, and who may change the state from each side. Test the rule with reporter replies, reopened work items and tickets merged in the help desk, since these edge cases are where synchronized records usually diverge.
Keeping reporters' email threads intact
The first decision is which mailbox the help desk reads and sends from, because that determines whether a reply lands in the right ticket. FreeScout connects to mailboxes over IMAP and POP3 and sends through SMTP, and its README lists OAuth for Microsoft 365 and Google Workspace, so a shared support address can stay where it is. Confirm how Zammad handles mailbox connections and OAuth in the version you deploy, since the sources reviewed here cover its third-party login rather than its mailbox channels. Threading depends on standard email headers: the Message-ID on each outgoing notification and the In-Reply-To and References headers on the reporter's reply. The help desk matches replies to tickets through these values, so any gateway, relay or signature tool that rewrites headers will break threads silently. Check each hop before cutover.
Reporters who reply to old YouTrack notifications are the main migration risk. Those messages carry YouTrack's sender address and Message-IDs that the new help desk has never issued, so without preparation they arrive as new tickets with no link to the original issue. Identify every sender address YouTrack used for notifications, keep those addresses forwarding to the new mailbox for as long as reporters still reply to them, and decide how replies to pre-cutover threads will be attached to migrated tickets. Ask the team that owns reporter communication how long old notifications stay in circulation, since that sets how long forwarding must run. Also confirm with the vendor whether historical message headers can be imported, because the documented Zammad migrators cover Freshdesk, Kayako, OTRS and Zendesk, not YouTrack.
Test with live threads in a pilot mailbox before cutover, and keep that mailbox separate from production. Select a small set of threads that cover the cases that usually fail: a new question, a reply to a notification sent before cutover, a message with an attachment, a reply from a Gmail or Outlook account, and a reply-all with several recipients. Send each one through the pilot and check that the reply attaches to the correct ticket, that the reporter sees the expected sender and subject, that attachments arrive intact, and that the ticket links to the matching work item in the new tracker. Log every failure, fix the cause, and rerun the full set after each configuration change. A pass on a single thread type does not show that the others will attach correctly.
Migrating YouTrack Helpdesk tickets and mailboxes
This sequence moves reporter email threads, open tickets and agent routing from YouTrack Helpdesk to a self-hosted help desk, while keeping links to development work items intact through the cutover.
Inventory mailboxes, tickets, agents and automations
The help desk owner lists every inbound mailbox or address that reaches YouTrack Helpdesk, every open and recently closed ticket, each agent account, and every automation, rule or notification that routes or answers requests. Record which tickets link to YouTrack issues in the development projects, because those links must survive the move. Confirm with JetBrains, or in your own YouTrack administration, which export formats and fields are available for tickets, attachments and comments, since the export format specific to YouTrack Helpdesk must be verified before you plan the import. The step is done when you have a written inventory signed off by the support lead and the development lead.
Choose the target helpdesk
Decide between Zammad and FreeScout based on the inventory. Zammad needs PostgreSQL 15 or newer, Redis 7 or newer for realtime updates, and a reverse proxy such as Nginx or Apache, with Elasticsearch optional but strongly recommended for search and attachment content. FreeScout runs on PHP with MySQL, MariaDB or PostgreSQL and has lighter requirements. Check the requirements page for the version you plan to deploy, and confirm that the mailbox types you use (SMTP, IMAP, POP3, or OAuth for Microsoft 365 and Google Workspace) are supported by your chosen tool. The step is done when the platform, hosting model and license implications are recorded in the migration plan.
Export tickets and map them to the target format
Export tickets, comments, attachments and agent assignments from YouTrack Helpdesk in the format the vendor confirms. If Zammad has a built-in migrator for the source system, use it, since Zammad includes migrators for Freshdesk, Kayako, OTRS and Zendesk. For YouTrack Helpdesk, expect to write a custom import through the Zammad API or to have DeployOpen or Zammad build one, and ask for that scope in writing. Map ticket states, groups, priorities and customer records to the target help desk. The step is done when a test import of a sample set of tickets produces a matching count, correct requesters and intact attachments.
Map states, agents and customer records
Agree a mapping table that links each YouTrack Helpdesk state to a target state, each agent to a target user, and each reporter to a single customer record so that repeat senders do not split into duplicate profiles. Set up the target's login integration if your organization uses SAML, OpenID Connect, or Microsoft and Google accounts, so agents sign in with the identity they already use. The step is done when the agents review the mapping, sign off on it, and a second test import confirms that agent assignment and customer matching behave as expected.
Preserve links to development work items
Where a helpdesk ticket relates to a development issue, store the reference to the new work item tracker in an internal note or custom field on the ticket, and record the reverse link in the work item. Test the links on a sample set before the cutover, because broken references are hard to find later. The step is done when a reviewer can open a migrated ticket, follow the link to the work item in the new tracker, and see the ticket reference recorded on the work item side.
Cut over mail routing
Change the MX records or forwarding rules so that new messages to the support address reach the target helpdesk, and disable YouTrack Helpdesk mail collection only after the new route is confirmed. Verify that replies from agents go out with the correct sender address and that reporters' threads keep their subject lines and message identifiers, so their email clients group the replies properly. Plan the change with your mail administrator and record the time of the switch. The step is done when test messages sent from outside the organization arrive in the new helpdesk and replies reach the sender.
Run both systems until open threads close
Keep YouTrack Helpdesk available in read-only use for open threads until every ticket that was open at cutover is closed, or has been moved and confirmed. Monitor for any messages that still reach the old mailbox and forward them to the new helpdesk. Confirm with your vendor and your retention policy how long the old data must be kept before archival or deletion. The step is done when no open ticket remains in the old system, forwarding has stopped receiving mail, and the retained export is stored under your records policy.
Running the helpdesk next to the rest of the suite
Once Zammad or FreeScout sits beside the new tracker, four decisions shape daily use: who signs in and how, where reporting lives, where customers find answers, and which system owns development work. Settle each one before cutover so the helpdesk does not quietly become a second tracker.
Identity and single sign-on
Zammad supports third-party login through SAML, OpenID Connect, Microsoft, Google, GitHub and GitLab, among other providers. FreeScout offers SAML SSO and LDAP as paid modules, so its identity cost is a licensing question as well as a configuration one. Confirm which identity provider your agents already use, whether group membership maps to helpdesk roles, and how deprovisioning reaches both the helpdesk and the tracker.
Reporting boundaries
Helpdesk reports cover response times, ticket volume and agent workload, while tracker reports cover development throughput. Decide which dashboards each team owns and export the fields you need into a shared view, instead of rebuilding one report across both systems. Ask the reporting owner to list every metric they rely on today so nothing is lost at cutover.
Knowledge base choices
Self-service articles can live in the helpdesk, in a separate wiki, or in the tracker's own pages. FreeScout offers a Knowledge Base module as a paid add-on, while Zammad includes knowledge base features in the product. Pick one canonical location, link to it from ticket templates, and assign an owner who reviews articles that describe development fixes.
Tracker as system of record
A ticket that becomes a bug or feature should create one work item in the new tracker, and the helpdesk should keep only the customer conversation. Store the work item link on the ticket and the ticket reference on the work item, and agree who closes each side. Test this with a few illustrative cases before you rely on it, because duplicate items and orphaned tickets are the usual failure.
Email integration and mailboxes
Both products pull mail over IMAP and send through SMTP, and FreeScout also offers OAuth for Microsoft 365 and Google Workspace. Confirm which mailboxes route to the helpdesk, how replies thread back to the original reporter, and how automated notifications from the tracker avoid creating new tickets. Mail routing mistakes are hard to undo once customers have replied.
Cost, effort and what you need to run it
What replaces the YouTrack Helpdesk per-agent fee with Zammad or FreeScout?
Self-hosted Zammad carries no license fee, so the per-agent charge is replaced by the infrastructure, mail and staff time you already pay for, plus an optional Zammad support subscription. Zammad sells self-hosted support subscriptions named Business at 2,999 EUR per year, Enterprise at 5,999 EUR per year and Corporation at 9,999 EUR per year, according to its pricing page. FreeScout is licensed under AGPL-3.0 and advertises unlimited agents and mailboxes, but its paid modules are sold as lifetime licenses per instance, so ask which modules you need before comparing totals. Confirm current prices with each vendor, because the cost of a support tier does not depend on your agent count in the same way YouTrack's fee does.
Which costs recur after a self-hosted help desk goes live?
Recurring costs fall into four groups:
- Servers or cloud instances for the help desk, database, Redis and, where used, Elasticsearch and Memcached.
- Mail infrastructure, including the SMTP and IMAP service and any relay you use for outgoing ticket notifications.
- Staff time for patching, backups, upgrades and monitoring, because Zammad releases such as 7.2.1, 7.2.2 and 6.5.5 ship security fixes you must apply.
- Optional support subscriptions or a retainer for upgrades and testing.
One-time costs are the migration, mailbox configuration, integration with your issue tracker and the initial hardening. Ask any implementation partner to separate these two groups in the written scope.
How long does a help desk migration take and what drives the timeline?
The timeline depends on the number of mailboxes, the volume of historical tickets you keep, how many attachments must move, and how many systems you connect to the help desk. Zammad includes migrators for Freshdesk, Kayako, OTRS and Zendesk, while other systems need the Zammad API or custom development from Zammad, so a source that is not on that list usually adds the most effort. FreeScout offers a migration service from other help desks, which you should ask about for your source system. No supplied figure gives a duration, so request a timeline from your provider based on a written inventory of mailboxes, ticket counts and integrations.
Can an internal IT team run Zammad or FreeScout without outside help?
Yes, if your team already runs Linux services, PostgreSQL and a reverse proxy, but the first deployment and the migration are where most teams need extra skills. Zammad documents package installation, Docker Compose and a Kubernetes Helm chart, though on Kubernetes its support covers only the Zammad application and not Kubernetes-specific issues. FreeScout runs on Nginx, Apache or IIS with PHP and MySQL, MariaDB or PostgreSQL and lists a Docker image. Decide early who owns upgrades, because a help desk that falls behind on security releases creates risk for every customer email it holds.
What does the project need from our side before implementation starts?
You need to provide named owners for mail domains, identity, the existing issue tracker and the hosting environment, plus access to the source help desk for export. Ask for a list of the mailboxes, folders and shared inboxes that receive reporter email, the routing rules that send tickets to development work items, and the retention rules that apply to old conversations. Your security and compliance leads should confirm where ticket data and attachments may be stored. DeployOpen implements, integrates, hardens, backs up and documents self-hosted platforms in your own infrastructure under a written, fixed scope, and it prepares evidence for compliance assessments without issuing audit reports.
Do I need a FreeScout module to get single sign-on for agents?
Single sign-on for FreeScout agents is listed as a paid module, SAML SSO, which sits alongside LDAP Integration in FreeScout's module catalog. Zammad, by comparison, supports third-party login through SAML, OpenID Connect, Microsoft, Google, GitHub and GitLab, among other providers, without a separate module purchase listed in the supplied facts. Confirm which login path your identity provider needs and whether the module fits your environment before you choose. Also check whether a module license covers a single FreeScout instance, because a staging copy may need its own license.
How do I size Elasticsearch and Memcached for Zammad?
Elasticsearch is optional for Zammad but strongly recommended, because it speeds up search, supports reporting and indexes email attachment content, so size it for your ticket and attachment volume and expect it to be the largest component to tune. Memcached is needed for multi-instance Zammad deployments such as containers or cluster nodes, while a single installation can use the file system cache. Start with a single-node design unless you need redundancy, then confirm exact resource numbers with Zammad's software requirements page and load-test with a copy of your real ticket history before go-live.
What the cost of ownership is made of
The software license is the smallest and simplest line in a self-hosted Zammad or FreeScout deployment. Zammad is licensed under AGPL-3.0 and has no license fee when self-hosted, and FreeScout's core is AGPL-3.0 licensed as well. The costs that matter sit around the software: a server for the application, a PostgreSQL or MySQL-family database, Redis for Zammad's realtime features, and Elasticsearch and Memcached where the deployment needs search or multi-instance caching. Each of these is infrastructure a team builds, hosts, patches and monitors. Mail infrastructure is often the most underestimated item. A help desk is only as good as its inbound and outbound email, so the quote should cover mailbox connections, SMTP relay, SPF, DKIM and DMARC records, and OAuth setup for Microsoft 365 or Google Workspace.
Some costs are one-time and others recur. One-time work includes architecture, installation, the integration build that links helpdesk tickets to YouTrack issues, email routing and migration of historical threads. Recurring work includes backups, patching, version upgrades, monitoring, on-call response and agent administration. Paid features are a separate decision. Zammad sells self-hosted support subscriptions at 2,999 EUR per year for Business, 5,999 EUR per year for Enterprise and 9,999 EUR per year for Corporation, according to its pricing page. FreeScout sells module licenses per instance, including LDAP Integration, SAML SSO and API and Webhooks, and lists the AI Integration and S3 Storage modules as free. Confirm which modules your identity, reporting or integration requirements actually need before you compare totals.
When you request a written quote, ask each provider to separate the items above and state the basis for each. Ask for the backup scope and restore test frequency, the upgrade approach for both major and security releases, the named staff or partner hours for integration and migration, and what support covers on Kubernetes if you choose the Helm chart. Ask FreeScout for the module list and license terms for each instance, and confirm how many mailboxes and environments the quote assumes. For your own internal estimate, record staff time for administration and on-call support as a recurring cost. DeployOpen provides fixed-scope implementation, integration, backup and upgrade work against a written scope, so ask for the same breakdown from any implementation partner you compare.
How DeployOpen works on this
DeployOpen plans, implements, integrates, hardens, documents and supports self-hosted open-source platforms inside your own infrastructure. For a helpdesk replacement, that means agreeing the mail flows, ticket-to-work-item links and data handling in writing before any build starts, then delivering the system in your cloud account, data center or air-gapped network.
How we scope
- Written scope lists the mailboxes, reporter groups and agent roles that Zammad or FreeScout will handle.
- Scope records how ticket-to-issue links will reach your tracker, including which fields are mapped and which are not.
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts.
How we build
- Deploy the helpdesk with PostgreSQL, Redis and a reverse proxy in your environment, following the documented installation path.
- Configure SMTP, IMAP and OAuth mail connections so reporters' email threads stay intact and replies thread correctly.
- Test email routing, attachment handling, SSO login and the link from helpdesk tickets to development work items before go-live.
How we hand over
- Deliver runbooks covering mail connectors, backups, upgrades and the ticket-to-issue linking process for your team.
- Document data flows, retention settings and access roles so your compliance lead can review them against your own requirements.
- Run a knowledge transfer session with the agents and administrators who will operate the helpdesk after the engagement ends.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after the initial handover.
- Retainers can cover tracking of security releases for the helpdesk and the integration components you run.
- Ask any provider, including DeployOpen, to confirm which versions and integrations are covered in writing.
