Hi everyone, how are you? It's been a while since we last spoke! I'm having a problem and would like your help. We have Medplum 4.1.5, but when running the latest version, 4.3.13, we encounter a database version mismatch when the server tries to access a database. Any ideas on how to fix this? If I dump the 4.1.5 database, install version 4.3.13 with a clean database, and then insert the dump data, will it work? I appreciate any help, everyone.

https://www.medplum.com/docs/self-hosting/upgrading-server I think this doc is what you're looking for. TL;DR- Upgrade path is

4.1.12

->

4.2.6

->

4.3.13

and ensure all pre/post deploy migrations complete successfully first. Our experience seems to be an outlier but you may want to consider running

4.2.6

for a time period and monitoring db performance. Check out this [issue](https://github.com/medplum/medplum/issues/7310) for details.

Thank you very much, @nathan-watkins-unityai ! I didn't know this information, I apologize for not researching the documentation further. We'll update to version 4.2.6 and then monitor it for a certain period before moving on to the next ones. Very good indeed! Thank you! Could you please instruct me on how to figure out which versions I need to upgrade over time and where to find the available Medplum versions? For example, how did you arrive at the upgrade from versions 4.1.12 -> 4.2.6 -> 4.3.13? Is there a rule for defining which versions to upgrade? Thanks in advance, friend!

[Step 1](https://www.medplum.com/docs/self-hosting/upgrading-server#1-plan-your-upgrade-path) in that link above lines it out pretty well. Only thing I'd add is that you can view all releases on their [repo](https://github.com/medplum/medplum/releases) to determine what the latest patch version is for each minor version.