Salesforce Is Replacing Chatter With Slack: What to Move, What to Keep, and How to Prepare Your Org

At TrailblazerDX 2026, Salesforce Co-Founder Parker Harris stood on stage and said: "Why should I ever log into Salesforce? Maybe you never will. Maybe you will go into Slack." That was not a throwaway line. From Summer '26 onwards, every new Salesforce org ships with Chatter switched off and Slack set as the default. If your existing org still runs on Chatter, here is exactly what has changed and what to do about it.

What Salesforce actually announced — and what it means

Salesforce has made three significant Slack-related announcements in 2026, each building on the last:

Summer '26 (June 15, 2026): Chatter is now switched off by default in all new Salesforce orgs. Slack becomes the default collaboration platform for every new customer. Existing orgs are not forced to change — but the signal is unmistakable. New orgs will not experience Chatter as the default ever again.

TDX 2026 (March 2026): Salesforce positioned Slack as "the front door to the agentic enterprise." Agentforce agents for Sales, IT Service, HR Service, and Tableau went live natively inside Slack. Representatives can now query CRM records, get AI-generated account research, and update opportunities without opening Salesforce at all.

March 31, 2026: Salesforce announced 30 new AI features for Slackbot — including making Slackbot an MCP client. This means Slackbot can now route work to Agentforce and access Customer 360 data via the Model Context Protocol, turning it from a simple chatbot into an orchestration layer for the entire Salesforce ecosystem.

What actually changed in Slack

The Slack-Salesforce integration in 2026 is qualitatively different from what existed in 2024. These are not notification integrations or basic record links — they are native two-way connections that change how CRM work gets done:

• Salesforce Channels: Special Slack channels tied to a specific CRM record — an account, deal, or case. Every message is stored against that record. Agentforce participates in these channels automatically, summarising conversations, updating records, and taking actions without a Salesforce login.
• Agentforce in Slack: Full Agentforce agent deployment natively inside Slack. Agents for Sales (account research, opportunity coaching), IT Service (CMDB queries, ticket routing), HR Service (policy lookups, onboarding), and Tableau (analytics summaries) are all available.
• Slackbot as MCP client: Slackbot can now route queries to Agentforce via Model Context Protocol — enabling it to access live Salesforce data and take actions in Salesforce from within a Slack conversation.
• Meeting transcription and automation: Slackbot transcribes meetings, generates summaries, drafts follow-up emails, schedules next steps, and automates workflows across enterprise tools — all from inside Slack.
• Reusable AI skills: Teams can define reusable Slackbot skills — custom behaviours that Slackbot applies consistently across channels without per-channel configuration.

Is Chatter actually being retired?

No hard retirement date has been announced. Existing orgs will not lose Chatter — it continues to function without disruption. What has changed is the strategic direction: Salesforce has not announced new Chatter feature development since 2025. The Chatter roadmap, in any meaningful sense, is now the Slack roadmap.

The practical implication for existing orgs: anything you build in Chatter today will need to be rebuilt in Slack eventually. The question is not whether to migrate, but when — and whether you migrate proactively on your terms, or reactively after Salesforce makes a forcing move.

What to audit before you migrate

The organisations that have the hardest Chatter-to-Slack migrations are the ones that discover their Chatter dependencies mid-project. Audit these six areas before you start:

• Flow triggers listening to Chatter events — any Flow built on ChatterGroupMembership, FeedItem, or FeedComment objects will need to be rebuilt
• Approval processes that use Chatter notifications — approval request and approval comment notifications configured to post to Chatter feeds
• API integrations posting to Chatter feeds — third-party tools (marketing automation, ERP, service desk) that write to Chatter via the Chatter API
• Case Feed customisations — custom publisher actions, custom Chatter actions, or Case Feed layouts that surface Chatter in Service Cloud
• Reports and dashboards on Chatter activity — adoption metrics, collaboration reporting, or manager dashboards built on Chatter data
• @mentions in record alerts — automated @mention logic baked into Apex triggers or Process Builder that routes notifications via Chatter

What to move to Slack — and what to keep in Salesforce

The migration is not a binary switch. Salesforce Channels create a hybrid model where the right things live in the right place:

Move to Slack: Deal collaboration and account strategy discussions. Service case escalation conversations. Cross-functional project coordination. Approval requests where back-and-forth dialogue is expected. Team announcements. Customer success planning. Manager-to-rep coaching conversations.

Keep in Salesforce: Formal audit trails where legal or compliance requires a record within the CRM. Regulatory-required activity history. Record-level history tracking. Data that downstream reports and dashboards depend on. Anything that needs to survive a Slack workspace change.

The design principle that works: Slack for collaboration, Salesforce for record management. Salesforce Channels make this explicit — the conversation happens in Slack, but the CRM record in Salesforce remains the authoritative source of truth for what was decided and when.

What to do now if you are on an existing org

You are not being forced to migrate today. But these are the actions that pay off regardless of when you choose to move:

• Run the audit above. Map your Chatter dependencies now, while it is a discovery exercise rather than an emergency.
• Enable Salesforce Channels in Lightning Experience. This is available in Enterprise and Unlimited editions. Enabling it does not disrupt Chatter — it adds the Slack-native layer alongside your existing setup. Start a pilot on one team or one account type.
• Pilot Agentforce in Slack for one use case. Service case escalation alerts, deal room updates, or IT service ticket routing are all natural first Slack-native Agentforce use cases. Run the pilot, measure resolution rates, then decide on pace.
• Do not force the migration. Let the better tool win the work. Teams that switch to Slack-native collaboration and see the value will pull others along — that adoption pattern is far more durable than a top-down mandate.
• Plan user lifecycle management. Provisioning Slack access alongside Salesforce access is the operational change most orgs underestimate. Our Steward user lifecycle management package handles Salesforce provisioning and can integrate with Slack workspace management — ensuring new hires get both access points on day one and leavers lose both on their last day.

For orgs deploying Agentforce-in-Slack at scale, our Synapse MCP integration package extends the data connectivity layer — connecting Salesforce data to Claude and other AI tools via the same Model Context Protocol that Slackbot now uses natively.