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 Close CRM migrations. The assessment is free and comes before any commitment.
Running this for a client? Explore partnership options.
Pipedrive CRM
Close CRM
Keep deals linked to contacts and companies, and activities linked to their records in Close CRM.
We find your custom fields in Pipedrive CRM and plan how their values will travel to Close 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 Close 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 Close CRM for data with no matching field.
This is the shape to understand before you move, and it is Close’s model rather than a choice we made. Close’s primary record is the lead, and a lead is a company. Its own reference says to think of one as both a lead and an account, and that contacts, tasks, opportunities and activities are all children of a lead. So a contact with no company is not a poorer record in Close, it is not a record. We carry your companies first for that reason, and anything that would arrive orphaned is named on your plan rather than written beside an invented company.
Each row explains a limit and what you can do about it. Open the details for the reason and supporting source.
Everything in Close hangs off a company
View detailsHide detailsClose's primary record is the lead, and a lead is a company. Its own reference says to think of one as both a lead and an account, and that contacts, tasks, opportunities and activities must be children of a lead. So your organizations become leads and everything else arrives underneath the company it belongs to.
Verified against developer.close.comA record whose company did not come across has nowhere to be, which is why we bring the companies first and name anything orphaned before the run rather than during it.
A deal in Close has no name of its own
View detailsHide detailsA Close opportunity is identified by the lead it sits on and shown by the company's name. There is no title field on it. So whatever you called each deal does not survive as a title, and the deal is known by its company and its pipeline instead.
Verified against developer.close.comThe value, the stage, the owner and the close date all come across.
Nobody owns a company in Close
View detailsHide detailsA Close lead carries no owner or assigned user, only who created and last updated it. Ownership here sits on the opportunities and the tasks. So your Pipedrive record owners travel on your deals and tasks, and on the company itself there is no field for one to land in.
Verified against developer.close.comYour record owners travel on your deals and tasks, and you say who takes the companies and the people in them.
A Close custom field has no true or false, and no currency
View detailsHide detailsClose's custom field types are text, number, date, datetime, a list of choices, a user, a contact, a custom object, a long text area and a hidden value. There is no checkbox among them and no money type. So a yes or no field arrives as the text of the answer, and an amount keeps its figure and loses what it was denominated in.
Verified against developer.close.comWe show you which of your fields this affects in the free assessment.
An attachment cannot be taken back out
View detailsHide detailsClose has no way to delete a file. Its files reference documents one operation, generating a signed upload, and nothing that removes a file, so a file this migration attached stays attached even if you undo everything else. The undo tells you which ones it had to leave rather than passing over them quietly.
Verified against developer.close.comEverything else we wrote comes back out.
Your meetings stay in Pipedrive CRM
View detailsHide detailsClose builds a meeting from a calendar event synced out of Google Calendar or Outlook. Its API lists no way to create a meeting activity, only to search, read, update and delete the ones that sync made. So a meeting has nowhere to be written.
Verified against developer.close.comYour calls, emails, notes and tasks all come across as activities on the lead.
One action removes the records we wrote to Close 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 Close 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 Close CRM and refund you.
Every record ends up under a company. Close's primary record is the lead, which is a company, and contacts, opportunities, tasks and activities are all children of one. Your organizations become leads, and everything else arrives underneath the company it belongs to. It reads differently from Pipedrive and it is the thing to look at first in the free assessment.
Yes, and this is where Close is generous. Close keeps named pipelines with ordered statuses, so your funnel is built in Close as it stands rather than flattened onto one list. A status that means won or lost in Pipedrive is created as one that means won or lost in Close, so your reports add up without anybody re-marking the closing stages by hand.
Yes. The free assessment finds them, and they are created as Close custom fields on the lead, contact or opportunity they belong to before records are migrated.
They are logged as history, never sent. Every email we write into Close is written as one that has already been sent, so nothing reaches your customers and nobody is emailed twice. This is the single thing on this page we test on its own, because the failure worth being paranoid about is sending somebody's whole email archive to their own leads.
Your meeting activities, because Close builds a meeting from a synced calendar event and publishes no way to create one. And your product catalogue, because Close prices an opportunity as a single value on the deal rather than from a list of priced lines. You see all of it on your plan before you pay rather than 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 Close can be brought along as a new custom field instead of being left behind.
We run the migration and stay reachable. Connect Pipedrive for the free assessment and price, then Close 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