Convert a Contact CSV to VCF Without Mangling Names or Phone Numbers

A contact spreadsheet rarely matches a phone's address book exactly. One file has a single Name column. Another separates first name, surname, title, and organisation. Phone numbers may have spaces, local prefixes, extensions, or leading plus signs.

Converting the file is therefore a mapping task, not merely a change of extension.

Make a copy and inspect the columns

Work on a copy of the contact CSV. Keep one row per person and use clear, unique headings.

first_name,last_name,mobile,work_email,organisation
Ada,Okafor,+2348012345678,ada@example.org,Northwind
Musa,Bello,+2348098765432,musa@example.org,Contoso

Check for:

• duplicate rows;
• several people sharing one row;
• multiple phone numbers packed into one cell;
• phone numbers already damaged by spreadsheet number formatting;
• missing names; and
• confidential notes that should not be copied to a personal device.

Phone numbers should be stored as text. A leading + and leading zeros are meaningful. If Excel has already converted a long number or removed its prefix, return to the original export before creating the VCF.

Map the fields in HappyCSV

Open CSV to VCF, select the CSV, and review the detected field mapping. Correct it manually when a heading is unfamiliar.

Map first and last names separately when the source provides them. If there is only a full-name column, use it as the formatted name rather than guessing how to divide every person's name.

Preview the first few contacts, including one with punctuation, a long name, an international number, and non-ASCII characters. Then choose vCard 3.0 or 4.0 and download the .vcf file.

HappyCSV processes the contact data in your browser. The download can contain several vCards in one file, one after another.

What a vCard contains

A minimal card resembles this:

BEGIN:VCARD
VERSION:4.0
FN:Ada Okafor
N:Okafor;Ada;;;
TEL;TYPE=cell;VALUE=uri:tel:+2348012345678
EMAIL;TYPE=work:ada@example.org
ORG:Northwind
END:VCARD

FN is the formatted display name. N is a structured name with components in a defined order. TEL, EMAIL, and ORG hold communication and organisation details.

The current vCard standard is RFC 6350. Real contact applications support overlapping versions and sometimes interpret optional fields differently, which is why a sample import matters.

Choose a version for the destination

vCard 4.0 is the current standard and represents telephone numbers as URIs. vCard 3.0 remains common in contact applications and can be a practical compatibility choice.

There is no single version guaranteed to preserve every field in every product. Choose based on the destination and test it. If an older application rejects the file, try vCard 3.0 before stripping useful fields by hand.

Test before importing the whole list

Create a small VCF with three to five representative contacts. Import it into the actual destination and check:

1. given name and surname appear in the right places;
2. sorting is sensible;
3. mobile and work numbers retain their prefixes;
4. email addresses have the right labels;
5. organisation and job title are not swapped;
6. accented characters display correctly; and
7. a second import does not create an unexpected duplicate problem.

Delete the test contacts before the full import if the destination cannot merge them cleanly.

Apple documents VCF import through iCloud Contacts, and a single file may contain several people. On iPhone, a VCF attachment can be opened to import contacts. Google Contacts also accepts VCF files.

Menus change over time, so use the destination provider's current import instructions rather than relying on an old screenshot.

Treat contact data as personal data

A contact list may contain private telephone numbers, addresses, notes, and workplace information. Confirm that you are authorised to move it to the destination account or device.

After the migration, delete unnecessary working copies and downloads. Do not email the full VCF merely for convenience when a controlled transfer method is available.

If the import looks wrong

• Names are reversed: review the mapping between full name, given name, and family name.
• Numbers lost their +: repair the CSV from the source; numeric spreadsheet cells often cause this.
• Some details disappear: the destination may not support the property or version used.
• Characters look corrupted: regenerate the VCF as UTF-8 and test again.
• Contacts are duplicated: restore or clean the destination list, deduplicate the CSV, and repeat with stable source data.

For the reverse workflow, VCF to CSV can extract common contact fields for review. Keep the original VCF because a flat CSV cannot represent every repeated, labelled, or structured vCard property without compromise.

A successful contact migration is one you have sampled, checked, and can reverse. The conversion button is only the middle of that process.