#Slack download private conversation full version#
#Slack download private conversation install#
#Slack download private conversation zip file#
#Slack download private conversation update#
#Slack download private conversation zip#

#Slack download private conversation update#

If anyone takes this testing further to get the attachments in too, let me know and I’ll update the post.

#Slack download private conversation zip#

I just did a rollback (shown later), deleted the attachment files found inside the channel folder (private-channel-one above) as I didn’t really care for them anyway, re-did the zip and redid the import. The result is a partial import, up to that point. Not obvious at first, as the import silently bombed when it came across the first attachment in the channel. Note: In my testing, I found that Step 3 (importing) failed when there were attachments. private-channel-one (replace this with your own channel(s)).

#Slack download private conversation zip file#

The zip file (in this case) should therefore contain the following Now zip up the root folder into a new zip file. Note: If you can process multiple channels at the same time, just make sure that each corresponding folder is moved from the _privatechannels folder to the root, and that you modify the above values for each channel. Remove any JSON nodes for the channels that you are not messing with just to be safe. Save the JSON file. Change both is_group and IsPrivateGroup from true to false. Move the private-channel-one folder and the channels.json up to the root folder and edit the channels.json file Peek inside the _privatechannels folder and you will find the files you need Also remove the channels.json from the root. Remove any public channels folders from the root folder – in this case random and general. The channels.json file and every folder in the root that doest start with an ‘underscore’ relates only to your public channels.įor this post I’m going to convert one private channel called private-channel-one. Here you have some key files and folders for this process. Let’s consider the resulting extracted folder as the ‘root’ of what we want to manipulate. Extract that and open the resulting folder. Here you’ll find a zip file with your backup data. Open the folder and the RawBackup subfolder A good text editor like Sublime Text or Notepad++ will make your life a bit easier.Ĭlick on the View Backup button from the Status screen in Backupery, and it should open the folder where the backup was stored, and there should be a folder there with the date-time that the backup was taken. So this requires a little bit of JSON skill.

If all went well, you should have a backup of your slack data

#Slack download private conversation full version#

Buy the full version if you need to remove them.

Note below the limitations of the free version. Once Authorized, the backup should jog on all by itself If you have multiple workspaces make sure you are logged into and are authorizing the correct one!

It will also have popped open a browser with something like the below. If thats the case, you will see the screen below Most likely this will fail as Backupery isn’t authorized in your Slack Workspace. You can change the above settings if you want, and then click Start. The subsequent screen relates to the when and where for your backups

#Slack download private conversation install#

The paid version gives you better scale, so pay the good folks if you are going to use it to get you out of a hole 🙂ĭownload, install and launch Backupery and you should get a screen like the below. Depending on your needs, you may get away with the free version, which I am going to use for demonstration purposes here. Backupery for Slack ( ) has a free and a paid version. That may be resolvable…it just didn’t bother me enough to work it out.ĭetails below (provided with no warranty, your mileage may vary, please test with a dummy channel first warnings etc) ! Step 1: Backing up the dataĪs I mentioned, Slack doesn’t provide this functionality when it comes to private channels, but there is a tool out there that does. Not to be undone, I did a bit of digging around, and found a way, with one main caveat – that the import doesn’t like the attachments, screenshots etc.

You cannot export or import a private channel using Slacks native tools.

You cannot change a private channel back to being a public channel.

However, when we had cause to port a channel to a new workspace we quickly found out that there are a few limitations when it comes to private channels:

So we got into the habit of creating dedicated channels for different topics and we had quite a few ‘private’ channels where only those explicitly invited to them could see the content.Ĭhanging a Public Channel to a Private channel is straight-forward and part of Slacks native functionality. The organisation we work in is rather large and therefore while we had a need for a single workspace, the situation where everyone could see content from all the channels wasn’t really cutting it. The team I work in are pretty heavy slack users.