Slack and Salesforce: the org is not the workspace

On Thursday a project manager exports three Slack channels to a spreadsheet. The channels hold the incident thread, the pricing argument, and the customer war-room. The brief calls the export a Slack data migration to Salesforce. By Friday the rows are cases. The messages are comments. The people are missing, because a display name is not a user. On Monday someone archives the Slack workspace. They have been told the Salesforce org is now the workspace, so the old place is duplicate. Tuesday morning the incident starts again. The channel is gone. The cases are a dead copy of last week. The org cannot recreate the room the team used to decide.

That is the failure. A chat history was treated as a data load, and a workspace was treated as a CRM tenant. Neither is true. Slack was acquired and kept its name. A Salesforce org is not a Slack workspace. You still open Slack to speak, and you still open Salesforce to work the record. Collapsing them deletes the conversation and leaves a poor archive.

The same week a steering slide mentions a later acquisition and implies the org has absorbed the workspace. It has not. The only sentence you should take from that announcement is the completion line, and it does not say what the slide says.

#Slack kept its name

Slack was acquired and kept its name. Say Slack when you mean the workspace, the channels, and the members. Say Salesforce when you mean the org, the objects, and the users. A sentence that treats them as one product will assign a sandbox task to a workspace the sandbox does not contain. Refreshing a Salesforce sandbox does not refresh Slack. It does not restore a channel. It does not replay a thread.

People still search the old question because the names sit next to each other in a contract pack. The acquisition did not turn a channel into a case object. A case can link to a conversation. The link is a design you choose. It is not a side effect of the deal. If you want a case when a customer asks for help in a channel, write the rule: which channel, which case fields, which queue, which person still speaks in Slack after the case exists. Without that rule, an export is a paste.

Members are not migrated by copying display names into contacts. A Slack member may have no Salesforce user. A Salesforce user may never open Slack. Those lists are maintained by different people, often in different parts of the organisation. A quote that says "sync the users" has not named which list wins, what happens to a leaver, or who disables the account on the day they leave. Write the leaver down. A channel that still includes them after their Salesforce user is frozen is a gap, not a detail.

Retention is a decision, not a default you can assume from a CRM policy. How long messages stay. Whether a deleted message is gone. Who can export. A project that exports "for the migration" has already made a copy outside the workspace rules. Say where that spreadsheet will live, who can open it, and when it will be destroyed. If you cannot say, do not export.

#The Doti sentence does not merge the products

There is a later announcement. Quote it once, as a date, and stop: "Salesforce completed its acquisition of Doti on December 1, 2025." That sentence records a completion. It does not describe your tenants. It does not say a Salesforce org has become a Slack workspace. It does not say a channel history should be loaded into cases.

The announcement names Slack as the conversational interface. Read that as a role, not as a storage claim. A person may ask in Slack. The record they are asking about can remain in Salesforce. The interface and the system of record are different objects. Keep them apart on the diagram, including the one-slide version someone will paste into a pack. A conversational interface can sit in Slack and still read a case the asker is allowed to open. It does not follow that every message should become a case, or that every case comment should be posted back to a public channel.

Do not extend the sentence. It does not name a price, a migration method, or a daily limit. If a proposal cites the acquisition as the reason to archive the workspace, ask them to point to the words. The words are a date. Archiving is a separate decision, and it is usually the wrong one while people still decide things in the channel.

If you are also buying search or an assistant that speaks in Slack, scope that as its own page. Name the identity it runs as, and the channels where an answer may appear. A public channel is a publication. Restricted text from a case does not belong there because an assistant can see the case. That design is not this migration. Do not hide it inside a data-load quote.

#A channel is not a case

Take one channel the business would miss tomorrow. Write what it is for, in one sentence. The incident channel is for deciding the next action while something is broken. The pricing channel is for an argument that is not ready to be a quote. The customer room is for a named account, with people from both sides. Those three sentences already tell you they should not share one case record type.

For the customer room, a link can be honest. The account exists in Salesforce. The channel exists in Slack. A field or a related record can store the channel id, so a seller can find the room. The messages stay in Slack. The opportunity stays in Salesforce. You have related two systems. You have not migrated either.

For the incident channel, a case may be wrong. The thread is short-lived, full of guesses, and useful only while the incident is open. Copying it into the case object makes the guesses look like a record. Decide, in writing, whether a finished incident becomes a case or a document the incident owner keeps. Do not let an export decide for you because the column was easy to paste.

For the pricing argument, the danger is the opposite. The thread has numbers that are not approved. Pasting them onto an opportunity makes a draft look like a price. Leave the draft in the channel until the person allowed to set the price writes it on the opportunity themselves. The channel is where the argument happened. The field is where the decision lives. A migration that copies the argument into the field has skipped the decision.

#What the bill is made of

Implementation cost means the parts of the bill. It is not a dollar figure. A serious quote separates them.

Discovery names the workspaces, the channels that matter, and the owner of each. A workspace with no owner will be archived by someone who does not use it. Put the owner on the page. If a channel is unknown, say unknown. Do not invent a volume of messages to make the line look measured.

The boundary names what may be linked and what may not be copied. Channel id on the account is a link. Full message history on the case is a copy. They have different privacy consequences. The quote should say which one you are buying. A line that says "Slack integration" is not yet a choice.

Identity names who can post, who can read, and which Salesforce user a notification runs as. A bot that posts as a system administrator will write comments the seller could not have written. Choose the user the way you would choose a new starter, not the way you choose a token that happens to work in a sandbox.

The morning-after test names who still needs the channel on the day after go-live. If the answer is the same people as today, you are not archiving the workspace. Write that down so a later phase cannot "clean up" the room. Cutover, if any, is the hour a link starts working, who watches it, and how you turn the link off without deleting the channel. Hypercare is the next incidents, with the channel still there.

Licences are a separate conversation, and this page will not pretend to know which ones you hold. Ask your account team, against the contract, whether Slack and Salesforce are both already entitled. A news sentence is not an order form. A quote that bundles a new Slack purchase inside a data load has mixed procurement with a paste. Split them. You can need a link and already own both products. You can need neither a link nor a load, and still need someone to own the leaver habit. Those are different purchases. Write the one you mean.

The same split applies to history. A compliance officer may ask for an export for a legal hold. That export is a copy with a purpose, a recipient, and an end date. It is not a migration, and it should not be the seed of a case object. Name the officer. Name the folder. Name the date the file is destroyed. If the quote has a line for "historical Slack data" and no officer, send it back. Volume is not a scope. A purpose is.

#The test a buyer should use

Searches ask for the best Slack Salesforce integration agency, for a consultant to hire, and for an implementation partner. The adjective is the search. It is not a result. Use a test in your workspace.

Ask the firm to name one channel, the Salesforce record it may relate to, and the person who still needs that channel tomorrow morning. Ask them to say, out loud, that a Salesforce org is not a Slack workspace. A partner who will not say it will archive the wrong thing. Ask them to refuse a full history load until the link-or-copy choice is written. A partner who prices the load first has picked the paste.

Ask where the Doti completion date ends and the work begins. A firm that treats the date as a migration plan has not read the sentence. The sentence is a completion. Your channels are still yours to list. Ask who disables a leaver in Slack on the day their Salesforce user is frozen. A name, in the organisation, with a same-day habit. If the name is absent, the quote is unfinished.

Do not crown a firm, including this one. Two firms that can name the same channel can be compared on link versus copy, and on the leaver. Two firms that offer a bundle cannot. If nobody passes, do not lower the test. Finish the channel list. The partner you want can pass it in a workshop.

#What you settle before anyone exports

Write five lines. The workspace. The three channels you would miss tomorrow. Whether each is a link or a copy. The Salesforce user a notification runs as. The person who still needs the channel the next morning.

Then do not export. Open the channel. Open the record. Confirm a person can move between them without a spreadsheet. If the only way to see the conversation is a case comment full of old guesses, you have built the archive and lost the room. Turn that design off before it spreads.

Agentic marketing on a website is a different acquisition and a different room. Keep it off this quote. The neighbouring page is Qualified and inbound buyers. A site conversation is not a Slack channel, and a Slack channel is not a journey.

The quote is ready when a new administrator can see the workspace, the channels that stay, and the records they may link to, without asking the partner who sold the work. If the page still says data migration and names no channel, send it back. Slack kept its name. The org did not become the workspace, and a spreadsheet of messages did not become the implementation.

#The other searches

The project quote is on slack implementation cost. That page does not print a figure. Who bought the company is on what happened to slack. The connector is on integrating slack with Salesforce. Whether to move is on should I migrate from slack. The customer fee is on slack licence cost. Who to hire is on hiring for slack. This page does not rank an agency.