Pipedrive API V1 to V2 Migration in Make.com: A Practical Checklist

Migrate Pipedrive scenarios from API v1 to v2 in Make.com without breaking automations. Use this step-by-step checklist to test modules, fields, and edge cases.

Automation Basics Workflow Automation

Mar 9, 2026

Pipedrive API V1 to V2 Migration in Make.com: A Practical Checklist

TABLE OF CONTENTS

Why this migration matters

Migration checklist (Make.com)

1) Inventory what you have

2) Create a test plan

3) Migrate scenario by scenario

4) Watch for common breaking points

5) Validate end-to-end outcomes

6) Cutover safely

When to use an “automated migration tool”

If you have Make.com scenarios using Pipedrive’s older API modules, you need a repeatable way to migrate without breaking production automations. The safest approach is to inventory scenarios, migrate in a test workspace, and validate edge cases like Activities, custom fields, and silent failures before you cut over.

Why this migration matters

Pipedrive’s API is moving from v1 to v2, and Make scenarios built on older modules can eventually stop working or lose coverage as endpoints change. As of Make’s January 2026 update, affected v1-based scenarios are expected to remain functional until July 31, 2026. After that date, those v1 endpoints are expected to no longer be available.

Migration checklist (Make.com)

1) Inventory what you have

List every scenario that uses Pipedrive modules.

Identify which ones touch Activities, webhooks, and custom fields.

Flag scenarios with high business impact.

2) Create a test plan

Pick 3 to 10 representative scenarios.

Test with:

a simple deal flow
an activity creation flow
a webhook-triggered flow
a scenario that uses multiple Pipedrive modules

3) Migrate scenario by scenario

Duplicate the scenario first.

Replace v1 modules with v2 equivalents (or HTTP calls if needed).

Keep a notes log of every module swap and field mapping.

4) Watch for common breaking points

Activities can be tricky during migration. Validate due date and due time handling, and confirm fields map as expected.

Confirm field keys.

Validate option IDs are correct.

Confirm updates do not silently drop values.

Some v2 endpoints use different pagination patterns. If you are listing large datasets, confirm you are not missing records.

5) Validate end-to-end outcomes

Verify the scenario output in Pipedrive.

Verify downstream writes (Notion, Airtable, Slack, email, etc.).

Verify error handling.

6) Cutover safely

Pause the old scenario.

Enable the migrated scenario.

Monitor logs closely for the first 24 to 72 hours.

When to use an “automated migration tool”

If you have many scenarios and complex blueprints, a migration tool that converts blueprints in bulk can save time. One option discussed recently is Innovaty. Still, you must test edge cases and confirm the converted blueprint behaves the same.

📅

Need help migrating complex Pipedrive + Make scenarios without production downtime? Book a discovery call.

Notion Page-Level Access: How to Lock Down Client Portals Without Exposing Your Database