From 699021e7d8f41cc174ae501df9971a7b3aa781b0 Mon Sep 17 00:00:00 2001 From: Rhea Parekh Date: Sat, 3 Feb 2018 15:07:21 +0530 Subject: [PATCH] slack importer: Update Documentation with slack's legacy token method. --- templates/zerver/help/import-data-from-slack.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/templates/zerver/help/import-data-from-slack.md b/templates/zerver/help/import-data-from-slack.md index 11db19808e..433e97ee1f 100644 --- a/templates/zerver/help/import-data-from-slack.md +++ b/templates/zerver/help/import-data-from-slack.md @@ -10,10 +10,18 @@ `slack_data.zip`. Currently we only support standard export. See https://get.slack.help/hc/en-us/articles/201658943-Export-data-and-message-history for more detail on this step. -2. Convert the zip file `slack_data.zip` to Zulip export format using the - command `./manage.py convert_slack_data --output `. -3. Import the converted data. If you are importing into an existing database, - run the command `./manage.py import --import-into-nonempty `, +2. Generate a Slack API token using Slack's test + [token generator](https://api.slack.com/custom-integrations/legacy-tokens) + to import all of the necessary data. We use this as current Slack exports don't + include user's email data, however, we still get that data from Slack's older + method of legacy tokens. + **Note:** Once Slack starts including user emails in the exports, + this extra step of using legacy tokens to get user data would no longer be + necessary. +3. Convert the zip file `slack_data.zip` to Zulip export format using the command + `./manage.py convert_slack_data --token --output `. +4. Import the converted data. If you are importing into an existing database, + run the command `./manage.py import --import-into-nonempty `, otherwise, if you are importing into a new Zulip instance, run the command `./manage.py import --destory-rebuild-database `.