Row & Page / Guides
GoHighLevel import error 1013: "Could not parse the phone number"
GoHighLevel Import Fix
We map your contacts to your exact pipelines, stages and custom fields and return an import-ready CSV plus a field map.
Your HighLevel (GoHighLevel) contact import reports 1013, Could not parse the phone number, or contacts came in without their phone numbers. Here is what HighLevel says, a free E.164 converter, and the steps we follow.
What the error means
HighLevel's troubleshooting article describes error 1013 as a phone value with non-numeric characters or a number not formatted as per E.164. HighLevel says the affected records were imported, but the phone field is empty.
HighLevel's CSV format guide recommends E.164, for example +11234567890, and lists 123-456-7890 and (123) 456-7890 as accepted for US numbers only. It lists 1234567 and abc1234567 as invalid. The troubleshooting article's FAQ adds that if the sub-account country is the US you don't need +1 for US numbers, but numbers from other countries need their country code.
Sources (retrieved October 14, 2026; check them for current wording before you re-import):
- HighLevel Help Center, Troubleshooting Bulk Imports Via CSV, https://help.gohighlevel.com/support/solutions/articles/48001223155-troubleshooting-bulk-imports-via-csv
- HighLevel Help Center, How to Format CSV Files for Contact and Opportunity Imports, https://help.gohighlevel.com/support/solutions/articles/155000005143-csv-file-format-for-importing-objects
- HighLevel Help Center, Importing Contacts and Opportunities via CSV, https://help.gohighlevel.com/support/solutions/articles/155000003905-importing-contacts-and-opportunities-via-csv
Check your CSV before you re-import
Pick your phone column and enter the country code to assume when a number has none. The checker strips spaces, dashes, dots and brackets, adds the country code, and flags numbers with letters, extensions or the wrong length. A trunk 0 is dropped for non-US codes (for example UK 07... becomes +447...). Your file stays in your browser; nothing is uploaded.
How we fix it
- Export the failed rows from the import's error log (HighLevel's import status page links to it).
- Run the phone column through the converter with your default country code.
- Download the converted file and fix flagged rows by hand (move extensions into a separate column, confirm the country of short numbers).
- Re-import only the corrected rows, mapping the column to Phone.
- If you also store second numbers, HighLevel's format guide says to put them in an Additional Phone Numbers column, separated by commas.
Row & Page is not affiliated with HubSpot or HighLevel. The checker is a format pre-check, not a guarantee that an import will succeed. Example values on this page are fictional.
GoHighLevel Import Fix
We map your contacts to your exact pipelines, stages and custom fields and return an import-ready CSV plus a field map.