# Upgrade Version

**URL:** <https://forum.mattermost.com/t/upgrade-version/25805>\
**Category:** Upgrade\
**Created:** [March 19, 2026, 1:05pm UTC](https://forum.mattermost.com/t/upgrade-version/25805 "2026-03-19T13:05:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jhuayane](https://avatars.discourse-cdn.com/v4/letter/j/898d66/32.png) [@jhuayane](https://forum.mattermost.com/u/jhuayane)\
**Post date:** [March 19, 2026, 1:05pm UTC](https://forum.mattermost.com/t/upgrade-version/25805/1 "2026-03-19T13:05:37Z")

</div>

Hello,

I have a question. I have a server running Mattermos 10.4.2 and PostgreSQL 11. I’m migrating to a new server running PostgreSQL 15, but my question is: to update and upgrade to the latest version 11, how should I proceed? Do I need to download the latest version, or should I upgrade step by step from one version to the next?

Best regards

---

<div class="post-metadata">

**Author:** ![rtfm98](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@rtfm98](https://forum.mattermost.com/u/rtfm98)\
**Post date:** [March 19, 2026, 3:42pm UTC](https://forum.mattermost.com/t/upgrade-version/25805/2 "2026-03-19T15:42:17Z")

</div>

The recommended way is:

- Update your current version to the latest patch version (in your case: v10.4.x, where “x” is the latest patch version)
- Upgrade to the next extended support release (ESR) (v10.5.x, where “x” is the latest patch version)

From there on, jump from ESR to ESR without missing one.  
ESR+1 is possible, ESR+2 not.

You’ll find all extended support releases in the changelog or the release lifecycle explanation in the docs.

---

<div class="post-metadata">

**Author:** ![RianKellyIT](https://avatars.discourse-cdn.com/v4/letter/r/edb3f5/32.png) [@RianKellyIT](https://forum.mattermost.com/u/RianKellyIT)\
**Post date:** [April 2, 2026, 10:20pm UTC](https://forum.mattermost.com/t/upgrade-version/25805/4 "2026-04-02T22:20:53Z")

</div>

The safest approach here is to separate your two migrations rather than doing them at the same time. Upgrading Mattermost AND migrating to a new Postgres version simultaneously doubles the blast radius if something goes wrong, and the troubleshooting becomes a nightmare.

**Recommended order:**

1. **First: Get Mattermost to current ESR on your existing server + existing Postgres 11**

2. **Then: Migrate the database to Postgres 15 on your new server**

3. **Finally: Cut over Mattermost to the new server + Postgres 15**

**Why not simultaneously?** If you hit a Mattermost upgrade error, you won’t know if it’s the app version, the Postgres version, or a data issue. Keeping them separate gives you clean rollback points at each step.

What version of Mattermost are you currently on? That determines how many hops you need for the incremental upgrade path.

---

<div class="post-metadata">

**Author:** ![Erin\_Hong](https://avatars.discourse-cdn.com/v4/letter/e/e36b37/32.png) [@Erin\_Hong](https://forum.mattermost.com/u/Erin_Hong)\
**Post date:** [May 25, 2026, 5:43am UTC](https://forum.mattermost.com/t/upgrade-version/25805/5 "2026-05-25T05:43:07Z")

</div>

I’d also recommend checking the official upgrade path between your current version and target version. Skipping too many major versions at once can sometimes cause weird issues with plugins or the database migration. Taking incremental upgrades usually goes much smoother.