Guide, migration

Migrate from Pipedrive to GoHighLevel

To move from Pipedrive to GoHighLevel, plan on a CSV migration. We did not find a native Pipedrive importer in HighLevel's help center when this was written. People become contacts, organizations become companies, and deals become opportunities. Rebuild pipelines first, import contacts next, and use the HighLevel Contact IDs to link opportunities.

Last updated November 1, 2026

What maps to what?

Why does the order of work matter?

An opportunity-only row in HighLevel needs a Contact ID. That ID only exists once the contact has been imported. So contacts go first, then you export them from HighLevel with their IDs, then match deals to those IDs by email.

1. 1Create pipelines, stages and custom fields in HighLevel.
2. 2Import a small test file of people, then all of them.
3. 3Export contacts from HighLevel, with their Contact IDs.
4. 4Match each Pipedrive deal to a Contact ID, by email.
5. 5Import a small test file of deals, then the rest.
6. 6Reconcile the deal count and total value per stage against Pipedrive.

What are HighLevel's CSV import rules?

• Each opportunity-only row needs a Contact ID, an Opportunity Name and a Pipeline.
• Opportunity custom fields must exist under the Opportunity object before import, not the Contact object.
• Opportunity CSV files must stay under 30 MB.
• Contact notes import at one note per contact, up to 5,000 characters.
• HighLevel's articles disagree on the contact file limit, 50 MB in one and 20 MB or 10,000 rows in an older one. Check your own import screen.
• There is no one-click rollback for a completed opportunity import, so start with a small test file.