Please do not include PDF and usable in one sentence. Setting up some simple Postgres with sonic for fuzzy search would be _usable_, but PDF is like migrating from Slack to Teams.
We did the migration in stages, basically this:
- Provide access to Teams
- Create all of the new teams / channels there
- Make Slack read-only but still keep the lights on
- Allow folks to search and reference historic data as needed with Slack
- Ensure everyone was moved over to Teams and felt ok enough using it
- Remove access to Slack
- Perform Slack export / PDF creation of important channels
- Attach Slack PDFs to important Teams channels
- Cancel Slack subscription
We also took this as an opportunity to stop using chat as a source of truth for long lived information. Anything that should be stored long term made its way somewhere else (Jira, Confluence, etc.).
Or, they could not in some practical manner do searches on previous posts, so they didn’t use them?
I don't know their exact reasons, probably budget related since they were already using O365.
I can nearly guarantee it wasn't because Teams offers a better user experience. :D
At a high level though, Salesforce is often seen as a predatory company. Prices are high and they will squeeze their users for every nickel (as demonstrated here). They will also monetize your data in ways that you probably don't want.
Teams chat is pretty bad, I agree. But it does have these benefits:
- Free if you're already in the Microsoft ecosystem, which most companies are.
- Microsoft is probably a better steward of your data.
- Teams video / audio calls are much much better than Slack huddles.
- That's pretty much it tbhNot for long, at least for the EU and I assume for us in the EEA. https://www.reuters.com/sustainability/boards-policy-regulat...