# Migrating from KeyCRM: what transfers and in what order

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

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 KeyCRM connector moves into Krokul, the order of the steps and what stays behind.

**Short answer.** To migrate from KeyCRM to Krokul, create a public API key in KeyCRM, connect it, match pipelines, statuses and managers, run a dry run that writes nothing, then import. Krokul reads companies, buyers, products and pipeline cards, writes them in a fixed order and keeps every KeyCRM ID. A rollback removes what a run created.

## What transfers when you migrate from KeyCRM to Krokul

Migrating from KeyCRM moves four 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 KeyCRM.

The KeyCRM connector reads through the public KeyCRM API and turns every record into a Krokul record. The table shows what each KeyCRM record becomes and which of its fields arrive.

KeyCRM records and the Krokul records they become:

| KeyCRM | Becomes in Krokul | What arrives |
|---|---|---|
| Companies | Client companies | The name, or the legal title when the name is empty, the legal title as a separate field, the notes and the responsible manager. The bank account is a free-text field in KeyCRM, so it is kept in the record’s custom data. |
| Buyers | Contacts | The full name, or the first phone or email when the name is empty, every phone and every email, the note, the birthday and the link to the company of the buyer. |
| Products | Products | The name, description, SKU, unit, category and purchase price. The price is the lowest price among the variants, the currency is the product’s currency code or UAH, and an archived product arrives inactive. |
| Pipeline cards | Deals | The title, the manager’s comment, the planned contact date, the total as the expected amount, the lines (name, SKU, quantity, price), the pipeline and status, the source, the responsible manager, the buyer as the deal contact and the tags. |
| Pipelines, statuses, sources and tags | Reference data | Read together with the records, then matched to your Krokul pipelines, stages, sources and tags by mapping rules. |
| Tasks | Not transferred | The public KeyCRM API has no resource for tasks. The planned contact date of a card travels with the deal, and separate tasks are not created. |
| Chats and call logs | Not transferred | They exist only in the internal API of KeyCRM. Export them from KeyCRM and keep the archive. |

## In what order does a KeyCRM migration run

A KeyCRM migration runs in six steps, and Krokul writes the records in a fixed order: client companies, contacts, products and then deals, so every link finds its target 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 KeyCRM

Write down how many companies, buyers, products and cards you have, and note the pipelines you use. These numbers are the totals you compare with at the end.

Merge the obvious duplicate buyers and companies first. By default the import skips a duplicate company, contact or product, and the dry run counts it.

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

Invite the people who manage KeyCRM cards, because the import never creates users. Prepare the pipeline and its stages, so each KeyCRM status has a Krokul stage to land in.

The statuses are matched in step 4 by rules, so prepare the stages before that step.

### 3. Create a public API key in KeyCRM and connect it

In KeyCRM open Settings, Public API and create a key. Open the Migration screen in Krokul as an administrator, choose KeyCRM as the source, paste the key into the API key field and click Check connection.

The server reads the key, and the screen does not show it again after the check. The connector only sends read requests, so nothing changes in KeyCRM. The check reads one record of each kind and reports the totals when KeyCRM returns them.

> **Tip.** The API base field can stay empty, and the source page size defaults to 50, the largest value the connector accepts.

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

### 4. Match pipelines, statuses, sources and managers

KeyCRM statuses become Krokul stages by mapping rules, and sources and managers are matched 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.

KeyCRM returns no list of managers, so the list on the check step is empty, and a manager rule has to be written by hand to keep the KeyCRM manager. Without it, Krokul assigns the responsible person by its own rules: the manager of the client company, then of the contact, then the pipeline pool. A card whose pipeline has no rule lands in the first mapped pipeline, and a card whose status has no rule lands in the first stage of its pipeline. With no pipeline rule at all and no default pipeline, a card is reported as a failed row with the reason that no pipeline is mapped and no default pipeline is set.

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

Start the dry run from the check step. It takes the key from the connection check on the server, reads the whole KeyCRM account at 60 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 failed row has a reason you accept and the skip counts match your audit.

### 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 KeyCRM. Keep KeyCRM readable until that check passes.

## How do KeyCRM pipeline cards become deals in Krokul

A KeyCRM pipeline card becomes a Krokul deal with its status as a stage, its lines and its buyer. The amount of the card, its grand total, becomes the expected amount of the deal, and the currency of every deal is UAH.

- The buyer of the card becomes the contact of the deal.
- The lines of the card keep the name, the SKU, the quantity and the price, so the deal shows what was ordered.
- The tags of a card are written after the deal is created. If a tag cannot be written, the deal stays and the row is listed as an error.

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

A dry run of a KeyCRM 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 for each. The connection check alone does not do this, because it only counts the records it can see.

Example: a dry run report for a KeyCRM account:

| Records | Would be created | Would be updated | Would be skipped |
|---|---|---|---|
| Client companies | 220 | 0 | 9 |
| Contacts | 1,260 | 0 | 85 |
| Products | 310 | 0 | 0 |
| Deals | 940 | 0 | 0 |

In the example nothing would be updated, because no earlier run exists. The report only counts the 9 companies and 85 contacts that would be skipped, because by default Krokul skips a record that duplicates one already in the workspace. The duplicate policy is one for the whole run: skip, update or create. Decide it before the real run.

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

A rollback of a KeyCRM 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 KeyCRM ID of every record it writes, so a second run updates the records that already moved and creates no duplicates.

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

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

- Tasks, chats and call logs are not transferred. Export them from KeyCRM first.
- Every deal is written with the currency UAH, whatever currency the card had, and a product without a currency code gets UAH too, so check the amounts after the dry run.
- Without a manager rule the KeyCRM manager is not kept, and Krokul assigns the responsible person by its own rules, so write the manager rules before the run if you need them. The dry run does not pass the validation of a real write, so the real run can still fail on rows the dry run let through.

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

A company with a short list of buyers and a few users can connect KeyCRM, run the dry run and read the report on its own. A business with a running pipeline, several managers and years of orders gets the pipeline, status and manager rules, the reading of the dry run and the final check from an implementation partner, who also trains the team.

The page on the [sources the Krokul migration reads](https://krokul.com/en/solutions/migration/) lists what it moves and what it leaves behind. A smaller source follows the same steps, for example migrating from SalesDrive, which reads orders only.

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

- Starting the import before the pipeline rules exist. Cards then land in the first mapped pipeline and its first stage, or fail with the same reason when no pipeline is mapped, so write the pipeline and status rules first and repeat the dry run.
- Skipping the dry run. The same mapping error repeats on every card, and only a dry run shows it before anything is written.
- Closing KeyCRM on the import day. Chats and call logs are not available through the public API, so keep the account readable for a working week and export them first.
- Leaving managers unmatched. The KeyCRM manager is lost and Krokul assigns another responsible person, so write the manager rules before the run.

## Frequently asked questions

### How long does a KeyCRM migration take?

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

### Does KeyCRM change during the migration?

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

### Are chats and tasks moved?

Tasks, chats and call logs are not moved, because the public KeyCRM API does not provide them. The manager’s comment and the planned contact date of a card do arrive with the deal.

### What happens to duplicates?

By default the import skips a record that duplicates one already in the workspace, and the dry run report counts the skipped rows.

### Who can run a migration in Krokul?

Only an administrator runs a migration. The key 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
