You have a spreadsheet of customers, leads, and business contacts ready to move into your CRM. Uploading it seems straightforward—until names land in the wrong fields or existing records change unexpectedly.
A successful GoHighLevel contact import starts before you click the import button. Preparing identifiers, checking field mappings, and testing a small batch helps you catch problems while they are still easy to correct.
This guide walks through seven steps for importing contacts from a CSV file, organizing the results, and checking errors before you use the data in follow-up campaigns.
Table of Contents
What Is a GoHighLevel Contact Import?
A GoHighLevel contact import brings contact information into a sub-account from a CSV file. Depending on the selected import mode, you can add new records, update existing records, or handle both.
This is useful when moving from another CRM, collecting customer records from several spreadsheets, or updating a known set of contacts.
Define the intended result first. “Add our approved customer list” is a different task from “Update phone numbers on existing records.” That distinction affects the file, matching identifiers, and import settings you should use.
Prepare Your GoHighLevel Contact Import in 7 Steps
1. Create a Working Copy and Export a CSV
Keep the original spreadsheet unchanged. Prepare the import in a separate working copy so you can compare the result with the original information.
Use one header row and one contact per row. Remove title rows above the headers, blank rows, totals, and commentary that does not belong in a contact record.
HighLevel’s contact importer accepts CSV files. If you work in Excel or Google Sheets, export the intended sheet as CSV rather than uploading an XLSX file or renaming its extension. See HighLevel’s contact import guide.
For example, a practical starting file might contain:
| CSV column | Purpose |
|---|---|
| First Name | Contact’s first name |
| Last Name | Contact’s last name |
| Primary email address | |
| Phone | Primary phone number |
| Business Name | Associated business |
| Relationship | Your own customer, vendor, or contractor classification |
| Tags | Labels you intend to apply |
“Relationship” is an example custom field, not a claim that these classifications are built-in contact types.
Include only information you plan to use. A smaller, clearly defined file makes a GoHighLevel contact import easier to review.
2. Check Identifiers and Field Values
For updates, include a reliable identifier that the importer can use to find the existing contact, such as the correct HighLevel Contact ID, email, or phone.
Do not substitute an ID from another CRM for a HighLevel Contact ID.
Review repeated emails and phone numbers. Two rows with the same identifier may represent the same person, but a shared office number can belong to several people. Investigate before combining records.
HighLevel’s CSV formatting guide explains identifying fields and accepted field formats.
Before your GoHighLevel contact import, check:
- Email cells contain addresses rather than display names.
- Phone numbers retain the necessary country information.
- Spreadsheet formatting has not changed phone numbers into scientific notation.
- Dropdown answers match the options in the destination field.
- Date values follow a supported format.
- Headers describe the actual contents of each column.
Do not guess missing contact information. A clearly identified gap is easier to handle than an invented value that later reaches a customer message.
3. Select the Sub-Account and Import Mode
Open the sub-account that should receive the records.
Go to Contacts, open the import control, select Contacts, and upload the prepared CSV. If the interface offers both contacts and opportunities, choose contacts only for this guide.
Select the mode that matches your purpose:
| Import mode | Intended use |
|---|---|
| Create | Add contacts that do not already exist |
| Update | Change existing records |
| Create & Update | Process a file containing new and existing contacts |
Review the matching controls shown in your account. Do not assume that changing a general duplicate-contact preference replaces checking the import’s own configuration.
For an update, test one record whose current values you know. Confirm that the importer finds that record and changes only the fields you intended.
HighLevel’s combined import guide describes these import choices.
Before continuing, inspect any available empty-value controls. Include a blank-cell case in your test so you can see whether existing information is preserved or cleared.
4. Map Every Column to the Correct Field
Field mapping tells HighLevel where each column belongs.
Do not accept a suggested mapping without reading it. “Business Name” and a person’s name may look similar in a spreadsheet while representing different information.
Here is an illustrative mapping plan:
| Your column | Destination | Check |
|---|---|---|
| First Name | First Name | Does not contain a full company name |
| Last Name | Last Name | Contains the person’s surname |
| Contains the intended primary address | ||
| Phone | Phone | Contains the intended primary number |
| Business Name | Business Name | Contains the organization name |
| Relationship | Your “Relationship” custom field | Field exists and options match |
| Tags | Tags | Contains only the labels you want applied |
Create missing contact custom fields before completing the import. Under Settings → Custom Fields, add the required field, choose a suitable type, and save it.
A dropdown is useful when you want consistent choices such as Customer, Vendor, and Contractor. A text field suits information that does not fit a fixed list.
HighLevel’s getting-started import guide covers custom fields and mapping.
For a GoHighLevel contact import, deliberately skip columns you do not want to import. Unmapped information should not be assumed to exist in the contact record afterward.
5. Plan Tags and Review Affected Workflows
Give the batch a descriptive tag, such as import.website-customers.2026-10.
This example identifies the source and period. It helps you find the affected contacts later.
Use a separate classification tag when needed:
| Example tag | Purpose |
|---|---|
| customer | Classify customers |
| vendor | Classify suppliers |
| contractor | Classify contractors |
| import.website-customers.2026-10 | Identify this import batch |
HighLevel supports importing tags through a Tags column and applying tags through import options. Its Contact Tag guide also explains that imported tag changes can start workflows that use tags as triggers.
Before applying a tag, check whether an existing workflow uses it. A tag named customer might already start a welcome sequence.
Also review the import’s optional workflow enrollment setting. For a first test, keep deliberate campaign enrollment off unless that behavior is part of the test.
Your GoHighLevel contact import should produce an organized list before you use it for customer outreach.
6. Run a Small Test Import
Select a small sample that represents the different cases in your file.
For example, test:
- A new contact with an email and phone.
- An existing contact you intend to update.
- A contact with only one available identifier.
- A record with a custom-field answer.
- A record with several intended tags.
- An update containing a blank optional cell.
Five to ten representative rows are often a useful starting sample. The variety matters more than the exact number.
After importing, open each test contact and compare it with the CSV. Check names, primary contact details, business information, custom fields, tags, and existing information you expected to preserve.
Record the settings that produced the correct result.
Do not include the same pilot rows in the remaining batch without reviewing how your chosen import mode will treat them. A successful pilot should inform the next upload, not create unnecessary repeat processing.
7. Import the Remaining Records and Check Results
Prepare the remaining file using the settings confirmed in your pilot.
Review the destination, mode, mappings, tags, and optional actions again. Name the import clearly and confirm the required import declarations accurately.
Start the import, then open Bulk Actions to inspect progress. HighLevel documents Show Stats, error details, and downloadable error logs in its combined import guide.
For your GoHighLevel contact import, compare:
- The number of source rows submitted.
- The reported import results.
- The rows identified as errors.
- A sample of newly created records.
- A sample of updated records.
The increase in your total contact count does not need to equal the CSV row count when some rows update existing records.
Correct the affected rows based on their actual error details. Prepare a targeted retry file and choose the appropriate mode rather than immediately submitting the entire original file again.
Troubleshoot a GoHighLevel Contact Import
An import can complete while some rows or fields need attention. Read the error report and inspect the affected records before choosing a fix.
| Issue | What to check |
|---|---|
| Invalid email or phone | The original value, formatting, and required country information |
| Invalid Contact ID | Whether the ID belongs to the intended record in this sub-account |
| Missing dropdown value | Whether the CSV answer matches a supported field option |
| Owner not assigned | Whether the owner value identifies the intended HighLevel user |
| Unexpected contact update | The selected mode and matching identifier |
| Custom data missing | Whether the field existed and the column was mapped |
HighLevel’s bulk import troubleshooting guide explains validation and field errors.
Some errors affect only a field while the contact record is still imported. Confirm the actual outcome before creating a retry file.
Make one correction at a time. Keep a short note of the affected rows, the change, and the retry result.
Common GoHighLevel Contact Import Mistakes
Treating a Batch Tag as an Undo Button
A batch tag helps identify affected contacts. It does not restore earlier field values.
The tagged group may include existing customers that were updated. Deleting that group would also delete those customers’ records.
Use your original data and import results to plan a correction for the specific issue.
Starting Outreach Before Checking the Data
A stored email address or phone number does not by itself establish that a contact should receive a campaign.
Review the source of the list, existing opt-outs, and applicable communication preferences before enrolling it in follow-up.
Assuming Every CSV Row Became a New Contact
Some rows may update existing records or fail validation.
Check the import results and inspect records. A successful GoHighLevel contact import is measured by correct data, not simply by a larger contact count.
Frequently Asked Questions
Can I Upload an Excel File Directly?
Export the relevant sheet as CSV first. HighLevel’s contact import guide specifies CSV as the supported upload format.
Can a GoHighLevel Contact Import Update Existing Records?
Yes. Select the appropriate update mode and include the identifier needed to match the intended record. Test the matching behavior before processing the full file.
Why Is My Custom Field Missing?
Confirm that the contact custom field exists in the sub-account and that the CSV column is mapped to it. Also check that its values fit the field type.
Should I Add Imported Contacts to a Workflow Immediately?
Only when you have checked the data and intentionally want that workflow to run. Review automations triggered by tags as well as the import’s direct enrollment option.
Need Help Importing Your Contacts?
If you want help preparing a GoHighLevel contact import, contact HL Xperts to discuss your CSV, field mappings, and update requirements.
When your customer records are ready for follow-up, read GoHighLevel Review Requests: 7 Easy Setup Steps.
