Make.com has rolled out the Module Migrator, a tool that detects deprecated modules in your existing scenarios, identifies available upgrades, and provides warnings and manual fix instructions for cases that can't be migrated automatically. The feature was announced in Make's April 15 release notes and is now available across all workspaces.
This addresses a long-standing pain point. Anyone maintaining Make.com scenarios for more than a year knows the feeling: a scenario you built in 2024 starts failing in 2026 because the underlying app module was deprecated. You then spend hours figuring out which modules need replacing and how to wire the new ones to behave like the old ones.
The Module Migrator automates the detection and provides guidance for the fix.
What it actually does
The tool runs across your workspace and produces a report with three categories of findings:
Auto-upgradeable modules. Make.com can replace the deprecated module with a new equivalent automatically. You review the proposed change, approve it, and the migration runs in place. Most common for minor version updates or rebrand changes.
Warning-level changes. The new module exists and is mostly compatible, but some inputs/outputs have changed in ways that need manual review. The tool flags these scenarios so you don't accidentally break them with an automatic upgrade.
Manual-fix required. The deprecated module has no automatic replacement — the new module has different behavior or different inputs. The tool provides specific instructions for manual remediation.
How to use it (step-by-step)
- Access the Module Migrator from your Make.com workspace settings (look for "Tools" or "Maintenance" section depending on your plan)
- Run the scan — takes 1-5 minutes depending on workspace size
- Review the report, sorted by severity
- For auto-upgradeable: review the diff, approve in bulk or one at a time
- For warnings: open each scenario, review the changes, approve or schedule a manual fix
- For manual fixes: follow the provided instructions, test in a sandbox first
Suggested workflow: run the scan monthly as part of your operational hygiene. Doesn't take long if you stay on top of it. Run it before any major changes or new builds to clean up technical debt first.
Why deprecated modules even exist
Make.com's app ecosystem is huge — 3,000+ apps with hundreds of modules each. As underlying SaaS APIs evolve (new endpoints, deprecated fields, breaking changes), Make.com has to keep up. This creates a constant background churn:
- An app vendor updates their API → Make.com ships a new module version → old version gets a deprecation warning
- App vendor sunsets a feature → Make.com module loses functionality → old scenarios break
- App vendor renames itself or gets acquired → Module name changes → scenarios pointing at the old name break
- Make.com finds a better implementation pattern → ships new module → old one deprecated
Before the Module Migrator, you only discovered these issues when a scenario started failing — usually at the worst possible time.
Real-world impact
From a client workspace we audited last week (about 35 production scenarios, oldest scenarios from 2024):
- 4 scenarios used auto-upgradeable modules — fixed in 10 minutes
- 7 scenarios had warning-level changes — most were Slack and Google Sheets modules that needed minor input remapping
- 2 scenarios required manual fixes — both were custom HTTP modules with hardcoded endpoints that changed in the third-party API
Total cleanup time: about 90 minutes. Without the tool, the same audit using the UI alone took us 4-5 hours when we did it manually last year.
Who needs this most
The Module Migrator is most valuable for:
Workspaces with scenarios over 12 months old. The older the scenarios, the more likely modules have drifted. Annual workspace audits become much cheaper.
Agencies and Solution Partners. When you take over a client's existing Make.com setup, running the Migrator first gives you a clear inventory of what needs updating before you build anything new on top. We're adding this as a standard first step in our audit engagements.
Teams that experienced silent failures recently. If you've had unexplained "this scenario worked last week but is broken today" incidents, deprecated modules are a likely culprit. Running the Migrator answers whether that's the issue.
What it doesn't fix
Setting expectations: the Migrator detects and helps fix module-level deprecations. It doesn't:
- Catch logic errors in your scenarios (filters that exclude the wrong records, etc.)
- Optimize operations consumption (you still need an audit for that)
- Update third-party app connections (if your OAuth tokens are expired, that's separate)
- Fix scenarios that broke for non-module reasons (rate limits, data structure changes in source apps)
It's a hygiene tool, not a magic wand. Use it as part of broader workspace maintenance, not as a substitute for it.
Why this is a meaningful release
Two reasons this matters more than it sounds:
Operational maturity signal. Make.com is shipping tools that serve the boring-but-critical needs of running production automations long-term. This is enterprise iPaaS territory — Workato and similar tools have had migration tooling for years. Make.com catching up here removes one of the enterprise objections to the platform.
Long-term workspace health. Without this tool, Make.com workspaces accumulated invisible technical debt. Now teams can stay current without dedicated maintenance windows. Makes the platform more sustainable for long-running automations.
What to do this week
Two actions worth doing:
- Run the Module Migrator on your workspace once, even if you don't think you have issues. You'll likely be surprised.
- Add a recurring calendar reminder to re-run it monthly. 15 minutes per month prevents 4 hours of emergency debugging later.
If the report flags more than 10 scenarios needing attention and you don't have the time or expertise to address them, this is exactly the situation our troubleshooting service handles.
Full documentation in the Make.com Help Center.