Files
zulip/help/import-from-slack.md
Shubham Padia a54d247111 help: Use 1. for numbered lists everywhere.
The conversion script for help-beta assumes that all items in a numbered
list start with 1. which was a wrong assumption. This commit attempts to
fix that. We are not introducing any lint step to tackle this since it
will be easy to just check for this again before the cutover happens.
We do not change this for `numbered-list-examples.md` since that example
shows how the current numbered lists work and we might still want to
show that. We can decide what to do with that file once the time of
cutover arrives.
2025-06-23 09:48:43 -07:00

6.5 KiB

Import from Slack

{!import-workspace-to-zulip.md!}

Import process overview

To import your Slack organization into Zulip, you will need to take the following steps, which are described in more detail below:

{start_tabs}

  1. Export your Slack data.

  2. Import your Slack data into Zulip.

  3. Clean up after the Slack export.

  4. Get your organization started with Zulip!

{end_tabs}

Import your organization from Slack into Zulip

Export your Slack data

Slack's data export service allows you to export all public channel messages, including older messages that may no longer be searchable under your Slack plan.

Unfortunately, Slack only allows workspaces that are on the Business+ or Enterprise Grid plans to export private channels and direct messages. Slack's support has confirmed this policy as of August 2022.

Owners of Business+ or Enterprise Grid workspaces can request special access in order to export direct message data.

Export message history

{start_tabs}

  1. Make sure that you are an owner or admin of your Slack workspace. If you are one, the Slack web application will display that in your profile, in a banner covering the bottom of your avatar.

  2. Export your Slack message history. You should be able to download a zip file with your data a few minutes after you start the export process.

{end_tabs}

Export user data and custom emoji

{start_tabs}

  1. Make sure that you are an owner or admin of your Slack workspace. If you are one, the Slack web application will display that in your profile, in a banner covering the bottom of your avatar.

  2. Create a new Slack app. Choose the "From scratch" creation option.

  3. Create a bot user, following the instructions to add the following OAuth scopes to your bot:

    • emoji:read
    • users:read
    • users:read.email
    • team:read
  4. Install your new app to your Slack workspace.

  5. You will immediately see a Bot User OAuth Token, which is a long string of numbers and characters starting with xoxb-. Copy this token. It grants access to download user and emoji data from your Slack workspace.

!!! warn ""

You may also come across a token starting with `xoxe-`. This token cannot
be used for the Slack export process.

{end_tabs}

Import your data into Zulip

{!import-your-data-into-zulip.md!}

{start_tabs}

{tab|zulip-cloud}

{!import-into-a-zulip-cloud-organization.md!}

  1. Your Slack Bot User OAuth Token, which will be a long string of numbers and characters starting with xoxb-.

{!import-zulip-cloud-organization-warning.md!}

{tab|self-hosting}

{!import-into-a-self-hosted-zulip-server.md!}

  1. To import into an organization hosted on the root domain (EXTERNAL_HOST) of the Zulip installation, run the following commands, replacing <token> with your Slack Bot User OAuth Token.

    {!import-self-hosted-server-tips.md!}

    cd /home/zulip/deployments/current
    ./scripts/stop-server
    ./manage.py convert_slack_data /tmp/slack_data.zip --token <token> --output /tmp/converted_slack_data
    ./manage.py import '' /tmp/converted_slack_data
    ./scripts/start-server
    

    Alternatively, to import into a custom subdomain, run:

    cd /home/zulip/deployments/current
    ./scripts/stop-server
    ./manage.py convert_slack_data /tmp/slack_data.zip --token <token> --output /tmp/converted_slack_data
    ./manage.py import <subdomain> /tmp/converted_slack_data
    ./scripts/start-server
    
  2. Follow step 4 of the guide for installing a new Zulip server.

{end_tabs}

Import details

Whether you are using Zulip Cloud or self-hosting Zulip, here are few notes to keep in mind about the import process:

Slack role Zulip role
Workspace Primary Owner Owner
Workspace Owner Owner
Workspace Admin Administrator
Member Member
Single Channel Guest Guest
Multi Channel Guest Guest
Channel creator none
  • Slack threads are imported as topics with names like "2023-05-30 Slack thread 1".

  • Message edit history and @user joined #channel_name messages are not imported.

Clean up after the Slack export

Once your organization has been successfully imported in to Zulip, you should delete the Slack app that you created in order to export your Slack data. This will prevent the OAuth token from being used to access your Slack workspace in the future.

Get your organization started with Zulip

{!import-get-your-organization-started.md!}

!!! tip ""

Zulip's [Slack-compatible incoming webhook](/integrations/doc/slack_incoming)
makes it easy to migrate integrations.

Decide how users will log in

{!import-how-users-will-log-in.md!}