The content of this site is also available in other languages: Deutsch
Following the announcement regarding the shutdown of Mattermost, we would like to provide you with specific information today about the transition to Matrix. We have developed a strategy for Helmholtz that enables a clean and data-protection-compliant restart.
The Transition Plan
- Independent Migration: Since team structures and message histories cannot and may not be transferred automatically, teams will organize their move to Matrix independently. We are currently developing guides on how to ensure an efficient transition.
- Data Backup / Archiving: We will support you in backing up your previous chat histories and providing archive files. We are currently working on providing the technical tools so that this can be done via self-service.
- Why no automated migration? We examined this option extensively. Due to data protection regulations, high technical effort, and the goal of creating a “clean” new environment, we decided on a fresh start.
- Open Hour: Starting March 20, 2026, we will offer an Open Hour every Friday from 10:00–11:00 AM (Video Conference, Meeting ID:
620 6808 2608, Code:030485), where you can meet the team behind Matrix, give feedback, and ask questions. We look forward to seeing you there 👋. Furthermore, we are available at any time via support@hifis.net.
We understand that this represents extra work for you. However, since our team is very small, this is the only path we can support reliably and scalably.
Thank you for your understanding and your contribution to placing our communication on a new, future-proof foundation together!
The Timeline
- End of March 2026: Matrix becomes available as a new Helmholtz Cloud Service.
- April 2026: The creation of teams in Mattermost will be deactivated; new teams will be created in Matrix.
- Mid-July 2026: Mattermost will no longer be available in the Helmholtz Cloud.
- Data Archiving: Data will be archived and direct access will be lost. Deadlines for final deletion are currently being discussed with data protection officers.
