Your custom fields, your history, your relationships. Not only the fields both apps happen to have in common.
Start free assessmentWe run Pipedrive CRM to Attio CRM migrations. The assessment is free and comes before any commitment.
Running this for a client? Explore partnership options.
Pipedrive CRM
Attio CRM
Keep deals linked to contacts and companies, and activities linked to their records in Attio CRM.
We find your custom fields in Pipedrive CRM and plan how their values will travel to Attio CRM before migrating their records.
Your activity history arrives on the record it belongs to. This page names which types transfer and any limit on them.
We match them to your Attio CRM users and stages.
The plan flags values that change during migration. The original value comes across beside the converted one.
Where possible, we create a field in Attio CRM for data with no matching field.
Each row explains a limit and what you can do about it. Open the details for the reason and supporting source.
Calls, meetings and your catalogue need an Attio Pro workspace
View detailsHide detailsAttio lets a workspace add an object of its own only from Pro upwards. Below that a workspace is companies and people plus one or three of Attio's own, and there is nowhere for a call, a meeting or a product to be created. Your organizations, people, deals, notes, tasks and files need no object at all and land on any plan.
Verified against attio.comWe tell you which of these your migration needs before you commit.
An Attio deal has six fields
View detailsHide detailsName, stage, owner, value, and the company and people it links to. That is the object, and Attio designed it that way. So a Pipedrive deal's expected close date, its label, its lost reason and the custom fields you use to qualify it have no attribute of their own to land in.
Verified against docs.attio.comEach one is preserved on the deal exactly as Pipedrive had it, rather than pushed into a field that means something else, and the free assessment shows you which of your deal fields this affects before anything runs.
Attio keeps one list of deal stages, not pipelines
View detailsHide detailsA Pipedrive account is built around pipelines, each with its own stages, and most accounts run several. An Attio deal has one stage attribute, a single status with one list of options. Two stages that share a name merge onto one, and which pipeline it came from is not something Attio can hold afterwards. That is the largest single change of shape in this migration.
Verified against docs.attio.comEvery deal keeps the stage it was in, won or lost or still open, so nothing needs re-marking by hand.
Won and lost do not travel as their own fact
View detailsHide detailsPipedrive keeps won and lost on the deal itself rather than at the end of the funnel, which is why it survives a migration into most CRMs. An Attio deal publishes six attributes, its name, stage, owner, value and the two records it links to, and no won or lost flag beside them. So the outcome has to travel as the stage it was in.
Verified against docs.attio.comA deal you marked won lands in your won stage, and we do not read a win off a stage name.
A note does not keep who wrote it
View detailsHide detailsAttio's create-a-note endpoint takes no author, so a note arrives stamped with the workspace member whose connection wrote it. A note that says Priya wrote it in Pipedrive will not say so in Attio. The note itself, its title, its text and the date it was written all come across, on the record it belonged to. It is a small loss, and one we would rather you read here than notice later.
Verified against docs.attio.comThe note itself, its title, its text and the date it was written all come across, on the record it belonged to.
Nobody owns an organization in Attio
View detailsHide detailsAttio's writeable attributes for a company are its name, domains, description, team, categories, location and social links. There is no owner among them, because Attio models ownership on the deal and leaves the rest to lists and views. Your Pipedrive owners travel on your deals, and the owner on an organization is one of the few things this migration reads and cannot place.
Verified against docs.attio.comYour owners travel on your deals, and you say who takes the organizations and the people.
One action removes the records we wrote to Attio CRM. Review what will remain before you undo and retry.
A paused run resumes where it stopped, without losing progress or duplicating records.
We only read Pipedrive CRM. Nothing is written back to it.
Keep working in Pipedrive CRM while you check the results. Then bring across the latest changes before switching over.
In Attio CRM after the migration
After you undo
Covers up to 20,000 records. Larger migrations use higher tiers. You pay once per migration, with no recurring charge.
Connect Pipedrive CRM to see your record count and price before you commit.
Ask for a refund within 30 days of your migration being marked complete. We reverse the migrated data out of Attio CRM and refund you.
Yes. The free assessment finds them in Pipedrive, and they are created as attributes on the matching Attio object before records are migrated. Review the plan and choose whether to leave unused fields behind.
Your call activities and meetings land in one activities object we create in your workspace, because Attio ships no record for an interaction at all. Every other activity type, including the ones you added yourself, lands as an Attio task. Your notes land as Attio notes, which Attio has natively.
Because landing them means adding an object to your workspace, and Attio allows that only from Pro upwards. It is a choice on your plan rather than a surprise. Leave them out and this migration creates nothing in your workspace at all, and your organizations, people, deals, notes, tasks and files still come across.
The stages do, the pipelines do not, and this is the biggest change of shape in the migration. Every stage your deals sit in is created on Attio's deal stage list before the load runs, so each deal arrives in the stage it was in. Attio keeps one list rather than a stage set per pipeline, so two pipelines that both have a Qualification stage arrive as one.
It lands in the stage that meant won. Pipedrive keeps won and lost on the deal itself, and Attio has no equivalent flag, so the outcome travels as the stage rather than as its own fact. We do not read a win off a stage name, and the free assessment shows you how your stages will land before anything runs.
No, and the reason is on Pipedrive's side. Pipedrive keeps email in each user's own synced mailbox and that inbox stays private to that user whatever the permissions in the account, so there is no company-wide email history for us to read. Your calls, meetings, tasks and notes come across.
Your product catalogue comes across into an Attio products object. The line items priced on each Pipedrive deal do not yet, and that one is our limit rather than Attio's, so it is on your plan before you pay rather than a surprise after the run.
No. We work out what each value becomes, so nobody builds a field map. You review the plan before the migration runs. A Pipedrive field with no native home in Attio can be brought along as a new attribute instead of being left behind.
We run the migration and stay reachable. Connect Pipedrive for the free assessment and price, then Attio to complete the plan. Nothing moves until you ask.
Yes. We only read Pipedrive and never write back to it. Keep working while you check the results, then bring across the latest changes before switching over.
You can undo the migration, correct the issue and run again. Created fields, shared catalogue data and any other items listed as retained stay in place.
One payment, based on the records that move. The free assessment of Pipedrive gives you the exact count and price before you commit. Payment is by invoice, with no subscription.
Next step
Create an account and connect Pipedrive CRM for your free assessment. See your record count and price before you commit. Nothing moves until you ask.
Start free assessment