Skip to content

update slack migration docs#8741

Open
vish9812 wants to merge 1 commit intomasterfrom
slack
Open

update slack migration docs#8741
vish9812 wants to merge 1 commit intomasterfrom
slack

Conversation

@vish9812
Copy link
Contributor

@vish9812 vish9812 commented Feb 13, 2026

  • Updated Slack export terminology from "Regular export"/"Corporate export" to current Slack terms ("Public channels export"/"All channels and conversations export") and corrected the UI navigation path
  • Removed the slack-advanced-exporter section and all references — Slack exports already include emails and file download links, making this tool unnecessary
  • Removed the Additional Tools subsection (mm-emoji, mmimportjs, slack-migrate-pinned-posts) as they are archived, broken, or no longer maintained
  • Added mmetl check slack validation step before running the transform
  • Added documentation for useful mmetl transform flags: --skip-attachments, --allow-download, --default-email-domain, --skip-empty-emails, --discard-invalid-props
  • Added mmctl import validate step before processing the import
  • Fixed incorrect command mmctl import list process to mmctl import job list
  • Fixed typos and minor errors throughout the document

PS: I've not tested it with the Enterprise export. So, no changes around that.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Slack-to-Mattermost migration documentation to improve accuracy, clarity, and alignment with current tooling. The updates remove references to the deprecated slack_advanced_exporter tool, add a validation step using mmetl check slack, correct terminology around Slack export types, fix numerous spelling and grammar errors, and refine configuration guidance.

Changes:

  • Removed deprecated slack_advanced_exporter tool instructions and streamlined to focus on the officially supported mmetl tool
  • Added validation step for Slack exports before transformation using mmetl check slack
  • Corrected multiple spelling and grammar errors throughout the document (necessary, enough, additional, associated, Starred, Threaded conversations)
  • Updated Slack export type terminology to "Public channels export" and "All channels and conversations export" with clarified descriptions
  • Fixed configuration guidance for TeamSettings.MaxChannelsPerTeam and removed extra space in ElasticsearchSettings.EnableIndexing

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@github-actions
Copy link
Contributor

Newest code from mattermost has been published to preview environment for Git SHA 92255d6

1 similar comment
@github-actions
Copy link
Contributor

Newest code from mattermost has been published to preview environment for Git SHA 92255d6


.. code-block:: sh

mmctl import validate ./mattermost-bulk-import.zip
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this command work on local files or on files already uploaded? The syntax here is for local files.

- ``--allow-download`` / ``-l``: Allow downloading attachments from URLs.
- ``--default-email-domain <DOMAIN>``: When a user's email is missing from the export, generate one from their username and the provided domain (e.g., ``--default-email-domain example.com``).
- ``--skip-empty-emails``: Allow users with empty email addresses to be included in the output. Note that this results in invalid import data that will need to be manually corrected before importing.
- ``--discard-invalid-props`` / ``-p``: Discard posts with invalid properties instead of skipping them entirely.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The description for --discard-invalid-props says posts will be discarded and also says "without skipping them entirely". It's unclear what that means. In code the comment says, "Skips converting posts with invalid props instead discarding the props themselves". I don't think the whole post is discarded, just the invalid props.


commit;

Additional tools
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these tools no longer needed? If so, can we add a line explaining why?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants