# Upgrading mongo community v6 to Percona mongo v8

**URL:** <https://forums.percona.com/t/upgrading-mongo-community-v6-to-percona-mongo-v8/36219>\
**Category:** Percona Server for MongoDB\
**Created:** [January 20, 2025, 6:00am UTC](https://forums.percona.com/t/upgrading-mongo-community-v6-to-percona-mongo-v8/36219 "2025-01-20T06:00:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rgillan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/rgillan/32/19848_2.png) [@rgillan](https://forums.percona.com/u/rgillan)\
**Post date:** [January 20, 2025, 6:00am UTC](https://forums.percona.com/t/upgrading-mongo-community-v6-to-percona-mongo-v8/36219/1 "2025-01-20T06:00:11Z")

</div>

Hi,  
Looking at swapping across to Percona after a very long relationship with Mongo community. Have a customer sharded global cluster that is at v6, and wondering if we need to go through the usual version by version upgrade process or could we possibly just go to Percona mongo v8, or do we need to do the whole v7 then v8 step. Looking forward to the monitoring and all the other goodness this will add.  
Thanks, Rob

---

<div class="post-metadata">

**Author:** ![radoslaw.szulgo](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/radoslaw.szulgo/32/17315_2.png) [@radoslaw.szulgo](https://forums.percona.com/u/radoslaw.szulgo)\
**Post date:** [January 20, 2025, 8:49am UTC](https://forums.percona.com/t/upgrading-mongo-community-v6-to-percona-mongo-v8/36219/2 "2025-01-20T08:49:19Z")

</div>

Hi @rgillan , welcome to Percona Community!

The recommended approach is to upgrade to v7 and then v8.

We’ve tried to use our PBM - back and restore tool to upgrade with less risk - it’s possible, but it might cause some problems. If you’re interested, read here:

> **[How to Upgrade MongoDB Using Backups Through Many Major Versions](https://www.percona.com/blog/how-to-upgrade-mongodb-using-backups-through-many-major-versions/)**
>
> Skipping versions to upgrade MongoDB from v3.6 to v7.0 is not recommended, but this is how to update binaries through each major revision step-by-step.

Of course our team can also assist you with the robust upgrade process - just let us know!

---

<div class="post-metadata">

**Author:** ![rgillan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/rgillan/32/19848_2.png) [@rgillan](https://forums.percona.com/u/rgillan)\
**Post date:** [January 20, 2025, 9:08am UTC](https://forums.percona.com/t/upgrading-mongo-community-v6-to-percona-mongo-v8/36219/3 "2025-01-20T09:08:02Z")

</div>

Hi and thanks for the prompt response. I would have been very surprised if we could have skipped but thought I’d ask anyway being advantageous 🙂 , would have just saved the multiple steps per instance. Looking forward to putting your builds through their paces. Cheers

---

<div class="post-metadata">

**Author:** ![radoslaw.szulgo](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/radoslaw.szulgo/32/17315_2.png) [@radoslaw.szulgo](https://forums.percona.com/u/radoslaw.szulgo)\
**Post date:** [January 20, 2025, 9:13am UTC](https://forums.percona.com/t/upgrading-mongo-community-v6-to-percona-mongo-v8/36219/4 "2025-01-20T09:13:18Z")

</div>

Another way is to use cluster-to-cluster synchronization (mongosync), but that’s currently only available within the MongoDB Enterprise subscription. We’re working on an alternative tool that will be available to our customers.