Import from Slack
Starting with Zulip 1.8, Zulip supports importing data from Slack,
including users, channels, messages, attachments, avatars, custom
emoji, and emoji reactions.
This tool has been used to import Slack workspaces with 10,000 members
and millions of messages. If you're planning on doing an import much
larger than that, or run into performance issues when importing,
contact us for help.
Note: You can only import a Slack workspace as a new Zulip
organization. In particular, you cannot use this tool to import from Slack
into an existing Zulip organization.
Import from Slack
First, export your data from Slack.
Note: Only Slack owners and admins can export data from Slack.
guide to data exports
for more information.
Get a Slack API token.
It will be a long string starting with
xoxb-. It is required to
fetch data that Slack doesn't include in their data exports, like
Create a new Slack app.
Add OAuth scopes
to your app. We need the following 'bot token scopes':
Install the app
to your workspace. You will get an API token that you can now use to fetch
data from your slack workspace.
Export your Slack data
Now, Export your Slack data. You will
receive a zip file
This step will also generate a different token starting with
xoxe-; you don't need it.
Import into Zulip Cloud
Email firstname.lastname@example.org with
slack_data.zip, the Slack API token
generated above, and your desired subdomain. Your imported organization will
be hosted at
If you've already created a test organization at
<subdomain>.zulipchat.com, let us know, and we can rename the old
Import into a self-hosted Zulip server
install a new Zulip server,
skipping "Step 3: Create a Zulip organization, and log in" (you'll
create your Zulip organization via the data import tool instead).
Log in to a shell on your Zulip server as the
zulip user. To import with
the most common configuration, run the following commands, replacing
<token> with the value generated above.
supervisorctl stop all # Stop the Zulip server
./manage.py convert_slack_data slack_data.zip --token <token> --output converted_slack_data
./manage.py import '' converted_slack_data
This could take several minutes to run, depending on how much data
you're importing. The server stop/restart is only necessary when
importing on a server with minimal RAM, where an OOM kill might
The commands above create an imported organization on the root domain
EXTERNAL_HOST) of the Zulip installation. You can also import into a
custom subdomain, e.g. if you already have an existing organization on the
root domain. Replace the last line above with the following, after replacing
<subdomain> with the desired subdomain.
./manage.py import <subdomain> converted_slack_data
Once the import completes, all your users will have accounts in your
new Zulip organization, but those accounts won't have passwords yet
(since for very good security reasons, passwords are not exported).
Your users will need to either authenticate using something like
Google auth, or start by resetting their passwords.
You can use the
./manage.py send_password_reset_email command to
send password reset emails to your users. We
recommend starting with sending one to yourself for testing:
./manage.py send_password_reset_email -u email@example.com
and then once you're ready, you can email them to everyone using e.g.
./manage.py send_password_reset_email -r '' --all-users
'' with your subdomain if you're using one).
Slack doesn't export private channels or direct messages unless you pay
for Slack Plus or contact Slack support. See
for more details.
(Slack Plus import) Message edit history is currently not imported.
Slack doesn't export user settings or organization settings, so
you'll need to configure these manually.
Import of user roles:
Workspace Primary Owner and
Workspace Owner users
are mapped to Zulip
Organization Owner users.
Workspace Admin users are mapped to Zulip's
Member users is mapped to Zulip
Single Channel Guest and
Multi Channel Guest users
are mapped to Zulip
Channel creators have no special permissions in Zulip.
The "joined #channel_name" messages are not imported.