What Happens to Your Automations If You Switch Project Management Tools?

Your automations don't move with you. If you switch project management tools — say from Asana or Monday.com to ClickUp, or the other way round — any Zaps, automations or integrations built around the old tool will break, because they're wired to that specific app's triggers, fields and record IDs, not to "project management" in the abstract. Nothing transfers automatically. Every automation has to be rebuilt, one by one, in the new platform. That's the honest answer before anything else in this post.

I'm Jack Lenton, a ClickUp Verified Consultant and Zapier Silver Solutions Partner at Toki, based in Norwich. I've moved businesses between project management tools more than once, and the automation side is almost always the part people underestimate. Here's what actually breaks, what doesn't, and how to migrate without losing weeks of work.

Do Zapier automations move with you when you switch tools?

No. A Zap is built around a specific app's triggers and actions — "new task created in Asana," for example — and those triggers don't exist in a different platform. Even where the concept is identical (a new task, a status change, a due date), the underlying app connection has to be swapped out and reconfigured, field by field, in every affected Zap.

What exactly breaks?

• Every Zap that triggers from, or acts on, the old tool — the app connection itself stops working the moment you stop using that tool
• Custom field mappings, since field names and IDs are rarely identical between platforms
• Any links pointing to old task or project URLs, embedded in emails, docs or other tools
• Notification routing built around the old tool's structure
• Reporting or dashboards built on top of the old tool's data

What doesn't need to be rebuilt?

Anything that doesn't touch the project management tool at all. An automation that sends an invoice from a form submission to Xero, for instance, is unaffected by a PM tool switch, because neither app in that chain has changed. It's specifically the automations with one foot in the old tool that need attention.

How do you migrate automations safely?

Treat it as a proper project, not a weekend task. Start by auditing every existing Zap or automation connected to the old tool — most businesses find at least a few nobody remembers building. Prioritise by business impact, rebuild the highest-priority automations first in the new platform, and run old and new in parallel for a verification window before switching over fully. Only decommission the old automations once you've confirmed the replacements are working as expected, and document the new setup as you go so it doesn't become undocumented on day one.

Should you migrate everything, or rebuild from scratch?

A migration is usually the best moment to cut dead weight rather than replicate it. Most audits turn up automations that were built for a process that no longer exists, or that duplicate something the new tool does natively. Rebuilding only what still earns its place tends to leave you with a cleaner system than the one you started with.

How Toki approaches a project management tool switch

The process is consistent: a discovery conversation to understand what's actually running today, a full audit of existing automations before touching anything, a prioritised rebuild in the new tool, a parallel-run verification period, and a plain-English handover document once everything's confirmed working.

Frequently asked questions

Do my Zapier automations transfer automatically when I switch project management tools?
No. Automations are built around a specific app's triggers and fields, so switching tools means every affected automation has to be manually rebuilt in the new platform.

How long does it take to migrate automations to a new tool?
It depends on how many automations you're running and how complex they are, but a structured migration — audit, rebuild, parallel run, cutover — typically takes a few weeks rather than days.

Should I rebuild every automation exactly as it was?
Not necessarily. A migration is a good opportunity to audit what's actually still needed and cut anything built for a process that's since changed or disappeared.

Almost done! When you're ready, here are four ways I can help you:

1. Read it. A guide on how to use ClickUp and actually make it work for you.
2. Connect it. Let's be LinkedIn pals. I make funny videos sometimes.
3. Workshop it. Book a 30-minute chat to talk processes and build a Miro together.
4. Go for it. Fill in my contact form — let's talk ClickUp or Automations. Whatever tickles your pickle.

Wanna hear from the unfiltered version of me? Sign up to my newsletter. The Working Notes. 2 minute reads. Behind the scenes. Hopefully helpful. Maybe funny.