# Moving published app from current to new runtime

**URL:** <https://community.developer.atlassian.com/t/moving-published-app-from-current-to-new-runtime/76077>\
**Category:** Forge Platform and Tools\
**Tags:** forge-native-nodejs-runtime\
**Created:** [January 9, 2024, 11:52am UTC](https://community.developer.atlassian.com/t/moving-published-app-from-current-to-new-runtime/76077 "2024-01-09T11:52:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AdamRepask](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AdamRepask](https://community.developer.atlassian.com/u/AdamRepask)\
**Post date:** [January 9, 2024, 11:52am UTC](https://community.developer.atlassian.com/t/moving-published-app-from-current-to-new-runtime/76077/1 "2024-01-09T11:52:34Z")

</div>

Hello! I would like to ask whether there are some additional steps to be aware of when transitioning the app already published on the marketplace from current runtime to the native Node.js runtime. Is it sufficient to just follow the steps specified [here](https://developer.atlassian.com/platform/forge/runtime-reference/native-nodejs-runtime/#before-you-begin)? Thanks for any insights.

---

<div class="post-metadata">

**Author:** ![AlexeyKotlyarov](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/alexeykotlyarov/32/45643_2.png) [@AlexeyKotlyarov](https://community.developer.atlassian.com/u/AlexeyKotlyarov)\
**Post date:** [January 9, 2024, 11:12pm UTC](https://community.developer.atlassian.com/t/moving-published-app-from-current-to-new-runtime/76077/2 "2024-01-09T23:12:40Z")

</div>

Hi, thanks for giving the new runtime a try!

All the caveats we are aware of are listed on that page (see [breaking changes](https://developer.atlassian.com/platform/forge/runtime-reference/native-nodejs-runtime/#breaking-changes) section).

Note that the runtime is chosen for every _deployment_ of the app, so you are free to deploy and test your published app in development and staging first. When you’re satisfied with its behaviour there, you can make a production deployment with the new runtime as well.

If you run into problems not listed there, let us know!

---

<div class="post-metadata">

**Author:** ![AdamRepask](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AdamRepask](https://community.developer.atlassian.com/u/AdamRepask)\
**Post date:** [January 10, 2024, 11:33am UTC](https://community.developer.atlassian.com/t/moving-published-app-from-current-to-new-runtime/76077/3 "2024-01-10T11:33:00Z")

</div>

Thank you for the response. We will test it out eventually and let you know if any issues arise.
