PEVENDE team ·
Import CSV Contacts Without Duplicates or Surprises
A safe import starts with a preview and ends with a result per row. Matching a phone number does not authorize automatic merging or imply permission to send messages.
Prepare columns
Use explicit columns for name, company, phone, email and source. Preserve phones as text to keep + signs and leading zeros. If country is missing, ask before normalization; do not assume every number belongs to the same market.
Separate matching from merging
Show the original row, candidate record and fields that would change. Allow accepting, rejecting or correcting a match. Two people may share a business phone; a technical match does not prove identical identity.
Protect spreadsheet output
OWASP documents CSV formula risks when a cell is interpreted as a formula. Treat values as data and review export handling. Do not open unknown files or execute imported content to test an importer.
Review exercise
Hypothetical example: 50 rows include three invalid emails and two matches. The preview distinguishes these five rows; the operator corrects or rejects them before confirmation. The summary reports created, updated and rejected records. This is guidance, not a claim that PEVENDE import is available. Keeping an import-batch reference helps locate errors after confirmation. Before repeating a batch, review its results to avoid creating new contacts on every retry. Preserve the original row number so an operator can find and correct the source record.
Practical checklist
- Keep phones as text with an explicit country.
- Review candidates before merging.
- Keep per-row errors and consent separate.
Primary sources
Checked October 2, 2026. Policies and products can change; review the source before implementation.