---
title: "MongoDB version 5.0 to 6.0 upgrade plan"
canonical: "https://support.appfire.com/space/PP/248840340/MongoDB%20version%205.0%20to%206.0%20upgrade%20plan"
format: markdown
---
| **Step** | **Details** | **Status** | **Time** | **Rollback steps** |
| --- | --- | --- | --- | --- |
| Realease package update to staging | Deploy app with updated MongoDB Node Driver to staging. | [done] | 3/28/2023 | Revert the last commit on master |
| Upgrade  staging MongoDB version on Atlas | 1. Update MongoDB version from 5.0 to 6.0 for Planning Poker - Staging on MongoDB Atlas
2. Verify everything is working correctly on Planning Poker Staging | [DONE] | 3/28/2023 |  |
| Realease package update to production | Deploy app with updated MongoDB Node Driver to production. | [Done] | 3/28/2023 | 1. Revert the last commit on master
2. Run “Deploy production” action |
| Prepare MongoDB backups | Take database snapshot and download it | [Done] | 4/1/2023 |  |
| Upgrade production MongoDB version on Atlas | 1. Update MongoDB version from 5.0 to 6.0 for Planning Poker - Production on MongoDB Atlas
2. Verify everything is working correctly on Planning Poker Production | [Done] | 4/1/2023 | Restore backup |

Upgrade done on 4/1/2023 at 5pm.

**Post-upgrade notes:**

We missed changing `mongo_db_major_version` from `5.0` to `6.0` on `mongodb.tf` file, which caused error on prod while trying to connect to MongoDB on  4/2/2023 , which resulted in app on production being **dead!**

It was not discovered on staging even though staging upgrade was done couple of days before, because problem emerged after the app restart, which didn’t happen on staging.