Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Merge several Slack exports #30

Open
svenssonaxel opened this issue May 10, 2023 · 1 comment
Open

Feature: Merge several Slack exports #30

svenssonaxel opened this issue May 10, 2023 · 1 comment

Comments

@svenssonaxel
Copy link

There are several scenarios where it'd be nice to transform several Slack exports to one MM import:

  • One is unable to obtain a Slack corporate export, but the number of users are sufficiently small that it's possible to obtain one export from each user's perspective that includes direct messages.
  • One would like to migrate several Slack workspaces to one Mattermost team.
  • One happens to have several Slack exports with overlapping time periods.

It's possible that some of the above scenarios, at least some of the time, can be solved by transforming and importing each export separately, but there is at least two reasons why this might be undesirable:

  • Transforming and importing a large number of Slack exports one at a time can be tedious, since one first has to upload it, then obtain an id to run the import job and check the result.
  • Some Slack exports can have some user information missing that is present in other exports, such as email addresses for users. Currently, if one were to transform/import such an export, mmetl would make up an email address for this user. Then, when trying to transform/import another export that contains the correct email address, the mismatched email address would cause the import to fail.
svenssonaxel added a commit to svenssonaxel/mmetl that referenced this issue Jul 3, 2023
@huyz
Copy link

huyz commented Nov 19, 2023

For this issue:

Some Slack exports can have some user information missing that is present in other exports, such as email addresses for users. Currently, if one were to transform/import such an export, mmetl would make up an email address for this user. Then, when trying to transform/import another export that contains the correct email address, the mismatched email address would cause the import to fail.

I wonder if this could help "pre-process" the exports before mmetl tries to import: https://github.com/grundleborg/slack-advanced-exporter

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

No branches or pull requests

2 participants