One API key. Seventeen entity types. Safe to run twice.
No credit card. Read-only against your Pipedrive account — nothing is changed or deleted there.
Most of them are a CSV export, a column-mapping spreadsheet, and a fortnight of discovering what didn't come across. Usually it's the custom fields, the email history, or the deal-to-contact links — the things that made the old system worth having.
Blob's Pipedrive importer talks to the API directly. You paste a key, tick what you want, and it pulls structure first (pipelines, stages, users) so that everything after it lands in the right place. It's idempotent, meaning you can run it as many times as you like without creating duplicates — each record is matched on its Pipedrive ID and updated rather than re-inserted.
| Contacts & organisations | Including owners, labels, addresses, and every custom field |
| Deals & deal products | With pipeline, stage, value, currency, and won/lost reasons |
| Activities & activity types | Your own activity types are recreated, not flattened to a default |
| Notes | Attached to the right contact, organisation or deal |
| Mail history | Threading rebuilt from the original message headers |
| Email templates | Merge fields converted to Blob's equivalents |
| Products | SKU, price, tax and cost |
| Leads & lead labels | The Pipedrive leads inbox, with its labels |
| Files | Attachments, linked to their records |
| Filters | Your saved views |
| Custom fields | Surfaced as named fields, not hashed keys |
| Pipelines, stages & users | Structure first, so everything else lands in the right place |
Pipedrive stores custom fields under 40-character hashed keys — a field called "Postcode" is really f9bbebad… in the data. A CSV export carries the values but not the definitions, so they land in your new CRM as either nothing at all or a column of unlabelled hashes.
Blob reads the field metadata too, and creates a matching named field for every visible Pipedrive custom field. Your Postcode field is called Postcode, it's the right type, and it's editable.
Conversations are reconstructed from the original Message-ID, In-Reply-To and References headers rather than being dumped in date order. A three-month back-and-forth stays a single thread attached to the deal it belongs to.
| 1 | Start a free Blob trial — email and password, no card. |
| 2 | In Pipedrive, go to Personal preferences › API and copy your personal API token. |
| 3 | Paste it into Blob's setup wizard and tick the entity types you want. |
| 4 | The import runs in the background with a live progress tree. Close the tab if you like — it keeps going. |
| 5 | Look around. Re-run the import any time to pick up anything that changed in Pipedrive since. |
The importer only reads. Nothing in your Pipedrive account is modified or deleted, and you can run both systems side by side for the whole trial.
Being straight about this, because finding out later is worse.
Pipedrive's automations don't transfer. The trigger and action models are different enough that a mechanical conversion would produce something you'd have to check line by line anyway. Blob's workflow builder has a template library to start from, and most teams find they had fewer live automations than they thought.
Blob has its own reporting, and it isn't a superset of Pipedrive's — Pipedrive's custom report builder is more capable. Anything you've built there needs recreating, and some of it may not have an equivalent. Worth checking before you commit.
Data held inside LeadBooster, Web Visitors or Projects belongs to those products rather than the core API, so it isn't part of the import.
Most teams finish in under ten minutes. You paste a Pipedrive API key, tick the entity types you want, and the import runs in the background while you watch a progress tree. Very large accounts take longer, but you don't have to sit and wait — it continues if you close the tab.
Contacts, organisations, deals, activities, notes, mail history, products, deal products, leads, lead labels, files, filters, custom fields and email templates, plus your pipelines, stages, users, activity types and lost-reason options. Deal-to-contact and contact-to-organisation relationships are preserved, as are owners.
No. Every record is matched on its Pipedrive ID, so re-running updates the existing row rather than creating a second one. That makes it safe to do a trial import, look around, and re-run later to pick up anything that changed.
They arrive as named, editable fields on the record. Pipedrive stores custom fields under 40-character hashed keys, and most importers carry the values across while leaving them invisible — the data is technically there but nothing displays it. Blob creates a matching field definition for every visible custom field so the values show up where you'd expect.
Yes, and it keeps its threading. Conversations are rebuilt from the original RFC 2822 message headers, so replies stay attached to the right contact and deal rather than arriving as a pile of loose messages.
No, and we'd suggest you don't. The import only reads from Pipedrive, so you can run both in parallel during the 14-day trial and cancel once you're satisfied.
14 days free, no credit card. Import your Pipedrive account, run both side by side, and decide with everything in front of you.