
Make Module Migrator: How to Migrate Your monday.com Scenarios to V2
TL;DR: „monday.com V1 modules in Make stop working May 1, 2026. The new Module Migrator scans your scenarios and automates the upgrade to V2 – use it now."
— Till FreitagThe Clock Is Ticking: V1 Ends May 1, 2026
monday.com is deprecating their V1 API – and with it, all V1 modules in Make.com. After May 1, 2026, scenarios still using legacy modules will stop working or return errors.
If you're running monday.com automations in Make, you need to act now. The good news: Make just launched a free tool that makes the transition painless.
What's Changing?
monday.com updated their API version, and Make released a new V2 app to support it. The transition involves:
- Module replacement – V1 modules need to be swapped for their V2 counterparts
- Field mapping changes – Some fields have been renamed or removed
- Timeline – Both versions run in parallel until May 1, then V1 is gone
Affected Field Changes
Not all modules require manual adjustments. But if you're using these, pay attention:
Discontinued Fields
Modules: List Boards, Get a Board
The following fields no longer exist in V2:
bordervar_namedone_colorscolor_mappinglabels_position_v2hide_footer
Action: Remove any mappings that reference these fields.
Renamed Timestamp
Modules: Get an Item, Get an Item's Column Value, List Board's Items, List Group's Items, Search Items, Watch Board's Items, and all related watch modules.
Change: changed_at is now updated_at.
Action: Remap all references from changed_at to updated_at.
The Module Migrator: Automated Migration
Instead of manually editing every scenario, Make's Module Migrator handles the heavy lifting:
How It Works
- Open the Module Migrator – Access it directly in Make at apps.make.com/module-migrator
- Scan your folders – Select which folders to scan; the tool identifies all scenarios with V1 modules
- Choose your migration path:
- In-place update – Upgrade modules directly in existing scenarios
- Clone to new folder – Recreate scenarios in a new folder (recommended for testing)
- Review warnings – The tool flags modules that need manual field remapping
- Confirm and migrate – The tool swaps all compatible modules automatically
What Gets Automated vs. Manual
| Automated | Requires Manual Work |
|---|---|
| Module swap from V1 → V2 | Discontinued field mappings |
| Connection re-linking | changed_at → updated_at remapping |
| Basic field mapping | Custom formulas referencing old fields |
Guided Troubleshooting
For scenarios that can't be fully automated, the Module Migrator returns a Warning bundle with step-by-step instructions on exactly what to adjust.
Best Practices for Migration
1. Audit Before You Migrate
Before running the migrator, document your critical scenarios. Know which ones touch monday.com and what they do.
2. Use the Clone Method First
Always clone to a new folder first. Test the migrated scenarios before replacing your production workflows.
3. Check for Downstream Dependencies
A renamed field (changed_at → updated_at) can break downstream modules – filters, routers, or connected apps that reference the old field name.
4. Test with Real Data
Don't just check that the scenario runs – verify that the output data is correct. Field removals can silently break logic without throwing errors.
5. Use Make DevTool for Bulk Updates
The Make DevTool has a "Swap Variable" function that lets you update mappings across multiple modules at once – much faster than editing each module individually.
Migration Checklist
| Step | Status |
|---|---|
| Identify all monday.com scenarios | ☐ |
| Document critical workflows | ☐ |
| Run Module Migrator scan | ☐ |
| Clone scenarios to test folder | ☐ |
| Review warning bundles | ☐ |
| Remap discontinued fields | ☐ |
Update changed_at → updated_at |
☐ |
| Test migrated scenarios | ☐ |
| Replace production scenarios | ☐ |
| Verify downstream integrations | ☐ |
Timeline
| Date | Event |
|---|---|
| Now | V1 and V2 both available; Module Migrator launched |
| May 1, 2026 | V1 support ends – scenarios may fail |
⚠️ Don't wait until the last week. Complex scenarios with many modules need time for testing.
Conclusion
The transition from V1 to V2 is mandatory – but Make's Module Migrator removes most of the pain. Scan, clone, review, and test. If you start now, the May 1 deadline is completely manageable.
For teams with complex monday.com automations that need expert support with the migration, get in touch with us – we've been through this process with dozens of clients.
Want to learn more about monday.com and Make? Read our Make automation guide, the guide on Error Handling & Retry Strategies, the Monitoring & Observability setup with Datadog & Better Stack and our Security & Secrets Management guide – or visit the monday.com tool page.
Make Mastery Series
Six articles that take you from first scenarios to production-grade, secure, and performant automations.
1. make.com Automation – The Ultimate Guide
Intro, comparison with Zapier & n8n, 5 use cases.
Read2. Error Handling & Retry Strategies
Resume, Rollback, Commit, Break – with interactive decision tree.
Read3. Monitoring & Observability
Native dashboards + Better Stack heartbeats + Datadog deep dive.
Read4. Module Migrator: monday.com V1 → V2
HereMandatory migration before May 1, 2026 – step-by-step guide.
5. Security & Secrets Management
Connections, webhooks, IP whitelisting & vault patterns for production setups.
Read6. Performance & Operations Optimization
Bundle size, filter order, aggregators & sub-scenarios – 40–70% fewer ops.
Read









