Migrate from Pipedrive to Close Without Losing Your Sequences

The moment teams decide to leave Pipedrive is almost always the same: a rep misses a follow-up because sequence automation simply is not there, or the ops lead realizes they are duct-taping Pipedrive together with Zapier workflows just to get basic cadence functionality that Close ships out of the box. The decision is usually obvious. The execution is what trips people up, specifically what happens to active sequences, open deals, and the custom fields your team spent two years building.

This guide covers the full migration path from Pipedrive to Close: what to export, what to rebuild, what silently breaks, and how to verify you landed cleanly. I will also flag where n8n makes the API-based path significantly cleaner for larger datasets.

Before you migrate

Do not touch the importer until you have done this prep work. I have watched teams skip it and spend a week untangling duplicate contacts and broken field mappings. It is not a fun week.

• Audit your Pipedrive pipeline stages. Document every stage name and map it to a Close status or pipeline stage before import day. Close uses a different status model and your stages will not auto-match.
• Export everything from Pipedrive. Go to Settings > Data Fields > Export Data. Pull separate CSVs for contacts (People), organizations (Companies), deals, and activities. Do this at off-hours to get a clean snapshot.
• Pause active sequences. If you are running email sequences via Lemlist, Outreach, or a Zapier-triggered Gmail cadence, pause them before you migrate. You do not want leads getting step-two emails while their contact record is mid-transfer.
• Inventory custom fields. List every custom field in Pipedrive with its data type (text, number, date, dropdown). You will create matching fields in Close before importing. Skip this and you will be doing cleanup at midnight.
• Capture your email templates. Export or copy every sequence email template into a Google Doc. Close has its own template system and you will rebuild these, not paste them from a CSV.
• Notify your team. Set a hard cutoff time. Any deal updates after export but before import create a data gap. Freeze Pipedrive for 2 to 4 hours on migration day.

The migration steps

What breaks and what does not transfer

Most of the pain in a Pipedrive migration lands in three places: sequence steps, email threads, and automation triggers. Here is the honest breakdown.

What does not transfer: Pipedrive workflow automations (their built-in trigger-action rules) have no equivalent export. You will need to recreate any automation logic in Close’s built-in workflows or in n8n. Email thread history is the other significant loss. Pipedrive stores email as synced threads. Close imports activity-based email exports as flat text notes.

What transfers cleanly: Contact and company records, deal amounts and close dates, pipeline stage names (once mapped), notes entered manually by reps, and attachments if you use the API path.

# Use Close API to bulk-delete test contacts before real import
# Pull all contacts created after your test import timestamp

GET https://api.close.com/api/v1/contact/
  ?query=date_created > "2024-03-15T00:00:00"
  &fields=id,name,emails

# Then DELETE each by id
DELETE https://api.close.com/api/v1/contact/{id}/

# Or use n8n: HTTP Request node (GET),
# Split In Batches node,
# HTTP Request node (DELETE) per record

The sequences concern deserves its own moment, since it is often the reason teams hesitate to pull the trigger. If your current sales sequence health is already shaky, migration is actually a forcing function to rebuild them properly in Close with native tooling rather than carrying forward a broken stack.

Verify it worked

Before you flip reps onto Close, run these four checks:

1. Contact count match. Pull a row count from your Pipedrive export CSV and compare it to the contact count in Close under Settings > Data. Allow for intentional deduplication, but a variance over 5% means something went wrong.
2. Custom field spot check. Open 10 random contact records in Close. Verify that custom field values match the Pipedrive source records for those same contacts. Pay special attention to dropdown fields and date fields.
3. Deal-to-contact linkage. Open five imported deals and confirm each one has a linked contact and company. Orphaned deals (no contact attached) break pipeline reporting immediately.
4. Sequence enrollment test. Create one test contact and manually enroll them in your first rebuilt sequence. Confirm step 1 sends, step 2 is scheduled at the correct day offset, and that a reply from the test inbox skips remaining steps.

Who should switch, who should stay

Pipedrive or Close: where do you land?

Choose Close if

• Your team needs native multi-step sequences with call tasks and email steps in one tool
• You are running outbound SDR motions and your reps live in the CRM all day
• You want built-in power dialer and SMS without adding a third-party integration

From $49/month (Startup) Try Close →

Choose Pipedrive if

• Your team is primarily inbound and manages a visual deal pipeline, not outbound sequences
• You rely heavily on Pipedrive's Marketplace integrations that do not have Close equivalents
• Your deal cycles are long and complex with many custom pipeline stages that map cleanly to Pipedrive's model

From $14/seat/month (Essential) Try Pipedrive →

Choose Salesflare if

• You want a lightweight CRM that auto-logs emails and meetings without manual rep input
• Your team is small (under 10 reps) and you want something between Pipedrive and Close in complexity
• You are not running high-volume outbound and do not need a built-in dialer

From $29/seat/month (Growth) Try Salesflare →

Salesflare is worth considering for teams moving away from Pipedrive but not yet ready for the outbound-heavy Close model. It auto-enriches contact records from email and calendar data, which reduces the manual logging burden that frustrates most Pipedrive users. The Close docs on importing from CSV and the Pipedrive data export documentation are both solid references to keep open on migration day.

For teams using n8n for the API path, the Pipedrive API v1 reference covers pagination and rate limits. Pipedrive caps at 100 requests per 10 seconds on most plans, so build a rate-limit node into your n8n workflow before you run it against a 25,000-row dataset and hit a wall at row 8,000.

Make the switch count

A Pipedrive migration to Close is not technically hard. The CSV importer works, the field mapping is straightforward, and the sequence rebuild is mostly copying text from a Google Doc into Close’s UI. What makes it painful is skipping the prep: not auditing custom fields, not pausing sequences, not running a contact count QA after import. Do the prep work, run the four verification checks, and your team will be on Close with clean data in under a week.