Open-source alternative to Help Scout Docs: the short answer
If you are a support or documentation lead looking to move off Help Scout Docs at renewal or to meet a data residency requirement, you can replace it on self-hosted infrastructure. FreeScout's paid Knowledge Base module, Chatwoot's Help Center portal or a standalone BookStack site can each host your articles inside your own environment. The choice comes down to whether you want documentation sitting next to the shared inbox or in a dedicated documentation system. Keeping articles inside FreeScout or Chatwoot means agents search the same tool they answer tickets in, and customers reach help content from the same support setup. The trade-off is that these modules are built around support workflows, so you should check whether their article structure, editor and permissions meet the needs of your technical writers. A standalone BookStack instance, organized as books, chapters and pages, gives you a fuller documentation system with its own role and permission model, at the cost of running one more application and linking it to your support tool. Whichever path you choose, plan the cutover before moving content. Help Scout Docs article URLs are likely linked from emails, macros, your website and your support widget, so inventory those references and decide which new URLs will replace them, including redirects where the platform supports them. Confirm the export options for your current Docs content with Help Scout and test that the new URLs and widget links resolve before you switch off the old site.
Which open-source option covers each Help Scout Docs capability
This table maps the main Help Scout Docs capabilities to FreeScout Knowledge Base, Chatwoot Help Center and BookStack. Read each cell as a starting point, since knowledge base features change between releases and should be checked against the current version before you commit.
| Docs capability | FreeScout Knowledge Base | Chatwoot Help Center | BookStack |
|---|---|---|---|
| Articles and collections | Articles grouped in a paid lifetime module, licensed per single instance | Articles, FAQs and guides in a Help Center portal | Books, chapters and pages grouped on shelves |
| Public and private visibility | Confirm per-article and per-category visibility in the module | Confirm public portal versus internal-only content in your release | Pages can be restricted by role and permission |
| Search | Confirm search scope and ranking in the module | Confirm portal search behavior in your release | Built-in search across books and pages; confirm indexing options |
| Branded public site | Confirm custom domain and theme options in the module | Portal branding available; the Premium plan lists custom branding | Theme and logo customization available; confirm for your install |
| Widget links from the support widget | Link to articles from the module; confirm URL structure after migration | Native integration with the live chat widget | No inbox or widget; links must be rewritten to BookStack URLs |
| Analytics | Confirm article view reporting in the module | Portal and conversation reports listed; confirm article-level views | Confirm page view history and activity logs in your version |
| Sign-in control | SAML SSO is a separate paid module; confirm access rules | SSO with SAML is on the Enterprise plan | OIDC, SAML2 and LDAP sign-in with enforced MFA by role |
| Inbox or ticketing | Included, since the knowledge base sits beside the shared inbox | Included, as an omnichannel inbox | Not included; BookStack has no inbox and needs a separate help desk |
Choosing between FreeScout, Chatwoot and BookStack for articles
Help Scout Docs bundles articles with the shared inbox, so each replacement splits that job differently. The three options below differ in how much they bundle with the support tool, how they handle sign-in and how much infrastructure they need. Pick the one that matches where your articles are read and who maintains them.
FreeScout with Knowledge Base module
FreeScout is AGPL-3.0 and keeps the article library next to the shared inbox, so agents can link an article in a reply without leaving the tool. The Knowledge Base is a paid module sold as a lifetime license for a single FreeScout instance, with lifetime updates. This fits teams that want one self-hosted application for mail and articles and can accept an AGPL obligation. Check whether the module covers the public-facing article views and search your customers expect, and confirm how it handles redirects from old Help Scout Docs URLs.
Chatwoot Help Center portal
Chatwoot's Help Center is a portal for articles, FAQs and guides that sits inside the same omnichannel product as its live chat widget, email and social inboxes. The core is MIT Expat, but single sign-on with SAML arrives only on the paid Enterprise Edition, and Premium Support adds Captain AI and custom branding. It fits teams that already plan to run Chatwoot for chat. The main trade-off is infrastructure: Chatwoot requires PostgreSQL and Redis, and its requirements page lists sizing that grows with conversation volume. Confirm that the portal's URL structure and multi-language support meet your needs before you commit.
Standalone BookStack site
BookStack is MIT licensed and organizes content as books, chapters and pages grouped on shelves, which suits long-lived documentation with clear owners. It supports OIDC, SAML2 and LDAP sign-in, and built-in multi-factor authentication can be enforced per role. It runs separately from the support tool, so agents link to it instead of embedding it. The trade-off is that BookStack has no official Docker images and relies on community setups, so you need your own support channel and patching routine. Ask your partner to confirm which PHP and database versions your chosen installer targets.
Choosing by reader and maintainer
The right choice depends less on features than on who reads the articles and who edits them. Customer-facing articles that must sit on your own domain with brand controls point toward a portal. Internal runbooks that agents and engineers maintain point toward a standalone wiki-style site with strong access control. Ask who will own updates, how redirects from old Help Scout Docs links will be handled, and whether article search must work across all sources. Write those answers down before the migration plan is set.
How to keep Help Scout Docs links and the support widget working
Before any article moves, build a complete inventory of every place that points at a Help Scout Docs URL. Start with the public article addresses, then search the places where links hide: outbound and auto-reply emails, saved replies, macros, the Beacon or help widget embedded in your website and product, in-app help tooltips, onboarding emails, social profiles, and partner or marketing pages. Export or crawl what you can, and record for each link who owns it and whether it can be edited by your team. The inventory is the cutover checklist: a link you did not find is a support ticket you will receive later.
Once the inventory exists, build a link map that pairs each old Docs article URL with its new address on FreeScout's Knowledge Base module, Chatwoot's Help Center portal or your BookStack site. Keep the map in version control so it can be reviewed and reused. Then confirm whether your chosen platform can answer old URLs with a permanent redirect to the new page. Do not assume it can. Test this in a staging instance with a few sample articles, and ask the vendor or check the official documentation for the exact behavior. If no redirect feature exists, plan for a web server rule on your own domain, or accept that emailed and bookmarked links will break and must be replaced at the source.
Replace the widget or help center reference in the product itself. For Chatwoot, the website live chat widget and Help Center portal are configured in the product, so confirm the new portal domain and update the widget script or link on each site. For FreeScout, confirm which module and embed options are available on your license before removing the Help Scout Beacon snippet. Test on every template and environment, including the mobile site and any single sign-on pages. Schedule the change so old and new addresses both work for a defined period, and keep the old Docs site online until the redirect or replacement test has passed and inbound link traffic has been reviewed.
Running the new knowledge base beside the rest of the suite
This setup leaves conversations, mailboxes and agent accounts in Help Scout while Docs moves to a new site. Agent sign-in does not change on day one, so identity work is limited to the public documentation. The main effort is in the links: every article address that the support widget, saved replies and macros point to must resolve to the new location, and agents need to know which system holds the answer they are citing.
- Identity: Agents keep signing in to Help Scout. Decide whether readers of the new site are anonymous customers or internal staff, and create accounts only for the internal group.
- Article links: Update the widget and every article link inside saved replies, then set permanent redirects from the old Docs addresses. Confirm with Help Scout the exact address pattern its Docs widget generates.
- Agent replies: Agents keep the same reply editor, so a link to the new site appears as an ordinary URL. A short internal note listing which articles moved helps agents cite the right page.
- Reporting: Article view and search data in Help Scout stop reflecting the new site. Confirm which analytics you need to keep on the new host and how you will collect them.
Before you retire the old Docs addresses, check the redirect list against the articles that appear most often in saved replies.
Moving the inbox and the knowledge base to FreeScout or Chatwoot removes the cross-system link problem, but it moves identity work into the new help desk. FreeScout's Knowledge Base is a paid module with a lifetime license for a single instance, and its SAML SSO and LDAP Integration are also paid modules. Chatwoot's Help Center portal is part of its open-source code, while SAML SSO is in the Enterprise Edition, which Chatwoot lists at $99 per agent per month on its self-hosted plans page. The Premium Support tier, listed at $19 per agent per month, adds Captain AI, custom branding and roles but not SAML.
- Identity on FreeScout: Accounts are local by default. Budget for the SAML SSO or LDAP module if agents must sign in through your directory, and plan offboarding for any local accounts you keep.
- Identity on Chatwoot: Check whether your directory integration needs the Enterprise Edition before committing to a support tier, since SSO with SAML is not part of Premium Support.
- Article links: Map each old Docs address to the matching article or portal path on the new system. Confirm the URL structure of the knowledge base module or Help Center in a test instance before you write redirects.
- Agent view: Agents can search articles from inside the conversation and insert a link into the reply without leaving the ticket. Confirm in a test instance whether the article appears as a link or as an embedded snippet.
Before choosing between FreeScout and Chatwoot, test SSO and article URL mapping in a staging instance that uses your real directory settings.
This setup keeps the help desk where it is, whether that is Help Scout or a self-hosted inbox, and runs BookStack as a separate documentation site that the inbox links to. BookStack has OIDC, SAML2 and LDAP sign-in and built-in multi-factor authentication that can be enforced per role, so identity can be handled in one place for the documentation even though the inbox has its own sign-in. Articles sit at BookStack's own addresses, so the link work is the same as in the other setups.
- Identity: Connect BookStack to your identity provider over OIDC, SAML2 or LDAP and enforce MFA by role. Set permissions per shelf so that public articles can be read without an account while internal books stay restricted.
- Article links: Inbox macros, saved replies and the widget point to BookStack page addresses, and old Docs paths need redirects. Agents paste the full address into replies.
- Agent view: Agents see a link, not the article text, unless the inbox supports link previews. Confirm that preview behavior in your inbox before promising it to agents.
- Installation: BookStack provides official install scripts for Ubuntu 22.04, 24.04 and 26.04 and requires PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later. It does not publish official Docker images, so a community container image means you own its update path.
Confirm your server's PHP and database versions against the BookStack installation documentation before choosing this setup, because those versions are minimums.
Moving Help Scout Docs articles and collections
This sequence moves your Docs articles, collections and images into a self-hosted knowledge base, keeps the links your support widget and emails depend on working, and ends with a tested cutover that your team and customers can rely on.
Confirm the Docs export scope and format
Ask Help Scout which export options your plan and account support for Docs articles, collections, categories, images and attachments, and whether the export runs through the Docs API or another method. Confirm the rate limits that apply to your plan, because large knowledge bases may need to be pulled in batches. The person who owns Help Scout admin access makes this request. You know this step is done when you have a written answer on scope, format and limits, and a full inventory of published and draft articles with their collection assignments.
Export articles, collections and media
Pull every published article, its collection, its URL slug and its embedded images from Docs, and store the raw export in a secured location on your own infrastructure. Record the count of articles per collection and the count of images so you can compare them after import. The support or documentation owner runs the export with an administrator account. You know this step is done when the record counts match the inventory from the previous step and the image files open correctly.
Map collections to the target structure
Decide where each Docs collection lands. In FreeScout, the Knowledge Base module uses categories, in Chatwoot the Help Center portal uses categories under portals, and in BookStack collections typically become shelves with books inside them. Write the mapping in a table that lists the old collection, the new location and the owner of that content. Review the table with the support lead before any content moves. You know this step is done when every collection has a named destination and an owner has signed off.
Convert content and rehost images
Convert article bodies from the Docs format into the editor format of the target platform, then re-upload images to storage you control, such as the local disk or an S3-compatible store. Keep the original titles, slugs and meta descriptions where the target allows. Expect some formatting, tables and embedded blocks to need manual cleanup. The content editor or technical writer performs the conversion, and a test import on a staging instance comes first. You know this step is done when a sample of articles renders with the same text, headings and images as the originals.
Check internal links and build a link map
Find every link between articles and every link from the support widget, emails, macros and saved replies that points to a Docs URL. Build a link map that pairs each old URL with its new URL, and rewrite internal references to the new addresses. Where a page has no equivalent, decide whether to point the old URL to a related article or to a clear fallback page. Identify the owner of each external reference before changing it. You know this step is done when every old URL in the export has either a new target or a documented decision.
Set up redirects from the old Docs URLs
Configure redirects on your own web server or reverse proxy so that old Docs addresses send visitors to the matching new pages, using the link map as the source. Test a sample of old URLs from a clean browser session and from the support widget. Confirm that search engine indexing and any bookmarked links still resolve. The web or platform engineer owns this configuration. You know this step is done when the test list of old URLs returns the expected pages and no redirect loops appear.
Run user acceptance testing with support staff
Have support agents and a small group of customers search the new knowledge base, open articles from the widget and follow internal links. Collect findings in a shared tracker with severity labels and owners. Retest after each fix, and confirm that the search, categories and access settings behave as the mapping specifies. The support lead coordinates the testers. You know this step is done when every critical and high finding is closed and the testers have signed off on the sample journeys.
Cut over DNS and the support widget
Update the DNS record for the knowledge base hostname and replace the Docs script or link in the support widget with the new endpoint. Keep Help Scout Docs available in read-only form until you have confirmed that traffic and search behavior are healthy, and keep the export archive for your records. Confirm that the widget loads on every page where it appears. The platform owner performs the change under your change process. You know this step is done when the new hostname resolves, the widget opens the new help content, and the old URLs redirect as tested.
What does it cost and take to replace Help Scout Docs?
What are the cost components of replacing Help Scout Docs?
The cost falls into four components: hosting, software licensing, staff time and migration work. Hosting is recurring and paid to your cloud provider or data center. Software is mostly free to download, but FreeScout's Knowledge Base is a paid module sold as a lifetime license for one instance, Chatwoot's Help Center portal is included in its Community Edition, and BookStack is MIT licensed with paid support plans available from its developers. Staff time covers content review, configuration and admin work, and it is usually the largest unpriced line. Ask any partner to split its quote by these components so you can see what recurs.
Does FreeScout's Knowledge Base module cost extra?
Yes. FreeScout's official modules page sells the Knowledge Base module as a lifetime license for a single FreeScout instance, with lifetime updates included. The page lists other paid modules such as SAML SSO and LDAP Integration, while the AI Integration and S3 Storage modules are free. Confirm the current license terms on the modules page before budgeting, and check whether your article volume and image storage need the S3 Storage module.
When do I need a Chatwoot plan to replace Help Scout Docs?
You need a paid Chatwoot plan only if you require features the Community Edition does not include, such as SSO with SAML or SLA policies, which sit in the Enterprise Edition. Chatwoot's self-hosted plans page lists Premium Support at $19 per agent per month, which adds Captain AI, custom branding and priority support, and the Enterprise Edition at $99 per agent per month. Multiply the per-agent price by the number of agents who need the feature, not by everyone who reads articles. Confirm current prices on Chatwoot's pricing page before you commit.
Is BookStack support worth buying for a standalone docs site?
BookStack is free under the MIT license, so you can run it without paying anyone. Paid support plans and sponsorship are available from the project's developers and are optional. Buy support if your team lacks PHP and Linux administration skills, needs a response commitment for an internal documentation portal, or wants upgrade help. Ask the vendor what the support plan covers, how upgrades are handled and whether it includes help with single sign-on configuration.
What makes replacing Help Scout Docs take more effort?
The main drivers are article count, images and embedded files, custom domains, and sign-in requirements. Large libraries need more time for export mapping, link rewriting and review. Image-heavy articles require asset transfer and checks that images still display after the move. Custom domains need DNS and TLS work, and the support widget links must be repointed to the new URLs. Single sign-on or role-based access for internal articles adds configuration and testing. Inventory these four factors before you ask for a quote, since they explain most of the difference between proposals.
Can my team replace Help Scout Docs without outside help?
Yes, a team with Linux, web server and database administration skills can deploy FreeScout, Chatwoot or BookStack alone. FreeScout runs on PHP with MySQL, MariaDB or PostgreSQL, BookStack requires PHP 8.2 or later with MySQL 8.0 or MariaDB 10.6 or later, and Chatwoot requires Ruby 3.2 or later with PostgreSQL and Redis 7.0 or higher. Outside help is most useful for moving articles and redirects without breaking links, hardening the server, and setting up backups and upgrades. Decide which of these your team will own before you start.
How long does the migration take, and what should the scope say?
No supplied figure gives a reliable duration, so the timeline depends on your article count, images, integrations and staff availability. Agree on a timeline in a written scope before work starts, and make sure it lists the content to move, the link redirects to verify, the sign-in method, the cutover date and the acceptance tests. Most DeployOpen engagements are fixed-scope, so the scope and timeline are fixed in writing before any work begins.
What should I ask a partner for in a quote?
Ask for a quote built from a written scope, with each cost component listed separately: hosting setup, software configuration, any paid module or plan, migration of articles and collections, redirects for existing support widget links, testing, backup setup and handover documentation. Ask what is one-time and what recurs, which party pays for hosting and licenses, how upgrades are handled after go-live, and what is excluded. Ask how the partner validates that every widget link resolves before you retire Help Scout Docs.
Risks to plan for in the Docs migration
Moving a knowledge base changes more than the content. URLs, search rankings, article history, media, access rules and widget settings all shift at once, and each can break without an obvious error. The cards below pair each risk with a mitigation and a check to run before you switch the support widget to the new site.
Broken external links
Help Scout article URLs are linked from emails, product screens, partner portals and bookmarks that you do not control. Before cutover, export every article URL from Docs and map each one to its new address on FreeScout, Chatwoot or BookStack. Keep the old Help Scout paths answering with a permanent redirect for as long as your links are in circulation. Check by crawling a sample of inbound links from your analytics and confirming each returns the destination article, not a generic home page.
Search ranking loss after URL changes
Search engines credit established article URLs. If the new site uses different paths or lacks redirects, pages that ranked for product questions can drop out of results for weeks. Plan the URL structure before importing content, mirror the old slugs where the new platform allows it, and submit a fresh sitemap after cutover. Check that each redirected URL resolves in a single hop and that your search console shows no spike in not-found errors in the first weeks after launch.
Lost article history and authorship
Help Scout does not give you a clean history of who edited an article and when, so a naive import often flattens every page to a single author and a single date. Decide which history matters for audit or support purposes, then export revision data where available and record the original author and last-updated date in a page field or BookStack page metadata. Check a sample of imported articles against the originals for author, date and version notes before you retire the source.
Image and attachment loss
Articles often embed screenshots and link to PDFs stored on Help Scout's file hosting. When you copy the HTML, those references can keep pointing at the old service, which may stop serving files once the account is closed. Download every embedded image and attachment, store them on your own server or object storage, and rewrite the references in each article. Check by loading every migrated article with images disabled from the old domain and confirming nothing breaks.
Access control mismatch with private articles
Some Help Scout content is internal-only, such as agent runbooks or pricing notes, while other articles are public. The new platforms handle visibility differently: Chatwoot's Help Center is a public portal, FreeScout's Knowledge Base is a paid module, and BookStack uses role and permission settings with optional SSO. Map each collection to an audience before import, then confirm that private content is not reachable by anonymous visitors through direct URLs, search or attachments.
Widget configuration drift
The Help Scout Docs widget or Beacon usually sits in your product and website with its own settings for search, article links and contact options. After cutover, those settings can still point to the old knowledge base, show articles from both sources, or lose the contact form. Inventory every place the widget loads, record its settings, and replace them in one controlled change. Check each page in a staging environment, then confirm that search results, article links and the contact path all resolve to the new platform.
When staying on Help Scout Docs is still the right call
Staying on Help Scout Docs is the right call when the knowledge base supports the team's work without being a system the organization must control. If the team wants a vendor-hosted site that someone else maintains, has no capacity to patch a server or manage PHP and database upgrades, and has no contractual requirement to keep help content in a specific country, the operating cost of a self-hosted replacement is hard to justify. With Docs, the team's effort goes into writing and reviewing articles. Before deciding, confirm the current Docs plan terms, custom domain and sign-in options, and how article content, collections and redirects can be exported, because those answers set the baseline for any comparison.
The view changes when specific conditions apply. A data residency or sovereignty rule that requires help content, or the customer details quoted in it, to stay in your own environment is a frequent driver. Other triggers include sign-in tied to your own identity provider through SAML or LDAP, several brands or languages managed by separate teams, or a need to keep article history and attachments under your own backup policy. Write each of these down as a requirement before comparing platforms. Then test the FreeScout modules list, the Chatwoot Help Center portal and BookStack against the same list, because the paid modules and plan tiers differ in what they include.
Also weigh the cost of leaving. If the knowledge base is linked from the support widget, email signatures, product screens and public documentation, every move creates broken links unless redirects are planned. Ask who owns the URL structure, and check whether Help Scout's export returns article bodies, collections and images in a form you can reuse. A short audit of inbound links, and a decision on keeping the old domain for redirects, will show whether migration is a small task or a project in its own right. If none of the conditions above apply, keeping Docs and revisiting the decision at renewal is a defensible outcome.
