Freshdesk vs FreeScout: when a self-hosted shared inbox fits email-first support
If most of your customer conversations start as email, a self-hosted shared inbox can be a sound fit, and Freshdesk's per-agent plans remain a sound fit for teams that want a vendor to run the platform and add channels over time. The decision turns on four questions: your channel mix, how many features you need that FreeScout sells as paid modules, whether you must keep customer data on infrastructure you control, and whether someone on your team can run a PHP and database stack. FreeScout's free core has unlimited agents, tickets and mailboxes, so the cost question moves from seats to modules, hosting and administration. Freshdesk's per-agent pricing scales with headcount, which is easier to forecast for a fixed team.
Start with the channel mix. FreeScout's README describes centralizing email alongside WhatsApp, Telegram, Facebook, Slack and live chat, but teams that depend on live chat or social messaging as a primary channel should compare that breadth with Freshdesk's plans in detail before committing. Next, list the Freshdesk features your team uses every week, such as the knowledge base, satisfaction ratings, time tracking and automations, and map each one to the FreeScout module that provides it. Each module is a lifetime license for a single instance, so confirm the current prices on the FreeScout modules page and add them to your comparison. The module list is short, but a team that needs most of it may find the total cost approaches a plan comparison.
Data control and operations are the other half of the decision. Self-hosting keeps mailboxes, customer records and attachments inside your network or your chosen provider, which matters for regulated teams. It also means you own backups, PHP and database upgrades, mail server configuration and patching. Confirm whether you have an administrator who can handle these tasks, and whether your mail platform supports the OAuth or IMAP setup you plan to use. If the answer is no for either, a managed hosting partner or a different support model may be the better route. Check the current release notes before each upgrade, since the project publishes frequent releases.
Which option fits which support team
This table maps common support team situations to the better fit between Freshdesk and self-hosted FreeScout, with the condition that would change the answer. Read each row against your own volume, channels and staffing, because the advantage in each case depends on the stated condition holding.
| Scenario | Better fit | Reason and when the advantage stops |
|---|---|---|
| Email-only shared inbox with a small agent group | FreeScout | Unlimited agents and mailboxes in the free core remove per-agent fees, but the advantage holds only if you can run the PHP and database stack or pay a provider to run it. |
| Mixed live chat, social and messaging channels | Freshdesk | FreeScout centralizes email-led conversations, while omnichannel coverage is a separate question. If channel breadth is central, confirm each channel against the FreeScout README and modules before committing. |
| Strict data location rules requiring a named region or own facility | FreeScout (self-hosted) | Running FreeScout in your own or an EU provider's data center gives direct control of location. This stops mattering if a contractual Freshdesk EEA region already satisfies your rule, so check with your data protection lead. |
| Small team with no dedicated administrator | Freshdesk | A managed SaaS removes patching, backups and mail configuration from your staff. FreeScout becomes a fit only if someone accepts ongoing server, SMTP and upgrade duties, or you engage a provider or support retainer. |
| Team that needs knowledge base and CSAT on day one | Freshdesk | Freshdesk includes these features in its plans. In FreeScout, the Knowledge Base and Satisfaction Ratings modules are paid lifetime licenses, so the advantage flips if you accept a one-time module purchase and setup before go-live. |
| Team with heavy workflow automation and time tracking needs | Freshdesk | FreeScout offers Workflows and Time Tracking as paid modules. Confirm that the module behaviour matches your rules during a trial, because the advantage ends if your automations depend on features not listed in the modules page. |
| Team already running a PHP and MySQL or PostgreSQL stack with an admin | FreeScout | Your existing operations skills lower the effort of hosting and upgrading. The advantage shrinks if upgrades, backups and mail deliverability fall to staff who lack capacity for weekly releases. |
How FreeScout runs an email-first shared inbox
FreeScout is a lightweight PHP and Laravel help desk built around shared mailboxes. Each mailbox connects to your email over SMTP, IMAP or POP3, and Microsoft 365 and Google Workspace mailboxes can authenticate through OAuth rather than stored passwords. Conversations arrive as tickets in the mailbox they were sent to, and collision detection shows when another agent is already viewing or replying to the same conversation, which matters when several people share one support address. Agents work in the web interface or the progressive web app, and the Android and iOS apps are documented as supporting the same functionality and modules as the web version. Ask your mail administrator to confirm which authentication method your tenant allows before you plan mailbox connections, because that decision sets how much access the application holds.
The main trade-off is architectural. A single self-hosted application keeps conversations, mailboxes, agents, saved replies and settings in one database that you operate, so there is one system to back up, patch and audit. Everything depends on that one installation, so the hosting, database backups and mail connectivity your team owns become part of the support service itself. The README also lists conversations from WhatsApp, Telegram, Facebook, Slack and live chat as sources that can be centralized. Each of those channels is a separate integration with its own setup, credentials and terms, so list the channels your customers actually use today and confirm with the FreeScout documentation and modules page how each one is connected before counting it as covered.
Freshdesk vs FreeScout feature by feature
This table compares Freshdesk and FreeScout on licensing, agent and mailbox limits, data export, email channels, paid modules, mobile apps and deployment. Read the FreeScout column as the free core plus any lifetime modules you buy for one instance. Confirm each Freshdesk entry against your current plan, because plan-level features change.
| Capability | Freshdesk | FreeScout |
|---|---|---|
| License and hosting model | Proprietary SaaS subscription hosted by Freshdesk in a region you choose at signup | AGPL-3.0 open source, installed and run on your own servers or a managed host |
| Agents, tickets and mailboxes | Per-agent pricing on paid plans; confirm current agent and mailbox limits | Unlimited agents, tickets and mailboxes in the free core |
| Data export | Admins export tickets, solutions, forums and customers as XML on all plans | Data sits in your own database; confirm export options for your installed version |
| Email channels | Email ticketing included; confirm which channels and mailbox features your plan includes | SMTP, IMAP and POP3, plus OAuth for Microsoft 365 and Google Workspace and collision detection |
| Knowledge base, ratings, time tracking and workflows | Included in plan tiers; confirm each feature against your current plan | Knowledge Base, Satisfaction Ratings, Time Tracking and Workflows are paid lifetime modules per instance |
| Directory login and API | SSO and API access depend on plan; confirm before migrating | LDAP Integration, SAML SSO, and API and Webhooks are paid lifetime modules |
| AI and file storage | AI features and attachment storage depend on plan; confirm current terms | AI Integration and S3 Storage modules are free |
| Mobile apps | Freshdesk mobile apps; confirm feature parity with the web app on your plan | Android and iOS apps support the same functionality and modules as the web version |
| Installation options | No installation; administered through the vendor's hosted service | Docker image, one-click installs through Softaculous and Cloudron, or managed hosts; PHP 7.4 to 8.x with MySQL, MariaDB or PostgreSQL |
Which FreeScout modules replace which Freshdesk plan features
FreeScout's core covers unlimited agents, mailboxes and tickets, so the cost question is which Freshdesk plan features your team actually uses. Most of those features map to paid FreeScout modules, each sold as a lifetime license for one instance with lifetime updates. Map your own Freshdesk plan features to these modules before buying anything.
Knowledge base module
The Knowledge Base module adds a public help center of articles that customers can search before they open a ticket. It matters if your Freshdesk plan use includes solutions or a self-service portal. Check whether you need one public site, multiple languages, or internal-only articles, and confirm how the module handles categories and access for your team.
Satisfaction ratings module
The Satisfaction Ratings module sends customers a rating request after a conversation closes and reports the results to agents and managers. It replaces Freshdesk's customer satisfaction reporting for teams that track CSAT per agent. Confirm which report views you need and whether your team will use the ratings to coach agents or only for trend reporting.
Time tracking module
The Time Tracking module records the time agents spend on each conversation, which matters if you bill support work or report effort by customer. Freshdesk includes time tracking in certain plans, so compare your current plan with what your finance or account teams expect. Confirm the export format and whether reports must reach a billing tool.
Workflows module
The Workflows module applies rules to conversations, such as assigning, tagging or changing status when a condition is met. It replaces Freshdesk automations for routing and escalation. Before buying, list the rules you run today, count how many need conditional logic, and test whether the module covers each one without custom code.
LDAP and SAML SSO modules
The LDAP Integration and SAML SSO modules connect FreeScout logins to your directory or identity provider. They matter when your security policy requires central account management, offboarding through the directory, or single sign-on. If you already use OAuth for Microsoft 365 or Google Workspace, confirm whether that covers your sign-in needs before adding either module.
API and webhooks module
The API and Webhooks module lets other systems read and write conversations and receive event notifications. It matters if your Freshdesk integrations push tickets into a CRM, billing system or internal tool. Inventory each integration, confirm which endpoints it calls, and check whether your developers can rebuild it on the FreeScout API.
Where the data lives under each hosting model
Running FreeScout on your own servers, in your data center or in a cloud account you control, keeps mailboxes, conversation history, attachments and customer records inside your own boundary. Your team chooses the region, the storage encryption, the backup targets and the network paths. The trade-off is that every layer of the stack becomes your responsibility, from the PHP runtime and web server to the MySQL, MariaDB or PostgreSQL database and the operating system beneath them.
- Data location: The database,
storagedirectory and attachments sit wherever you place them, so residency decisions are yours to document and enforce. - Patching: Your team applies FreeScout releases, which the project publishes roughly weekly, plus PHP, the web server, database and OS updates.
- Identity: Authentication can use built-in accounts, OAuth for Microsoft 365 and Google Workspace, or the LDAP Integration and SAML SSO modules, which are sold as lifetime licenses on the FreeScout modules page.
- Audit evidence: Access logs, change records, backup restore tests, patch history and role reviews are artifacts you must produce and retain yourselves.
- Access control: Administrator accounts, mailbox permissions and API tokens must be inventoried and reviewed on a schedule you set.
Before you commit, confirm where your backups replicate, who holds database credentials and how mailbox passwords are stored and rotated.
FreeScout can also be placed on a managed hosting provider or installed through Softaculous, Cloudron or a managed host's control panel. The data still lives on a server operated by a third party, so the question shifts from whether you run the stack to how much of it the provider runs and where that provider's facilities are located. One-click installers reduce setup work but do not, on their own, establish a patching or backup regime, so those duties must be written into your agreement or your runbook.
- Data location: The provider chooses the data center. Ask for the country, the facility operator and whether backups leave that region.
- Patching: Confirm whether the provider updates FreeScout, PHP and the database, or whether it only supplies the container or installer, which leaves updates to you.
- Identity: Confirm which SSO options the installer exposes and whether the modules needed for LDAP or SAML can be licensed on that host.
- Audit evidence: Request the provider's own control evidence, such as its security documentation and access review records, and keep your own record of tenant configuration.
- Shared responsibility: Document which party holds each responsibility in writing, including incident notification.
Before you sign, ask the provider to show, in writing, which layers it patches and which backups it keeps, and where each one is stored.
Freshdesk is a hosted service in which Freshworks operates the application and the data stores. Customers choose a data center region at signup, and the platform handles application patching, database administration and infrastructure. Your organization controls the access granted to its agents and administrators, but it does not control the underlying servers or the timing of platform changes. Moving to a different region is a request to the vendor rather than a self-service action, so residency decisions made at signup carry forward.
- Data location: The region is selected at signup and changed through vendor support. Confirm the region for your tenant and for backups in writing.
- Patching: The vendor deploys application and infrastructure updates. Your team receives release notes and tests integrations against them.
- Identity: Use the SSO and user management options included in your plan, and review them against your identity provider's logs.
- Audit evidence: Request the vendor's current assurance reports and security documentation through your procurement process, then map them to your own controls.
- Client copy: The account export, which an administrator runs from Admin, Account, Account Details, Export data as XML, gives you a copy of tickets, solutions, forums and customers that you hold independently.
Before renewal, confirm the data region, the export retention you keep, and the vendor's notification process for security incidents.
What a Freshdesk subscription and a self-hosted FreeScout each cost to run
Freshdesk cost is a recurring per-agent subscription, so the bill moves with two things: how many people hold agent seats and which plan tier contains the features you actually use. Before comparing totals, list the features your team needs, such as knowledge base, satisfaction ratings, time tracking and workflow automation, and check which Freshdesk plan includes each one. Then ask for a written quote for the agent count you expect in 12 to 24 months, not only today's headcount, because seat growth is the main driver of the subscription line. Confirm whether annual or monthly billing, add-on charges and any regional data center choice change the figure.
A self-hosted FreeScout splits cost into different buckets. The core is free under AGPL-3.0, with unlimited agents, tickets and mailboxes, so the license line is zero for the core. Modules that Freshdesk would bundle into plans, such as Knowledge Base, Satisfaction Ratings, Time Tracking, Workflows and SAML SSO, are sold as lifetime licenses for a single instance, so they are one-time purchases per instance rather than per-seat fees. The recurring costs are server or managed hosting, backups, mail deliverability setup for SMTP, IMAP or OAuth mailboxes, and upgrades. FreeScout releases arrive roughly weekly, with 1.8.248 published on October 17, 2026, so budget for regular patching by whoever runs the stack. Ask any managed host or implementation partner for the hosting, backup, upgrade and support scope in writing, and ask the module price list for the exact lifetime amounts at your module count.
Your cost comparison should be built on a three-year view and on the people who run each stack. Freshdesk cost rises with each agent, while FreeScout cost rises mainly with the number of modules, the size of the hosting plan and the admin hours spent on patches and mail issues. Name who is paid for each item: an internal admin, an external host, or an implementation partner for setup and hardening. Ask that a quote separate one-time items (installation, module purchases, data migration) from recurring items (hosting, backups, upgrades, support). Confirm whether module licenses cover only one instance, which matters if you add a staging server, and whether the Freshdesk quote includes a data export for exit planning, which the account owner can run from Admin, Account, Account Details, Export data.
Moving from Freshdesk to FreeScout: export, import and rebuild
This sequence moves a shared email support inbox from Freshdesk to a self-hosted FreeScout instance, with a verified copy of your Freshdesk data kept as a fallback throughout.
Confirm the feature list before exporting
Before touching any data, list what your team actually uses in Freshdesk: mailboxes, saved replies, automations, SLAs, satisfaction surveys, knowledge base articles and reporting. Compare that list with FreeScout's core features and its paid modules for knowledge base, satisfaction ratings, time tracking and workflows, which are sold as lifetime licenses for a single instance. Confirm the current module prices and terms on the FreeScout modules page with FreeScout directly. The step is done when each Freshdesk feature is marked as covered by the core, covered by a module, or to be rebuilt by hand.
Run the Freshdesk account export
A Freshdesk account administrator opens Admin, Account, Account Details, then Export data, and requests an export of tickets, solutions, forums and customers as XML. The option is available on every Freshdesk plan. Store the resulting files in encrypted storage that you control, and record the export date. Treat this export as your fallback copy: keep it until the cutover is verified and your retention policy allows deletion. The step is done when the files are downloaded and checked for completeness against ticket counts shown in Freshdesk.
Convert the XML before loading it
The Freshdesk XML is not a format FreeScout reads directly, so conversion work is required. Decide whether FreeScout's migration service or an import through the FreeScout API fits your data. Either path needs the export mapped to FreeScout's conversations, customers, mailboxes and attachments, with fields such as status, assignee and tags translated. Ask FreeScout what the migration service covers and what it does not before you commit. The step is done when a sample of tickets from the converted file matches the originals in the test instance.
Choose the migration path and set up the target
Compare the FreeScout migration service with a custom import through the FreeScout API. The service reduces in-house effort but may not cover every field or attachment, and it is a paid engagement you should quote in writing. An API import gives your team full control and is also a recurring engineering task if you migrate more than once. Install FreeScout on your own infrastructure, using the Docker image or a supported installer, and configure the database. The step is done when the target instance runs and the migration approach is agreed in writing.
Re-create mailboxes and connect email
Create one FreeScout mailbox for each Freshdesk support address, and connect each one over IMAP or POP3 with SMTP for sending. For Microsoft 365 or Google Workspace mailboxes, use the OAuth authentication options so credentials are not stored as passwords. Confirm that inbound and outbound mail works from each address in a test instance. The step is done when test messages arrive, send correctly and appear as conversations in the right mailbox.
Rebuild saved replies, workflows and knowledge base content
Freshdesk saved replies, automations and knowledge base articles do not carry over as working configuration in the same form, so rebuild them by hand or through the import tooling you chose. Rebuild the workflows you need using the FreeScout Workflows module if you purchased it, and rebuild knowledge base content in the Knowledge Base module if that fits your plan. Assign owners to each rebuilt item and review it with the agents who use it. The step is done when each item on the step one list is either live in FreeScout or formally dropped.
Run a test cycle with real agents
Run a test period in which agents handle sample and copied conversations in the FreeScout test instance. Check reply threading, attachments, customer records, tags, user roles, notifications on the mobile apps and any module-driven features such as satisfaction ratings or time tracking. Log each defect with a clear owner and fix it before the next run. The step is done when agents sign off that the conversations they need are complete and the defect log is closed or accepted.
Cut over mail routing and verify the fallback
On the agreed cutover date, change the MX records or forwarding rules so new mail reaches FreeScout, and update the reply addresses that customers use. Keep Freshdesk running until incoming mail has been confirmed in FreeScout and no messages remain in the old queue. Keep the XML export and a verified copy of the FreeScout data under your own backup controls. The step is done when inbound and outbound mail is confirmed on the new system, the old routing is removed, and the Freshdesk export is stored as your retained fallback.
Freshdesk vs FreeScout: questions buyers ask before moving
How much effort does a move from Freshdesk to FreeScout take?
The effort depends mostly on how much of your Freshdesk setup you need to carry across. A team that uses Freshdesk as a shared email inbox has a simpler job than one with many automations, custom fields and integrations. The main work is exporting tickets and customers, deciding how the FreeScout migration service or the API will load them, re-creating mailboxes and saved replies, and checking which paid FreeScout modules replace the Freshdesk plan features you rely on. Ask any implementation partner to confirm the export format and the import path for your volume before agreeing on scope.
How long does it take to move a shared inbox to self-hosted FreeScout?
The timeline is set by the number of mailboxes, the volume of history you need to keep, how many modules you adopt, and how quickly your team can approve the cutover. No duration is fixed by the software itself, so treat any single figure you hear as a question to challenge. Plan for a test instance, a trial import, a mailbox cutover window where email forwarding changes, and a period where agents work in both systems. Ask for a written timeline with milestones in the scope document before work starts.
What does my team need to provide during a FreeScout migration?
Three things decide whether the project runs smoothly. You need mailbox owners who can confirm which addresses forward to the help desk and who approves DNS, MX or forwarding changes. You need an administrator with access to the current Freshdesk account export and the authority to create the FreeScout admin accounts. You also need a named owner for the server, who accepts responsibility for patching, backups and the database. Without that last role, the self-hosted instance tends to drift after go-live. Confirm these owners in writing during scoping.
Can one in-house administrator run a self-hosted FreeScout alone?
A single administrator can run a small FreeScout instance if they are comfortable with Linux, a PHP and Laravel stack, a MySQL, MariaDB or PostgreSQL database, mail protocols and routine upgrades. FreeScout ships frequent releases, so someone must own the update routine and test it before applying it. The risk is a single point of knowledge, especially if that person leaves or is unavailable during an email outage. Many teams cover this with written runbooks, documented backups and a retainer for upgrades and after-hours support. Decide who covers the role when the primary administrator is away.
What recurring costs remain after moving from Freshdesk to FreeScout?
The FreeScout core is free, so the recurring costs shift from per-agent subscriptions to the infrastructure and people who keep the system running. These include the server or hosting in your own or a managed environment, backup storage, mail service fees if you use a provider for SMTP or IMAP, and staff time for patching and monitoring. Paid FreeScout modules are licensed for a single instance with lifetime updates, so they are a one-time purchase per module rather than a monthly seat fee, according to the FreeScout modules page. Ask for the module list you need, the hosting model, and whether ongoing support is a separate retainer.
Does the free FreeScout core cover what a support team needs?
The free core covers a lot for teams that work mainly from email. The README lists unlimited agents, tickets and mailboxes, SMTP, IMAP and POP3 integration, OAuth for Microsoft 365 and Google Workspace, collision detection, a progressive web app and translations into 33 languages. Features such as the knowledge base, satisfaction ratings, time tracking and workflows sit in paid modules, along with LDAP and SAML single sign-on and API and webhooks. Before you commit, list each Freshdesk feature your team uses and map it to the free core or a module.
How does DeployOpen scope a FreeScout migration in writing?
DeployOpen plans and implements self-hosted open-source platforms inside your own infrastructure, and most engagements are fixed-scope. Before work starts, the scope, deliverables and timelines are agreed in writing, so you can see which mailboxes, modules, integrations and migration steps are included. The scope also names the client responsibilities described above, such as mailbox owners and the server owner. Quotes follow from that written scope, and DeployOpen does not publish a price list. Ask for a written scope that covers testing, cutover, backups and handover documentation.
How DeployOpen helps evaluate, implement and migrate FreeScout
DeployOpen, a Chainscore Labs company, plans and implements self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For Freshdesk vs FreeScout, we work from a written scope that covers the mailboxes, module decisions and export steps your team needs.
How we scope
- We inventory shared mailboxes, agent seats and the Freshdesk features your team actually uses today
- We map each feature to a FreeScout core function or a paid module, and flag any gaps
- We agree deliverables, timelines and responsibilities in writing before any work starts
How we build
- We install FreeScout on your chosen stack, with mail, database and backup settings in your environment
- We configure SMTP, IMAP or OAuth connections for each mailbox and test inbound and outbound mail
- We document saved replies, workflows and module configuration, and test them with your support staff
How we hand over
- We provide an operations runbook covering updates, backups, mailbox monitoring and restore steps
- We walk your administrators through agent roles, module licensing and day-to-day configuration
- We deliver a record of the Freshdesk XML export and how it was checked against the new instance
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover
- We can test FreeScout upgrades in a staging copy before your production inbox changes
- Support scope, response expectations and fees are set in the written agreement, not assumed
