Pipedrive → Attio

Catalog plan outline

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

Migration friendliness

Pipedrive 7/10 · Attio 7/10

Speed to live

Pipedrive 8/10 · Attio 7/10

Catalog migration difficulty

Pipedrive medium · Attio 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

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

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 Attio only after the field map is written down. A CRM that treats your data model as the product. Attio is flagged for custom objects. Collapse unused fields before loading them.

3. Prove a sample

   Attio scores 7/10 on speed to live and 7/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 Attio. 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 Attio: what the vendor docs actually cover

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

What to export from Pipedrive

Use Pipedrive's exporting-data article, updated 3 September 2026. Global admins export XLSX or CSV. The record types named are leads, deals, organizations, people, products, activities, notes, and files. Projects require Premium or the add-on. A deal export does not include the activities, notes, and files hanging off that deal. Export those on their own. Google Drive attachments are omitted from the global export. The download lives for 28 days. The article also documents an API token. Import slugs that omit the spreadsheet title still 404. The article that loaded is Importing data into Pipedrive with spreadsheets, last updated 7 October 2026. Global permission is required. Formats are XLS, XLSX, and CSV. You can add or update people, organizations, leads, deals, projects, activities, notes, and products. Limits written on that page: a single tab, column names in the first row, 200,000 rows, and 50 MB. People require a name, organizations require a name, and deals or leads require a linked person or organization. Pipedrive links the values that share a row. You can revert the import afterward. Keep that path for undoing a cutover. It does not relax Attio's ban on notes and tasks in CSV.

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

How Attio imports

Attio's migration article names Pipedrive as a supported Import2 source, alongside the other CRMs it lists. Admins run it, and only on Plus, Pro, and Enterprise. Attio describes the tool as free for its users. Existing people matched by email and existing companies matched by domain do not receive attribute updates from Import2. Recordings of calls are not in that tool. CSV remains available with a required header and ceilings of 100,000 rows, 100 columns, and 100 megabytes. The CSV article's ban on notes and tasks collides with Pipedrive's habit of exporting notes as their own file: that file is not a CSV Attio will accept as notes. Developer docs cover REST, webhooks, and SQL if you script around Import2.

• Attio migrate from another CRM — checked 2026-10-08
• Attio CSV import — checked 2026-10-08
• Attio developer overview — checked 2026-10-08

Object and field mapping

• Pipedrive people go to Attio people. Email match means Import2 leaves the existing Attio person unchanged.
• Pipedrive organizations go to Attio companies. Domain match means the existing company is left unchanged.
• Pipedrive deals are in scope only as far as Import2's Pipedrive source actually maps them. The article names Pipedrive. It does not paste every deal field.
• Pipedrive notes are a separate export and are a poor fit for Attio CSV, which rejects notes and tasks.
• Pipedrive activities are their own file. Do not assume they become Attio tasks.
• Pipedrive products and projects need a custom destination. They are not named as Attio objects in the migration article section read for this page.

What will not carry over

• Notes and tasks via Attio CSV, even if Pipedrive handed you a notes spreadsheet.
• Attribute updates on Attio records that already match.
• Google Drive files from the Pipedrive global export.
• Call recordings via Import2.
• Emails in a later Attio workspace export. Attio's docs exclude emails from that export.
• Pipedrive workflows and campaign automations. They are not in the export article's file list as configuration.

Cutover checklist

1. Have a global admin run the Pipedrive export.
2. Produce separate files for notes, activities, and attachments.
3. Save them before day 28.
4. Skip Google Drive items in the inventory.
5. Check the Attio plan is Plus, Pro, or Enterprise.
6. Have an admin start Import2 rather than a member.
7. Search Attio for the emails and domains you are about to load.
8. Park the Pipedrive notes file. Do not drop it into CSV import.
9. Compare a sample of open deals in both products before anyone loses Pipedrive access. You do not have a verified Pipedrive import doc to undo this.

Common pitfalls

• Feeding Pipedrive's notes export into Attio CSV. The destination article forbids notes and tasks.
• Re-running Import2 to fix a bad field. Matches on email and domain will not update.
• Forgetting the 28-day Pipedrive retention and the 30-day figure from some other vendor. This pair's source window is 28 days.
• Using a dead Pipedrive import slug as the undo plan. The spreadsheet article is the one that loaded, and it includes a revert.
• Reading Attio's conflicting seat caps on the pricing page as a migration limit. The pricing page disagrees with itself, so the cap is not a planning number.

Related catalog pages

• Best AI-native Pipedrive alternatives (2026) — Which tool, compared
• What should replace Pipedrive? — Switch narrative
• Attio product page — A CRM that treats your data model as the product.
• CRM & sales category — Catalog hub for this category