What happened to Slack

The project plan usually enters the room already agreed. Somebody says the Salesforce org is now the Slack workspace, and every file should move into a channel, because Salesforce owns Slack and the agreement feels settled: one vendor means one system. On Monday a seller searched the opportunity and found a link to a channel with forty unread messages and no amount, no close date, and no owner. The channel had the customer's name. It did not have the record.

By Wednesday the thread and the record disagreed. Support had pasted the case comment into the thread and closed the case in the wrong system. Nobody could say which one a manager was allowed to trust. The agreement is the problem. It is easy to reach, and it fits an ownership change, which does not merge a channel and a record.

The distinction that matters is the object each person is allowed to update. Salesforce bought Slack, and Slack kept its name. The deal closed in 2021. Salesforce owns Slack. A Salesforce org is not a Slack workspace. A channel is a conversation. A Salesforce record is a record. Slack is not a place where every company document now lives. A later acquisition, Doti, completed on 1 December 2025. That date does not rewrite 2021, and it does not say the org has become the workspace.

What follows are the questions that keep those objects apart. A good answer names the record, the channel, the year, or the contract. A general answer pastes the CRM into a thread and calls the paste a close.

#The questions, and what a bad answer signals

#1. What happened, and why does December 2025 keep appearing?

The question is not whether Slack and Salesforce share an owner. It is what the close changed, and which later sentence people are holding when they redraw the timeline.

Salesforce bought Slack, and Slack kept its name. The deal closed in 2021. You still ask for Slack by that name. Customers who already work in a workspace keep a workspace. They do not receive a second CRM because the vendor changed. The acquisition did not merge a channel and a record into one object.

The page cited here is about a later deal, not about the Slack close. It states that later deal in one sentence: "Salesforce completed its acquisition of Doti on December 1, 2025." Read the date on that sentence as 1 December 2025, and read the name as Doti. Doti is a different acquisition. It does not rewrite 2021. It does not say a Salesforce org has become a Slack workspace. It does not say every company document now lives in Slack. It also does not say why Salesforce acquired Slack, or why Slack sold. If a timeline draws one arrow from Slack to December 2025, the arrow is wrong. Put Doti on its own line.

What happened, for a customer, is an ownership change with a close in 2021 and a name that stayed. What did not happen is a shutdown, a Slack purchase price on the cited page, or a rule that the org and the workspace are the same thing. People searching what happened to Slack often land on a newer acquisition because the names share a vendor. Say both, and do not let one stand in for the other.

A good answer sounds like the person who wrote the plan saying Slack was bought, the name was kept, the deal closed in 2021, and the sentence in the pack is the Doti completion on 1 December 2025.

A bad answer sounds like "Slack closed in December 2025, so the org is the workspace and the files move this sprint." The seller's opportunity still has no amount in the channel, and the board brief is wrong about the year.

#2. Who owns the workspace, and who owns the record?

Salesforce owns Slack. You do not own the product because you have a Salesforce org, and you do not turn the org into a workspace by connecting them. Your organisation owns the workspace you administer, the channels you create, the members you allow, and the records in the CRM. Those are different estates. A risk register that lists one owner for both will approve a paste that neither estate wanted.

Is Slack owned by Salesforce? Yes. Did Salesforce buy Slack? Yes. Who owns Slack? Salesforce. Say the three answers the same way in the steering pack, the vendor form, and the support template. A form that still treats Slack as an unrelated company, and ignores the Salesforce relationship, is stale. A form that treats a channel as a standard object inside the org is also wrong. Ownership of the company is not the same fact as a shared login screen.

The acquisition did not move contracts, files, or knowledge articles into Slack. A channel can point at a record. The record remains the place a seller updates the amount. If a supplier asks who owns Slack, give them Salesforce, the close in 2021, and the statement that the name was kept. Do not give them the Doti date as the Slack date.

A good answer sounds like a named workspace admin and a named opportunity owner agreeing which channel may point at which record, and who checks that the amount in the thread matches the amount on the opportunity.

A bad answer sounds like "Salesforce owns Slack, so every company document now lives in a channel, and the org is the workspace." The case gets closed in the wrong system, and Wednesday is a reconciliation.

Paste the CRM into Slack and you have a copy that goes stale. Point the channel at the record and you have a path a person can check. Connecting them is a choice about one record and one channel, not a merger. The org holds records, permissions, and the fields a seller may edit. The workspace holds channels, members, and messages. You still have both, if your contracts say you do.

#3. Which year is the Slack close?

When did Salesforce acquire Slack? The deal closed in 2021. There is no day and month to add on top of that year from the record this guide follows. The parent record says the deal closed in 2021. If a slide needs a day, it needs a document that states the day. A guessed day looks like care and functions as fiction.

Put 2021 on the timeline as the Slack close. Put 1 December 2025 on the timeline as the Doti completion, and label that line Doti. Do not draw an arrow from the 2025 line back onto Slack. The dates sit near each other only because both are Salesforce acquisitions. They are not one event. A reader who merges them will brief a board that Slack was bought at the end of 2025, and the brief will be wrong.

Your own connection go-live, if you have one, is a third date, and it is yours. The cited page states the Doti completion. It is not a 2021 Slack press release. State the close year for Slack in your own words. Send a reader who wants the legal instrument for Slack to the contract, not to the Doti sentence.

A good answer sounds like two lines a board can check: Slack, deal closed 2021, name kept; Doti, completed 1 December 2025, a different company.

A bad answer sounds like one date, December 2025, labelled Slack, because that was the sentence someone found first. The 2021 close disappears, and the file-move plan inherits the wrong year.

#4. Where is the price written?

How much did Salesforce pay for Slack? The page this guide cites does not publish a Slack purchase price or a licence fee. How much was Slack sold for? Same answer. A Salesforce Slack acquisition price does not appear on that page. The Doti sentence quoted above is a completion. It is not a price. A blank is more honest than a borrowed number with a year attached.

The deal price, even if another document later shows you one, is not your licence. A historical figure would not tell you what you pay for the workspace next year. Your licence is the contract in your drawer. If the contract is silent, write that the price is not in the paper you are holding. Procurement can ask the account team for the commercial paper. That paper is the price that binds you.

What you pay a partner to connect a channel to a record belongs in a statement of work. That figure is not the 2021 purchase price, and it is not a Doti figure. A quote that leads with a historical deal number, and never names which record the channel may touch, has answered the wrong question.

A good answer sounds like procurement stating the Slack fee from the order form, or stating that the form is silent, and refusing to treat the 1 December 2025 sentence as a number.

A bad answer sounds like a business case that borrows a Slack price from a video or a forum, or that reads the Doti completion as if it priced the workspace. Neither number is in the paper you are holding.

#5. Is there an end date, and where do the files stay?

Was Slack shut down or given a sunset date? No end date is stated here. An acquisition is not a shutdown. A later acquisition of Doti is not a shutdown of Slack. A keyword that pairs Slack with sunset is a question. The answer is that no end date is stated. Write that in the column, and leave the column otherwise empty.

If a vendor tells you to leave Slack because Salesforce bought it, ask for the retirement notice. A year in a search box is not a notice. 2021 is the year the deal closed. It is not an expiry. Customers still use Slack as Slack. The name was kept so that you can still ask for it by that name. A support template that has renamed the workspace to "the org" will send people to the wrong place when a message fails.

Confirm your own contract term, your renewal, and the person who administers the workspace. Those are your dates. They are not a product sunset. A plan that moves every file into a channel because the product was finished will strand the record. Leave Slack as a workspace until you have a written rule for which messages may be linked to which records, tested with the people who read both.

A channel is a poor system of record for a contract, a price, or a case status. If a document must be found, name the system that already holds it, and name who may read it. The Doti completion does not say December 2025 moved the file share into Slack. You were not, on the facts used here, forced to abandon the workspace or to abandon the org. If a programme is connecting them, write the record, the channel, and the person who checks the amounts. If those three are missing, you are looking at a paste.

A good answer sounds like the workspace admin reading the renewal from the contract and naming the one channel that may point at the opportunity, with the amount still edited on the record.

A bad answer sounds like "move every file into Slack, the product is finished, and the org is the channel." Support will close the next case in the thread, and the manager will still have two versions.

A DVD, a Reddit thread, a YouTube clip, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown.

#Where the decision goes next

The record, the channel, and the failure when they disagree live on the Slack page. Read it when you are ready to name what may be written back. The acquisition question ends when the pack can say the owner, the close year, the missing price, and the missing end date.