Migration
CRM Migration: Bring Your Records, Your Pipelines and Your History
Coming from Pipedrive? Paste an API token and KudosCRM reads your account directly — no export, no spreadsheet, and your pipeline structure comes with it. From any other CRM it is a CSV import with column mapping, duplicate handling and a report of every row that failed.
- ✓Auto-detected columns mapped to Contact, Company, Deal or Task
- ✓Three duplicate strategies, with the impact previewed before you commit
- ✓Row-level error reporting after every import
- ✓Pipedrive connects over the API — no export at all
Pipedrive import
API tokenPipedrive API token
Company settings → API → copy your personal token.
What to bring across
The short definition
What a CRM Migration Is, and the Five Reasons Teams Run One
A CRM migration is the process of moving your records — contacts, companies, deals and their activity history — out of one CRM and into another, then rebuilding the pipelines, custom fields and automations that made the old system work. CRM data migration is the narrower half of that: the records themselves.
These five reasons each have a page that argues them properly:
If you are still deciding whether to move, those pages are the better read. This page is what happens after you have decided.
Migrating from Pipedrive? Nothing to Export.
Paste your Pipedrive API token and KudosCRM reads your account directly over Pipedrive’s API. No CSV export, no file per object, no re-uploading because one column was wrong. You choose which record types to bring, see the real counts before anything is written, and watch the run advance batch by batch.
Eight record types, in dependency order
Companies are written before contacts, and contacts before deals, so every deal has a company and a contact to attach to instead of a dangling reference.
| From Pipedrive | Read with | Becomes |
|---|---|---|
| Organizations | GET /organizations | Companies |
| Persons | GET /persons | Contacts |
| Deals | GET /deals | Deals, with pipeline, stage and owner resolved |
| Leads | GET /leads | Leads |
| Activities | GET /activities | Done ones become history, open ones become tasks |
| Notes | GET /notes | Notes on the matching record |
| Note comments | GET /notes/:id/comments | Replies under the note |
| Deal mail | GET /deals/:id/mailMessages | The email thread on the deal |
The part a CSV cannot do
Your Pipeline Structure Comes With It
Before a single record is written, the connector reads your Pipedrive workspace and rebuilds it here.
- Pipelines — Matched by name, created when missing.
- Stages — Created inside the matched pipeline, keeping Pipedrive's order and each stage's win probability.
- Won and Lost — Appended where a pipeline has none — Pipedrive treats won/lost as a deal status, KudosCRM parks closed deals in terminal stages, so the two shapes are reconciled for you.
- Owners — Matched to your users by email, then by name. Anyone not found falls back to whoever ran the migration, so no record lands unowned.
What a Long Run Gets You That a One-Shot Import Does Not
Resume, not restart
A run is a graph of checkpointed batches, each holding its own cursor. A dropped connection, a rate limit or a cancelled run picks up where it stopped.
Retry only what failed
Failed batches are re-armed one by one. The ones that succeeded are never touched again.
Safe to run twice
Every migrated record is recorded against the source record's own ID, so a second pass does not duplicate what the first pass brought.
Dry run first
Validate the whole thing — counts, mappings, pipeline and stage structure — without writing a single record.
Rate limits handled
The connector meters its own API spend against your Pipedrive budget and paces itself, instead of getting your account throttled.
The token is temporary
Your API token is encrypted at rest and cleared the moment the run reaches a final state. It exists for the length of the migration and no longer.
Before you export
The CRM Migration Checklist: Seven Things to Do First
Every item here is work in your current CRM, not in KudosCRM. Doing all seven before you export is the difference between a migration and a cleanup project.
The route
Two Ways In, Depending on What You Are Leaving
Over the API
Five steps and no file at any point.
Running
Phase 4 of 6 · resumes from its own cursor if it stops
- 1Paste your API tokenIn Pipedrive: Company settings → API → copy your personal token.
- 2Pick your record typesAny combination of the eight. Bring contacts first and deals later if you prefer.
- 3See the real countsA live sample and the true total per record type, read from your account before anything is written.
- 4Confirm the field mappingStandard fields are already mapped. Custom fields are listed with their real labels and types for you to confirm.
- 5Run it, and watch itProgress advances per batch on a page you can share. Failed batches retry themselves.
Over CSV
Six steps, one file per record type.
Header row detected
Your first rows, shown with the header KudosCRM read.
- 1Export a CSV from your current CRMOne file per record type — contacts, then companies, then deals.
- 2Upload it and check the mappingKudosCRM reads the header row and suggests a destination for each column. You correct what it guessed wrong.
- 3Choose how duplicates are handledSkip duplicates, merge into existing, or create both. Applied before anything is written.
- 4Preview, then commitYour first rows are shown with the mapping applied. Fix anything wrong, then commit.
- 5Read the row-level reportRows that could not be imported are listed individually, each with its reason.
- 6Connect Gmail or Outlook and your calendarOAuth, once. From then on new email and calendar activity attaches to the matching record.
Only one migration runs at a time per workspace. If a run is in progress the next one waits for it — which is deliberate, because two concurrent runs writing the same records is how duplicates get made.
Migrate from
What Comes Across, Source by Source
From Pipedrive
Organizations, persons, deals, leads, activities, notes, note replies and deal email history. Pipelines, stages and owners rebuilt automatically.
KudosCRM vs PipedriveFrom HubSpot
Contacts, companies, deals, activities and custom properties, mapped from your export.
KudosCRM vs HubSpotFrom Salesforce
Accounts, contacts, opportunities, activities, notes and custom fields.
KudosCRM vs SalesforceFrom monday Sales CRM
Boards exported to CSV, mapped to Contact, Company, Deal or Activity.
KudosCRM vs monday Sales CRMFrom Excel or Google Sheets
Any CSV carrying email, name and company columns.
Copper and Freshsales are on the connector roadmap too. Until a connector ships, every source above imports cleanly by CSV — the route is what differs, not whether your data arrives.
Duplicate handling
One Setting Decides Whether You End Up With Duplicates
It is applied before anything is written, and the preview shows the impact before you commit. Pick one to see what it does.
| Incoming row | Already in CRM? | Result |
|---|---|---|
| Priya Ramanpriya@meridian.in | Match found | Skipped |
| Arjun Mehtaarjun@cobalt.health | New | Created |
| Sara Khansara@atlasretail.com | Match found | Skipped |
| Dev Pateldev@northwind.co | New | Created |
2 of 4 rows skipped as duplicates. Existing records untouched.
All three are available for contact imports and for API migrations. Deal imports offer skip or import-as-new, and lead imports offer skip or update — worth knowing before you plan a deal import around updating what is already there.
After the import
What You Get That You Did Not Import
What you imported
1,232
Contacts
310
Companies
86
Deals
2,410
Activities
14
Custom fields
Records. Static until something happens around them — which is the rest of this section.
One record per contact, with its history on it
Emails, meetings, notes and tasks attach to the record once your inbox and calendar are connected, so you stop looking in two systems for one conversation.
One board showing every open deal
Your stages, dragged to move, with a weighted forecast calculated from them.
Follow-ups that keep running while you work
Email sequences send their steps on schedule and stop when the contact replies.
CSV and JSON export, from day one
Everything exportable again, with custom fields and the activity timeline intact.
Pricing
What Help You Get on Free, Basic, Professional and Enterprise
The migration wizard, the CSV importer, column mapping, the duplicate strategies and row-level error reporting are on every plan, including Free. What scales with the plan is how much of the work we do beside you. Every workspace starts with 14 days of Professional, no credit card.
Free
Up to 3 users
$0forever
No card, no expiry
Self-serve
- The migration wizard and the CSV importer
- The documentation
- The community forum
Basic
Small teams getting organised
$9/seat/mo
Billed yearly · $12 monthly
Guided
- A migration call with a KudosCRM specialist
- A field-mapping review before you commit
- Help translating your most-used workflows
- A post-migration data audit
Professional
Growing teams that sell and deliver
$24/seat/mo
Billed yearly · $29 monthly
Guided
- A migration call with a KudosCRM specialist
- A field-mapping review before you commit
- Help translating your most-used workflows
- A post-migration data audit
Enterprise
Multi-team and compliance-led
$49/seat/mo
Billed yearly · $59 monthly
Project managed
- A dedicated customer success manager
- A managed migration timeline
- Reports and dashboards rebuilt
- Training sessions for your team
Prices in USD, per seat per month. Yearly billing shown as the equivalent monthly rate. See full pricing.
What your import has to fit
| Free | Basic | Professional | Enterprise | |
|---|---|---|---|---|
| Contacts / records | 1,000 | 25,000 | 250,000 | Unlimited |
| Pipelines | 1 | 3 | Unlimited | Unlimited |
| Custom fields | 10 | 50 | Unlimited | Unlimited |
| Automation runs / mo | None | 1,000 | 25,000 | 250,000 + |
A book of more than 1,000 contacts needs Basic or above, and rebuilt automations need Basic to fire at all. See full pricing.
Your data
Encrypted, Scoped, Logged — and Exportable
Encrypted in transit
Data moves over TLS. Integration and mailbox tokens are encrypted at rest on top of storage-level encryption from the cloud provider.
Scoped to your workspace
Every record is row-scoped to your tenant, and roles and permissions control who can see and do what.
Logged, imports included
Every meaningful action is recorded in the audit trail — a migration run is not an exception to it.
And you can leave
No Lock-In. Export Anytime.
Every record in KudosCRM is exportable as CSV or JSON, custom fields preserved and activity timeline intact. Teams stay because KudosCRM works, not because they cannot get out. On certifications we say the same thing plainly: we do not claim what we do not hold.
Straight about the limits
Four Things This Migration Does Not Do
No API connector for the other CRMs yet.
Pipedrive is the one live connector. HubSpot, Salesforce, Zoho, Copper, Freshsales and monday.com migrate by CSV today; their connectors are on the roadmap, and we are not going to name a date we cannot keep.
Automations and custom code do not transfer.
Workflows, Apex and Deluge are rebuilt rather than moved — the logic does not translate between systems. We help with the rebuild on every paid plan.
No support tickets and no custom objects.
The eight record types above are what migrates. Custom fields do come across, with their types; tenant-defined custom objects and helpdesk tickets do not.
No automation runs on the Free plan.
Workflows you rebuild there will not fire until you move to Basic. Migrate on Free by all means — just know that part stays quiet.
FAQ
Frequently Asked Questions
The wizard is on the Free plan
Test the whole thing before you decide anything.
Start free, run a dry run against your real account, and keep your old CRM switched on while you check.