Are there any plans to include attachments in the exported dump?

Thank you Michael for the question.

That is correct. However, we have a community contribution which adds direct and group message channels to the export: https://github.com/mattermost/mattermost-server/pull/9603

To be clear, the new feature doesn't export direct messages, correct?

we need to make sure that:

1- exported files are compatible with Mattermost bulk import functionality (to allow users to export from current instance of mattermost and import into new instance at a later date)

2- Admins are able to select what level of export they need. Options might be:

a. export only users and teams
b. export only users, teams and public channels
c. Export users, teams, public channels and messages

This would help admins create a fresh new instance (without older messages) of Mattermost without having to manually add all users, create teams/channels etc.

I would expect this feature to become mandatory if one as EU users due to the upcoming GDPR...

Especially now that Slack has this, it should definitely exist; important for compliance, too.

Being unable to export data from mattermost in a slack-compatible format is a big factor keeping us from adopting it at my company.

It makes no sense that you can export data from slack, import it into mattermost, but once you switch to mattermost there's no going back. It makes the risk of adopting mattermost much higher than the potential benefits.

Should I register an account on the mattermost Jira to vote there as well?

Go to https://mattermost.atlassian.net/browse/PLT-49 and login to vote for this issue in the backlog also.

please

+1

This would be a must to keep control on datas.
The export should be easy to read to allow quick searches on archived discussions without the need of using the application itself...

+1

I agree 100% with Michael Hawks below. In academia, in particular, groups and projects move from place to place all the time. Data needs to move with them, so the ability to export a particular team makes a great deal of sense.

No-one likes vendor lock-in; in my world that sort of thing will tend to prevent solutions from being adopted.

+1

I am also excited about Mattermost, but I wouldn't want to adopt it unless I could export my team. This is super important for following a "You control your data" philosophy.

The ability to export / import Team Data (users, channels, messages, attachments, etc) would be very beneficial for cross organization collaboration. We have many divisions and companies that we work with that each have their own MM server. It would be great to move the MM Team from one server to another if migration makes sense based on current project ownership.

+1

+1

Now tracked at https://mattermost.atlassian.net/browse/PLT-49

This feature was partially implemented, then cut, and the tracking ticket was unfortunately closed without writing in the explanation.

The ticket has been re-opened to track this issue

Hi
One of customer(*** MOSAIC), they have also request similar feature, but they want to export of specific channel's message with filter options(time). I will update to Ian.

This appears to be discussed here: https://mattermost.atlassian.net/browse/PLT-49
Has this already been implemented for enterprise users?

I found this suggestion via your forum post: http://forum.mattermost.org/t/how-do-i-export-data/560