What to check before uploading contacts to a CRM

Importing a contact list can create duplicate records, put details in the wrong fields, or bring old opt-outs back into your CRM. A quick check of the CSV before uploading can prevent a messy import that takes longer to undo.

Use the CSV Editor to inspect, find, sort, and edit your file in a browser. It can also remove duplicates. Check the CRM's import template and your organization's data rules too, because a CSV editor cannot know which fields your CRM requires or whether you are allowed to use every contact.

Check the contact file before importing

1. Make a copy of the original CSV, then open the copy in the CSV Editor. Keep the untouched original in case you need to compare or recover records.
2. Get the CRM's import template or field requirements. Compare its expected column names and required fields with the first row of your CSV. A column called email_address, for example, may need to map to the CRM's email field during import.
3. Check the basic layout. The first row should contain column headers, each following row should represent one contact, and each column should contain one kind of information. Look for blank rows, notes above the headers, or several phone numbers packed into one cell.
4. Sort or inspect important columns such as email, name, phone number, and company. Look for blank required values, extra spaces, misspellings, inconsistent formats, and values that appear in the wrong column. Use search to check specific values when you have a known example.
5. Review potential duplicates before removing any. Exact repeated rows are different from two records that share an email address but have different names or other details. Keep a copy and check what the duplicate-removal action will remove before applying it.

Do not start with the full import. If the CRM allows it, try a small group of representative contacts first, including a record with a phone number, an accented name, and any optional fields you plan to map.

What the results mean

Each row has one contact and the required fields are present

The file's structure is probably ready for field mapping, but that does not guarantee the CRM will accept every value. During import, match each CSV column to the right CRM field and check the preview before confirming. A field can have a different header and still contain the right information, but it needs to be mapped correctly.

The same email appears on more than one row

These may be duplicate contacts, or they may be separate records that share an address, such as a shared business inbox. Compare names, phone numbers, company details, and any existing CRM record before merging or deleting. Do not remove a contact just because one value matches.

Some cells are blank or contain mixed values

A blank optional field may be harmless, while a missing required email or name could cause an import error or an incomplete record. A cell containing several phone numbers, email addresses, or notes is harder to map reliably. Split details into separate columns if the CRM has matching fields, or leave out information you do not need.

Phone numbers or names look altered

Check numbers for missing country codes, lost leading zeros, or unexpected punctuation. A spreadsheet program may change a phone number when it treats it as a number rather than text. Also look at accented letters and punctuation in names. If characters appear garbled, do not assume they will correct themselves during import.

Fix problems before uploading

1. Work from a copy. Keep the original unchanged and make edits to a separate file. This gives you a way to compare the data if a correction removes or changes something unexpectedly.
2. Match the CRM's field names and layout. Rename or rearrange columns to match the template when needed, and make sure the first row contains headers rather than contact details. During import, map each field deliberately instead of relying on similar-looking names.
3. Standardize values carefully. Remove accidental spaces, use a consistent phone number format, and keep phone numbers as text if a leading zero matters. Do not rewrite names or addresses based on guesses. Check unusual values against a trusted source if you have one.
4. Resolve duplicates one at a time when they are not exact copies. Compare the records and decide which details are current. Use duplicate removal only for records you have verified should be removed, and retain an original copy before making the change.
5. Check opt-outs and data permissions. Make sure the file does not undo an unsubscribe or suppression status. Keep source and consent details if your organization needs them, and do not import personal information that the CRM workflow does not require. Follow your organization's policies and applicable rules for contact data.
6. Run a small test import. Review the CRM's preview, field mapping, and any warnings. Check the resulting records in the CRM before importing the rest. If values landed in the wrong fields or were changed, cancel or correct the import rather than repeating it with the full list.

Keep contact data private while checking it

The CSV Editor runs in your browser, and the file stays on your device while you inspect or edit it. Uploading the prepared file to a CRM is a separate action: the CRM receives the contact data you send. Use an approved device and account, limit the file to information needed for the import, and avoid sharing the CSV through an unsecured link or an unnecessary email attachment.