Import contacts

Import the vendor list from the CSV I received from procurement: file Vendors_Jun2026.csv. Map Name to Full Name, Company to Organization, Email to Email Address, Phone to Business Phone, Mobile to Mobile Phone, Address to Business Address, and Notes to Notes. Skip duplicates when email matches, tag all imported as Vendor and add source field set to Procurement CSV. After import, report how many new contacts were created and how many duplicates skipped.

Before I run the vendor CSV import, make it easy for procurement reviewers: surface highest-risk rows (missing email or company), show a sample of how name fields will map, and flag rows that match existing contacts by email so we can choose merge rules. Recommend mapping defaults that minimize duplicate creation and a step to back up existing contacts first.

I have a 1,200-row Vendors_Jun2026.csv from procurement with inconsistent name formats and some missing emails. I’m not sure whether to skip duplicates or merge them; I fear creating thousands of fragmented entries. What’s the safest import strategy that protects current contacts and delivers usable vendor records by morning?

Over multiple imports we keep ending with fragmented vendor records and duplicates, costing procurement time to reconcile. Where are we failing in the process and what single recurring habit (or gate) will prevent this from happening again? Propose a simple import checklist and one policy for dealing with mismatched rows.