# Migrating from Pipedrive: what transfers and in what order

https://krokul.com/en/blog/migrate-from-pipedrive/ · Krokul Team · Updated 2026-11-03

Krokul CRM is a B2B CRM for contract-based companies: deals, projects and profit per client in one system, implemented by integration partners. This guide lists what the Pipedrive connector moves into Krokul, the order of the steps and what stays behind.

**Short answer.** To migrate from Pipedrive to Krokul, connect a personal Pipedrive API token, map pipelines, stages and users, run a dry run that writes nothing, then import. Krokul reads organizations, persons, products, deals and activities, writes them in a fixed order and keeps every Pipedrive ID. A rollback removes what a run created.

## What transfers when you migrate from Pipedrive to Krokul

Migrating from Pipedrive moves five kinds of records and keeps the links between them. The method behind the order is described in the guide on [how to switch CRM without losing data](https://krokul.com/en/blog/topics/switching-crm/), and this page applies it to Pipedrive.

The Pipedrive connector reads through API version 2 and turns every Pipedrive object into a Krokul record. The table shows what each object becomes and which of its fields arrive.

Pipedrive objects and the Krokul records they become:

| Pipedrive | Becomes in Krokul | What arrives |
|---|---|---|
| Organizations | Client companies | The name and the address. The address is written into the notes as text, and every other simple field is kept in the record’s custom data. |
| Persons | Contacts | The name, every phone number, every email, the notes and the link to the organization. |
| Products | Products | The name, description, code as SKU, unit, the first price of the price list, the cost as purchase price and the currency of that price. |
| Deals | Deals | The title, the value as the expected amount, the currency, the expected close date, the pipeline and stage, and the links to the person and the organization. The state open, won or lost goes into custom data. |
| Activities (calls, meetings, tasks) | Tasks | The subject as the title, the type, the done flag and the note in the description, the due date and time, and the links to the deal and the person. |
| Pipelines, stages and users | Reference data | Read together with the records, then matched to your Krokul pipelines, stages and users by mapping rules. |
| Email correspondence and call logs | Not transferred | Export them from Pipedrive and keep the archive. Planned calls and meetings arrive as tasks. |

Sources and tags of Pipedrive records are not read either. Whatever else sits in a Pipedrive account, such as files, stays in Pipedrive.

## In what order does a Pipedrive migration run

A Pipedrive migration runs in six steps, and Krokul writes the records in a fixed order: client companies, contacts, products, deals and then tasks, so every deal finds its company and contact already in place. The general list of checks is in the [CRM migration checklist](https://krokul.com/en/blog/crm-migration-checklist/).

### 1. Count and clean the records in Pipedrive

Write down how many organizations, persons, products, open and closed deals and activities you have, and note the currency of each product and deal. These numbers are the totals you compare with at the end.

Merge the obvious duplicate organizations and persons first. A duplicate in Pipedrive arrives as a second record or as a skipped row in Krokul.

### 2. Prepare users, pipeline and stages in Krokul

Invite the people who own Pipedrive records, because the import never creates users, and a deal whose owner is not matched keeps no Pipedrive owner, so the usual Krokul rules pick its responsible person: the manager of the client company or contact, or the pipeline pool. Prepare the pipeline and its stages, so each Pipedrive stage has a Krokul stage to land in.

A deal whose stage is not matched lands in the first stage of its pipeline.

### 3. Connect Pipedrive with a personal API token

Open the Migration screen as an administrator, choose Pipedrive as the source and paste your personal API token, which you find in Pipedrive under Personal preferences, API. Then click Check connection.

The server reads the token, and the screen does not show it again after the check. The connector only sends read requests, so nothing changes in your Pipedrive account.

> **Tip.** The API base field can stay empty. It defaults to the Pipedrive cloud address.

![Migration wizard, Source step with Pipedrive chosen: the API token field, a hint on where to get the key and Check connection](https://krokul.com/img/en/blog/migrate-from-pipedrive-token.webp)

### 4. Match pipelines, stages and users

Pipedrive stages become Krokul stages by mapping rules, and Pipedrive users become Krokul users by rules as well. The Migration screen has no step for these rules today, so they are written to the run through the migration API, by an implementation partner or by an administrator who works with the API.

With no pipeline rule at all and no default pipeline set, a deal has nowhere to go and is reported as a failed row with that reason. When at least one pipeline is matched, a deal whose own pipeline is not matched lands in the first matched pipeline, and a deal whose stage is not matched lands in the first stage of its pipeline.

### 5. Run a dry run and read the report

Start the dry run from the Check step. It takes the token from the connection check on the server, reads the whole Pipedrive account at 80 requests per minute, applies the rules and writes nothing in Krokul.

Compare its totals with the counts from step 1 and repeat the dry run after every change to the rules, until each failing row has a reason you accept and the skipped count is the one you expect.

### 6. Run the import and check the summary

Start the real run. It works on the server in the fixed order, so you can pause and resume it, or close the page and come back to the summary. The summary lists created, updated and failed rows, and each failed row comes with its reason.

Compare the totals with step 1, open twenty records chosen at random and compare every field with Pipedrive. Keep Pipedrive readable until that check passes.

## What does a dry run of a Pipedrive migration show

A dry run of a Pipedrive migration shows, for each kind of record, how many Krokul records the real run would create, update and skip, and lists the rows that would fail, with the reason. The connection check alone cannot do this, because Pipedrive API v2 returns no totals, so the connection check only proves that records exist.

Example: a dry run report for a Pipedrive account:

| Records | Would be created | Would be updated | Would be skipped |
|---|---|---|---|
| Client companies | 420 | 0 | 15 |
| Contacts | 1,310 | 0 | 90 |
| Products | 85 | 0 | 0 |
| Deals | 640 | 0 | 0 |
| Tasks | 2,210 | 0 | 0 |

In the example nothing would be updated, because no earlier run exists. The 15 organizations and 90 contacts that would be skipped are duplicates of records already in the workspace, and the report only counts them, so check them in Pipedrive before the real run. Rows that would fail are listed with their reasons. The dry run does not run the validation of the write, so the real run can still fail on rows it let through.

## How to roll back a Pipedrive import that landed wrong

A rollback of a Pipedrive import removes the records that this import created and leaves everything else alone. It applies to one run at a time and is available only for a real run.

- Records the run created are removed, with the last kind of record going first.
- Records the run only updated keep their new values, so correct them by hand if needed.
- Records that someone changed after the import stay in place.
- A dry run created nothing, so there is nothing to roll back.

Krokul keeps the Pipedrive ID of every record it writes, so a second run updates the records that already moved and creates no duplicates. This lets you bring over late changes from Pipedrive with a repeated run.

## What stays behind or needs a decision when you leave Pipedrive

> The Pipedrive connector was written from the Pipedrive documentation and tested on simulated responses. It has not been run against a live Pipedrive account yet, so the dry run on your own data is the first real test, and a transfer without it should not start.

- Email correspondence and call logs are not transferred. Export them from Pipedrive first. Planned calls and meetings arrive as tasks.
- Pipedrive keeps the state of a deal apart from its stage. Krokul puts the deal into the matched stage and writes the state into the deal’s custom data under pipedriveStatus, so match the final stages deliberately.
- A product or a deal without a currency in Pipedrive is written with the currency UAH. Check the currencies in step 1.
- An activity with a date and no time becomes an all-day task. An activity with a time keeps its time.
- Activities are assigned only to users that you matched in step 4, and a task without a matched user has no assignee, unless a default assignee is set through the API.

## Who should run the move: your team or an implementation partner

A company with a short list of organizations and a few users can connect Pipedrive, run the dry run and read the report on its own. A business with a running pipeline, several users and years of deals gets the pipeline, stage and user rules, the reading of the dry run and the final check from an implementation partner, who also trains the team.

The page on [moving Pipedrive data into Krokul](https://krokul.com/en/solutions/migration/) lists the sources it reads, what it moves and what it leaves behind, and [Krokul compared with Pipedrive](https://krokul.com/en/compare/pipedrive/) puts the two systems side by side. Another source follows the same steps, for example [migrating from HubSpot](https://krokul.com/en/blog/migrate-from-hubspot/).

## Which mistakes cost the most when you migrate from Pipedrive

- Starting the import before the pipeline rules exist. Every deal then fails with the same reason, so write the pipeline and stage rules first and repeat the dry run.
- Skipping the dry run. The same mapping error repeats on every record, and only a dry run shows it before anything is written.
- Closing Pipedrive on the import day. Email correspondence and call logs cannot be exported later, so keep the account readable for a working week and export them first.
- Leaving users unmatched. Deals then get the responsible person from the usual Krokul rules instead of the Pipedrive owner, so invite the users and match them before the run.

## Frequently asked questions

### How long does a Pipedrive migration take?

The connector reads Pipedrive at 80 requests per minute, so a large account takes longer, and no timing has been measured on a live Pipedrive account, so there is no estimate here. Run the dry run first, because it reads the whole account without writing.

### Does Pipedrive change during the migration?

No, the connector only sends read requests to Pipedrive. Your Pipedrive data stays as it is, which is why you can keep the account open until the check passes.

### Are emails and calls moved?

Email correspondence and call logs are not moved. Planned calls and meetings arrive as tasks, because Pipedrive activities become Krokul tasks. Export the correspondence and the call logs from Pipedrive and keep the archive.

### What happens to duplicates?

By default the import skips a record that duplicates one already in the workspace, and the report counts the skipped rows. Records created by hand with the same phone, email or name stay unchanged.

### Who can run a migration in Krokul?

Only an administrator runs a migration. The token you paste is read by the server and is not shown again after the connection check.

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs
