With the recent deprecation of Monday modules, I’m wondering if anyone else has reached out to support to ask if the upgrade to the new version can be done automatically or via the version switcher. I hardly see any distinct changes between the new modules and old modules, and having to replace each one by one will be severely time consuming. I have over a 1000 monday modules across clients, so this will take so much time to do.
There is no automatic way of updating yet. so will need to do manually. But support for the old version is maintained until May 2026. So you have time. Plus, older version doesn’t necessarily require to update, unless there is a major change in API. So if you encounter any problem with that in future, then you can update, otherwise go with the existing version.
Best regards, Msquare Automation Platinum Partner of Make @Msquare_Automation
This is not acceptable. We can’t update all monday modules. It is just not possible. The biggest problem is that upgrading the module generates new module (with new numbering) which basically impact the complete scenario. The way API deprecations are handled is not supportive at all. Is there an alternative here?
We are sorry for the frustration caused by the Monday API changes that led to the development of our v2 app. Please visit our Help Center to read all about the transition process and the dedicated timeline for the change.
I am a 100% with @AlejandroAlvarez on this topic. There needs to be a better way than there is right now! This is an unacceptable amount of work to replace the V1 to V2 versions! The link to help page is almost useless, have you guys actually tried to replace the modules in a bigger scenario? I could almost rebuild them from scratch in the same time…
Are there any plans to offer a better solutions???
Thank you for sharing your concerns and feedback with the community.
First of all, I’d like to apologize for the tedious process of upgrading each of the modules individually. It’s absolutely understandable that while dealing with big, complex scenarios, the amount of work will be equally great.
I highly encourage you to go to our Idea Exchange page and upvote the Scenario Builder: make the upgrade of modules easier. By voicing your concerns and upvoting, you increase the priority of this feature for our developers.
Thanks for your reply. I did as you recommended and left a message and upvote at the Idea Exchange Page and can only encourage more people that are reading this to do the same!
I can only hope that there is some movement till the end of the support period of V1….
Just a reminder that we’re unable to guarantee that the bulk upgrade feature will be introduced before May 1, 2026, so I’d still strongly recommend you upgrade all your Monday modules to v2 before the deadline to avoid any errors in your scenario.
@vendy is this something you can verify with the Make dev team, to determine if it would work. Or at the very least that the monday module version is indeed converted to the new one without risk of being blocked for future updates?
I deleted this post because this approach is suspect. It seems that there are other upgrades to the Monday modules from V1 to V2 other than these ones mentioned here. The way the JSON’s are structured behind the graphical interface of the module do vary, some are the same, and some of not. It can be simple things, but it is unclear if they lacks these changes they would still work.
Thus, success cannot be guaranteed.
Working on a new approach to swap out each module with the new module structure. Not sure if that will work.
Well, even a very simple module like List Users. In the V2 module it has “filter”: null, added in the JSON, not present in the V1 version. Thus, the updated via code V2 would also not have this. Unclear if this is needed or not needed. Could lead to future issues.
Then a more complicated module like Change Multiple Column Values: V1 version incorporates a file size check as a filter, by default, V2 excludes that file size limit.
These discrepancies mean that each module needs to be upgraded for the new structure to be safe, so a different automation flow requiring a lot more work. Need a module mapping step. Not sure this will even work.
I also checked in with our Product team internally and can confirm that this approach might work only if the modules are identical to v1. If you use this for modules with different fields, the transition might not work whatsoever.
I agree. Make’s proposed “upgrade” path is not really an upgrade at all. Because the Monday modules do NOT in fact “upgrade” but are instead replaced with a totally new (and differently numbered) module, we are essentially required to rebuild the entire scenario,
This is not an “upgrade” path. It is a forced rebuild. For those of us with a lot of Monday modules, it’s going to require massive amounts of time and money to rebuild the affected scenarios.
What is the problem?