Zendesk vs FreeScout: when a shared email inbox on your own server is the right fit
If your renewal is pushing you to ask where support data lives and what the help desk will cost once modules and agents are counted, the first question is whether your team actually needs a managed suite. Zendesk fits organizations that run support across many channels, maintain a large knowledge base and depend on advanced reporting. FreeScout fits teams whose work arrives mostly by email and who want unlimited agents, tickets and mailboxes on a PHP and Laravel application that runs on MySQL, MariaDB or PostgreSQL, under the AGPL-3.0 license. Before comparing prices, list the features your agents use every day and sort them into those FreeScout includes and those it sells as modules.
The modules decide the comparison more than the base product does. FreeScout sells lifetime licenses for single instances, and its paid modules include LDAP Integration, SAML SSO, Knowledge Base, Satisfaction Ratings and Workflows, while its AI Integration and S3 Storage modules are free. Ask your identity team whether SAML or LDAP is a hard requirement, ask your knowledge base owner whether articles must be public, and ask your reporting lead which satisfaction or workflow reports you rely on. Each answer maps to a line item you must buy or build, and each one changes the total cost of ownership more than the base install does.
The last decision is who runs the server. FreeScout is simple to install, but a help desk holds customer conversations, mailbox credentials and attachments, so someone must own patching, backups, mail delivery and access control on the hosting stack. Confirm that your team can keep up with FreeScout's frequent releases, and document who restores the database if a mailbox sync fails. If that ownership is not clear, the managed suite may be the safer choice, and the decision should rest on that finding rather than on license fees alone.
Which help desk fits which support model
This table matches common support models to either Zendesk Suite or self-hosted FreeScout and flags where a paid FreeScout module is required. Read each row for the better fit and the reason, then check the module note against your own feature list before deciding.
| Support model | Better fit | Reason and module notes |
|---|---|---|
| Shared email inbox only, small team | FreeScout | FreeScout centers on email over SMTP, IMAP and POP3 with unlimited agents and mailboxes, and works with Microsoft 365 and Google Workspace OAuth. Core inbox use needs no paid module. |
| Multichannel support with live chat and social | Zendesk Suite | FreeScout can centralize email, WhatsApp, Telegram, Facebook, Slack and live chat, but a multichannel operation should confirm each channel's setup and support level before committing. Zendesk Suite is the broader native option. |
| Public knowledge base with articles | Either, with a module for FreeScout | FreeScout's Knowledge Base is a paid lifetime module. Confirm article features, languages and layout against your current Zendesk Guide content before planning the move. |
| SAML SSO requirement | FreeScout with paid SAML SSO module | FreeScout offers SAML SSO as a paid lifetime module for one instance. Budget for that license and confirm your identity provider works with it during evaluation. |
| Automated routing and workflows | Zendesk Suite or FreeScout with paid Workflows module | Workflows in FreeScout are a paid lifetime module. Map the rules you run today and test them on a staging instance before deciding. |
| Satisfaction ratings and reporting | Zendesk Suite or FreeScout with paid Satisfaction Ratings module | Satisfaction Ratings is a paid FreeScout module. Compare the reports you rely on in Zendesk with what your team can build and maintain. |
| Strict data residency or full control of data location | Self-hosted FreeScout | A FreeScout instance runs in infrastructure you choose, so data location follows your own hosting decision. Confirm your hosting region and backup location with your compliance team. |
How hosting and data control differ
Zendesk Suite is a vendor-hosted service. Zendesk runs the application, the databases and the storage that hold your tickets, comments and attachments, and it operates the backups. Your team configures the account, but it does not manage the servers, patch cadence or backup schedules. Regional data placement is a contract and plan question rather than something your team sets directly on its own hardware, so confirm current hosting regions and any data residency add-on with Zendesk before you rely on them.
- Data location: Mailbox content and attachments sit in Zendesk's environment. Ask Zendesk for the current data center locations for your plan and region.
- Database backups: Zendesk holds the backups. Your own copy depends on exports you take, which are enabled by the account owner through Zendesk support on eligible plans.
- Identity: SSO and provisioning options depend on the Zendesk plan. Confirm which identity providers and protocols your tier supports.
- Compliance evidence: Zendesk supplies its own assurance documentation to customers. Request the current reports and their scope from Zendesk directly.
- Exit path: Your copy of ticket history is only as complete as the exports you have taken.
Before signing, ask Zendesk where each data type is stored, who can access it, and which documents cover the services in scope.
FreeScout is AGPL-3.0 software that you install on infrastructure you control. You can deploy it with the Docker image, on a server you manage with Nginx, Apache or IIS, or through a one-click installer such as Softaculous or Cloudron, or through a managed hosting provider. The deployment model determines who owns the database, the mail storage path and the backup routine, so the choice of host matters as much as the software.
- Data location: Mailbox data, attachments and the database stay where you install them, whether that is your data center, your cloud account or a managed host's environment you contract for.
- Database backups: You or your hosting provider own the backup schedule, retention and restore testing. Test restores from the database and the attachment store together.
- Identity: OAuth sign-in for Microsoft 365 and Google Workspace is listed in the README. SAML SSO and LDAP are paid lifetime modules, so budget for them if your identity policy requires them.
- Compliance evidence: You produce the logs, configuration records, access reviews and change records. An independent auditor assesses them, and DeployOpen prepares the controls and evidence for that assessment but does not issue audit reports.
- Shared hosts: Shared hosting lowers cost but gives you less control over isolation, patching and backup timing. Confirm these terms in writing.
Before deploying, decide who owns each layer of the stack and write down how backups are verified.
Identity decides who can sign in to the help desk and how quickly access is removed when someone leaves. In Zendesk, identity options are set by the plan and the account configuration. In FreeScout, sign-in can use the application's own user accounts, OAuth for Microsoft 365 and Google Workspace, or the paid SAML SSO and LDAP Integration modules. Each path leaves different records for your access reviews.
- Built-in accounts: Users authenticate against FreeScout's own database unless you add an external method. Plan a joiner and leaver process that disables accounts promptly.
- OAuth: Microsoft 365 and Google Workspace sign-in for mailboxes reduces stored mail credentials. Confirm the required admin consent and scopes with your identity team.
- SAML SSO and LDAP: These are paid lifetime modules on FreeScout's modules page. Check the directory and identity provider versions you run against the module documentation before purchase.
- Access evidence: Your identity provider logs and directory exports become the primary evidence for access control on a self-hosted instance.
- Mailbox permissions: Shared mailbox access is separate from user login. Review which agents can read each mailbox, not only who can sign in.
Ask your identity team which sign-in method your audit controls require, then confirm that the matching FreeScout feature exists in your edition.
Each side produces different evidence. Zendesk's assurance documents describe its service controls, but your own configuration evidence still lives in the Zendesk admin console. A self-hosted FreeScout instance puts more evidence in your hands: server hardening records, backup logs, update history, access reviews and change tickets. That gives you more control over the record, and more work to keep it current.
- Vendor reports: Zendesk provides its own third-party reports, and you should check their scope against the products and regions you use.
- Self-hosted records: Keep patch records for the PHP runtime, database and FreeScout releases, since FreeScout publishes new releases roughly weekly.
- Backup and restore evidence: Record scheduled backups, retention settings and periodic restore tests for both the database and attachments.
- Access evidence: Export user lists, role assignments and identity provider logs on a set schedule.
- Independent assessment: Auditors and certification bodies issue reports. DeployOpen prepares the systems, controls and evidence for those assessments, but it does not issue audit reports, attestations or certifications.
Ask your auditor which evidence types they will sample before you choose a hosting model, because that decides how much recurring work the self-hosted option adds.
Which FreeScout modules you need to match Zendesk features
Start with the feature list, not the module list. FreeScout's core covers unlimited agents, tickets and mailboxes over SMTP, IMAP and POP3, with OAuth for Microsoft 365 and Google Workspace. Knowledge base, SAML SSO, LDAP, API and webhooks, satisfaction ratings, time tracking and workflows are paid modules, each sold as a lifetime license for a single FreeScout instance with lifetime updates, according to the FreeScout modules page. AI Integration and S3 Storage are free. Before buying anything, export a list of the Zendesk features your team actually uses in the last quarter: views, triggers, macros, the help center, SSO sign-in, directory-based access, API integrations, CSAT surveys and time reporting. Many small teams find that only a few of these are in daily use.
Map each feature the team uses to one module or to the core. Shared inbox routing, mailboxes, tags and internal notes are core features. Automated routing and status changes that Zendesk handles with triggers usually map to the Workflows module. Customer-facing answers that Zendesk Guide publishes map to the Knowledge Base module. Agent sign-in through an identity provider maps to SAML SSO, and directory group sync maps to LDAP. Integrations that call Zendesk's API or receive its webhooks map to the API and Webhooks module. Confirm the exact behavior of each module against the vendor's current documentation, since trigger logic and conditions may not match one for one. Count the purchases before you commit: each module is a separate one-time license per instance, so a team that needs four paid modules should total them against its Zendesk renewal and a possible second instance for staging.
What drives the cost of each option
Zendesk and FreeScout put cost in different places: a recurring per-agent subscription on one side, and module licenses, infrastructure and administration on the other. The cards below separate one-time from recurring costs and name what moves each figure up or down, so you can build a comparison from written quotes and your own agent count.
Zendesk per-agent subscription and add-ons
Zendesk Suite is billed per agent on a recurring basis, and the cost grows with the number of seats, the plan tier and any add-ons you attach, such as data residency or advanced security options. Ask for a written quote that lists each agent role, the plan tier, the add-ons and the billing term, because the list price and the amount you pay can differ. Confirm which features your team needs, since the tier you need determines the recurring total. Also confirm whether data exports are included in your plan, because they are not enabled by default and need a request to Zendesk support.
FreeScout module licenses
FreeScout the application is free under AGPL-3.0, but the modules that cover knowledge base, SAML SSO, LDAP, workflows and satisfaction ratings are sold as lifetime licenses for a single FreeScout instance. These are one-time purchases with lifetime updates, so the cost does not recur, but each instance you run may need its own license. Count the modules you need before you start, and confirm current module pricing and license terms on the vendor's modules page, since it can change. The AI Integration and S3 Storage modules are free, which lowers the total if you use them.
Server and backup infrastructure
FreeScout runs on Nginx, Apache or IIS with PHP and a MySQL, MariaDB or PostgreSQL database, and it can run on shared hosting. Zendesk hosts all of this in its cloud. A self-hosted FreeScout costs you the server or hosting plan, storage for attachments, and the backup target, which are recurring. Scale these costs to your mailbox volume and attachment history. Backups matter more here because you own the copy, so budget for off-server storage and test restores. Ask your hosting provider for quotes that include backup retention and bandwidth.
Installation and configuration time
Setup is a one-time cost. It covers installing FreeScout, configuring SMTP and IMAP or OAuth for each mailbox, setting up the database and TLS, and choosing an install route such as Docker, Softaculous, Cloudron or a managed host. Effort rises with the number of shared mailboxes, the identity integration you need and the volume of historical email you import. If you move from Zendesk, the migration path adds export and mapping work. Ask any partner for a written scope that lists mailboxes, modules and migration steps before work starts.
Ongoing admin and patching effort
Once running, a self-hosted FreeScout needs recurring internal time for PHP and Laravel updates, module updates, security patches, mailbox troubleshooting and user administration. Zendesk handles platform updates for you, so this is the main effort you take on. Estimate it in admin hours per month for your environment, and plan for a named owner. Weekly upstream releases mean regular patching, so a staging copy helps you test changes before they reach production.
Optional outside support
Outside support is a recurring option rather than a requirement. A retainer can cover upgrades, monitoring, backups and incident response, and a fixed-scope project can cover the initial build. Costs rise with service levels, after-hours coverage and the number of systems in scope. Ask for a quote that names deliverables, response times and who handles module licensing, so you know what the fee includes and what you still pay separately.
How a move from Zendesk to FreeScout works
The sequence takes a small support team from a Zendesk export through a tested FreeScout instance with its mailboxes, modules and mail routing in place, ending with a cutover that leaves Zendesk as a read-only reference.
Confirm export eligibility with Zendesk
The Zendesk account owner checks the plan tier, since account exports in JSON, CSV and XML are available on Suite Growth and higher and Support Professional and higher, but not on Team plans. Exports are not enabled by default, so the owner must ask Zendesk support to turn them on. Done means the owner has written confirmation that exports are enabled and has a list of the mailboxes, agents and groups in scope. Ask Zendesk support to confirm the export format you need before you start.
Export tickets and users from Zendesk
Run the account export and save the files in a location with restricted access, because they contain customer personal data. Note that the CSV export omits ticket comments and descriptions, so conversation history needs JSON or a separate pull through the API. XML exports are capped at 500 MB and unavailable above 200,000 tickets, so larger accounts should use JSON. Done means you have a complete copy, checked by record counts against Zendesk, stored as your backup of record.
Choose the import route
Decide between the migration service that FreeScout links from its README and a scripted import through the FreeScout API. The managed service suits teams that want the vendor to move data, while the API route suits teams with in-house developers who need control over field mapping and attachments. Ask the migration provider in writing what it imports, how it handles comments, attachments, users and customer records, and what it needs from you. Done means one route is chosen and its scope is recorded in writing.
Build the server and mailboxes
Install FreeScout on your own server or in a container, following the README's requirements for PHP 7.4 to 8.x and a supported database. Create one mailbox for each support address, then configure IMAP for receiving and SMTP for sending, with OAuth for Microsoft 365 or Google Workspace where that applies. Test each mailbox by sending a message in and replying out. Done means every mailbox receives and sends, and outbound mail passes your SPF, DKIM and DMARC checks.
Buy and configure the modules for parity
List the Zendesk features your team uses, such as SAML SSO, LDAP, workflows, satisfaction ratings, knowledge base or API integrations, and match each to a FreeScout module. The modules listed as paid are sold as lifetime licenses for a single instance, while the AI Integration and S3 Storage modules are free. Check the module page for current terms before purchase. Done means each required feature has a configured module or a documented gap your team accepts.
Run the import and a parallel period
Load the migrated tickets and users into a staging instance first, then into production once staging checks pass. Compare counts, assignments, tags and attachments with the Zendesk export, and sample conversations for missing comments. Keep Zendesk live while agents work in FreeScout on mail that is copied to both systems, so you can catch gaps. Done means agents have signed off on a sample of real conversations and the discrepancy list is closed or accepted.
Cut over mail routing and retire Zendesk access
Change the MX or forwarding rules so new mail for each support address reaches FreeScout, and update any autoreply, webform and integration endpoints. Watch the first days of inbound mail closely, then move Zendesk to read-only or cancel the subscription once the team is satisfied and the export archive is confirmed. Done means all inbound support mail lands in FreeScout, no messages sit in Zendesk, and the archive is stored under your retention rules.
Questions buyers ask before choosing FreeScout over Zendesk
How much does FreeScout cost to run compared with Zendesk Suite?
The FreeScout core is free under AGPL-3.0, so the license line is zero, but running it costs hosting, mail infrastructure, backups and admin time. Zendesk Suite charges per agent on a subscription. The gap depends on your agent count, how many modules you need and who operates the server. FreeScout's modules are sold as lifetime licenses for a single instance, so you pay once per module rather than every year, though you should confirm current module prices on the FreeScout modules page. Ask any hosting or implementation provider for a written quote built from your scope, and compare total cost over three to five years, including the modules you actually need.
Which FreeScout features need paid modules?
The core product covers unlimited agents, tickets and mailboxes, email over SMTP, IMAP and POP3, and OAuth for Microsoft 365 and Google Workspace. The following are paid lifetime modules: LDAP Integration, SAML SSO, API and Webhooks, Knowledge Base, Satisfaction Ratings, Time Tracking and Workflows. The AI Integration and S3 Storage modules are free. If your Zendesk setup depends on automations, a public help center or satisfaction surveys, price those modules into the comparison before you assume parity.
Does FreeScout support SAML SSO for our identity provider?
FreeScout offers SAML SSO only as a paid module, and it is listed on the official modules page. Before buying, confirm with the vendor that the module supports your identity provider, the metadata and attribute mapping you need, and how role assignment works for agents. LDAP Integration is a separate paid module if your directory is Active Directory or LDAP rather than a SAML provider. Your security team should also review how sessions, MFA enforcement and account deprovisioning are handled, because those controls live in your identity stack as much as in the help desk.
How long does a migration from Zendesk to FreeScout take?
The duration depends on ticket volume, attachment size, how many mailboxes you connect, and whether you move history or only open conversations. FreeScout links a migration service from its README, and the alternative is a scripted import through the FreeScout API. Both need an export from Zendesk first. Zendesk's account exports are available on Suite Growth and higher and Support Professional and higher, not on Team plans, and the account owner must ask Zendesk support to enable them. Plan for mailbox setup over IMAP and SMTP, DNS and mail flow testing, and a parallel run. No fixed timeline is supplied here, so ask the migration provider for a duration tied to your data volumes.
What happens to comments and attachments during a Zendesk export?
It depends on the export format. Zendesk's CSV export omits ticket comments and descriptions, so it is not a complete record of conversations. XML exports are capped at 500 MB and unavailable above 200,000 tickets, and Zendesk recommends JSON for accounts above that size. Confirm with Zendesk exactly which attachment and comment data each format includes for your plan, and test the export on a sample before relying on it. Keep the original export as a retained copy, because a migration that loses comments or attachments is hard to correct later.
Can our own admins run FreeScout without outside help?
Yes, if you have people who can operate a PHP and Laravel application on Nginx, Apache or IIS with MySQL, MariaDB or PostgreSQL. FreeScout lists a Docker image and one-click installs through Softaculous, Cloudron and managed hosts, which reduces setup work. Ongoing tasks include PHP and database patching, backups, mail deliverability, TLS certificates, weekly releases (for example, 1.8.248 was published on October 17, 2026), and module updates. Ask yourself whether your team can own these recurring tasks for the life of the system, not just the first deployment.
When should we hire an implementation partner for FreeScout?
Consider a partner when the migration spans many mailboxes, when you need SSO, LDAP or workflows configured and tested against your directory, or when your security team requires documented hardening and backup evidence. DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted open-source platforms inside your own infrastructure, typically under a fixed scope agreed in writing before work starts. It does not issue audit reports or certifications. Ask any provider for a written scope, deliverables, a test plan and a support option after go-live.
Does FreeScout cover the channels our Zendesk team uses today?
FreeScout centralizes conversations from email, and its README also lists WhatsApp, Telegram, Facebook, Slack and live chat. Confirm each channel against the current README and the modules page before you commit, because channel support can depend on add-ons or third-party connectors. If you rely on voice, SMS or a full help center, map those needs separately. Your agents will also need training on collision detection and mailbox routing, which differ from Zendesk's ticket views.
What to confirm with vendors and your own environment
Start by confirming what your current Zendesk plan allows before you plan an export or a migration. Zendesk's account exports in JSON, CSV and XML are available on Suite Growth and higher and on Support Professional and higher, not on Team plans, and the account owner has to ask Zendesk support to switch them on. Ask Zendesk for the API rate limits that apply to your specific plan, because they change how long a bulk pull of tickets and comments takes. Also confirm with your Zendesk contact which channels and reporting views your agents use today, such as live chat, social messaging, SLA dashboards and custom reports, and test each one against FreeScout in a staging instance. Parity on paper is not enough, so record every gap you find.
On the FreeScout side, check the current price and license terms of each module you need before you budget for it. The modules page lists lifetime licenses for a single FreeScout instance with lifetime updates, but prices and terms can change, so confirm them on the FreeScout modules page and get the license scope in writing. Map your required features to specific modules, such as Knowledge Base, SAML SSO, LDAP, Workflows and Satisfaction Ratings, and decide which ones you truly need on day one. Ask whether the migration service linked from the FreeScout README is a paid engagement, what it covers, what data it moves, who handles attachments and what its timeline and support terms are. Get those terms in writing before you rely on them.
Your own environment sets the technical requirements, so verify them against the release you plan to deploy. FreeScout's README lists PHP 7.4 to 8.x and MySQL 5.0+, MariaDB 5.0+ or PostgreSQL, but the exact combination supported by the release you choose can differ from that range, so check the requirements in the release notes of the version you install. Check the latest version on the FreeScout releases page rather than relying on any version named in this guide, since releases ship roughly weekly. Test mailbox connections over IMAP, SMTP and OAuth for Microsoft 365 or Google Workspace in a non-production environment, and confirm that your hosting, backups and patching process can keep pace with that release cadence.
How DeployOpen helps you evaluate, implement or migrate
DeployOpen plans, implements, hardens and supports self-hosted open-source help desks inside your own cloud accounts, data centers or air-gapped networks. For a Zendesk vs FreeScout decision, we start by confirming which channels, modules and integrations your team actually needs before anything is built.
How we scope
- We confirm which Zendesk channels, mailboxes and reports your support team uses day to day.
- We map each required feature to FreeScout core or to a paid lifetime module, and flag any gaps.
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts.
How we build
- We install FreeScout in your environment with the web server, PHP and database you choose.
- We configure shared mailboxes over IMAP, SMTP and OAuth for Microsoft 365 or Google Workspace.
- We test mail routing, collision handling and any licensed modules against your real support scenarios.
How we hand over
- We document the installation, mailbox setup, module configuration and backup procedure for your team.
- We plan the migration from a Zendesk export, covering which tickets, users and attachments move and how they are checked.
- We deliver runbooks and a validation checklist so your administrators can operate the system after handover.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Upgrades to new FreeScout releases can be planned, tested in staging and then applied to production.
- Quotes follow from the written scope, so you can ask for each cost component to be itemized.
