When FreeScout fits a small team's Zoho Desk shared inbox
FreeScout fits a small team that uses Zoho Desk mainly as a shared inbox: a handful of mailboxes, one instance, support that runs through email, and staff who can operate a PHP application and a MySQL, MariaDB or PostgreSQL database. Its README describes unlimited agents, tickets and mailboxes, with email over SMTP, IMAP and POP3 and OAuth for Microsoft 365 and Google Workspace, so per-user licensing stops driving the cost. Zoho Desk fits better when the team needs multi-department routing with separate queues and teams, layered SLA rules, or tight coupling with other Zoho applications. Confirm this against your own process before deciding, because the answer depends on how many departments share the inbox and how strict the response commitments are.
The decision turns on two inventories. First, list which Zoho Desk features your agents use every week, such as departments, automation rules, SLA policies, the knowledge base, satisfaction surveys, time tracking, and single sign-on. Second, map each one to FreeScout. Several of these are not in the free core: FreeScout sells lifetime module licenses for a single instance, including Knowledge Base, Satisfaction Ratings, Time Tracking, Workflows and SAML SSO, while the AI Integration and S3 Storage modules are free. Ask FreeScout for current module prices, and add the time to install, configure and test them, because the license is only one line of the total. Features with no FreeScout equivalent in your list are a reason to choose a different platform, not a gap to accept silently.
Which scenarios favor FreeScout and which favor Zoho Desk
This table maps common shared inbox and support scenarios to the platform that usually fits better. Read each row against your own mailbox count, escalation rules and identity setup, then confirm any Zoho Desk feature you depend on against Zoho's current documentation. The main takeaway is that FreeScout suits email-centered teams that value unlimited agents and mailboxes, while Zoho Desk fits teams that rely on its multi-department and suite features.
| Scenario | Better fit | Why |
|---|---|---|
| One shared mailbox for a small team | FreeScout | Unlimited agents and mailboxes are included in the open-source core, so the team pays no per-user license fee. |
| Several product or region mailboxes | FreeScout | Unlimited mailboxes are part of the base product, and each mailbox can be connected over SMTP, IMAP or POP3 or OAuth for Microsoft 365 and Google Workspace. |
| No multi-department routing needed | FreeScout | A single team working one inbox does not need the department structure that drives Zoho Desk plan choices. |
| Multi-department routing across several teams | Zoho Desk (confirm) | Confirm current department, queue and routing capabilities in Zoho's documentation, since FreeScout has no direct equivalent to build on. |
| SLA-style escalations | Either, after checking modules | FreeScout offers a paid Workflows module for lifetime license purchase, so confirm the escalation rules you need against it and against Zoho Desk's SLA features. |
| SSO required by policy | FreeScout (with paid module) | The SAML SSO module is sold as a lifetime license per instance, so budget for it as a one-time purchase. |
| Team already standardized on the Zoho suite | Zoho Desk | Native links to other Zoho applications reduce integration work, and leaving the suite changes those connections. |
Where the conversations and credentials live under each model
A shared inbox holds customer emails, attachments, staff identities and mailbox credentials, so the hosting model decides who can reach them. The cards below set out the points that differ between staying on Zoho Desk and running FreeScout on your own servers.
Data location
Zoho Desk stores your tickets and attachments in Zoho's infrastructure, and the location depends on your plan and region with Zoho. Confirm that location in writing with Zoho before you compare it with your own requirements. With FreeScout, conversations, attachments and mailbox credentials sit in the database and file storage you provision, which can be in your own data center, your cloud account or a managed host you contract directly. If you use the S3 Storage module (free), attachments move to an object store you choose.
Who operates the server
On Zoho Desk, Zoho runs the application, the infrastructure and the patching. On FreeScout, your team or a contracted operator owns the web server, PHP runtime, database and mail connectivity. FreeScout's README lists Nginx, Apache or IIS with PHP 7.4 to 8.x and MySQL 5.0+, MariaDB 5.0+ or PostgreSQL. Decide who receives security advisories, who applies the 1.8.248 release and later updates, and who is on call when IMAP polling stops.
Identity integration
Staff sign-in and mailbox access work differently. SAML SSO and LDAP Integration are paid FreeScout modules sold as lifetime licenses for a single instance, so budget for them if your identity provider must govern agent access. Mailboxes can instead use OAuth for Microsoft 365 and Google Workspace, which is included in the core product. Confirm which of these your identity provider supports and who holds the client secrets.
Backups and patching
With Zoho Desk, the backup and retention behaviour is part of the vendor contract, so ask Zoho for its current export and retention terms. With FreeScout, you own the backup of the database, the attachment store and the configuration, and you must test restores. Releases arrive roughly weekly, so write down a patch window, a staging copy and a rollback plan before go-live.
Compliance evidence
DeployOpen can prepare the controls, configuration records, access reviews and backup evidence that an assessor will ask for, and run security testing against the deployment. DeployOpen does not issue audit reports, attestations or certifications. Independent auditors and certification bodies make those determinations. Ask Zoho for its own current assurance reports, and agree in writing which evidence your organization will produce for a FreeScout deployment.
How FreeScout's capabilities map to Zoho Desk's features
This table maps the Zoho Desk capabilities that small shared-inbox teams rely on against what FreeScout provides, based on its README and modules page. Read the FreeScout column to see what ships in the core product and what needs a paid lifetime module, then use the third column to confirm your current Zoho plan before deciding. Multi-department routing and some automation depth have no direct FreeScout equivalent in the supplied material, so treat those rows as gaps to test.
| Capability | FreeScout | What to check in your Zoho plan |
|---|---|---|
| Ticket and shared inbox handling | Unlimited agents, tickets and mailboxes in the core product, with collision detection to flag overlapping agent work. | Confirm your current agent, mailbox and ticket limits, and how Zoho shows concurrent replies. |
| Email channels | SMTP, IMAP and POP3 integration, plus OAuth for Microsoft 365 and Google Workspace. | List which mailbox connection methods and sending domains you use today. |
| Multi-channel intake | README says email, WhatsApp, Telegram, Facebook, Slack and live chat can be centralized. Confirm which need modules or connectors. | List every channel you use in Zoho and test each one against a sample conversation. |
| API, webhooks and integrations | API and Webhooks module (paid lifetime license). Zapier and Make integrations are linked in the README. | Confirm which Zoho APIs, webhooks and marketplace apps your workflows call. |
| Knowledge base and satisfaction ratings | Knowledge Base and Satisfaction Ratings modules, each sold as a paid lifetime license. | Check whether your Zoho knowledge base and CSAT surveys are included in your plan or sold as add-ons. |
| Workflows and SLA-style rules | Workflows module (paid lifetime license). No dedicated SLA module is listed, so test your timers and escalations. | Export your automation rules and document each trigger, action, SLA timer and business-hours setting. |
| SSO and directory sign-in | SAML SSO and LDAP Integration modules, each sold as a paid lifetime license. | Check which sign-in methods your Zoho organization uses and which users depend on them. |
| Mobile apps | Android and iOS apps with the same functionality and modules as the web version. | Confirm which mobile features your agents use in Zoho and test them on the FreeScout apps. |
| Multi-department routing | No direct equivalent to Zoho departments appears in the supplied material. Mailboxes and folders are a starting point to confirm. | Map each department, team and routing rule. Treat this row as a gap until a test confirms it. |
What the paid FreeScout modules cost and what they leave to you
FreeScout itself carries no license fee. The core application is licensed under AGPL-3.0, so the recurring cost question is about the optional modules and the infrastructure underneath them. FreeScout's modules page sells LDAP Integration, SAML SSO, Knowledge Base, Workflows and Time Tracking as lifetime licenses for a single FreeScout instance, with lifetime updates. The AI Integration and S3 Storage modules are listed as free. A lifetime license is a one-time purchase per instance, so a team that needs SSO, a knowledge base and workflows should total those module prices once and compare them with what it currently pays Zoho Desk each year. Lifetime licenses are tied to one instance, so add a second FreeScout instance (for example, a staging copy) and check whether it needs its own license.
Module prices are not stated in this section, and you should not assume them. Pull the current figures from the FreeScout modules page, list every module your team needs (SSO, LDAP, knowledge base, workflows, satisfaction ratings, API and webhooks, time tracking), and ask FreeScout for a written quote that covers that exact list and any multi-instance needs. Confirm whether module updates after the purchase are included, since the lifetime terms are what make the one-time figure meaningful over several years.
The costs that never go away sit with your team or your hosting provider. Server hosting, backups of the database and the attachment storage, monitoring, and patching of PHP, the database and the operating system all recur. Email deliverability is easy to underestimate: the shared inbox depends on SMTP, IMAP or OAuth access to your mailboxes, so someone must own SPF, DKIM and DMARC records and watch for mailbox authentication changes. Staff time to run the system is the largest unknown. Estimate it honestly, note who covers on-call duty for a broken inbox, and decide whether to buy a support or implementation retainer from DeployOpen, priced from a written scope.
Where FreeScout closes the gap and where it does not
FreeScout handles shared inboxes well: each mailbox is a separate inbox with its own email connection, and the README describes unlimited agents, tickets and mailboxes. A small team that routes mail by address (for example, billing@ or support@) usually gets what it needs from the core product. Routing by department, team ownership and skill across many queues is a different problem, and it is where Zoho Desk's multi-department model is more elaborate.
- Mailbox-based routing: Separate mailboxes map cleanly to separate teams, and conversations from email, WhatsApp, Telegram, Facebook, Slack and live chat can be centralized.
- Assignment rules: Confirm in the current FreeScout version whether automatic assignment by mailbox, tag or customer attribute covers your rules without a paid module.
- Department hierarchies: Zoho Desk departments with nested teams and sub-departments have no direct FreeScout equivalent, so model them as mailboxes and tags and test the result.
- Collision detection: Use a pilot to check that two agents do not answer the same customer at the same time under your real volume.
- Custom routing logic: Where rules go beyond what the interface offers, the API, Zapier and Make integrations are the route for custom logic.
Before committing, replay a month of real routing decisions through a pilot mailbox setup and count how many need manual reassignment.
FreeScout's Workflows module is a paid lifetime add-on that the official modules page lists alongside the API and Webhooks module, so automation is split between the core product and paid components. Lifetime licenses cover a single FreeScout instance with lifetime updates, which makes the cost of automation a one-time item per instance rather than a recurring per-user charge. Teams with simple triggers such as auto-replies, tagging and assignment on arrival are often covered. Teams that rely on layered, multi-condition automations across many ticket states need to test more closely.
- Workflows module: Confirm which trigger types, conditions and actions it supports against your Zoho Desk automation list.
- Webhooks and API: The API and Webhooks module, together with the README's links to Zapier and Make, is the route for logic that the interface does not express.
- Zoho Desk macros and blueprints: Zoho Desk features that have no named equivalent should be rebuilt as workflows, then tested with sample tickets.
- Automation volume: Check how automations behave under peak queues, since behavior at scale depends on your own hosting.
- Ownership of logic: Custom integrations need an owner who can maintain them after upgrades.
In the pilot, export your top ten Zoho Desk automations as written rules and recreate each one, then confirm the outcome on test tickets.
FreeScout offers a Knowledge Base module as a paid lifetime add-on on its modules page. Self-service needs are usually modest for a small team: a public article list, search and a few categories. The module is adequate when the team controls the content and does not need deep portal branding, multiple languages with separate review cycles, or customer-specific article visibility. Zoho Desk's portal and knowledge base features are broader, so compare what your customers actually use before moving.
- Article publishing: Confirm how the module handles drafts, categories, search and public visibility.
- Branding and layout: Check whether the portal can match your site design without custom theming work.
- Language coverage: The FreeScout interface is translated into 33 languages, but article translation workflows are a separate question to confirm.
- Analytics and feedback: Satisfaction Ratings is a separate paid module, so price it alongside the knowledge base if you need feedback on articles.
- Migrating content: Zoho Desk knowledge base articles are included in its CSV backup, but attachments need separate handling.
In the pilot, measure whether your top customer questions are answered by the articles you would migrate, and test search with real customer phrasing.
FreeScout does not present SLA management as a core feature in its README, so teams that depend on Zoho Desk's SLA timers and escalation paths should treat this as a gap to verify. The modules page lists a Time Tracking module and a Workflows module, which may cover some reminder and escalation logic, but whether they reproduce response and resolution targets with breach alerts must be confirmed with FreeScout directly. A team that tracks response times informally, or uses a simple reminder for unanswered mail, may be satisfied. A team with contractual response targets is not.
- Response and resolution targets: Confirm whether any module supports time-based targets with breach states.
- Escalation paths: Test whether an unanswered conversation can move to a senior agent or mailbox automatically.
- Reporting: Compare the reports Zoho Desk produces for SLA compliance with what you can extract from FreeScout.
- Business hours: Check how working calendars, holidays and time zones are handled.
- Custom timers: A timer built with the API and an external scheduler is possible, but it needs an owner and testing.
Before committing, write down every SLA your contracts or internal policies require and confirm each one in a pilot against a test queue.
FreeScout supports OAuth authentication for Microsoft 365 and Google Workspace in its README, which covers mailbox connections and sign-in for many small teams. The SAML SSO and LDAP Integration modules are paid lifetime add-ons on the modules page. Access control for a small team with a few roles is usually manageable, but finer permissions by department, field-level restriction or audit reporting need to be checked against Zoho Desk's role model.
- Single sign-on: The SAML SSO module is the route for centralized sign-in; confirm which identity providers you use are supported.
- Directory sync: The LDAP Integration module can map directory groups, so confirm how group changes propagate when staff leave.
- Role model: Compare Zoho Desk's roles and permissions with what FreeScout's agent and admin roles can express.
- Mailbox access: Check which agents can see which mailboxes, since this is the main access boundary in a shared inbox.
- Audit trail: Confirm what activity is logged and how long logs are retained in your deployment.
In the pilot, sign in with each role you need, attempt an action outside that role and record whether it is blocked.
What a move from Zoho Desk to FreeScout involves
The sequence turns a Zoho Desk shared inbox into a self-hosted FreeScout instance with mailboxes, users and history in place, and proves the setup in parallel before mail routing changes. Each step closes with a check the team can sign off.
Inventory mailboxes, departments and automations
Your team lists every Zoho Desk department, email address that creates tickets, agent group, automation rule, SLA and macro in use, and marks which ones the shared inbox actually depends on. Agents who handle escalations should review the list, since automations are where undocumented behavior tends to hide. The step is done when each item has a named owner and a keep, change or retire decision. Confirm current Zoho Desk features against Zoho's documentation, because plan tiers and feature names change.
Export data and confirm what it omits
Use the export and backup options that Zoho currently provides for your plan, and confirm with Zoho which formats, scope and retention apply to your account. Compare the export against your inventory to see what is missing, such as attachments, forum content, custom fields or automation logic. Record each gap and decide how it will be handled, for example by archiving files separately. The step is complete when the team has a written list of exported data and a documented list of gaps.
Decide the FreeScout module set
Map each capability your team relies on to FreeScout's core features or to a paid module, and confirm current module availability, license terms and what each license covers on the FreeScout modules page. Identify any function with no FreeScout equivalent, such as multi-department routing or automation depth that Zoho Desk provides, and decide whether to adapt the workflow, add a custom build or accept the change. The step closes with a signed module list and a list of accepted gaps.
Install and configure mailboxes and identity
Your infrastructure or DeployOpen's team installs FreeScout on your own servers using a supported stack, then connects each mailbox over IMAP, SMTP or OAuth for Microsoft 365 or Google Workspace, and sets up user roles and single sign-on if you use a SAML module. Test sending and receiving on every mailbox, along with notification and signature settings. The step is done when test threads arrive, replies leave from the right address and each agent can sign in with the intended access.
Migrate or import tickets
Confirm whether the FreeScout migration service supports Zoho Desk as a source for your version and data set. If it does not, plan an import through the FreeScout API from the exported files, with a mapping of customers, conversations, statuses and agents. Run the import on a copy first, then check counts, timestamps, attachments and threads against the export. The step is complete when a reconciliation report shows which records match and which were excluded or handled manually.
Run a parallel pilot
Route a limited set of real inbound mail through FreeScout while Zoho Desk stays live, so agents can compare routing, replies, notifications and any integrations you rely on. Collect issues in a single log with an owner and resolution for each. Hold the pilot until the open issues are either fixed or accepted in writing by the team lead. The step ends with a signed pilot result that lists what changed and what remains.
Cut over DNS and mail routing
Change MX or forwarding rules and any integration endpoints so new mail reaches FreeScout, set a clear date for agents to stop using Zoho Desk, and keep Zoho Desk readable for reference until the archive is verified. Monitor delivery, bounces and spam scores in the first days after the switch and keep a rollback path documented. The step is done when inbound mail arrives in FreeScout, the archive is confirmed and the team has closed the Zoho Desk subscription on its own timeline.
What buyers ask before moving a shared inbox off Zoho Desk
What does moving a shared inbox off Zoho Desk cost, and who pays for each part?
The FreeScout software itself carries no per-agent fee, because it is licensed under AGPL-3.0. The move still has four cost groups, each paid to a different party. First, server and hosting, in your own cloud account or data center. Second, mail infrastructure, including the mailboxes and OAuth setup for Microsoft 365 or Google Workspace. Third, module licenses, which are one-time purchases per instance with lifetime updates, and some modules are free. Fourth, labor, either your staff's time or fixed-scope work from an implementation partner. Ask every quote to split these lines and to mark which items recur, such as hosting, backups and patching.
How long does a FreeScout migration take, and what sets the timeline?
No duration can be stated from the researched facts, so ask for a written scope with a timeline before you plan renewal dates. The main drivers are the number of mailboxes and shared inboxes, how much conversation history you must carry over, how many modules you need, whether your login system needs SAML or LDAP integration, and how many people must test before cutover. DeployOpen agrees scope, deliverables and timelines in writing before work starts. If your own team does the work, add time for the Linux server build, mail routing tests and a parallel run before you switch live mailboxes.
Can our team move off Zoho Desk without outside help?
A team with Linux and mail administration skills can install FreeScout from the Docker image or a managed host, but the risk sits in the details. FreeScout runs on PHP 7.4 to 8.x with MySQL, MariaDB or PostgreSQL, and mail routing, OAuth and sender authentication decide whether customer messages arrive. FreeScout also publishes releases roughly weekly, so someone must own patching, backups and upgrades after go-live. If that skill set is thin, outside help is one option. DeployOpen plans, implements, hardens, backs up, upgrades and supports self-hosted platforms in your own infrastructure, under written scope or a retainer.
What access and people does a FreeScout move need from us?
The move needs four things from your side, and each should have a named person.
Does FreeScout cover SLA and multi-department needs from Zoho Desk?
Confirm this before you commit, because FreeScout's modules page does not list a dedicated SLA or multi-department module. The Workflows module is the closest supplied match for automated routing and rules, and Satisfaction Ratings and Time Tracking cover other reporting needs. Map every department, team and SLA policy you run in Zoho Desk to FreeScout mailboxes and workflows in a test instance. Ask the vendor to demonstrate the exact escalation timing and reporting output your managers depend on. Any gap that remains should be written into the scope as a custom build or a documented manual step.
What changes for agents after the switch from Zoho Desk?
Agents will see a different interface, and most of the change is in navigation, saved replies and automation. FreeScout is built around a shared inbox of email conversations, and its README says conversations from WhatsApp, Telegram, Facebook, Slack and live chat can be centralized. Mobile apps for Android and iOS support the same functionality and modules as the web version. Plan a short training session, run a pilot with one mailbox, and document the saved replies, tags and workflows agents use daily. Confirm which channels your agents use today so the cutover covers all of them.
Which FreeScout modules do we need, and do we pay for them once?
Module licenses are one-time purchases for a single FreeScout instance, and each includes lifetime updates. The modules page lists LDAP Integration, SAML SSO, API and Webhooks, Knowledge Base, Satisfaction Ratings, Time Tracking and Workflows as paid options, while AI Integration and S3 Storage are free. Make a list of the Zoho Desk features your team uses today, then match each one to a module before you buy. Ask the vendor whether a separate staging or test instance needs its own license, because that changes the one-time total.
How DeployOpen helps evaluate, implement and migrate FreeScout
DeployOpen plans, implements, customizes, integrates, hardens, backs up, documents and supports self-hosted open-source platforms inside your own infrastructure. For a move from Zoho Desk to FreeScout, the work starts with agreeing which mailboxes, modules and workflows you actually need, then builds and documents them in writing before any cutover.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts
- We inventory shared mailboxes, agents, routing rules and the Zoho Desk features your team depends on today
- We map each feature to FreeScout core, a paid lifetime module or a gap that needs a workaround
- Ask us to confirm which FreeScout modules fit your needs, since module availability can change
How we build
- We deploy FreeScout in your cloud account, data center or air-gapped network with your chosen database and mail setup
- We configure SMTP, IMAP or OAuth mailbox connections for Microsoft 365 or Google Workspace where your mail runs
- We set up modules you have licensed, such as SAML SSO or Knowledge Base, and test them end to end
- We test email routing, attachments and notifications with a representative sample of real conversations
How we hand over
- Handover includes written runbooks for installation, upgrades, mailbox configuration and module licensing
- We document how Zoho Desk exports were transformed and loaded, including what was left out and why
- Your team receives an operating guide covering agent roles, backups and the update routine
- Compliance evidence, where your assessor needs it, is prepared for review by your independent auditor
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover
- A retainer can cover FreeScout version upgrades, module updates and backup restore tests on a schedule you agree
- Security testing of the deployed help desk can be scoped separately, including its web and API surfaces
- Ask for the retainer terms, response expectations and included services in the written quote
