# Move your Pipedrive CRM data into Close CRM

Your custom fields, your history, your relationships. Not only the fields both apps happen to have in common.

Migratez runs Pipedrive CRM to Close CRM migrations. The assessment is free and comes before any commitment.

Canonical page: https://migratez.com/migrations/pipedrive-to-close-crm-migration

## What lands in Close CRM

- Organizations → Leads (a Close lead is a company, and everything else hangs off it)
- People → Contacts on that lead
- Deals → Opportunities on that lead
- Pipelines and stages → Built in Close as pipelines and their statuses (both apps keep named funnels, so yours crosses whole)
- Notes → Notes on the lead
- Call activities → Call activities
- Your other activities → Tasks on the lead (every activity type that is not a call or a meeting, including the ones you added yourself)
- Files → Close files, on the lead the record belongs to (a Close file attaches to a lead, so one you hung off a contact or a deal follows that record to its company)
- Custom fields → Created as custom fields on the lead, contact or opportunity they belong to
- Users → Matched to your Close users by email (and you name who inherits the records of anyone with no match)
- Links between records → Close's own parentage, with every record hanging off its lead

## What comes across

Comprehensive by default, customizable on request.

- **Relationships, not just records.** The graph survives. Deals stay attached to the right contacts and companies, activities stay on the record they belong to, and the links between them are rebuilt in Close CRM rather than left behind.
- **Your custom fields come with you.** They are found in Pipedrive CRM and created in Close CRM before a single record is written. Not flattened into a notes field.
- **History, not just the current state.** Notes, calls and meetings arrive on the record they belong to, with their owners and timestamps intact.
- **Owners, pipelines and stages are reconciled.** Matched to your Close CRM users and stages rather than reset to a default.
- **Nothing is silently rewritten.** Where a conversion is genuinely lossy, the original value comes across alongside the converted one, so you can always see what the data was before we touched it.
- **A field with no home is brought along.** If Close CRM has no native place for something you use, we can create one for it rather than drop it.

## Everything in Close hangs off a company.

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](https://developer.close.com/api/resources/leads) 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.

## What happens to the rest

- **Everything in Close hangs off a company** (degraded). 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 must be children of a lead. So your organizations become leads and everything else arrives underneath the company it belongs to. Instead: A 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. Verified against https://developer.close.com/api/resources/leads
- **A deal in Close has no name of its own** (degraded). A 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. Instead: The value, the stage, the owner and the close date all come across. Verified against https://developer.close.com/api/resources/opportunities/list.md
- **Nobody owns a company in Close** (degraded). A 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. Instead: Your record owners travel on your deals and tasks, and you say who takes the companies and the people in them. Verified against https://developer.close.com/api/resources/leads/list.md
- **A Close custom field has no true or false, and no currency** (degraded). Close'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. Instead: We show you which of your fields this affects in the free assessment. Verified against https://developer.close.com/api/resources/custom-fields
- **An attachment cannot be taken back out** (degraded). Close 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. Instead: Everything else we wrote comes back out. Verified against https://developer.close.com/resources/files/
- **Your meetings stay in Pipedrive CRM** (unsupported). Close 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. Instead: Your calls, emails, notes and tasks all come across as activities on the lead. Verified against https://developer.close.com/resources/activities/meeting/

## If it goes wrong

- **Undo the records we wrote.** Every write into Close CRM is recorded, so one action takes the records we wrote back out again, in reverse. If it is not what you expected, restore and retry.
- **Paused, not lost.** A stop, an error or an API limit pauses the run at its last checkpoint rather than killing it. Nothing is lost and nothing is written twice.
- **Read-only in Pipedrive CRM.** Nothing is ever written back into Pipedrive CRM. It is the system you are leaving, and we only read it.
- **A last catch-up before you switch over.** After the main load, one action brings across everything that changed in Pipedrive CRM since, so you can verify with both systems live and then switch over.

## What it costs

One price, one time, set by how many records you move.

- **From $399.** That covers up to 20,000 records. The price steps up with volume and it is for the migration, not a subscription. Nothing recurs.
- **The free assessment settles the number.** It reads Pipedrive CRM and reports what is actually in it, so your price comes from your real record count rather than a sales call. You see it before you commit to anything.
- **A 30-day money-back guarantee.** 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.

## Questions about moving Pipedrive CRM to Close CRM

### What is the biggest change of shape in this move?

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.

### Do my pipelines survive?

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.

### Will my custom fields come across?

Yes. The free assessment finds them, and they are created as Close custom fields on the lead, contact or opportunity they belong to before a single record is written.

### What happens to my emails?

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.

### What will not come across?

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.

### Do I have to build a field map?

No. The mapping is written for this one direction and shown to you before anything runs, so your part is reviewing it rather than assembling it. A Pipedrive field with no native home in Close can be brought along as a new custom field instead of being left behind.

### Who actually runs the migration?

You create an account and connect Pipedrive, and the free assessment tells you what is in it and what it costs. Close is connected next, so we can check it against what your organization can hold. I run the migration itself and stay reachable while it does. Nothing moves until you ask for it.

### Can I keep working in Pipedrive while this happens?

Yes. Nothing is ever written back into Pipedrive, we only read it. After the main load, one action brings across everything that changed in Pipedrive since, so you can verify with both systems live and switch over when you are ready.

### What if the result is not what I expected?

Every write into Close is recorded, so one action takes the records we wrote back out again. You can sort out what was wrong and run it again.

### What does it cost?

One price, one time, based on how many records the migration moves. The free assessment counts them in your Pipedrive and gives you the exact price before you commit to anything. There is no subscription and no card form.