Sources: spreadsheets and three CRMs
CSV and XLSX from any program, plus ready-made migrations from KeyCRM, KeepinCRM and SalesDrive — with deals, contacts, client companies and comments.
Shared
Move from another CRM or a spreadsheet in one evening
Upload a CSV or XLSX file, map the fields to Krokul’s and see how the data lands. Don’t like it? Roll back the import and try again.
Available on the free Deals plan, 100 transactions per month
Migration
TransferSource links1Source2File3Trial4Run5Summary
Where are we migrating from *
File (CSV / TSV / XLSX)What is in the file *
Choose an entityWhat it looks like without Krokul
Three years of sales live in a forty-column Google Sheet. The move keeps getting postponed because “it’s all connected” and nobody knows what’s actually needed.
The old CRM exports deals without contacts, and comments as a separate file. Everything has to be moved by hand, and half the history gets lost.
You tried an import — half the rows landed in the wrong place. Deleting and redoing it is scary: what if it wipes what was already entered by hand?
What Krokul does
Field mapping
Your “Company” column → client company, “Stage” → pipeline stage, “Manager” → user. Krokul suggests the mapping itself, you fix what it didn’t guess; custom fields are created on the fly.
A check before the run
Before the import, the wizard shows the file’s columns, its first rows and any required fields missing from the mapping. After the run, the report says how many records were created and how many rows were skipped and why; if something landed wrong, roll back, fix the file and run again.
Full rollback
Each import is a separate batch. If it landed wrong, one action returns the database to its state before that batch, without touching what you’ve entered by hand since.
How it works
Upload a file or connect your CRM
For a spreadsheet — a CSV or XLSX file; for KeyCRM, KeepinCRM and SalesDrive — the old system’s API key. Krokul reads the structure and shows what it found.
Map the fields
File columns against Krokul fields; duplicate client companies by name and registration number (EDRPOU) are merged as you choose.
The run and fixes
The run report: created, updated, skipped with a reason. Roll back, fix the file or the mapping and run it again.
Import — and work from day one
The real import creates records with their history; the deal board is full, contacts are in place. If something is off — roll back the batch.
Result
- The move takes an evening, not a quarter, and it isn’t scary to start.
- Client history stays with you, not in an old system you no longer pay for.
- An import mistake can be undone in one action, without cleaning the database by hand.
What’s not included
Migration from CRMs other than the three named is done via a spreadsheet or the API — typically a day or two of work for an implementation partner. File attachments and emails from the old system are not migrated; neither are call recordings.
Questions
What exactly gets migrated?
Contacts, client companies with their details, deals with stage, amount and owner, tasks and comments as history. Products and price lists — via a separate spreadsheet import.
Can I move part of the data now and the rest later?
Yes: each import is a separate batch, you can have as many as you like, and each one rolls back separately.
What about duplicates?
Client companies are matched by name and registration number (EDRPOU), contacts by phone and email. You choose: merge, skip or create alongside.
Do I need an implementation partner?
For a spreadsheet and the three named CRMs — no. For a non-standard structure or tens of thousands of records with custom fields, a partner will save you a day.
How much does it cost?
Migration is included in every plan, including the free Deals plan. Imported records don’t count as transactions — only those created during day-to-day work do.
Move your spreadsheet over tonight
Sign up, upload the file, check the mapping and run it. Tomorrow morning your team works with a full deal board.
Included in the Deals plan — free.