Contact and spreadsheet CSV workflows
Convert Excel Contacts for Android or iPhone Import
Choose an Android or iPhone contact-import route before exporting Excel, and distinguish CSV field mapping from vCard conversion and account synchronization.
There is no single CSV format that imports directly into every mobile phone. First choose the contact service or app that will receive the records, then export Excel into a format that route supports. For many workflows, the file is imported into an account on a computer and the resulting contacts synchronize to the phone.
Identify whether you want contacts or a spreadsheet
If the goal is simply to read a table on a phone, a spreadsheet app can be the destination. If the goal is to add names and telephone numbers to the address book, the contact importer needs field mapping. Opening a CSV attachment in a spreadsheet does not itself create phone contacts.
Also identify the intended account. A phone may display contacts from several accounts, a device-only store or a SIM. Record where the imported contacts should live so that a later synchronization check does not mistake a hidden account for a failed conversion.
Use a supported Android route
One route is to prepare a Google Contacts CSV, import it through Google Contacts on a computer and use the same Google account on Android. Google documents account contact synchronization; check the selected account when several are present.
A local phone-file route is different. Google’s Android import instructions describe VCF files. Do not assume that a CSV attachment will work with that importer simply because both files can hold contact information.
Choose an iPhone-compatible account or desktop route
For an Apple contact workflow, Contacts on Mac supports CSV import with field-label review. Contacts stored in iCloud can then be available across devices using the same Apple account with Contacts enabled. Confirm the import destination in the desktop app.
iCloud’s web import documentation describes vCard files. A CSV-to-vCard conversion must translate fields into the vCard structure; changing contacts.csv to contacts.vcf only changes its name and does not perform that translation.
Prepare the workbook for the chosen importer
Create an export sheet with one contact per row and a single header row. Use the chosen destination’s template or mapping rules. Keep telephone numbers as text so that a plus sign, leading zero or long sequence of digits is not lost before export.
A useful trial record includes a name with an accent, a telephone value with a country code and a note containing a comma. A second record should leave an optional field empty. Together, these cases test encoding, identifier preservation, quoting and column alignment more effectively than two identical simple rows.
Check the actual file contents
Export the intended worksheet and inspect the resulting file as text or with a CSV-aware preview. Confirm the header names and record count. If the importer requires commas, verify that regional export settings did not produce semicolons instead.
Some CSV values require quotation marks around them. Those marks are file syntax and should disappear when the field is parsed. Do not remove them indiscriminately to make the file look simpler; doing so can turn one organization name containing a comma into two fields.
Separate import failures from display or synchronization issues
After a small deliberate import, inspect the contact in the account where it was created. Then inspect the phone’s displayed contact sources and the relevant synchronization setting. If the account contains the correct record but the phone does not show it, changing the CSV is unlikely to fix the actual problem.
Conversely, if the account itself shows a number in the wrong field, review the export and mapping. Repeated full imports can create duplicates while leaving the original mistake unresolved. Identify the stage that failed before retrying.
Finish with field-level checks
Compare the name, phone digits, email address and any secondary fields against the source workbook. A matching total number of contacts does not prove that those details stayed associated with the correct person. Check two distinct records, including the one with non-ASCII text.
Keep the original workbook and the final import file separately. The exact contact app, account and import route determine compatibility; the word mobile alone does not. Local CSV checks can establish file structure, while actual account import and synchronization must be verified in the chosen applications.
Related guides
How To Convert Txt To CSV In Excel. Check delimiters, column types and the saved file using a small example. Keep original source records.
Import JSON with Power Query, choose a row meaning before expanding nested lists, preserve identifiers as text and verify the worksheet before CSV export.
Learn how to convert excel to csv with delimiter: practical steps plus final checks for delimiter choice, quoting, line breaks and character encoding.