Keep the source file unchanged
Exported contacts can contain more than names and phone numbers. Start from a copy, then keep the original until the receiving person or service has confirmed the result. A copy gives you a safe way to undo an unwanted removal or conversion choice.
1. Decide whether you are transferring contacts or sharing them
These are different jobs. A full transfer to your own contacts app usually needs as much usable data as possible. A shareable list for a colleague, supplier, event, or support request usually needs less. Do not remove data merely because a field exists; decide what the recipient actually needs.
Move contacts to another app
Choose a format and mapping that the destination understands. Preserve the original export until you have checked the imported records.
Prepare a Google Contacts importSend a smaller contact copy
Choose only the fields that the recipient needs. A smaller copy reduces accidental disclosure, but it does not replace your organisation’s approval process.
Review VCF privacy fields2. Check the fields that can travel with a contact
Look beyond the obvious name and email columns. Depending on the export, a contact can include notes, addresses, birthdays, organisations, titles, categories, web links, and an embedded photo. A value that helps a personal address book may be unnecessary for a shareable list.
- Write down the purpose and recipient before you change the file.
- Check notes and address fields for internal context, personal details, or copied correspondence.
- Check photos, categories, roles, links, and any custom fields that the recipient did not request.
- If a field is unclear, keep it in the original and ask the recipient whether it is needed.
3. Make one deliberate change at a time
Choose the tool that matches the specific job. This is safer than repeatedly converting a file until it looks different, because each extra transformation makes review harder.
Remove selected VCF fields
Select supported privacy field types to remove while leaving the rest of each vCard line structure unchanged.
VCF Privacy FilterRemove embedded contact photos
Create a smaller VCF copy without readable embedded photos. Remote photo links and other contact fields stay outside this specific removal job.
VCF Photo StripperReview possible duplicates
Inspect exact duplicate email or phone signals before deciding whether people should be merged. Do not treat a possible duplicate as permission to delete a contact.
Contact Duplicate FinderMove between a VCF and a spreadsheet
Use a CSV only when the next review or import needs rows and columns. Check mappings and warnings before treating an exported copy as final.
Convert VCF to CSVDo not ask a tool to guess who is a duplicate or which detail is safe
Two people can share a name, company address, or family email address. A contact list can also contain context that software cannot classify reliably. Use the review list to make the decision yourself, and inspect any field a tool did not explicitly support.
4. Open the final copy before sending or importing it
A successful download only means the file was created. It does not prove that the recipient needs every remaining value or that the destination will interpret every field as you expect.
Records
Check the first, last, and one representative contact. Confirm the intended records are present.
Fields
Search for a note, address, photo, or identifier you meant to remove. Check that it is gone only when that was your decision.
Destination
Import a small, non-sensitive test copy first when the next system permits it. Review the destination’s current field rules.
When the copy is ready
Share the reviewed download, not the original. Keep the original export until the handoff or import is complete. If the result needs another change, return to that source instead of reworking an already modified copy.
Questions this checklist answers
Should I convert a VCF file to CSV before sharing it?
Only if the recipient needs a spreadsheet-style review or import. Converting formats is not itself a privacy step. Review the fields and the final destination before sharing either format.
Can a duplicate finder safely merge my contacts?
A possible duplicate is a signal for review, not proof that two records describe the same person. Review the source contacts before you decide to merge or remove anything.
Does removing a field make the list safe to share?
No. It reduces the information visible in that copy. Other fields and the surrounding context can still be sensitive, and your organisation may have rules that apply to contact data.