Just wanted to remind you about the Monday module migration, which we already raised, that needs to be done by May 1st.
As previously communicated, the monday.com V1 API is being discontinued on May 1, 2026, and you must migrate your modules to V2 to keep your scenarios running.
To ensure this transition is as seamless as possible for you, we’ve just launched a new Module Migrator tool.
Introducing the Module Migrator
Manually swapping modules and remapping fields across all scenarios is no small task. This free tool automatically scans your folders, identifies scenarios using deprecated modules, and migrates them to V2 in just a few clicks.
Note: The Module Migrator currently supports only monday.com migrations. Support for more apps may be added in the future.
How to migrate your scenarios
Open the app: Access the Module Migrator in Make.
Scan: Select the folders you want to scan, the tool will identify all scenarios with V1 modules.
Choose your path: Update your scenarios in place or recreate them in a new folder (recommended for testing).
Confirm: Review any items requiring manual adjustment and complete the migration.
I’ve been testing the new Migrator on 3 different Make accounts and bumped into a problem.
After a scenario gets updated with Migrator, if you click on any Update Column Values module - it starts showing empty mappings - item ID is the most frequent case, sometimes there is more empty columns.
The fun part is that if you click copy on the Update module and paste it in a text editor - all mappings are in place. But if I want to edit the Update module - it opens with the empty item ID every time.
Our developers are aware of this issue, and they are currently investigating it further to release a fix. I’ll keep you updated about the progress in this thread.
Is the 1st May 2026 Deadline going to be extended…?
Our Business alone has close to 1000 monday.com modules within our scenarios and given that there are still issues with the Module Migrator and the fact it was released for us to use only 14 days before the Deadline. Surely this should be extended.
More importantly if we blindly use the Migrator Tool and expect it to have upgraded the modules properly we will encounter the issues noted on other threads where the Automations are silently failing and not updating or clearing column values properly. We are dependent on these changes being through to ensure that the items which are linked to accounting are carried forward to onsite production and invoicing stages etc.
I appreciate Make.com’s efforts to develop the Migrator Tool, But it needs more work and we need more time to apply the changes once it is fixed.
Hello, i cant find any Migration module in Make. So please tell me were am i supposed to find it ?
Also, in the first emails received, it was clear that we will not be forced to migrate to V2, so i dont understand now we have to do. What will append tomorrow, because havent time to do that manually.
I just dont understand we have to do that, in 2026, it is just mind-boggling. And even if i find the migration tool, as mentioned, it seem to not work. I dont know if you understand the quantity of job needed to migrate all modules from V1 to V2.
Thanks to give me an answer, as i get an appointment to your Make support team by Google Meet, but your support never come on (nice for the time spent to wait). Sorry but that i see here is a poor support, for an app i pay a lot for, and some communications issues.
Yeah i already quickly saw that, but that have nothing to do like explained above and in the email received. What is explain above and in the email :
Open the app: Access the Module Migrator in Make. => There is not this in Make, no Module Migrator menu or section
Scan: Select the folders you want to scan, the tool will identify all scenarios with V1 modules => There is not that.
Choose your path: Update your scenarios in place or recreate them in a new folder (recommended for testing) => There is not that.
Confirm: Review any items requiring manual adjustment and complete the migration => there is not that.
So that is confusing. In one way we have one information, and when we search we find another…
I will try to understand your link below. I just hope that as we are the first may all my module work again.
I’m experiencing the same issues still and am finding it difficult to keep track of the automation runs which are not clearing columns as I have multiple automations in our quote to invoicing lifecycle that validate using an empty column as a condition. Very scary considering in our 200 active scenarios there is over 1300 Mondays.com modules that still require updating to v2. I need this sorted out properly and fast!!! Is there going to be any compensation for this poorly executed forced upgrade?
Even an error or warning from make to ensure that modules don’t fail silently would be a start. Meaning that we could pause the module and properly fix it before it gets beyond our control, especially in cases we’re a blank column value is depended upon as conditions of downstream automation triggers.
Introducing the Module Migrator
