How to Import Contacts Deals and Notes Into GoHighLevel

Written by Niyamul Islam Sajal, COO & GHL Certified AdminBlog
GoHighLevel import contacts: a person preparing a CSV spreadsheet on a laptop

A completed GoHighLevel import can't be undone with a one-click rollback, so the work that counts happens before you press start. A GoHighLevel import contacts job that goes wrong usually goes wrong in the spreadsheet: a blank header row, a phone number with dashes, a pipeline name that doesn't exist yet.

This guide covers all three record types people actually move: contacts, deals (HighLevel calls them opportunities) and notes. This one goes past the basic contact upload into deals, notes and errors, with help from our GoHighLevel setup team if you'd rather not do it yourself.

GoHighLevel import contacts: what the CSV needs

HighLevel accepts a single-sheet .csv file under 30 MB and nothing else. According to HighLevel's help article on importing contacts, Excel and Google Sheets files are rejected, only Admin users can run the import, and larger files need splitting.

Any GoHighLevel CSV import follows the same row rule: each row needs at least one of name, email or phone. The first row can't be blank, and at least one header has to match a system field, which is what lets HighLevel map columns for you.

Clean three things before you upload:

  • Headers that match HighLevel's field names.
  • Phone numbers stripped of spaces, dashes and letters.
  • Duplicate records removed from the file itself.

Phone numbers cause the most grief. The numbers need to be in E.164 format, and a number outside the sub-account's country needs its country code, such as +44 for the UK. A non-US sub-account needs +1 on US numbers, per HighLevel's troubleshooting article for bulk CSV imports.

The five steps to import contacts into GoHighLevel

The import runs from the Contacts tab and takes five steps. Do them in a test sub-account first if you have one, because there's no undo.

  1. Open the Contacts tab and click Import Contacts.
  2. Choose Contacts only, or Contacts and Opportunities.
  3. Upload the CSV and pick an import type: create new records, or update existing ones.
  4. Map each CSV column to a HighLevel field.
  5. Set your preferences, review the mapping, confirm consent and start.

New to the platform and want somewhere safe to practise? HighLevel's 30 day Bootcamp trial gives you an account to run a small test file through before touching live data.

Mapping columns and custom fields

In a GoHighLevel import contacts job, map every mandatory field, and leave the columns you don't want unmapped. Unmapped columns are ignored once you confirm the skip prompt.

Custom fields are the catch. Any custom field in your CSV must already exist in the account, so create it under Custom Fields before you upload, not halfway through the mapping screen.

Tick "Don't update Empty Values" whenever you're updating records. Without it, a blank cell in your file can overwrite a good value that's already in HighLevel.

Before you start, you can also create a Smart List for the new contacts, add them to a workflow or tag them. A tag such as "imported-2026-11" makes a bad batch easy to find and fix later.

Updating existing contacts without creating duplicates

When a GoHighLevel import contacts run is set to update, HighLevel looks for the existing record by Contact ID first, then email, then phone. So a file exported from HighLevel and edited will match cleanly, while a file from another system relies on email or phone being identical.

Whether HighLevel creates a second copy of a matching contact also depends on your account's duplicate-contact setting, called Allow Duplicate Contacts. Check it before a big import.

Duplicates inside the file are worse than duplicates against the account. Remove them first, and keep one row per Contact ID, the most current one.

Moving from another CRM entirely? Our guide to migrating to GoHighLevel without losing data covers the planning around the import itself.

Importing deals and opportunities

GoHighLevel import contacts file checked on a computer screen before upload

Photo by Israel Torres on Pexels

To import opportunities into GoHighLevel, use the Opportunities tab, or alongside contacts if both sit on the same CSV row. Pick the route by whether the contacts already exist.

Import typeUse it whenRequired columns
Opportunities onlyContacts already exist in HighLevelContact ID, Opportunity Name, Pipeline
Contacts and OpportunitiesContacts need creating from the same fileContact rules apply, plus the opportunity columns

That comes from HighLevel's help article on importing opportunities. Pipeline Stage is recommended if you want deals placed in the right column, while Opportunity Value, Status and Opportunity ID (updates only) are optional.

The importer doesn't create pipelines. Build the pipeline, its stages and any opportunity custom fields first, and note that opportunity custom fields are separate from contact custom fields. A stage name has to exist inside the pipeline named on that row, or the deal lands in the wrong place.

A GoHighLevel import contacts file that also carries deals needs the Pipeline, Stage, Status and Opportunity Name columns filled in, or those deals won't be created correctly. Status values must be one of HighLevel's four: Open, Won, Lost or Abandoned. Translate your old CRM's labels in the spreadsheet before upload.

To update deals rather than create them, include and map the Opportunity ID. A missing or wrong ID is the main way to end up with a duplicate deal instead of an edited one.

How to bring notes across

A GoHighLevel import of notes is the awkward one. HighLevel's contact import documentation doesn't mention notes at all, so don't expect a column to turn into timeline entries.

You have two realistic routes. The simple one is a custom field called "notes": a feature request on HighLevel's feedback board describes exactly that as the only alternative for keeping notes with a contact export. It keeps the text, though it won't look like a timeline note.

The proper route is the API. HighLevel's Create Note endpoint adds a note to one contact with a POST to /contacts/{contactId}/notes, requiring a note body and the contacts.write scope. The docs mark it deprecated and warn it may be replaced, and it has no idempotency key, so a retried request can create a duplicate note.

For a few thousand notes that's a script, not a spreadsheet job. It's the kind of work our API integrations team handles, as part of the 100+ GHL accounts built and configured by GHL Prime.

Fixing rows that fail

Open Bulk Actions, click Show Stats and use the Error tab to see why rows failed. You can download the error log, fix those rows and re-import only them. Don't re-run the full file, since the successful rows already exist.

These are the codes you'll meet most, from the troubleshooting article above:

CodeWhat went wrongFix
1003More than one sheet in the fileRemove the extra sheets
1008Email isn't in a standard formatCorrect it to [email protected]
1013Phone couldn't be parsedUse E.164 with a country code
1014Date doesn't match the chosen formatMatch the format picked at import
1015Owner matches no userUse a user's email, or add the user first

Code 1002 is a close cousin of 1015: the owner's name matches more than one user, so the owner is left empty. Use the owner's email address instead of the name.

Fix the file, not the importer. Nearly every failed GoHighLevel import contacts row traces back to a value that doesn't match what the account expects.

Frequently asked questions

Can I import an Excel file into GoHighLevel?

No. Only .csv files are accepted, so save the workbook as CSV first and keep it to a single sheet.

Is there a limit on file size?

Files must stay under 30 MB, and larger lists should be split into several files. HighLevel's article doesn't state a maximum number of records.

Can I undo a GoHighLevel import contacts run?

Not with a one-click rollback. Tag every batch and test a small sample first, so you can find and fix anything that goes wrong.

Do I have to create custom fields before importing?

Yes. A custom field in your CSV has to exist in the account before the import, and opportunity fields have to be created on the opportunity object.

Will blank cells wipe my existing data?

They can during an update. Tick "Don't update Empty Values" and blank cells will leave existing values alone.

Sources

Cover photo by Kampus Production on Pexels

Need help implementing this in GoHighLevel?

Our team builds, automates, and scales GoHighLevel systems for agencies every day. Book a free call and we'll map out exactly what to ship next.

Book a free call