Pipedrive → Clarify

Catalog plan outline

General guidance from the Afterstack catalog for Pipedrive → Clarify. Not Pipedrive or Clarify vendor documentation.

Migration friendliness

Pipedrive 7/10 · Clarify 6/10

Speed to live

Pipedrive 8/10 · Clarify 7/10

Catalog migration difficulty

Pipedrive medium · Clarify not set

Data to export from Pipedrive

• pipeline and deal records
• sequences and cadences
• call and voice logs
• synced email and calendar links
• workflow rules
• saved reports
• campaign and automation records
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: pipeline, outbound

How the catalogs differ

• Clarify is flagged for custom objects. Collapse unused fields before loading them.
• Clarify is not flagged for: call and voice logs, campaign and automation records, installed marketplace apps.
• Clarify adds catalog flags Pipedrive does not have: custom objects.
• Pipedrive is flagged with an open API, which is the export path to test.
• Clarify is flagged with an open API for the load.
• Pipedrive is cataloged as a fit for: Deal-driven sales teams.
• Clarify is cataloged as a fit for: Teams leaving Pipedrive.

Phases

1. Export

   Take Pipedrive as the source of truth for this pair. Export pipeline and deal records; sequences and cadences; call and voice logs; synced email and calendar links; workflow rules; saved reports; campaign and automation records; installed marketplace apps; AI assistant configuration; records for the catalog use cases: pipeline, outbound. The visual pipeline CRM salespeople actually update.

2. Map

   Load into Clarify only after the field map is written down. The AI CRM that fills the pipeline so reps do not have to. Clarify is flagged for custom objects. Collapse unused fields before loading them.

3. Prove a sample

   Clarify scores 7/10 on speed to live and 6/10 on migration friendliness. Run one sample load and one report the team already uses in Pipedrive before a full cutover.

4. Cut over

   Pipedrive scores 7/10 on migration friendliness and is marked medium difficulty in the catalog. Keep Pipedrive readable until the team is working in Clarify. Pipedrive started as a deal board that did not feel like homework. It is still the clearest pipeline UX in the category, with add-ons for campaigns, projects, and a newer AI layer. Teams leave when they need a richer data model or automatic capture.

Pipedrive to Clarify: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not Pipedrive or Clarify vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from Pipedrive

Pipedrive's export article, updated 3 September 2026, says global admins can export leads, deals, organizations, people, products, activities, notes, and files. The formats are XLSX and CSV. Projects are included only on Premium or with the projects add-on. Activities, notes, and files that are linked to deals do not ride along inside the deal file. The article says to export them separately. Files stored in Google Drive are not in the global export. Exported files remain available for 28 days. An API token is the programmatic path the article points at. Shorter guesses, /en/article/importing-data-into-pipedrive and /en/article/how-can-i-import-data-into-pipedrive, still return 404. A separate article, Importing data into Pipedrive with spreadsheets, updated 7 October 2026, did open. It is how you would put rows back into Pipedrive, not how Clarify loads them. A user with the global import permission can create or update people, organizations, leads, deals, projects, activities, notes, and products from an XLS, XLSX, or CSV file. One worksheet per run, a header row, no more than two hundred thousand rows, and a file under fifty megabytes. A person needs a name. An organization needs a name. A deal or a lead needs a linked person or organization. Cells on the same row are linked. Custom fields have to exist before the upload. The article also explains how to revert that import.

• Pipedrive exporting data — checked 2026-10-08
• Pipedrive spreadsheet import — checked 2026-10-08

How Clarify imports

Clarify was not documented, in the pages opened here, as having a Pipedrive-native button. The workable paths are the CSV article and the API guide. CSV files are separate, each at most 30 megabytes. When a deal file maps a company column, load companies, then people, then deals. Deal-to-people links are not created from that CSV. The API guide describes bulk import with a match_on field. https://www.clarify.ai/docs 404'd. Use docs.clarify.ai and developer.clarify.ai. Pipedrive's separate notes export does not become a Clarify note automatically. The Clarify CSV article never says it ingests a Pipedrive notes file.

• Clarify CSV import — checked 2026-10-08
• Clarify API import guide — checked 2026-10-08

Object and field mapping

• Pipedrive organizations are the file to treat as Clarify companies, loaded first if deals point at them.
• Pipedrive people are the file to treat as Clarify people.
• Pipedrive deals are the deal file. Person links on those deals will not be reconstructed by the CSV load.
• Pipedrive leads are their own export. The Clarify articles do not name a lead object. Choose person, company, or a dropped archive.
• Pipedrive products need an explicit home. Nothing opened for Clarify describes a product catalog import.
• Activities and notes stay in their own Pipedrive files until you design a Clarify destination. Do not bury them in the deal CSV and hope.

What will not carry over

• Google Drive files, which Pipedrive excludes from the global export.
• Projects, unless the Pipedrive plan is Premium or has the add-on. Even then, Clarify's CSV article does not describe a project object.
• Deal-to-person links, per Clarify.
• Files over 30 megabytes in one CSV.
• Pipedrive automation, web forms, and email sync state. Those are not columns in the export article.
• A native Clarify button for Pipedrive. The spreadsheet article above reloads Pipedrive. It does not describe Clarify.

Cutover checklist

1. Export as a global admin.
2. Export deals, people, and organizations as their own files.
3. Export activities, notes, and files as extra files, because deal export omits them.
4. Download within 28 days.
5. Leave Google Drive files out of the expected bundle.
6. Split Clarify-bound files at 30 megabytes.
7. Load company, person, then deal order in Clarify.
8. Test match_on on the API with a handful of organizations before the full people file.
9. If you must undo the move, use Pipedrive's spreadsheet import and its revert step, not a 404 URL.
10. Keep Pipedrive's export available until Clarify's sample deals look right, because a Pipedrive import doc was not found.

Common pitfalls

• Assuming the deal export contains notes. Pipedrive says notes are separate.
• Waiting until day 29 to download. The article's window is 28 days.
• Treating the spreadsheet article as a Clarify field map. It only describes Pipedrive's own importer, including a revert step after the upload.
• Loading one combined workbook because XLSX feels easier. Clarify wants separate CSVs under 30 megabytes.
• Promising that products and projects appear in Clarify. Those destinations were not in the Clarify docs opened here.

Related catalog pages

• Best AI-native Pipedrive alternatives (2026) — Which tool, compared
• What should replace Pipedrive? — Switch narrative
• Clarify product page — The AI CRM that fills the pipeline so reps do not have to.
• Clarify vs Pipedrive — Head-to-head already in the catalog
• CRM & sales category — Catalog hub for this category