Before uploading a contact list, mark each row as a new person, an update to a known person or a match that needs a decision. Keep the undecided rows in a separate file. A successful upload tells you that the software could read the file. You still need evidence that each update reached the right customer.
Choose what identifies a person
Imagine a purchasing manager and a receptionist who both reply from the same company mailbox. A match on that address tells you which inbox they use. It tells you very little about who approved a quotation. HubSpot documents email matching for contacts and supports record IDs for updates through an import. Check the matching rules for your particular CRM and import mode before choosing a column. For an update to a known customer, export the existing identifier and keep it beside the source row throughout the exercise.
Give ambiguous rows a destination
Start with a copy of the sheet. Keep the original spelling, email and phone in separate columns from any cleaned values. Mark a row for review if two existing people share its proposed identifier, or if the name suggests one person while the email belongs to another. Ask the person who owns the relationship which record should receive the change. If all you know is that someone at a company requested a quote, keep the enquiry attached to the company where your process permits. Inventing a contact name creates another problem for the next import.
Rehearse an update and a repeat
Use fictional contacts in a test workspace. Include one existing buyer with a changed job title, one new buyer and the two people sharing an inbox. Write down the expected number of creations and updates before running the trial. Check the old buyer's quotation history and assigned salesperson afterwards. Repeat the same accepted rows and check whether the contact count grows. Also try a blank phone cell against a populated record so the team knows exactly how the chosen import settings treat missing values.
Hand over a reconciliation sheet
Give the import owner the input row number, decision, destination ID and outcome for each row. The total of created, updated, held and failed rows should explain the whole input file. Before approving a larger upload, ask a salesperson to find an existing quotation from the customer's screen and confirm that their next follow-up still belongs to the correct person.
Sources and further reading
Prepared with AI assistance and checked against the sources listed above. Planning examples are illustrative; your project scope is agreed separately.
