How to Migrate Make.com Scenarios from Pipedrive V1 to V2

What's Happening?

Pipedrive is deprecating its V1 API in favor of the newer, faster V2 API. If you're using Make.com (formerly Integromat) to automate your Pipedrive CRM workflows, this directly affects you. Every scenario that uses a Pipedrive module — whether it creates deals, updates contacts, or triggers on new activities — needs to be updated.

The challenge? Pipedrive V2 isn't just a version bump. It's a fundamentally different API architecture with breaking changes across the board:

• New module IDs — every Pipedrive action in Make.com has a different internal identifier in V2
• Different field formats — custom fields use new hash keys and different data structures
• Restructured webhooks — native triggers have a completely different payload format
• Changed API endpoints — URLs, request formats, and response schemas are all different
• New metadata structure — entity field definitions are organized differently

The Problem: Manual Migration is Painful

Make.com does not offer a built-in upgrade path. There's no "convert to V2" button. The official recommendation from both Make and Pipedrive is to manually rebuild each scenario — delete the old V1 modules, add new V2 modules, reconfigure every field mapping, and re-wire every connection.

For a single scenario with 5 modules, this might take 30–60 minutes of careful work. But most real-world Make.com accounts have dozens of scenarios, each with complex logic, filters, routers, and custom field mappings. The manual approach means:

• Weeks of tedious work for agencies with multiple client accounts
• High risk of human error — one wrong field mapping can corrupt your CRM data
• Lost formulas and logic — Make.com expressions referencing V1 field names break silently
• Downtime risk — rebuilding live scenarios means potential gaps in automation

The Solution: Automatic Migration

Innovaty's Pipedrive Migration Engine solves this problem completely. It's the only tool that automatically converts Make.com scenario blueprints from Pipedrive V1 to V2 — no manual module-by-module rebuilding required.

How It Works

What Gets Migrated Automatically

Our engine handles every aspect of the V1 → V2 transition:

• Module upgrades — all Pipedrive V1 modules are replaced with their V2 equivalents (Deals, Persons, Organizations, Activities, Products, Notes, Leads, Projects)
• Custom field remapping — hash keys, select options, and object references are translated to V2 format
• Webhook migration — native triggers are converted to V2's new webhook architecture with correct payload structure
• Connection rewiring — all module connections are updated to use V2 connection types
• HTTP endpoint migration — raw HTTP calls to Pipedrive V1 endpoints are updated to V2 URLs and formats
• Formula preservation — Make.com expressions, dynamic variables, and nested data structures are preserved
• Integrity validation — the migrated blueprint is validated against Make.com's strict format requirements before export

Step-by-Step Migration Guide

Step 1: Identify Your V1 Scenarios

In your Make.com dashboard, look for scenarios containing Pipedrive modules. V1 modules are labeled as "Pipedrive" (without a version suffix) in the module selector. If you see modules like "Create a Deal", "Update a Person", or "Watch Deals" under the Pipedrive app — those are V1 and need migration.

Step 2: Export the Blueprint

Open the scenario in Make.com's editor, click the three-dot menu (⋯) at the bottom, and select "Export Blueprint". This downloads a JSON file containing your entire scenario configuration.

Step 3: Upload to Innovaty

Go to innovaty.co/get-started and upload your blueprint file. The engine will analyze it, identify all Pipedrive V1 modules, and show you a summary of what will be migrated.

Step 4: Review and Download

Review the migration summary — it shows module-by-module changes, any warnings, and the overall migration status. Download the migrated V2 blueprint.

Step 5: Import into Make.com

In Make.com, create a new scenario and use "Import Blueprint" to load the V2 file. Connect your Pipedrive V2 connection, verify the field mappings, and activate the scenario.

Step 6: Test and Switch Over

Run the new V2 scenario alongside your V1 version to verify everything works correctly. Once confirmed, deactivate the old V1 scenario.

Getting started is free — every account includes 3 free scenario migrations, no credit card required. Need more? View our pricing plans.

Don't Wait Until the Last Minute

The July 2026 deadline may seem far away, but agencies managing multiple client accounts need time to plan, test, and roll out migrations. Starting early means:

• You can test V2 scenarios alongside V1 before cutting over
• Any edge cases can be handled with time to spare
• Your clients experience zero disruption