Free tool
CRM import file checker
Pick the CRM, then drop in the CSV you plan to import. The checker counts rows, columns and file size against that CRM's documented import limits, finds the phone numbers, emails, dates and duplicates that make imports fail, and gives you a cleaned file, plus split files if it is too big.
No file yet
Choose a file or try the sample to see what your CRM will reject.
Column by column
| Column | Looks like | Filled | Findings |
|---|
Import limits by CRM
The checker splits and warns using these numbers. Full sources, dates and the per-plan detail are on our CRM import limits research page.
| CRM | Rows per import | File size | Watch for |
|---|---|---|---|
| GoHighLevel | 10,000 (older article) | Under 30 MB (current article) | CSV only, one sheet, E.164 phones, a name, email or phone on every row |
| monday CRM, new board | Fewer than 8,000 | 10 MB | Fewer than 50 columns, YYYY-MM-DD dates, no column with more than 40 unique labels |
| monday.com, existing board | 10,000 | 10 MB | Up to 100 columns, 100 files per account per hour |
| HubSpot (paid) | 1,048,576 per file | 512 MB | Fewer than 1,000 columns, UTF-8, one sheet |
| Pipedrive | 50,000 | Under 50 MB | One tab, header row required |
| Zoho CRM | 1,000 (Free) to 30,000 (Enterprise) | Not stated for the in-app importer | Blank row ends the import; dropdown values must exist first |
| Salesforce | 50,000 (Data Import Wizard) | Not stated | Data Loader above 50,000 |
| Dynamics 365 Sales | 20,000 recommended | 8 MB (32 MB zipped) | Programmatic import for large volumes |
How should phone numbers look in a CRM import file?
In E.164 format: a plus sign, the country code and the number, with no spaces, dashes, dots or brackets. (415) 555-0123 becomes +14155550123, and the UK number 07700 900123 becomes +447700900123 (the leading 0 goes). The ITU-T E.164 standard caps a number at 15 digits including the country code.
This matters most in GoHighLevel. HighLevel's troubleshooting article lists error 1013, "Could not parse the phone number", for values with non-numeric characters or not in E.164, and says the record still imports but without the number. It also says error 1007 appears when a number outside the sub-account's country has no country code. Texting depends on that field, so a contact imported without a phone is a contact you can't reach. Our guide to GoHighLevel SMS error codes covers what happens after import.
Which date format should a CRM import use?
YYYY-MM-DD is the safe choice everywhere, and monday.com requires it: its import article says dates "must be formatted in ISO format", for example 2021-10-23. GoHighLevel and Zoho read the format you choose at import time, and HighLevel's error 1014, "Could not parse the date", means the file doesn't match that choice. The common trap is a file that mixes 03/04/2026 (US) and 2026-04-03 in one column, or that came from a day-first country. The checker reports the format of each date column and rewrites it to YYYY-MM-DD when no value is ambiguous.
Why do CRM imports fail? What the checker catches
| Problem in the file | What the CRM does | What the checker does |
|---|---|---|
| More rows or MB than the CRM allows | Rejects the upload or stops partway | Counts files needed and builds the split files |
| Phones with brackets, dashes or no country code | Drops the number (HighLevel 1013, 1007) | Rewrites to E.164 or lists rows it can't fix |
| Dates in another format, or mixed formats | Imports the record without the date (HighLevel 1014) | Names the format, converts to YYYY-MM-DD |
| Bad or doubled email addresses | Skips the email (HighLevel 1008) | Lists invalid and multi-address cells |
| The same email or phone on several rows | Merges or updates the wrong record | Lists duplicates; can drop later ones |
| Blank rows | Zoho treats one as the end of the file | Finds them and removes them |
| Rows with no name, email or phone | HighLevel can't create or match the contact | Counts and lists them |
| A column with more than 40 different values | monday's import fails | Flags the column for monday |
| File not saved as UTF-8 | Accented names turn into strange characters | Detects broken characters |
| Excel errors and formulas (#N/A, =SUM) | Imports the text as data | Flags the cells |
Two failures can't be seen in a CSV: owner names that match no user (HighLevel error 1002; use the owner's email instead) and dropdown values that don't exist in the CRM yet. Create users and dropdown options before importing. More fixes are in how to clean CRM data before a migration.
Duplicates: what each CRM matches on
GoHighLevel finds existing contacts by email first, then phone, by default, and HighLevel says it merges matching contacts instead of creating duplicates. Importing into an existing monday.com board lets you pick the column that counts as a match, such as Email or Phone, and update matching items. In both cases, two rows with the same email in one file both hit the same record, and the later row wins. Clean the file first, and keep the untouched original export: if a merge goes wrong, the Source Row column in the cleaned file points back to the original line.
Updating records rather than creating them? Remove every column you don't mean to change before the import, so a blank cell can't clear a field you wanted to keep. For the full move between systems, our CRM migration guide covers mapping and cutover order, and the platform guides cover importing into monday.com, exporting contacts from GoHighLevel and moving Airtable to monday.com. Building formulas on the imported board next? Use the monday.com formula builder.
Sources
- HighLevel Support, Importing contacts and opportunities via CSV (read 2026-10-17): CSV only, under 30 MB, one sheet, a name, email or phone per row, no special characters in phones, match by email then phone, automatic merge. The same article's FAQ also mentions splitting files under 50 MB.
- HighLevel Support, Troubleshooting bulk imports via CSV (read 2026-10-17): 20 MB or 10,000 rows, errors 1002, 1003, 1007, 1008, 1012, 1013, 1014, E.164.
- monday.com Support, Import from Excel to monday CRM and Import files from Excel (read 2026-10-17): fewer than 50 columns and 8,000 rows, 10 MB, 10,000 rows and 100 columns into an existing board, ISO dates, 40 unique labels, 100 files per hour.
- HubSpot, Pipedrive, Zoho CRM, Salesforce and Microsoft limits as recorded with links on CRM import limits compared (vendor pages read 2026-10-06).
- ITU-T, Recommendation E.164: the international numbering plan behind the +country code format.
CRM import questions
Is my file uploaded anywhere?
No. The checker reads the file with your browser's own file reader and does every check on your device. Nothing in the file is sent to aibrevo or anyone else, and the cleaned and split files are built in the browser too. Close the tab and the data is gone. We only count that the tool was used, not what was in the file.
How should phone numbers be formatted for a CRM import?
Use E.164: a plus sign, the country code, then the number, with no spaces, dashes or brackets, for example +14155550123. E.164 numbers have at most 15 digits. HighLevel rejects other formats with error 1013, Could not parse the phone number, and needs a country code for numbers outside the sub-account's country.
How many contacts can I import into GoHighLevel at once?
HighLevel's current import article says the CSV must be under 30 MB and have one sheet. Its older troubleshooting article gives 20 MB or 10,000 rows, whichever comes first. Splitting into files of 10,000 rows or fewer is the safe choice, and the checker does that split for you.
Which date format does monday.com need for imports?
ISO format: four-digit year, two-digit month, two-digit day, such as 2026-10-23. monday.com's import article says dates must be formatted this way. The checker finds date columns, tells you if they are US or day-first format, and converts them to YYYY-MM-DD in the cleaned file when the order is clear.
Why did my CRM import fail?
Most failures come from a file over the row or size limit, more than one sheet, phone numbers with brackets or dashes, dates in a different format from the one chosen at import, invalid or doubled email addresses, owner names that match no user, dropdown values that don't exist yet, and blank rows. The checker flags each of these that can be seen in the file.
How do I remove duplicate contacts before importing?
Decide which column identifies a person, usually email and then phone, and keep one row per value. The checker lists duplicate emails and phone numbers with row numbers and can drop later duplicates from the cleaned file. Keep the original export untouched, and tick Add a Source Row column, so any removed row can be traced back.
How do I split a large CSV for a CRM import?
Split it into files under the target CRM's row and size limit, with the same header row in every file, and import them one after another. Pick the CRM in the checker and, if your file is over the limit, it offers download links for each part, already sized for that CRM.
Moving more than one file's worth of data?
Contacts are the easy part. Deals, notes, owners, history and the links between them are where migrations lose data. We map, test and move it, and you keep the old system until the new one checks out.