Scenario Builder: make the upgrade of modules easier
complete
Michael White
Now that there are upgrades to the Facebook modules, there should be an easy way to upgrade the modules that we are already using without having to delete and recreate them. I should be able to do this one module at a time so that I can test to make sure things are still working well.
Joscha Götzer: If you wanna go fancy, how about trying to guess the new field names in case of a V2, and showing some validation procedure output that tells the user what he has to fix by hand? :)
-----------------------------------
REPLY: Here is a step-by-step guide How to replace legacy modules with new modules in a scenario:
Your comments/experience/suggestions/etc. are very welcome.
Log In
Tereza Klobouckova
marked this post as
complete
Dear Makers,
We’re pleased to announce the release of the Module Migrator app, which helps migrate deprecated modules. Pipedrive is coming next, and more apps will follow on a rolling basis as new deprecations are announced.
Give it a try and let us know what you think. We’d love to hear your feedback on the new experience.
Resources:
📚 Get started with our technical guide: https://apps.make.com/module-migrator
📝 Read the full release notes: https://help.make.com/introducing-module-migrator
Happy Automating!
Tereza
The Make Team
Fab Rossini
Tereza Klobouckova thanks for the update! I’ve been testing the new Module Migrator and found a few critical issues. After running it, some 'Get Item' modules ended up with empty variables, and in my 'Update Item' modules, the column mappings were corrupted—resetting all fields to the same value.
Most concerningly, the migrator didn't flag these as errors, so the scenario appeared fine even though the data flow was broken. I’ve reached out to support, but wanted to mention it here for visibility!
Tereza Klobouckova
Fab Rossini: Thank you for your reply. The issues described above should already be fixed. If not, please reach out to our support.
Tereza Klobouckova
Merged in a post:
Automatic Migration Tool for app updates
Olushola A.
There is a dire need for a way/tool to migrate applications from one version to another instead of having to manually edit each scenario, change the modules and re-do the mappings each time there is an app update. The most recent example is the "Pipedrive" migration to v2.
Jonathan Evatt
It’s extremely disappointing—and materially costly for customers—that after four years, Make still does not provide a true upgrade path for modules when new versions are released.
With the release of v2 of the Monday app, my client is now facing thousands of dollars in redevelopment costs to rebuild multiple production scenarios. This is not due to any meaningful change in business logic, but purely because of how Make handles “upgrades.”
Make’s proposed upgrade path is not an upgrade in any practical sense. The existing modules are not upgraded in place—they are replaced with entirely new modules with different IDs. As a result, all downstream references break, and the scenario effectively has to be rebuilt.
This is not an upgrade path—it is a forced rebuild.
For scenarios with multiple interconnected Monday modules, the impact is significant. The time and cost required to “upgrade” can approach—or even exceed—the cost of the original build.
More importantly, this behaviour is architecturally unsustainable. By not preserving module identity, Make turns what should be a controlled, localised update into a full graph rewrite. This is not just inconvenient—it actively discourages long-term maintenance and scalability on the platform.
A viable upgrade path does not need to be fully automatic. Developers understand that schema changes may require manual review and adjustment. However, the platform should preserve module identity and connections, allowing updates to be applied in place with targeted fixes where necessary.
Until this is addressed, upgrading core apps will continue to impose disproportionate cost and risk on customers using Make for anything beyond trivial scenarios.
Samuele
I'd suggest redirecting to a more trending duplicate request: https://www.make.com/en/platform-ideas/p/scenario-builder-make-the-upgrade-of-modules-easier
Reynald Viva
I'm connected to several accounts more than 40 scenarios and 100+ modules need to update. (monday) This would be the best way to migrate from old to v2
Christian Lee
This method of replacing modules is almost slower than completely rebuilding the scenarios. This is such an easy to feature to release when modules introduce breaking changes. I cannot believe a better solution doesnt exist.
Julian Lindner
We absolutely need an easier way to upgrade module versions in large, complex scenarios. The current approach is mind-bogglingly manual and time consuming.
Samuel Tingel
Hi, I just wish to support your idea of replacing the versions of the modules. I encounter this now with Monday.com modules and I really hope there can be a more simple, more convenient way to replace all of them by one click - not one by one in hundreds of cases.
Autopilot
Merged in a post:
Being able to update outdated modules without needing to manually recreate the whole flow
Nandan Muthukumar
Kevin Smith
The problem is, the dev tool (F12) only copies mappings frmo old mod to new mod, it SHOULD also update all references to old mod with new mod.
its easy to code...
SrcMod = modules[source)
TarMod = modules[target)
FOREACH module IN module
IF module <> SrcMod THEN
FOREACH mapping IN module.mappings
FOREACH SrcMapping in SrcMod
IF mapping.item = SrcMod.item THEN mapping.item = TarMod.item
NEXT SrcMapping
NEXT mapping
ENDIF
NEXT module
Load More
→