How to Downgrade Enterprise Edition to Team Edition

[tpadioleau]

The section https://github.com/mattermost/docs/blob/master/source/administration-guide/upgrade/enterprise-install-upgrade.rst clearly details how to upgrade from the Team Edition to the Enterprise edition.

Unless I am mistaken, there is no detailed reverse procedure, from Enterprise edition to Team edition ? Is it supported ? Could we clarify this procedure ?

[cwarnermm]

@claude - How would a Mattermost system admin downgrade their Mattermost Enterprise workspace to Team Edition? What happens to the data in the system after downgrading? What would the downgrade process look like for:

• a High Availability environment consisting of multiple nodes
• a connected workspaces environment (aka: shared channels)
• a Docker deployment
• a Kubernetes deployment
• an Azure Marketplace Container deployment
• an Oracle Cloud Marketplace deployment
• a Linux deployment via tarball
• a Linux deployment via Ubuntu
• a Linux deployment via RHEL/CentOS

[claude]

Claude finished @cwarnermm's task —— View job • claude/issue-8558-20251120-1429 • Create PR ➔

---

Comprehensive Enterprise to Team Edition Downgrade Documentation Created

I've successfully created comprehensive documentation covering how to downgrade Mattermost Enterprise Edition to Team Edition across all deployment scenarios you mentioned.

Task List:

• Read repository guidelines and documentation structure
• Research existing upgrade documentation referenced in the issue
• Search for any existing downgrade documentation
• Analyze Mattermost documentation structure and conventions
• Research downgrade capabilities for High Availability environments
• Research downgrade capabilities for connected workspaces/shared channels
• Research downgrade capabilities for Docker deployments
• Research downgrade capabilities for Kubernetes deployments
• Research downgrade capabilities for Azure Marketplace Container deployments
• Research downgrade capabilities for Oracle Cloud Marketplace deployments
• Research downgrade capabilities for Linux tarball deployments
• Research downgrade capabilities for Ubuntu deployments
• Research downgrade capabilities for RHEL/CentOS deployments
• Document data handling implications during downgrade
• Create comprehensive downgrade documentation
• Follow repo formatting and structure conventions

What was created:

New Documentation: /source/administration-guide/upgrade/enterprise-downgrade-to-team.rst

Key sections included:

1. Overview - Process overview and data preservation guarantees
2. Data handling during downgrade - What's preserved vs. what gets disabled
3. Preparation steps - Backup procedures and feature review
4. General downgrade process - Standard procedure for most deployments
5. Deployment-specific procedures for:
   • High Availability environments (cluster to single node)
   • Connected workspaces/shared channels (feature disabling)
   • Docker deployments (container and image management)
   • Kubernetes deployments (Helm and kubectl procedures)
   • Azure Marketplace Container deployments
   • Oracle Cloud Marketplace deployments
   • Linux tarball deployments
   • Ubuntu package deployments
   • RHEL/CentOS package deployments
6. Post-downgrade verification - Testing and validation steps
7. Troubleshooting - Common issues and solutions

Data implications documented:

• ✅ Preserved: User accounts, messages, files, channels, teams, basic integrations
• ❌ Disabled: Advanced auth, guest accounts, compliance features, HA clustering, advanced reporting

Integration: Added the new documentation to the main upgrade index (/source/administration-guide/upgrade-mattermost.rst) so it's discoverable alongside the upgrade documentation.

The documentation addresses the gap identified in issue #8558 by providing the reverse procedure to the existing upgrade documentation, with specific guidance for each deployment scenario you mentioned.

---

[tpadioleau]

Hi, is the generated documentation correct ?