Migrate from Attio to Pipedrive

Attio People records map 1:1 to Pipedrive Person. Email address is the dedupe key. Custom attributes on the Attio Person object migrate as Pipedrive custom fields of equivalent type (text, number, date, select, multiselect). Relationship links from Attio People to Companies migrate as Organization links. Owner assignments migrate by email match to Pipedrive User.

Attio Company records map 1:1 to Pipedrive Organization. Domain is used as the dedupe key. Company attributes map to Organization fields and custom fields. Many-to-many Person-to-Company relationships are preserved as Pipedrive Person-Organization links, resolved after both objects exist in the destination.

Attio Deals map 1:1 to Pipedrive Deal. Attio must have Deals enabled in the workspace before migration begins; we confirm this during scoping. Deal status maps to Pipedrive Stage. Pipeline assignment maps to a Pipedrive Pipeline that we configure with matching stage names and probabilities before migration. The Deal status chain is sequenced last among standard objects so that all parent Organization and Person references are already resolved, avoiding orphaned Deals.

Each Attio Deal status value maps to a Pipedrive Stage within the corresponding Pipeline. Stage probability percentages migrate from Attio to Pipedrive stage probability fields. We pre-create the Pipedrive pipeline and stages before Deals are imported so that stage assignments are valid at insert time.

Attio custom objects have no direct Pipedrive equivalent because Pipedrive does not expose a standalone custom object API resource. We split custom objects into two migration strategies during scoping: attributes that relate to a Person, Organization, or Deal become Pipedrive custom fields on that standard object; attributes representing a standalone business entity (Subscriptions, Investments, Properties) are imported as labeled Activities with structured fields for reconstruction as a secondary entity list. The customer receives a written schema decision document explaining the trade-offs of each approach.

Attio Lists are workflow-context record collections, not standalone records. We extract every list membership (which records belong to which lists) via the Attio API. List memberships migrate as Pipedrive Labels on the Person, Organization, or Deal record. The membership relationship itself (list A contains persons X, Y, Z) becomes a label tag. We deliver a written segmentation map documenting the original list logic (criteria, filters, size) for the customer's admin to rebuild as a Pipedrive Filter or Automation segmentation rule.

Attio Notes are thread-level records attached to any object. We migrate Notes as Pipedrive Activities of type Note linked to the Person, Organization, or Deal record. Author attribution, timestamp, and note body transfer directly. Rich-text formatting in Attio notes converts to plain text or basic HTML in Pipedrive's activity note format.

Attio Tasks map 1:1 to Pipedrive Activities of type Task. Assignee, due date, status, and priority migrate directly. Owner resolution is by email match to Pipedrive User. Tasks with no assignee become unassigned Pipedrive activities.

Attio's automatic email and calendar sync creates activity records for People and Company records. These migrate as Pipedrive Activities with type Email, Meeting, or Call linked to the Person or Organization record. Attio's interaction metadata (open, click, reply tracking) transfers to Pipedrive as custom activity fields. Email content migrates as the activity body. Calendar event details migrate as Meeting activity fields including duration and attendee count.

Attio relationship attributes define foreign-key chains across objects (Deal linked to Company and multiple People). We query Attio's relationship attributes via API before any standard object import, reconstruct the parent-child chains, and write them to Pipedrive in dependency order: Organizations first, then Persons with Organization links, then Deals with Organization and Person links resolved. This sequencing prevents Deals from arriving orphaned from their Organization or Person associations.

Attio User records map to Pipedrive Users by email match. Owner assignments on People, Companies, Deals, Tasks, and Activities resolve to the Pipedrive User record at migration time. Any Attio Owner without a matching Pipedrive User goes to a reconciliation queue for the customer to provision before record import resumes.