Migrate from Pipedrive

If you are coming from Pipedrive, you do not have to go through CSV exports. KudosCRM connects to Pipedrive directly and pulls your organisations, people and deals across.

The migration is repeatable: it remembers which KudosCRM record came from which Pipedrive record, so running it again updates rather than duplicates.

Who this is for

Admins moving a workspace off Pipedrive.

Before you start

• A Pipedrive API token from your Pipedrive account.
• Admin access to migrations in KudosCRM.
• A decision about pipelines — it is worth having your KudosCRM pipeline in place first, so deals land somewhere sensible.

Pipedrive is the one that is built
You may see other CRM names listed as migration sources. Pipedrive is the one with a working importer today — it is the migration that has actually been built end to end. If you are moving from a different CRM, use CSV import for contacts and companies and talk to us about the rest, rather than assuming a listed name means a finished path.

Run the migration

1. Get your Pipedrive API token
   In Pipedrive, generate a personal API token. KudosCRM uses it to read your data through Pipedrive's API — it is a read of your account, not a change to it.
2. Set up your KudosCRM pipeline first
   Deals need somewhere to land. Building the pipeline you want before migrating saves moving everything afterwards.
3. Start a migration and connect
   Create a migration with Pipedrive as the source and supply your token. KudosCRM connects to your Pipedrive company account.
4. Let it import organisations, people and deals
   Organisations become companies, people become contacts, and deals become deals. Each imported record stores its originating Pipedrive id, which is what makes the next step safe.
5. Check the results
   Review what came across before you point your team at it. Spot-check a few records you know well — the ones with unusual fields are the informative ones.
6. Re-run if you need to
   Because each record remembers its Pipedrive id, running the migration again matches and updates existing records rather than creating a second copy. That makes a second pass safe if you kept working in Pipedrive during the switch.

What you get

• Your Pipedrive organisations, people and deals as native KudosCRM records.
• A stored link back to the original Pipedrive id on each record.
• A repeatable migration you can run again without duplicating what it already brought over.
• A clean cutover, because you can migrate, verify, keep working in Pipedrive, and re-run before switching.

Frequently asked questions

Will running the migration twice duplicate my deals?

No. Each imported record stores the id of the Pipedrive record it came from, and the importer matches on that id. A second run updates the records it already created.

Does the migration change anything in Pipedrive?

It reads your Pipedrive data through their API. It is a one-way import into KudosCRM.

Can I migrate from HubSpot or Salesforce the same way?

Not today. Pipedrive is the migration that is actually implemented. For other CRMs, export contacts and companies to CSV and import those, and get in touch about the rest rather than waiting for a path that is not built yet.

What about activities, notes and files?

The migration focuses on the core records — organisations, people and deals. Check what came across and plan for anything outside that set rather than assuming it followed.