Quick question: how much are you paying for Slack? For a 40-person company on the Pro plan, that's roughly $7,200 a year. And what does it do? Chat. Channels. Some integrations.
Now open your Odoo. See that little chat bubble icon? That's Discuss. It's included in your license. It does chat, channels, integrations — and one thing Slack will never do: it's wired directly into your business data. A Slack message says "the order shipped." An Odoo Discuss message can BE the order, with the chatter showing every update, approval, and attachment in context.
You're paying seven grand a year for a chat app while the better-integrated one sits in your ERP gathering dust. Let's fix that.
Why Discuss Wins on Integration
This is the argument that ends the debate. In Slack, business context lives somewhere else — you chat about the order, then go look up the order. In Odoo, the chatter IS the chat.
Every Odoo document — sales order, purchase order, invoice, task, lead — has a chatter: a running thread of messages, notes, and activity history attached to the record. When Discuss is set up right, channel messages and document chatter connect. Someone posts in #fulfillment: "Order S04218 is stuck in picking." That message can link directly to the order. Click it, and you're looking at the order, its chatter, its history, everything.
Try doing that in Slack. You'll get a message saying "order S04218 stuck," and then someone replies "which customer is that again?" and then someone pastes a link to the ERP, and then the link requires a login, and by then the moment's gone.
Integrated context is the killer feature. Not emoji reactions. Not huddles. The fact that the conversation and the data live in the same place.

The Setup That Actually Works
I've migrated three teams off Slack onto Discuss. Here's the playbook:
Week 1: Mirror, don't innovate. Create the exact same channels they had in Slack. #general, #sales, #support, whatever. Same names. The goal is zero learning curve on structure — the only change is the app. Teams resist change; they don't resist the same thing in a new window.
Connect the chatter to channels. This is the step everyone skips and it's the whole point. In Odoo, subscribe key channels to the document types that matter: #purchasing gets PO updates, #sales gets order updates, #support gets ticket updates. Now business events flow into chat automatically. The team stops asking "did that ship?" because the channel told them.
Set notification discipline on day one. The #1 reason chat tools become useless is notification noise. Rules: @channel mentions only for genuinely urgent things, threads for side discussions (not the main channel), and status/availability actually used. Write these down. Pin them in #general. Enforce them for two weeks until they're habit. Slack failed at this in most companies — Discuss is your second chance.
Week 2: The overlap. Run both for two weeks. Post in both. Then pick a Friday, export anything worth keeping from Slack, and turn it off. The overlap isn't for the team — it's for you, to prove nothing critical lived only in Slack. (Something always lived only in Slack. Usually a channel called #random-important or a DM thread with a vendor. Find it during overlap, not after.)

The Honest Limits
I'm not going to tell you Discuss is better at everything. It's not.
The app ecosystem is smaller. Slack has 2,000+ integrations. Odoo has... fewer. If your team lives in a web of 40 Slack bots, you'll feel the gap. But be honest: how many of those 40 does anyone actually use? Audit before you assume.
Video calls are basic. Discuss has video/voice calls and screen sharing. They work. They're not Zoom. If your company does heavy video collaboration, keep Zoom/Meet for that. Discuss replaces the chat, not the conference room.
Mobile is good, not great. The Odoo mobile app handles Discuss fine for reading and replying. Power users who live in Slack mobile will notice the difference. It's a 7 out of 10 versus Slack's 9.
Search is weaker. Slack's search is excellent. Odoo's Discuss search is... adequate. The mitigation: because conversations happen attached to documents (the chatter), you often don't need to search chat — you search the record, and the conversation is right there. Different model, same result.
The Math
40 users × $15/month × 12 = $7,200/year for Slack Pro. Odoo Discuss: $0 marginal — it's in your license.
Even if you keep Slack for one stubborn department, moving 30 of 40 users saves $5,400/year. That's a real number for a real SMB. It's a marketing budget. It's a training course. It's the holiday party.
And the integration dividend compounds: every month your team chats inside the system where the data lives, they get faster at finding context, and the "which order?" conversations disappear. You can't put a clean number on it, but every operations manager I've migrated feels it by month three.
The Migration Script
When someone says "but I like Slack," here's your answer: "Great — you'll like not paying for it more. Same channels, same people, and now the chat knows what the orders are doing."
Two weeks of overlap. Mirror the channels. Connect the chatter. Set the notification rules. Then turn off the $7,200/year chat app and watch nobody miss it by November.
Frequently asked questions
Can Odoo Discuss really replace Slack?
For most small and mid-size businesses, yes. Discuss has channels, direct messages, threading, file sharing, and voice and video calls — and it is included in the Odoo license you already pay for. A 40-person company on Slack Pro spends roughly $7,200 a year on chat alone.
What does Discuss do that Slack cannot?
It is wired into your business data. Every Odoo document — sales order, invoice, task, lead — carries a chatter thread of messages and activity. A message about an order can be the order, with its updates, approvals, and attachments in context, instead of a chat message pointing at a login screen somewhere else.
How do you migrate a team from Slack to Discuss without a revolt?
Mirror, don't innovate: recreate the exact same channels on day one, connect key document chatter to the channels so business events flow in automatically, set notification discipline from the start, and run both tools for a two-week overlap before turning Slack off on a Friday.
What are Discuss's honest limits?
A smaller app ecosystem than Slack's 2,000-plus integrations, basic video calls that will not replace Zoom or Meet for heavy collaboration, and a mobile app that is good rather than great. If your team truly lives inside dozens of Slack bots, audit how many anyone actually uses before assuming the gap matters.





