This can help you decide whether to migrate the channel.īy default, public channels content (messages and files) can be exported. If you have a paid Slack service plan (anything other than Free), you can use Slack’s analytics (./admin/stats#channels) to see how active a channel is, when it was last used, and how many people are members.
You’ll use the resulting list to figure out how to group your Slack channels into teams in Teams as well as who should be members of each team.
We recommend that you use Slack analytics to see how much activity happens in each channel to help you decide which channels to move. In Slack, users join a channel which is part of a Slack Workspace, whereas in Teams users join a team which is a collection of channels. If you don’t have access to the stats page, you’re not an admin or owner. Decide which workspaces you want to migrate (and which ones you want to leave behind). Review the Channels and Members tabs to look for usage patterns. If you’re a member of the Slack Workspaces you want to migrate, you can analyze the usage yourself by going to. For example, how many workspaces are being moved? Are they used by a specific department, many, or in use by an entire organization? Understanding how your Slack workspaces are being used helps you determine the scope of your migration.
It’s up here on GitHub, the code is REALLY rough but it works pretty well. – Generate an index.html with links to all channel logs in your SlackĪnd here’s how the output looks in a browser: – Generate a layout from channel logs (in HTML) – Compile daily logs into single channel logs (in JSON) – Load the channels file to identify channel ids – Load the users file to identify user ids (and add user pics) So I wrote a script that ties everything together and outputs nice Slack-looking HTML files of your entire JSON export. Point is, it’s a big maze of files and data. All channel names are also replaced by channel ids, which can be found in channels.json. They’re in a different file called users.json.
ZIP file full of JSON files.Įverything IS in fact in there, but it’s pretty hard to read.Īlso all usernames are replaced by user ids, and there’s no user images to be found in the chat logs. Slackbot will send you a message when it’s ready with a download link: You can access it at and then click Export Data. Awesome! Slack had this for ages, I just never saw it myself.
So Slack actually had an export function, which free users can use too.
It’d be fun to read the archive sometimes though. So we’ve just accepted it as being there. It’d cost about 4,000 * $15/m or $720,000/y to pay for, which I can’t afford.
Since it’s 4,000 people, we’ve always had issues with the 10,000 message limit for free Slack accounts. And it’s been going for almost a year now (actually, exactly 6 days and it will be one year, wow!). My chat community on Slack for digital nomads, called #nomads, has almost 4,000 members now.