Freshdesk alternative for omnichannel teams: when self-hosted Chatwoot fits
Chatwoot is a credible self-hosted replacement for a chat-heavy channel mix, provided your team can run its stack. It puts website live chat, email, Facebook, Instagram, Twitter, WhatsApp, Telegram, Line and SMS in one inbox, and its README also lists a Help Center portal, automation, CSAT and conversation reports. The open question is not whether the channels exist but whether you need the features that sit in its paid editions and whether your staff can operate Ruby on Rails, PostgreSQL and Redis on your own infrastructure. If you are facing a Freshdesk renewal, a data residency question or a lock-in concern, Chatwoot answers the hosting question directly because the data stays where you deploy it.
Freshdesk remains the simpler choice when you have no infrastructure team, want hosted operations and rely on Freshdesk-native features that you would have to rebuild or replace. Paying a vendor to run uptime, upgrades and backups is a legitimate trade, and a small team with a few channels may never need the control that self-hosting gives. Chatwoot fits when customer conversations must stay in your own environment, when most of your volume arrives through website chat, WhatsApp and social messaging rather than formal ticket queues, and when your engineers can take ownership of a Rails application. Chatwoot's self-hosted documentation covers a Linux VM installation script, Docker, and Kubernetes with a Helm chart for larger high-availability deployments, so the deployment method is a choice you make early. Confirm in writing which channel connectors you need, since some depend on third-party account approvals outside your control.
The decision turns on three things. First, channel requirements: list every channel and the volume on each, then check that each is supported in the edition you plan to run. Second, edition features: Chatwoot's Community Edition is free, while Premium Support at $19 per agent per month adds Captain AI, voice calls, custom branding, roles and permissions and priority support, and Enterprise at $99 per agent per month adds SSO with SAML and SLA policies, according to Chatwoot's self-hosted plans page. Check which of these your team actually needs before comparing totals. Third, operating capacity: Chatwoot requires Ruby 3.2 or later, supports only PostgreSQL, recommends Redis 7.0 or higher and lists Ubuntu 20.04 as the only officially supported distribution. Ask whether your staff can own that stack, patch it and monitor Sidekiq memory use, because that operating work is the cost Freshdesk's subscription currently absorbs.
Which option fits each support scenario
This table matches common support setups to the better fit between Freshdesk and self-hosted Chatwoot, based on channels, editions, hosting control and operating effort. Read each row as a starting point, and confirm channel and feature availability in your own environment before deciding, since Chatwoot's Premium Support and Enterprise features are paid add-ons on top of the free Community Edition.
| Scenario | Better fit | Reason |
|---|---|---|
| Chat-first e-commerce on a website widget | Chatwoot | The website live chat widget sits in the same inbox as email and social channels, and the Community Edition covers core chat and reporting at no license fee, though hosting and admin time remain. |
| Multi-channel service with WhatsApp and SMS | Chatwoot | Chatwoot lists WhatsApp and SMS among its inbox channels, but confirm each channel's setup steps and provider requirements in your own environment before committing. |
| Email-heavy support with occasional chat | Depends on the team | If email tickets dominate, a dedicated ticketing system may suit better than a chat-first inbox; Chatwoot can take over both if chat volume grows. |
| Teams that need SAML SSO | Freshdesk, unless on Chatwoot Enterprise | SSO with SAML sits in Chatwoot's Enterprise Edition, which is paid per agent, so the cost comparison changes as agent count grows. |
| Teams that need SLA policies | Freshdesk, unless on Chatwoot Enterprise | SLA policies are listed in Chatwoot's Enterprise Edition; confirm the exact SLA behavior you need against that edition before comparing. |
| Teams that need custom branding, roles and Captain AI | Chatwoot Premium Support | Captain AI, custom branding, agent capacity and roles and permissions are listed in the paid Premium Support tier rather than the free Community Edition. |
| Teams with no infrastructure staff | Freshdesk | Chatwoot requires you to run Rails, PostgreSQL, Redis and background workers, and the ongoing patching and backups fall to your team unless you contract a partner. |
| Teams with in-house platform engineers and data residency rules | Chatwoot | Running Chatwoot in your own or chosen cloud keeps conversations and customer data under your control, though you must confirm which regions and hosting providers meet your policy. |
How a Freshdesk alternative handles WhatsApp, SMS and web chat
Chatwoot puts several channels in one inbox: its README lists a website live chat widget, email, Facebook, Instagram, Twitter, WhatsApp, Telegram, Line and SMS. Before you plan a cutover, list every channel your team runs in Freshdesk today and match each one against that list. Pay particular attention to WhatsApp, SMS and any social account that feeds your queue, because each of these depends on a connection you configure in Chatwoot and on an account you hold with the provider. Note which channels carry the most volume, which ones create the most tickets that later move to email, and which ones your Freshdesk setup handles through a third-party integration that will need a replacement.
Every external channel depends on accounts and approvals outside your team and outside Chatwoot. WhatsApp and SMS connections depend on the messaging provider and, for WhatsApp, on Meta's business account approval, and the approval steps, sender registrations and message template rules can take time that you do not control. Social accounts depend on the platform's app permissions. Ask each provider, in writing, what they require from you, what they will verify, and how long they expect the process to take, and confirm that the account you will connect is owned by your organization rather than an individual employee. Do not schedule a cutover for a channel until its connection has been tested end to end in your own environment, including inbound messages, replies and attachments.
One inbox changes what agents see. A conversation that starts on the website widget and continues by SMS or WhatsApp appears in one place with its history, so an agent does not have to ask the customer to repeat the problem. Auto-assignment by agent availability and team routing decide who receives each conversation, and private notes let agents discuss a case without the customer seeing it. Test these settings with your real team structure and confirm how they behave when an agent is offline. Email ticketing needs separate thought. If your contracts, legal notices or audit trail depend on formal email threads, or if you rely on Zammad's ticket model for email, keep email there and route only chat and messaging channels into Chatwoot, as the sibling page on replacing Freshdesk chat and messaging channels explains.
Freshdesk and Chatwoot capabilities compared
This table compares how Freshdesk and self-hosted Chatwoot cover the workflows a multichannel support team runs every day. Chatwoot entries come from its published feature list and plans page, and some items sit behind paid Premium Support or Enterprise editions. Freshdesk entries tell you what to confirm against your current plan, because Freshdesk plan contents change.
| Capability | Chatwoot (self-hosted) | Freshdesk (what to confirm) |
|---|---|---|
| Live chat and messaging channels | Website live chat widget plus Facebook, Instagram, Twitter, WhatsApp, Telegram, Line and SMS in one inbox. Voice calls need Premium Support. | Confirm which chat, messaging and social channels your plan includes and whether WhatsApp or SMS carries add-on costs. |
| Email is a built-in inbox channel in the Community Edition. | Confirm mailbox limits, shared inbox routing and ticket threading on your plan. | |
| Help center | Help Center portal for articles, FAQs and guides, included in the open-source README feature list. | Confirm which knowledge base features and portal branding your plan includes. |
| Automation and auto-assignment | Automation rules, auto-assignment by agent availability, auto-responders and business hours. | Confirm which automation rule types, assignment methods and business hour settings your plan includes. |
| Teams, canned responses and notes | Teams, labels, canned responses and private notes. Roles and permissions require Premium Support. | Confirm team structure, shared macros and internal notes on your edition. |
| Contact segments and campaigns | Contact segments and campaigns listed in the README feature set. | Confirm whether segmentation and outbound campaigns are included or sold as add-ons. |
| Reports including CSAT | Conversation, agent, inbox, team and CSAT reports listed in the README. | Confirm which report types and CSAT survey features your plan includes. |
| AI responses (Captain) | Captain automates responses to common queries. Captain AI is a Premium Support feature. | Confirm which AI answer and bot features your plan includes and whether they are metered. |
| Integrations | Slack, Dialogflow, Shopify, Google Translate and Linear, as listed in the README. | Confirm native connectors and marketplace apps available on your plan for your tools. |
| SSO and SLA policies | SSO with SAML and SLA policies are Enterprise Edition features. Priority support is Premium Support. | Confirm SSO protocols and SLA policy features available on your plan and support tier. |
| Data export | Data stays in your own PostgreSQL database, so export means database and attachment extraction you run. Confirm the export tooling you need. | Export of tickets, solutions, forums and customers as XML is available to account administrators on every plan. |
Which Chatwoot edition covers which features
The Community Edition is the free, self-hosted release. Its code is available under the MIT Expat license, except content in the enterprise/ directory, which carries its own license, and third-party components keep their own licenses. For many teams this edition covers the core inbox work: website live chat, email, WhatsApp, Facebook, Instagram, Twitter, Telegram, Line and SMS in one inbox, plus the Help Center portal, auto-assignment, business hours, automation, teams, canned responses and the conversation, agent, inbox, team and CSAT reports listed in the README.
- Core channels and inbox: Omnichannel conversations, teams, labels, private notes and contact segments are part of the free code.
- Help Center and reports: Articles, FAQs and CSAT reports do not require a paid tier.
- Your own support: Without a paid tier, you rely on the community, documentation and your own staff for fixes and upgrades.
- Captain and SSO are not included: The AI agent and SAML single sign-on sit in paid editions, so plan manual workflows or another identity approach for those needs.
- Operating cost: Hosting, PostgreSQL, Redis, backups and administrator time still apply.
Before you rely on this tab, confirm with Chatwoot exactly which features are in the Community code path for the version you plan to run, since the enterprise/ directory boundary determines what you can use without a license.
Premium Support is the mid-tier paid edition, listed at $19 per agent per month on Chatwoot's self-hosted plans page. It adds Captain AI for automated replies to common queries, voice calls, custom branding, agent capacity, roles and permissions, and priority support. It matters most when your team needs the AI assistant, phone-style voice conversations, a branded agent experience or finer control over who can see and do what, and when response time from the vendor is part of your requirement.
- Captain AI: Automates responses to common queries, which reduces repetitive agent work on high-volume channels.
- Voice calls: Adds call handling that the Community Edition does not list.
- Roles and permissions: Lets you separate agent duties more precisely than the free tier.
- Agent capacity and branding: Supports larger agent counts and custom appearance for your brand.
- Priority support: Shortens the path to vendor help when production issues arise.
Pricing is per agent, so the monthly cost scales with headcount and recurs for as long as you keep the license. Confirm the current price, agent definition, billing terms and what happens to licenses if you reduce seats before you budget.
The Enterprise Edition is the highest listed self-hosted tier, at $99 per agent per month on the same plans page. It includes everything in the paid tiers and adds SSO with SAML and SLA policies. It matters when your identity team requires SAML-based sign-in through a central identity provider, or when procurement needs a written service level commitment instead of community or standard priority help. It is the tier to evaluate in regulated environments where access control and contractual support are audit questions.
- SSO with SAML: Ties agent sign-in to your central identity provider, so joiners, movers and leavers follow your existing process.
- SLA policies: Defines contractual service levels for vendor support, which your procurement team can compare against internal targets.
- Per-agent cost at scale: At $99 per agent per month, the license line grows quickly with headcount, so a small set of senior agents may justify it while the wider team does not.
- Mixed editions: Verify whether you can license only some agents at this level or must license every agent.
- Exit and renewal terms: Ask how the license behaves at renewal and what a downgrade involves.
Because the enterprise/ directory is under a separate license, check the enterprise/LICENSE file and the current terms with Chatwoot before budgeting, and ask in writing which features each tier covers in your target version.
Where the data lives and who controls it
Chatwoot keeps conversations, contacts and attachments on infrastructure you choose, but that control comes with work the vendor no longer does for you. The cards below cover where data sits, how you deploy it, how access is managed, and who is responsible for backups, patches and channel dependencies.
Data location and residency
Conversations, contact records and uploaded attachments are stored in the PostgreSQL database and file storage that your deployment uses, so residency is decided by where you host those components. Freshdesk assigns a data center region at signup and moves regions only through its support team. With Chatwoot, the region is whatever you provision. Confirm the location of every component, including the Redis instance and any object storage used for attachments, and check that backups and logs follow the same rules.
Hosting models and cloud guides
Chatwoot documents a Linux VM installation script, Docker, and Kubernetes with a Helm chart for larger high-availability deployments. Guides exist for AWS, Azure, DigitalOcean, Google Cloud and Heroku. Choose the model your platform team can operate, because the Helm path adds cluster skills that a single VM does not need. Ask who will maintain the Kubernetes cluster, the ingress and the database failover before choosing that route.
Identity and access controls
SAML single sign-on is part of the Enterprise Edition, which is priced per agent per month on Chatwoot's self-hosted plans page. Teams on Community or Premium Support must confirm how they will authenticate agents, how leavers are removed and how roles are assigned. Confirm whether other identity options, such as OAuth or directory-based provisioning, meet your policy, and document the agent offboarding steps you will run yourself.
Compliance evidence and audit scope
Hosting Chatwoot yourself moves the controls for access, encryption, logging and change management into your audit scope. DeployOpen can plan, configure and document those controls and prepare the evidence an assessor will ask for. DeployOpen does not issue audit reports or certifications. An independent auditor or certification body performs that assessment, so confirm early which framework applies and which evidence the auditor expects from you.
Channel provider dependence
Chatwoot can receive WhatsApp, Facebook, Instagram, Telegram, Line and SMS messages, but each channel depends on a third-party provider's account, approval rules and API terms. A WhatsApp Business account or an SMS carrier can suspend a number or change its terms without any change on your side. Before go-live, confirm which provider holds each channel account, who can rotate its credentials, and how you would move a number if the provider relationship ends.
Backup and patch ownership
With Freshdesk, the vendor operates the service, applies updates and holds the platform backups. With a self-hosted Chatwoot instance, your team owns the database backups, Redis persistence, attachment storage, the Ruby and Node.js runtimes and the operating system patch cycle. Set a written restore test, a patch schedule for each component, and an owner for each. Ask any implementation partner to state these responsibilities in the scope before work begins.
Running the Rails, PostgreSQL and Redis stack in your environment
Chatwoot is a Ruby on Rails application that your team runs on its own servers, so the runtime is the first decision. The requirements call for Ruby 3.2 or later, Node.js 20.x as the recommended version, PostgreSQL as the only supported database, and Redis 7.0 or higher. Ubuntu 20.04 is the only officially supported Linux distribution, so confirm with your platform team whether that release fits your patching policy before you pick a host image. Check the Chatwoot deployment requirements against the exact release you plan to install, since these versions can change between releases.
For sizing, the requirements page recommends at least 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day, and 8 cores and 8 GB for up to 20,000. It also recommends at least 1 GB of swap and notes that Sidekiq, the background job processor, can use more than 1 GB of memory on a very active server. Estimate your peak daily conversation volume from your current Freshdesk reports before you size the VM, and ask your infrastructure team to plan memory headroom for Sidekiq separately from the web process. Redis and PostgreSQL can run on the same host for a small pilot, but a separate database service is easier to back up and restore.
Ongoing work splits into two groups. Routine tasks include applying each Chatwoot release, such as the move from v4.17.0 to v4.18.0 published on September 18, 2026, running database migrations, rotating secrets, watching disk and Sidekiq queue depth, and testing PostgreSQL backups by restoring them to a scratch host. A small team with a Linux administrator can handle these if they follow a written runbook and keep a staging instance. Upgrade planning, PostgreSQL tuning, Redis persistence and failover, high-availability design with the Helm chart, and incident response for queue backlogs usually need a platform engineer. Ask any implementation partner to name who owns each of these tasks in the written scope.
What a self-hosted Chatwoot costs compared with Freshdesk
Chatwoot's Community Edition has no license fee, so the cost of a self-hosted Chatwoot is the sum of the infrastructure, the people who run it and any paid editions you add. Chatwoot's self-hosted plans page lists Premium Support at $19 per agent per month, adding Captain AI, voice calls, custom branding, agent capacity, roles and permissions and priority support, and the Enterprise Edition at $99 per agent per month, adding SSO with SAML and SLA policies. If your team needs SAML single sign-on or a contractual SLA, those per-agent fees apply to every agent who needs the feature, so confirm which edition you are pricing before comparing totals. Recurring costs include the servers or cloud accounts, a managed PostgreSQL database, a Redis service, backups, channel provider fees for WhatsApp, SMS and social channels, and staff time for upgrades and monitoring. Chatwoot's requirements page recommends 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day, and 8 cores and 8 GB for up to 20,000, so conversation volume is the main driver of hosting size.
On the Freshdesk side, the recurring cost is a per-agent subscription that depends on the plan and any add-ons you buy for channels, automation or reporting. Confirm current pricing, the plan that includes each feature you use, and any minimum seat counts in your own contract, because list prices change and negotiated terms vary. One-time costs on the self-hosted side include initial setup, configuring each channel with its provider (for example, WhatsApp Business API approval or SMS sender registration, which can take time and depends on the provider), and migrating existing conversations and contacts. Agent count, channel count and the edition you need for SSO or SLAs are the factors that move the total most, so model each scenario separately rather than assuming one blended rate.
Ask any implementation partner, including DeployOpen, for a written quote that states the scope in writing before work starts. The quote should name the Chatwoot edition assumed and the number of agents it covers, list each channel to be connected and who owns the provider accounts, state the hosting target (your cloud account, your data center or an air-gapped network) and who pays for the database, Redis and backups, and separate one-time setup from recurring retainer or support work. Ask for the Chatwoot release line you plan to run and the upgrade approach, since those determine ongoing effort. Compare that document against your Freshdesk renewal with the same agent count, channels and feature list, so both sides of the comparison reflect the same work.
Moving from Freshdesk to Chatwoot at a high level
This sequence turns a Freshdesk channel footprint into a self-hosted Chatwoot inbox in controlled stages, so each channel is proven before customers are moved. It also produces a record of what history was kept and where it lives.
Confirm channels and provider approvals
List every channel your team answers today, including website chat, email, WhatsApp, Facebook, Instagram, Telegram, Line, SMS and any Twitter accounts. For each one, confirm with the channel provider and your own compliance team what approvals, business accounts or phone numbers you need to connect it to a new self-hosted system, because some channels depend on the provider's account terms rather than on the software. Done when you have a written channel register with an owner and an approval status for each entry.
Export Freshdesk data as XML
An account administrator opens Admin, Account, Account Details, then Export data, and requests the export of tickets, solutions, forums and customers as XML. The export is available on every Freshdesk plan, so the cost of this step is administrator time only. Store the file in an encrypted location with restricted access. Done when the export is downloaded, its checksum is recorded, and someone other than the exporter confirms it opens.
Decide what history to keep and in what form
Agree with support leads, legal and compliance which ticket history must stay searchable, which can be archived as read-only files, and which can be dropped under your retention policy. Chatwoot does not document a Freshdesk importer in the material reviewed here, so treat the XML as a source to convert, not a file to load directly. Confirm with Chatwoot whether an importer exists for your version before you plan on one. Done when a signed retention decision lists each data class and its target form.
Stand up the self-hosted Chatwoot stack
Build the target environment in your own cloud account, data center or private network. Chatwoot requires Ruby 3.2 or later, recommends Node.js 20.x, supports only PostgreSQL as its database and recommends Redis 7.0 or higher. Its requirements page recommends at least 4 CPU cores and 4 GB of RAM for up to 10,000 conversations a day, and 8 cores and 8 GB for up to 20,000, plus at least 1 GB of swap. Ubuntu 20.04 is the only officially supported Linux distribution, so confirm your OS choice before building. Done when a test instance serves the web interface, sends and receives a test email, and backups of PostgreSQL run on schedule.
Configure inboxes and channel connections
Create one inbox per channel and connect each approved provider account, widget or phone number on the test instance only. Set the website live chat widget on a staging domain first. Record which webhooks, callback URLs and credentials each channel needs, and keep them in your secrets store rather than in notes. Done when every channel in the register shows a connected inbox and a test conversation has been sent and answered on each one.
Rebuild teams, automations and canned responses
Recreate teams, agent roles, auto-assignment rules, auto-responders, business hours, labels, canned responses and contact segments from your Freshdesk configuration. Freshdesk's exported XML does not carry these as working settings, so review them in Freshdesk and rebuild them by hand. Check the Chatwoot Premium Support and Enterprise feature lists against what you actually use, such as Captain AI, custom branding, roles and permissions, and SAML single sign-on, before you assume they exist in your edition. Done when a checklist signed by support leads matches each Freshdesk rule to a Chatwoot equivalent or a documented gap.
Run a parallel pilot
Route a limited set of live conversations through Chatwoot while Freshdesk stays active for everything else. Measure response handling, missed messages, assignment accuracy and CSAT collection, and log every defect with an owner. Keep the pilot scope and exit criteria written before it starts. Done when the pilot exit criteria are met or the gaps are assigned to a fix with a date agreed by the business owner.
Cut over channel by channel
Move one channel at a time from Freshdesk to Chatwoot, starting with the lowest-risk channel and updating the public contact points, widget embeds and provider routing as each one moves. Keep Freshdesk read access and the XML archive available until the retention decision is complete. Done when every channel in the register is live on Chatwoot, the Freshdesk routing for it is switched off, and the cutover log is signed off.
Questions buyers ask before moving from Freshdesk to Chatwoot
How much does it cost to move from Freshdesk to self-hosted Chatwoot?
The Community Edition has no license fee, so the cost is the work and infrastructure around it. Chatwoot's self-hosted plans page lists Premium Support at $19 per agent per month and Enterprise at $99 per agent per month, so the license choice is the largest recurring line if you need those features. The other costs are a Linux server or cluster, PostgreSQL, Redis, backups, monitoring, the one-time migration and configuration work, and admin time. Ask any implementation partner for a fixed-scope quote that lists channels, inboxes, automations, reports and data to move as separate items, and compare the recurring cost of Freshdesk's per-agent plans against hosting plus any Chatwoot support contract.
How long does a Freshdesk to Chatwoot migration take?
No migration duration is published in the sources for this page, so confirm timing against your own environment rather than a generic estimate. The pace is set by the number of channels you connect (website chat, email, WhatsApp, Facebook, Instagram, Telegram, Line and SMS each need their own setup and testing), the volume and age of conversation history you need to keep, how many automations, canned responses and teams must be rebuilt, and how quickly your agents can test the new inbox. Chatwoot has no built-in Freshdesk importer in the supplied sources, so plan for a scripted or manual data transfer and ask the provider to show its approach before you commit to a date.
What does our team need to provide during the move?
You need an owner for each channel, someone who can administer Freshdesk and export its data, and agents who will test real conversations before cutover. On the infrastructure side you need a server or cluster you control, a PostgreSQL database, a Redis instance and a way to terminate TLS and send email. Access to every connected channel account, such as the WhatsApp Business account, Facebook and Instagram pages, and the SMS provider, must be available to the people configuring them. Ask the provider to list these inputs in the written scope so that gaps surface before work starts.
Can our own engineers install and run Chatwoot without a partner?
Yes, if your team has Linux, Ruby on Rails and PostgreSQL operations skills. Chatwoot documents a Linux VM installation script, Docker, and a Kubernetes deployment with a Helm chart for larger high-availability setups, along with guides for several cloud providers. The deployment requirements list Ruby 3.2 or later, Node.js 20.x, PostgreSQL as the only supported database and Redis 7.0 or higher, and Ubuntu 20.04 as the only officially supported Linux distribution, so check that your target platform matches. A partner is most useful for channel integrations, data migration, hardening and handover documentation, which are the parts that usually take the longest to get right.
Does Chatwoot include a help center and CSAT reports like Freshdesk?
Chatwoot's Community Edition includes a Help Center portal for articles, FAQs and guides, plus conversation, agent, inbox, team and CSAT reports, according to its README. Those are core features, so you do not need a paid edition for them. Compare them against your Freshdesk setup in detail, though: check article workflows, multilingual publishing, survey wording and how CSAT responses are exported, and test each report against a month of your real data before you decide that it replaces what your managers use today.
Which Chatwoot features require Premium Support or Enterprise?
Premium Support, at $19 per agent per month on Chatwoot's self-hosted plans page, adds Captain AI, voice calls, custom branding, agent capacity, roles and permissions, and priority support. Enterprise, at $99 per agent per month, adds SSO with SAML and SLA policies on top of those. Core inbox, channels, automation, teams, labels, canned responses, campaigns and reports appear in the Community Edition list. Confirm the current edition matrix on the pricing page before you finalize a budget, because the features in each tier can change between releases.
Does the MIT license allow commercial self-hosting of Chatwoot?
The core code is available under the MIT Expat license, which permits commercial use, modification and self-hosting. The exception is the enterprise/ directory, which is licensed under the separate license in enterprise/LICENSE, so read that file before you deploy any paid-edition features. Third-party components keep their own licenses, so include them in your software bill of materials. Have your legal or procurement team confirm the terms against the repository's LICENSE file and any files in enterprise/, because this page does not provide legal advice.
How are upgrades and backups handled after go-live?
After go-live, the operations work falls on whoever runs the platform. Chatwoot publishes releases on GitHub, with v4.18.0 dated September 18, 2026, so you need a process to test each release in staging before production. Backups must cover the PostgreSQL database, uploaded attachments and the configuration, and you should rehearse a restore, not just the backup job. Monitoring for Sidekiq memory use is worth adding, since the requirements page notes it can exceed 1 GB on a very active server. Ask any retainer provider which upgrades, backup testing and monitoring they cover and how they report incidents.
How DeployOpen helps you evaluate, implement and migrate
DeployOpen plans, implements and supports self-hosted open-source platforms inside your own infrastructure, so a Freshdesk to Chatwoot move is scoped against your real channels, agents and data before any build starts. Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing first.
How we scope
- We inventory the channels you answer today, including live chat, email, WhatsApp, social and SMS, and confirm which ones Chatwoot must cover.
- We map Freshdesk automations, CSAT reports and help center content to Chatwoot features and flag the gaps in writing.
- We confirm which Chatwoot capabilities depend on Premium Support or Enterprise editions before you commit to a plan.
How we build
- We size the Rails, PostgreSQL and Redis stack against your conversation volume, using the vendor's published requirements as the baseline.
- We deploy Chatwoot in your cloud account, data center or air-gapped network, with channel connections configured and tested.
- We rebuild automations, business hours, teams, canned responses and help center articles, and test each workflow with your agents.
How we hand over
- We document the architecture, backup and restore steps, upgrade procedure and channel configuration for your operations team.
- We provide runbooks for Sidekiq, Redis and PostgreSQL monitoring so your administrators know what to watch.
- We agree a handover checklist in writing and confirm the cutover plan for each channel before switching traffic.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers, scoped against your own release schedule.
- We can run security testing on the deployed inbox and its integrations, including the Captain and Slack connections if you enable them.
- Quotes follow from the written scope, so ask for a breakdown of one-time build work against recurring support and hosting effort.
