# Should you migrate from Doti

Doti is agentic enterprise search. Slack is the conversational interface. Do not migrate every repository into Slack because the deal closed.

**Published:** 2026-08-07
**Canonical:** https://synconai.com/should-i-migrate-from-doti
**Author:** SynconAI Architecture Team

## In short

Salesforce completed the Doti acquisition on 1 December 2025. Doti is agentic enterprise search. Slack is the conversational interface, not a dump of every file. Do not migrate every repository into Slack because the deal closed. This page does not publish a price, a ranking, an AppExchange listing, or a shutdown date. Name the sources a search may read before you move anything.

## Sources

- **Salesforce Signs Definitive Agreement to Acquire Doti** (retrieved 2025-12-01)
  https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-doti/
  > Salesforce completed its acquisition of Doti on December 1, 2025.

## What to take away

- The close on 1 December 2025 makes Slack the conversational interface. It does not move every repository into Slack.
- Doti is agentic enterprise search. A reply in a channel is not proof the file moved.
- Native search inside Salesforce reads the org. Enterprise search across other systems is a different job, and this page does not pick a winner.
- This page does not publish a price, a ranking, an AppExchange listing, or a shutdown date.

## The guide

A programme owner hears that the Doti deal has closed and writes a migration line into the quarterly plan. The line says every repository will move into Slack, because that is where people will ask. The line has a date. It does not have a source list. It does not say which identity may read a file, or which channel may see the answer. The deal is real. The line is ahead of the record.

This page answers four questions. Should you migrate. What the software is now. How that compares with native Salesforce features. What the alternatives are, with no order and no winner. It does not price the work, rank a partner, name an AppExchange package, or give Doti an end date.

## Should you migrate

Migrate is the wrong verb until you know what would move. A repository is a store of files, history, and grants. Slack is a place a person asks. Copying the store into the place you ask collapses two objects the announcement keeps apart. If the only reason on the brief is that the deal closed, the answer is no. Do not migrate every repository into Slack because the deal closed.

A narrower move can still be honest. You might connect a source so a person can ask about it from Slack, while the file stays where it is. That is an access design. It is not a dump. You might also decide that a particular wiki is no longer the place people should look, and that the pages worth keeping will be rewritten as Salesforce records under a named owner. That is a content decision, one page at a time. It is not a repository migration triggered by a close date.

Write the decision as a yes or a no against a named source. "We will not copy the legal repository into Slack." "We will let search read the published help centre, and return a link, not the file text, in a public channel." Each sentence has a source, a behaviour, and a room. A sentence that says "migrate Doti" has none of those. Send it back.

People ask for a walkthrough because a walkthrough feels like permission to start. A walkthrough of clicks assumes a screen this close notice does not describe. The walkthrough you can write this month is a decision list. Which sources exist. Who owns each one. What the search identity may open. Which Slack rooms may receive an answer. What must return nothing. If a step in the list says "export the repository and import it to Slack", strike the step. That step is the failure this page is here to stop.

## What Doti is now

The sentence this page quotes from the close notice is: "Salesforce completed its acquisition of Doti on December 1, 2025." Completed means the deal is done. The date in Australian order is 1 December 2025. Same day. Doti is agentic enterprise search. The announcement named Slack as the conversational interface.

Agentic means the search can plan steps. It does not mean the steps may ignore the grant on a file. A conversational interface is where a person asks. The document stays in the system that already holds it, under the permission that system already enforces. A contract can stay in the contract system. A wiki page can stay in the wiki. A case can stay on the case. The reply can appear in a thread. Those are different objects.

What the software is now, on this source, stops there. The notice does not say your edition gained a search feature on the morning of the close. It does not describe a Doti database you lift into Salesforce objects. It does not say a tenant you held before the close has a new administrator. If you need the current screen, look in the tenant with the person who holds the login. Do not draw a screen from a news sentence.

The close is also not a licence change you can infer. Ask the account team what the contract includes, in writing. A completion date is a fact about the companies. Your order form is the fact about what you have bought. Keep them in different sentences when you brief a steering group.

## Slack is where you ask

The failure mode is ordinary, and it starts in a well meaning channel. A seller asks, in a public room, for the renewal terms on an account. Search finds the contract, because the identity it runs as can open the legal folder. The reply pastes the clause. Forty people now have text that two people were allowed to see. The file never moved. The publication happened anyway.

That is why a dump into Slack is worse than a bad diagram. Once the text is in the thread, the thread is a copy you do not control. People stop maintaining the source, because they believe the copy is the record. Other people forward the thread. The grant on the original file is still there, and it no longer matches who has read the words. You cannot undo a read.

Work the boundary before you connect a second repository. Public channels get a link the asker opens under their own login, or a refusal. Private channels are still a group. Direct messages still get forwarded. Write the rule for each in a sentence a channel admin can apply without a meeting. If you cannot write the sentence, you are not ready to connect the source.

Do not treat a pilot channel as proof. A private test room hides the publication problem. Run the same question in a channel that matches the room you intend to keep. If the only passing test used an admin token, the test did not pass. Change the identity and run it again.

## Versus native features

Salesforce already lets a person search inside the org they are logged into. They can open a record they have access to. They can see a file on that record if the file grant allows it. They can read a Knowledge article the org has published to them. Slack already lets a person search the messages and files that Slack itself holds, under Slack's own rules. Those are native behaviours of the systems you already run.

Doti, on this record, is a different job. It is enterprise search, with Slack named as the place a person asks. The sources can sit outside the org. The answer can mention a system the asker does not administer. Native search answers from what the org, or Slack, already stores for that person. Enterprise search answers from sources you connect, through an identity you choose. Same word, search. Different ceiling.

This page does not say the native search is better, and it does not say Doti is better. It does not rank them. A team whose questions are all about records they can already open does not need a new source list. A team whose questions cross a wiki, a file store, and the CRM has a boundary problem native org search will not solve by itself, and a dump into Slack will not solve either. The comparison is a way to see which job you have. It is not a league table.

| Job | What this record says about Doti | What native features already do | What you still write |
| --- | --- | --- | --- |
| Find a record the person can open | Not described as a replacement for org search | The person searches the org under their own login | Nothing, until a source outside the org is in scope |
| Ask in Slack about a file Slack does not store | Slack is the conversational interface | Slack search reads Slack. It does not become the archive | The source, the identity, and whether the reply may include text |
| Move a repository | Not in the close notice | Files on records stay files on records | A content decision, page by page, or a refusal to move the store |

Use the table in the steering pack. If a column is blank, leave it blank. Filling it with a product you hope exists is how a walkthrough starts to lie.

## Alternatives, with no order

The search for a Doti alternative on AppExchange expects a package name, a publisher, and a rank. This page does not have them. The close notice is not a directory. Naming an app here would invent a listing. This page will not do that, and it will not sort the options below into a first, second, and third.

The options are ways to do the job, not products this source certifies.

Stay with the sources you already have, and let people open them under their own login. That option fits when the pain is "people cannot find the link", and the cure is a better index you maintain, not a new identity that can read more than the asker.

Use native search inside Salesforce for questions whose answers are records, files, and articles already in the org. That option fits when the asker should see only what their user can see. You do not connect an outside repository to get that behaviour.

Connect a named source for search, and return a link rather than the file text, in rooms you have listed. That option fits when the question truly crosses systems, and you can name the owner of each source. It is the design the announcement points at. It is still a project, with a test, and it is not a migration of the repository.

Rewrite a small set of pages as Salesforce records, with an owner, when the page is the record you want people to trust. That option is editorial. It has a reviewer. It does not start with an export of every repository.

Do nothing new until the source list exists. Waiting is a decision. It is often the correct one in the week after a close, because the alternative is a channel full of text you cannot justify.

None of these is the alternative. They sit side by side until you match one to a source you can point at. A partner who arrives with a ranked shortlist, and no source list of yours, has brought a catalogue you did not ask for. Ask them to put the rank away and work through your repositories one at a time.

## What the walkthrough contains

A migration walkthrough people can follow without inventing a screen looks like this.

Name the repositories and the other stores. File shares, wikis, ticket tools, and the CRM. Each line has a human owner and a classification. A source without an owner does not get connected so a demo has something to show.

Name the identity. Search runs as a person, a service account, or a token. That identity is the ceiling. Choose it the way you would choose access for a new starter, not the way you choose a sandbox login that happens to work.

Name the Slack boundary. Workspace, and the kinds of channel that may receive an answer. Public means publication.

Write five questions that must return nothing. Another team's pay. A draft the author has not shared. A customer record the asker cannot open. A file in a legal hold. A source you have not connected. Test them.

Decide the log. Who asked, which source was touched, and whether the reply contained text or only a link. If you cannot read the log a month later, you cannot explain an answer to the person who owns the file.

Write the stop. When the search is unsure, it says so. It does not invent a clause. "I think the renewal is annual" is a guess. A stop names the gap: no source, no permission, or no confident match.

Put the out of scope line at the top of the statement of work, not in an appendix. "We are not copying repositories into Slack." A quote that cannot repeat that sentence is a quote for a different project. This page still will not give you a number to put beside the line. The price, if you need one, comes from your own scoping, against your own list. It is not in the close notice.

## Where the other pages fit

The implementation page is where the identity, the refusals, and the quote shape are worked in full: [Doti, Slack, and enterprise search](/doti-slack-enterprise-search). Go there when you are ready to name sources. Do not go there to collect a dollar figure. That page will not invent one either.

What happened, who owns Doti, the date, the missing price, and the missing end date are on [what happened to Doti](/what-happened-to-doti). Stay there when the question is the acquisition. Leave it when the question becomes whether a repository moves.

The integration page is the boundary between a reply and a file: [integrating Doti with Salesforce](/integrating-doti-with-salesforce). Read it when someone wants a connector diagram. The diagram still has to show the file staying put.

| Question | Where it belongs |
| --- | --- |
| Should we migrate? | This page. Not every repository. Not because the deal closed. |
| What is the software now? | Agentic enterprise search. Slack is the conversational interface. |
| Versus native? | Org search and Slack search answer from what those systems already hold. No winner is declared. |
| Alternatives? | Four ways to do the job, with no order, and no AppExchange listing. |

:::warn
Do not migrate every repository into Slack because the deal closed. Slack is the conversational interface. The files stay in the systems you connect, under the grants those systems already have.
:::

If the steering pack has a single box labelled Slack, and an arrow from "all repositories", send the pack back. Draw the interface and the sources as separate boxes. If the source list is blank, you are early. The close does not require you to pretend the list exists.

## Questions

### Should I migrate from Doti to Salesforce?

Do not migrate every repository into Slack because the deal closed on 1 December 2025. Doti is agentic enterprise search, and Slack is the conversational interface. Connect a named source, or rewrite a named page, when you can say who owns it and who may see the answer. A close date is not that decision.

### What is Doti software now?

Doti is agentic enterprise search, and Slack is where a person asks. The close was 1 December 2025. The notice does not describe a database you load into Salesforce objects, and it does not say your org gained the feature on the day of the close.

### How does Doti compare with native Salesforce search?

Native search returns records, files, and articles the person can already open in the org. Slack search returns what Slack holds. Enterprise search, with Slack as the interface, can be aimed at other systems. This page does not rank those jobs. It asks you to name which one you have.

### Is there a Doti alternative on AppExchange?

This page does not name an AppExchange listing, a publisher, or a rank. The close notice is not a directory. Alternatives here are ways to do the job: stay on the current source, use native org search, connect a named source and return a link, or rewrite selected pages as records.

### What belongs in a Doti migration walkthrough?

A source list with owners, the identity search runs as, the Slack rooms that may see an answer, five questions that must return nothing, and a line that says repositories are not being copied into Slack. A click-path for a screen the notice does not describe is not a walkthrough. This page does not add a price or an end date.

---

SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Agentforce consulting (https://synconai.com/salesforce-agentforce-consulting).