# Big server/app upgrade. What to look out for / Compatibility resources...?

**URL:** <https://community.parseplatform.org/t/big-server-app-upgrade-what-to-look-out-for-compatibility-resources/3414>\
**Category:** Uncategorized\
**Created:** [April 25, 2023, 2:53pm UTC](https://community.parseplatform.org/t/big-server-app-upgrade-what-to-look-out-for-compatibility-resources/3414 "2023-04-25T14:53:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![briquinn](https://community.parseplatform.org/letter_avatar_proxy/v4/letter/b/ed655f/32.png) [@briquinn](https://community.parseplatform.org/u/briquinn)\
**Post date:** [April 25, 2023, 2:53pm UTC](https://community.parseplatform.org/t/big-server-app-upgrade-what-to-look-out-for-compatibility-resources/3414/1 "2023-04-25T14:53:47Z")

</div>

I’ve need to upgrade my client’s Parse-based app and server. The server is currently on 2.7.2 and it looks like I can go up to 5.x on my host (NodeChef). I’m guessing there is a similar leap for the iOS SDK.

That’s a big upgrade and I’m wondering if there is a way to pre-empt the compatibility issues? Is there a chart somewhere about version compat for Parse Server / Node / SDK?

Also the app is presently write-only to Parse. Am I correct that there is no need in that case to migrate (Mongo) database structure? The incoming objects will manage that on-the-fly, right?

thx!

---

<div class="post-metadata">

**Author:** ![rogernolan](https://community.parseplatform.org/user_avatar/community.parseplatform.org/rogernolan/32/1566_2.png) [@rogernolan](https://community.parseplatform.org/u/rogernolan)\
**Post date:** [April 29, 2023, 12:13pm UTC](https://community.parseplatform.org/t/big-server-app-upgrade-what-to-look-out-for-compatibility-resources/3414/2 "2023-04-29T12:13:27Z")

</div>

We just went through a similar thing and it was relatively easy. Things that we had to change:

- S3 config moved to process.env
- The promises are no longer Parse specific so you can (but don’t need to) move to async await
- We needed to migrate a lot of cloud code away from old style request.success to returning a promise (or a success value it you use async/await)

---

<div class="post-metadata">

**Author:** ![operatordevelopment](https://community.parseplatform.org/user_avatar/community.parseplatform.org/operatordevelopment/32/1778_2.png) [@operatordevelopment](https://community.parseplatform.org/u/operatordevelopment)\
**Post date:** [May 17, 2024, 9:27am UTC](https://community.parseplatform.org/t/big-server-app-upgrade-what-to-look-out-for-compatibility-resources/3414/3 "2024-05-17T09:27:08Z")

</div>

I’m looking for similar answers. Have you figured anything else out?  
I’m on nodechef also and it appears they only go up to 5.4.0 but the latest parse-server “release” version is 7.0.0.  
At first it _seemed_ like the Parse Swift repo was the way to go for iOS but I discovered the last release was October, 2022.  
So it seems like I should be using the Parse-SDK-iOS-OSX repo, as it is being actively maintained. The last release was 3 weeks ago.  
Thanks!  
Del