Which fits: Help Scout or self-hosted FreeScout for your shared inbox
If a renewal, a per-user price change or a data residency requirement has put your shared support inbox under review, the first question is who should operate the software. Help Scout fits teams that want a managed service with no servers to own, along with built-in Docs and Beacon for the knowledge base and in-app widget. A self-hosted FreeScout fits when conversations must stay inside your own environment, when you run many agents or mailboxes and want to avoid per-seat growth, or when your team is ready to operate a PHP application on Nginx, Apache or IIS with MySQL, MariaDB or PostgreSQL. Either way, the core inbox work of email, assignments and saved replies is covered by both, so the difference lies in operations, data location and add-ons.
Start by listing the modules you actually need. FreeScout's core is free and its README lists unlimited agents, tickets and mailboxes, but its SAML SSO, LDAP Integration, Knowledge Base and API and Webhooks modules are paid lifetime licenses for a single instance, while AI Integration and S3 Storage are free. Confirm each module's current price and terms on the FreeScout modules page before comparing totals. Then assess in-house capacity: someone must patch the host, manage backups, handle mail deliverability and apply FreeScout releases, which currently arrive roughly weekly. Ask Help Scout for its current per-user pricing for the same mailbox count so you compare like with like.
The decision ultimately turns on three things: which modules you require, whether your team can operate the stack, and which compliance obligations apply to customer correspondence. If regulators or contracts require that support data never leave your infrastructure, self-hosting moves that responsibility to you, including access control, logging and retention. Document those controls with your compliance lead before migration. If none of these constraints apply and your team prefers a managed service, staying with Help Scout is a reasonable outcome.
Which option fits each support scenario
This table matches common support team situations to the better fit between Help Scout and self-hosted FreeScout. Read each row for the condition under which the advantage matters, because the same feature can be decisive for one team and irrelevant for another.
| Scenario | Better fit | Why |
|---|---|---|
| Small team on email only | FreeScout | Shared inbox, mailboxes and collision detection cover email support, and unlimited agents and mailboxes are included at no license cost. The advantage holds only if you can run the server and email integration yourself. |
| Team needing SAML or LDAP sign-in | FreeScout with paid module, or Help Scout | SAML SSO and LDAP Integration are paid lifetime FreeScout modules. Help Scout's own plan tiers should be checked for the sign-in option you need, since this comparison does not confirm them. |
| Team that relies heavily on Docs or Beacon | Help Scout | Docs and Beacon are built into Help Scout's hosted product. FreeScout offers a paid Knowledge Base module and widgets, so expect to rebuild and re-link articles if you switch. |
| Regulated team that must keep conversations in its own environment | FreeScout | Self-hosting keeps conversations, attachments and customer data inside your infrastructure. Your compliance obligations then fall on your own controls, hardening and backups, not on a vendor. |
| Team with no internal sysadmin capacity | Help Scout | FreeScout requires someone to patch PHP, the database, mail settings and backups. Without that capacity, a hosted product or a managed hosting provider for FreeScout is usually the safer choice. |
| Team with a mix of email and chat channels | Help Scout, or evaluate Chatwoot | FreeScout centralizes email, but its listed channels need confirming for your needs. Consider the sibling Chatwoot comparison if live chat and social messaging are central. |
Where your customer conversations live under each model
Help Scout keeps your conversations in its own SaaS, while FreeScout stores them wherever you choose to run it. With Help Scout, the vendor operates the infrastructure, so your review of data location is a review of its hosting terms and regions. With FreeScout, the database, mail store and attachments sit on a server you control, whether that is a VM in your cloud account, a data center, or an air-gapped network. The choice you make here determines who can access raw ticket data, where backups live and which jurisdiction applies to them. Confirm with Help Scout which regions and sub-processors apply to your account, and decide where your FreeScout instance will run before you move any mailbox.
FreeScout offers several installation routes, and each one shifts responsibility differently. The Docker image and a manual install on Nginx or Apache give you full control over the operating system, PHP version, database and backup schedule. One-click installs through Softaculous or Cloudron are faster but leave patching and configuration to the installer's defaults, so check them against your baseline. Managed hosts take on server operations under a contract you must read closely for data location, backup retention and incident notice. Shared hosting is the least suitable choice for customer conversations of any sensitivity, because you cannot control the host's isolation, logging or database access. The FreeScout README states that it has no minimum CPU or RAM requirements, which says nothing about whether a given host meets your security needs.
Identity integration and audit evidence move with the hosting choice. Help Scout's SSO and user lifecycle run inside its platform, so your evidence comes largely from its admin settings and reports. In FreeScout, SAML SSO and LDAP integration are paid lifetime modules, so you must buy them, deploy them and keep their configuration under change control. Access logs, admin actions and database backups will be yours to collect and retain. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports or certifications; an independent auditor or certification body makes that determination. Ask your assessor early which evidence they expect for hosting, identity and backup, and map each item to an owner in your own environment.
What you pay for in each model
Help Scout and self-hosted FreeScout spread cost across different line items. Some costs recur every month or year, others are paid once, and several sit outside the software price entirely. Use these cards to build a like-for-like comparison before you set a budget or ask for a quote.
Help Scout subscription and add-ons
Help Scout is a recurring subscription, and the amount scales with the number of users and the features on each plan. Capabilities such as HIPAA compliance or additional modules may be add-ons on top of the base plan. Ask Help Scout for the current price of every add-on you need, the user count it is quoted for, and whether the price changes at renewal.
FreeScout module licenses
The FreeScout software itself is AGPL-3.0 and carries no per-agent or per-mailbox fee. Paid modules such as LDAP Integration, SAML SSO, API and Webhooks, and Knowledge Base are sold as lifetime licenses for a single FreeScout instance, with lifetime updates. Confirm current module prices on the modules page, and check which modules you need before you count them as one-time spend.
Server and hosting
Self-hosting moves the platform cost onto infrastructure you pay for, either your own servers, a cloud account or a managed host. The recurring part is compute, storage and backups, and it grows with mailbox volume, attachments and retention. FreeScout's README states there are no minimum CPU or RAM requirements, so size the environment against your own traffic, not the documentation.
Outbound email deliverability
A shared inbox sends replies from your domain, so deliverability depends on your SPF, DKIM and DMARC records and your sending service. Transactional email relays are usually a recurring fee charged by volume. Help Scout handles sending within its own platform, so compare what each option expects you to configure and monitor.
Staff time to operate and patch
Self-hosting adds internal labor for installs, PHP and database upgrades, module updates, backups and monitoring. This is a recurring cost even when the software is free, and it is paid in staff hours. Estimate the hours per month from your own team's capacity, and decide whether that work stays in-house or sits under a fixed-scope support retainer.
Migration of past conversations
Moving historical threads, attachments and customers is a one-time project. The cost depends on how much history you keep, how much data the Help Scout Inbox API returns within plan rate limits, and how many mailboxes and saved replies must be rebuilt. Ask for a written scope that names the data types, the cutover approach and what happens to old links.
How a move from Help Scout to FreeScout runs
The sequence turns Help Scout's shared inboxes, saved replies and customer history into a FreeScout instance your team controls, with mail routing switched only after the new system has been verified.
Inventory mailboxes, saved replies and integrations
Before any data moves, list every Help Scout mailbox, its forwarding and email addresses, saved replies, workflows, tags, and each connected app or webhook. Record which mailboxes send outbound mail from a custom domain, since those will need authentication records on the new server. Assign an owner to each mailbox and note which features your team actually uses, because that list decides which FreeScout modules you will need to buy. The output is a signed-off inventory that both support leadership and the engineers who will build the instance can read. The sibling page on migrating from Help Scout to FreeScout covers the field-level detail of this mapping.
Export conversations and customers through the API
Pull threads, attachments and customer records from the Help Scout Inbox API using OAuth 2 credentials, and plan the run around Help Scout's published rate limits for your plan. Write the export to storage you control and keep the raw files as an untouched copy. Spot-check a sample of conversations for missing attachments, broken threads and customer records that have duplicate email addresses. The output is a complete, checksummed export with a short log of any records that failed. The sibling page on exporting data from Help Scout explains what the API returns and what the CSV or Excel reporting export does not cover.
Stand up FreeScout and its database
Have your platform or infrastructure team deploy FreeScout on your own servers, cloud account or container platform, using a supported PHP and database combination from the FreeScout README. Configure the web server, background jobs for mail fetching, backups and TLS. Confirm that the instance starts, that administrators can log in, and that a test mailbox can send and receive mail. The output is a working, empty instance with a documented build and a tested restore of its database.
Configure mailboxes and email authentication
Create one FreeScout mailbox for each Help Scout mailbox, connecting over SMTP, IMAP or POP3, or through OAuth for Microsoft 365 or Google Workspace where your tenant allows it. Set the SPF, DKIM and DMARC records for each sending domain so that outbound replies reach customers' inboxes, and test with messages to several major mail providers. Work through deliverability with your mail team before you rely on the new instance. The output is a set of mailboxes that send and receive test mail with passing authentication results. Ask your email provider and your DNS team to confirm the exact records for your domains.
Import or re-create conversation history
Load the exported conversations into FreeScout using FreeScout's migration service or an API-based import written by your engineers, then re-create saved replies, tags and customer records on the new instance. Compare record counts and a sample of threads against the export log, and fix mapping errors before loading production volumes. Keep the import repeatable so that a corrected run can replace a faulty one. The output is a reconciliation report showing which records loaded, which were transformed, and which need manual handling.
Buy and test the required modules
Purchase only the FreeScout modules that match the inventory from the first step, such as the paid modules for SAML, LDAP, API and webhooks, Knowledge Base, or Workflows. Check the module list on FreeScout's modules page for what each module covers and whether it is a lifetime license for a single instance. Install each module in a staging copy, then test the workflows your agents depend on, including SSO sign-in and any webhooks to internal systems. Confirm which features you intend to replace with other tools rather than with modules. The output is a test sign-off for each module with named owners and a record of licenses held.
Cut over mail routing
Schedule the change of mail routing with a rollback plan. Update forwarding rules or MX records, and any customer-facing help widgets or links, so that new inbound mail reaches FreeScout. Keep Help Scout running during the change so that messages in flight can be checked on both systems. Tell agents which system holds live conversations and how to report problems. The output is a confirmed routing change and a log showing that new messages arrive in FreeScout and that outbound replies send correctly.
Retire Help Scout after verification
Keep Help Scout available for a verification period agreed in advance by your team, then compare mailbox traffic, reply times and any integrations that depended on Help Scout. Confirm that your retained export archives are stored where your retention policy requires, and check your contract for the terms that govern closing the account. Only then close the Help Scout subscription. The output is a closure record listing the archive location, the date of final sign-off and the owner of the archive for future requests.
Questions buyers ask before switching from Help Scout
How much does it cost to move from Help Scout to self-hosted FreeScout?
The software itself costs nothing to download, because FreeScout is licensed under AGPL-3.0 and its README lists unlimited agents, tickets and mailboxes. The recurring and one-time costs come from the components around it: a server or hosting plan, mail infrastructure, administration time, and any paid modules. Modules are sold as lifetime licenses for a single FreeScout instance, so cost depends on which ones you need, such as SAML SSO, LDAP Integration, Knowledge Base or API and Webhooks. The AI Integration and S3 Storage modules are free. Ask any implementation partner for a quote that separates hosting, module licenses, migration, testing and ongoing support, so you can compare each line with your current Help Scout invoice.
How long does a FreeScout migration take?
The duration depends mostly on the volume of conversations, attachments and customers to move, the number of mailboxes and saved replies to rebuild, and how many modules you need configured. Email routing is often the longest step, because your mail domain, SPF, DKIM and DMARC records and inbound forwarding must point to the new server before cutover. Parallel running, user acceptance testing and staff training add time too. A fixed-scope written plan should state the phases, deliverables and dates before work begins, so ask for a timeline tied to your specific data volumes rather than a generic estimate.
What does our team need to supply for a FreeScout move?
You need four things in place before work starts. First, someone with Linux, web server, PHP and database administration skills to run the platform, since FreeScout runs on Nginx, Apache or IIS with PHP 7.4 to 8.x and MySQL, MariaDB or PostgreSQL. Second, control of the mail domain, including DNS records and the mailboxes that receive customer email. Third, a named backup owner who will test restores, not only schedule them. Fourth, access to the Help Scout Inbox API with an account that can export conversations, threads, attachments and customers. Confirm each of these with your IT and security leads early, because gaps here are the most common source of delay.
Can our own team migrate from Help Scout to FreeScout without a partner?
A capable administrator can install FreeScout from the Docker image or a supported host and configure mailboxes, but the migration is where the effort concentrates. Pulling conversations, threads and attachments through the Help Scout Inbox API, mapping users and mailboxes, and checking that every thread arrives intact requires scripting and verification. FreeScout also offers a migration service, which you should evaluate for coverage of your data types. Teams that handle regulated customer data often bring in outside help for scoping, testing and documentation. Decide early which steps your staff will own and which need an external specialist.
Which Help Scout features have no direct FreeScout equivalent?
Most core shared inbox functions have a close match, including shared mailboxes, email over SMTP, IMAP and POP3, and OAuth for Microsoft 365 and Google Workspace. The gaps appear in areas that depend on Help Scout's hosted products. Help Scout Docs and Beacon are separate products, so your knowledge base and in-app widget need a plan, such as FreeScout's paid Knowledge Base module or a standalone site. Workflow and reporting depth, plus any Help Scout add-ons you rely on, should be compared feature by feature. Ask for a written gap list from the migration partner, and test each workflow your agents use daily.
How does FreeScout module licensing work for one instance?
FreeScout's official modules page sells lifetime licenses for a single FreeScout instance, and each license includes lifetime updates for that installation. You pay once per module for each instance, so a second instance, such as a staging server, needs its own licenses. The page lists modules including LDAP Integration, SAML SSO, API and Webhooks, Knowledge Base, Satisfaction Ratings, Time Tracking and Workflows. Make a list of the modules your organization requires for identity, integrations and knowledge management, then confirm current prices and terms directly on the modules page before budgeting, since these can change.
Who keeps FreeScout secure and backed up after the move?
After cutover, your organization owns patching, TLS, access control, backups and monitoring. FreeScout releases are published regularly, with version 1.8.248 released on October 17, 2026, so plan a recurring upgrade process and test each release in staging first. Define who receives security advisories, how often backups run, and how restores are verified. If you are subject to a compliance framework, DeployOpen prepares systems, controls and evidence for assessments, but independent auditors and certification bodies issue any audit reports or certifications.
What to confirm before you commit
Before you commit, get the current Help Scout plan contents and add-on pricing in writing from Help Scout, not from a comparison page. Ask which features your team relies on (shared inbox rules, Docs, Beacon, reporting, SSO, HIPAA terms) sit on which plan, which add-ons are billed per user or per mailbox, and whether the price you are quoted is annual or monthly. Keep the answer with your renewal file, because the Help Scout side of the comparison is only as current as the day you asked.
FreeScout's core is licensed under AGPL-3.0, but the paid modules are sold as lifetime licenses for a single FreeScout instance. Confirm with the vendor how that license applies if you run separate instances for separate business units, a staging copy, a disaster recovery site or a managed host, and whether the lifetime updates cover the module versions you will run after the next FreeScout release. Ask for the license terms as a document, and confirm whether a module license can move to a replacement server if your hosting changes.
Do not assume that every integration your support workflow needs exists in a module. List each one, such as your SSO identity provider, your ticketing webhooks, your CRM sync, Zapier or Make flows, and any Docs or Beacon behavior your widget depends on, then check it against the modules page and the FreeScout README. Where a feature is missing, decide whether it is a build item for an implementation partner or a process change. Finally, test email deliverability from your own sending infrastructure: confirm SPF, DKIM and DMARC for the support domain, the IMAP or POP3 behavior for each mailbox, and how bounces and replies are routed, since shared inbox reliability depends on it.
How DeployOpen helps you evaluate and move to FreeScout
DeployOpen plans, implements, customizes, integrates, hardens, backs up, documents and supports self-hosted open-source platforms inside your own infrastructure. For a Help Scout to FreeScout move, we start from the shared inboxes, Docs content and modules your team actually uses, then build the target in your environment.
How we scope
- Inventory of shared inboxes, mailboxes, saved replies, workflows and the modules your team needs for parity
- Written scope covering hosting location, email routing, authentication and which Help Scout features are being replaced
- Confirmation of which FreeScout modules you need and the licensing terms your team will accept
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts
How we build
- Installation of FreeScout on your own servers or cloud accounts with the database and web stack you approve
- Configuration of SMTP, IMAP or OAuth mailbox connections for Microsoft 365 or Google Workspace
- Hardening, access control and backup routines set up and tested before any live conversations move
- Test migration of a sample of conversations, threads, attachments and customers to check fidelity
How we hand over
- Runbooks covering installation, mailbox setup, module configuration, upgrades and restore steps
- Documented record of which Help Scout data was exported, how it was mapped and what was left behind
- Walkthrough sessions with your administrators and support agents on daily operation
- Evidence and configuration records prepared for your internal or external compliance assessments
How we support
- Ongoing support, upgrades and continuous testing available as a retainer after handover
- Scheduled review of FreeScout releases so your team can plan upgrades against your own change process
- Security testing of the deployed help desk, if you want an independent view before go-live
- Confirm retainer scope and response expectations in writing with your DeployOpen contact
