Import subscriber contacts

Import 4,200 subscriber contacts collected at the May trade show from the CSV file John exported. Map fields so First Name, Last Name, Email, Company, and Source='May Trade Show' are set. Suppress duplicates and unsubscribes, and run a quick validation to flag invalid addresses. Report how many imports failed and which rows they were before I assign follow-up.

Before I import the trade show list, make it easy for the ops lead to approve — surface the percentage of addresses likely invalid, highlight records missing names or company, call out any '@example' or disposable domains, and show how duplicates will be handled. Suggest a conservative dedupe rule that keeps the highest-engaged record.

I opened John's trade show CSV and found two different column formats merged together so some rows have company in the email column. I need to import these 4,200 rows without trashing the main list, but I don't know whether to split the file, re-export from the scanner, or run a script to re-map. Recommend the most likely safe approach and the exact next steps to fix the file in the next hour.

Every event import creates messy CSVs, manual re-mapping and late-night fixes that eat two days per quarter. Where are we losing time and what three operational habits should we change—covering how we capture data at events, the export format, and pre-import validation—so imports stop being a scramble and the lists are usable on first pass?