On July 31, 2026, Pipedrive retires a set of widely-used API v1 endpoints - the ones behind most Make scenarios and Zapier zaps. Updating the automations involves a lot of manual work - and failing to do so, or making one mistake along the way, will result in broken automations.
Our tool automates 90% of the migration, including the messy multi-call rewrites, so your automations keep running without interruption.
Want to see how easy it is? Join our live demo!

The deprecation
Pipedrive is not retiring all of API v1 - just the endpoints that now have direct v2 replacements: Deals, Persons, Organizations, Activities, Products, Pipelines, Stages and itemSearch. Those happen to be the endpoints behind the vast majority of Make scenarios and Zapier zaps in production today.
Pipedrive is deprecating the v1 endpoints for Deals, Persons, Organizations, Activities, Products, Pipelines, Stages and Search after July 31, 2026. The rest of v1 stays - but those are the ones almost every automation uses.
Rewriting modules, remapping fields, retesting paths and filters. A typical agency or ops team has 50–500 scenarios and zaps to update.
Make and Zapier don't auto-upgrade Pipedrive modules. Every scenario and zap is a manual project - and a chance to introduce silent bugs.
Not all migrations are equal
About half of the work is mechanical - swap one v1 module for its v2 equivalent. The other half is where teams burn time: a single v1 call has to be split into several v2 calls, with reshaped payloads, renamed fields, and new pagination. That's exactly where the tool earns its keep.
A direct one-to-one replacement. Endpoint swap, light parameter rename, you're done. Annoying at scale, but each one only takes a few minutes - if you remember every spot to touch.
A single v1 call has to be split into multiple v2 calls, with reshaped data structures and renamed fields. Done by hand, each scenario like this is hours of careful work - and the easiest place to introduce a silent bug. The tool handles these end-to-end.
The tool
Innovaty's migration tool takes a Make scenario or Zapier zap built on Pipedrive v1 and produces a v2-equivalent - including the complex cases where a single v1 call has to become several v2 calls. Used as designed, the cutover happens with no downtime on either Zapier or Make, so the business keeps running.
Agenda
Speakers

Automation veteran and Pipedrive Elite Partner who has architected hundreds of Make and Zapier builds. Leads the migration tool's product direction.

15 years in business automation, hundreds of client projects shipped. Built the engine that powers the Pipedrive v2 migrations.
Register
Reserve your spot for the live session. You'll leave knowing exactly what changes in v2, how to handle the complex multi-call migrations, and how to cut over with zero downtime.
FAQ
No. Pipedrive is deprecating a specific set of v1 endpoints that now have direct v2 replacements - Deals, Persons, Organizations, Activities, Products, Pipelines, Stages and itemSearch. They remain available until July 31, 2026; after that, availability and functionality are no longer guaranteed.
Not when the tool is used as designed. The cutover is built so your existing v1-based automations keep running until the v2 versions are tested and switched on - zero downtime on either Zapier or Make.
Yes - that's the main reason it exists. When a single v1 call has to be split into several v2 calls with reshaped payloads and renamed fields, the tool produces the new flow automatically.
Yes. We support Make scenarios and Zapier zaps, including custom fields, filters, paths, and multi-step flows.
The tool flags anything it can't auto-rewrite and tells you exactly what needs manual attention - typically under 10% of the work.
Yes - register and we'll email you the recording even if you can't make it live.