How to Migrate Zapier Zaps from Pipedrive V1 to V2 — Complete Guide

Why You Need to Migrate

Pipedrive is retiring its V1 API on July 31, 2026. After that date, every Zapier Zap using Pipedrive V1 actions will stop working. This affects all Pipedrive-related triggers and actions that were created before the V2 integration was released.

The good news: the migration can be automated. You don't need to manually reconfigure each Pipedrive action step by step.

schedule

Deadline: July 31, 2026

All Zapier Zaps using Pipedrive V1 actions will stop working after this date. Start migrating now to allow time for testing.

swap_horiz

Using Make.com instead of Zapier?

We have a dedicated migration tool for Make.com scenarios with full custom field remapping, webhook migration, and formula preservation.

Read the Make.com Migration Guide arrow_forward

What Changes in Pipedrive V2

The V2 API brings several breaking changes that affect how Zapier Zaps interact with Pipedrive:

1. Action Names Are Different

Every Pipedrive action in Zapier has an internal action identifier. V2 uses completely different action names. For example, create_deal in V1 becomes a different identifier in V2. Our migration engine handles all these mappings automatically.

2. API Version Bumps

Each Pipedrive step in Zapier references a specific API version string. V1 Zaps reference the old Pipedrive app version — V2 requires the latest version identifier. The migration tool updates this for every Pipedrive node.

3. Trigger Fields Have Changed

V1 triggers return "flattened" data — for example, a new deal trigger returns person_name directly. V2 triggers only return person_id, requiring an additional API lookup to get the name.

Our migration engine handles this by injecting bridge nodes — automatic lookup steps that resolve IDs back into names, ensuring downstream steps continue working.

Two Migration Methods

Method 1: File Upload (Bulk Migration)

Best for: migrating multiple Zaps at once, non-webhook triggers.

In Zapier, go to Settings → Data Management → Download my Zaps
Upload the .json export to innovaty.co/zapier
Click Analyze — the tool scans for Pipedrive V1 actions
Select which Zaps to migrate (or all of them)
Click Migrate — download the V2 version
In Zapier, use Settings → Data Management → Upload Zaps to import the migrated file
Test each Zap with sample data before enabling

warning

Webhook Zaps Lose Their URL on Export

If your Zap uses a Webhook trigger, exporting and re-importing gives it a new webhook URL. External systems will need to be updated. For webhook Zaps, use the Chrome Extension method instead.

Method 2: Chrome Extension (In-Place Migration)

Best for: webhook-triggered Zaps, Zaps you want to migrate without disruption.

Install the Innovaty Zapier Migration Chrome Extension
Enter your Innovaty API token in the extension settings
Open any Zap in the Zapier editor
Click the extension icon → Migrate This Zap
The extension patches Pipedrive actions in-place — your webhook URL stays the same
Test the Zap before re-enabling

Post-Migration Checklist

After migrating, verify these items:

Re-authenticate Pipedrive — V2 may require re-linking your Pipedrive account in each Zap. The Chrome Extension does this automatically when possible.
Test with sample data — run each Zap manually before enabling. Check that all fields map correctly.
Custom fields — V2 uses different field IDs for custom Pipedrive fields. If you reference custom fields by name, they should still work. If by ID, verify them.
Filters and Paths — if your Zap has filter conditions referencing Pipedrive field names, verify they still match V2 output.

How Many Zaps Can I Migrate for Free?

Every new account gets 3 free Zap migrations — no credit card required. After that, credit packs are available starting at $250. See our pricing page for details.

Getting Help

If you run into issues during migration, we can help. Book a free consultation and we'll walk you through the process. For agencies managing multiple client accounts, we offer bulk migration packages.